{
  "schema": "securitystat.combined-source-bound-flow-package/1",
  "historical_three_pilots": {
    "schema": "securitystat.source-bound-exception-flow-package/1",
    "status": "REVIEWED_SOURCE_DRAFT_FOR_ISOLATED_RENDERER_INDEPENDENT_REVIEW_REQUIRED",
    "baseline_data_sha256": "1c70473cbe297b520d2b8fa11a7d7c0e5a0335c8009e9d790b7c819d49a76a10",
    "baseline_frozen_manifest_sha256": "0890b6d63b51a6364f41e37368c4f6084f1de26015f399d658d980cfcb1cceae",
    "original_records": {
      "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search": {
        "id": "DDS-paper-record-not-found-after-thorough-search",
        "title": "DDS cannot find a paper claim record after a thorough search",
        "when": "DDS has thoroughly searched for the paper claim record and cannot find it.",
        "you": "Keep the acknowledgement and inquiry details you receive. A missing record at this office does not mean your claim does not exist.",
        "ssa": "The instruction tells DDS to inform the inquirer that the inquiry is being sent to the field office for a reply. If staff cannot identify the servicing field office, the additional routing steps below apply.",
        "next": "This example does not show that the field office received the inquiry or replied.",
        "condition_logic": "all",
        "conditions": [
          "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
          "DDS is handling an inquiry concerning a paper claim.",
          "DDS cannot find a record of that paper claim after a thorough search."
        ],
        "source": "DDS_paper_inquiry005C_selected",
        "section": "C; regional-procedure note",
        "source_context_refs": [
          "005-C-whole"
        ],
        "qualifications": [
          "An unsuccessful search at DDS does not establish that no claim exists, that an appointment is invalid, or that no other office holds a record.",
          "The represented-case journey conditions remain unchanged; this example does not establish an appointment, claimant identity or disclosure authority.",
          "This is the paper-record search scenario in DI31005.005C, not the separate known-another-office route in B and not an electronic-folder search rule.",
          "The source notes that regional implementation procedures may vary; no particular regional instruction is supplied here.",
          "No actual search, acknowledgement, record entry, receipt, office transfer, deadline or completed reply is established.",
          "Both existing R19 source-comparison holds remain unchanged; this route does not determine PDE/PDN identity, issue date or incoming representation-document disposition."
        ],
        "timing": "No measured duration, follow-up clock or customer deadline is supplied by this instruction.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual forwarding, proper servicing office, receipt and reply remain unverified."
          ]
        },
        "full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search",
        "source_case_conditions": [
          "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
          "DDS is handling an inquiry concerning a paper claim.",
          "DDS cannot find a record of that paper claim after a thorough search."
        ],
        "additional_sources": [],
        "source_provenance": [
          {
            "source_code": "DI31005.005",
            "locator": "C full; original page regional-procedure note retained",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
            "whole_maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
            "start": 2460,
            "end": 3008,
            "offset_unit": "Unicode codepoints in captured rendered-main UTF8 text",
            "exact_text": "C. \nResponding to an inquiry if there is no record of a paper claim\n\nIf, you cannot find a record of the paper claim after a thorough search, inform the inquirer you are sending the inquiry to the FO for reply. If you cannot determine the servicing FO:\n\n•\n\ncomplete an SSA-408, annotated with the remark: “Please respond to inquiry, no record of a claim in our office;”\n\n•\n\nattach the SSA-408 to the inquiry; and\n\n•\n\nsend the inquiry and a copy of the acknowledgement to the parallel FO (in the locality of the DDS) for forwarding to the proper FO.",
            "span_sha256": "d2762d1c092f3a78be281c44c988491aaaabfa7c9944404e0262bd5b7d6c77f8",
            "scope": "New independently read future source context; current R19 applied B route and source/history unchanged. No actual case search or office identity established."
          }
        ],
        "source_instruction_summary": "C: only after a thorough unsuccessful search for the paper claim record, inform the inquirer the inquiry is being sent to FO for reply. Only if servicing FO cannot be determined: SSA408 exact remark; attach SSA408 to inquiry; send inquiry AND acknowledgement copy to parallel FO in DDS locality for forwarding to proper FO. This is not B office-in-possession/reply-copy handling.",
        "source_qualified_branch": {
          "kind": "selected_paper_record_inquiry_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "owner": "DDS staff under the selected paper-inquiry conditions",
        "route": "Inquiry forwarding for field-office reply; completion and return to the usual path unverified",
        "review_status": "Selected public paper-inquiry context; actual search, case facts and internal execution unverified.",
        "systems": [],
        "entity_ids": [],
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
          "snapshot_path": "/service/sources/DI31005.005-r19-main.txt",
          "report": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json"
        }
      },
      "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown": {
        "id": "DDS-paper-record-servicing-FO-unknown",
        "parent_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search",
        "title": "Staff cannot identify the servicing field office",
        "when": "The paper-record search conditions apply and DDS cannot determine which field office services the claim.",
        "you": "Keep any acknowledgement. The office named for forwarding may be a routing office rather than the office that will answer.",
        "ssa": "Staff complete an SSA-408 with the source-specified remark, attach it to the inquiry, and send the inquiry plus a copy of the acknowledgement to the parallel field office in the DDS locality for forwarding to the proper field office.",
        "next": "Forwarding to the proper field office and a final reply are not established by this illustration.",
        "condition_logic": "all",
        "conditions": [
          "Every condition of the full parent paper-record search route applies.",
          "DDS cannot determine the servicing field office."
        ],
        "source": "DDS_paper_inquiry005C_selected",
        "section": "C, conditional unknown-servicing-FO bullets",
        "source_context_refs": [
          "005-C-whole"
        ],
        "source_exact_SSA408_remark": "Please respond to inquiry, no record of a claim in our office;",
        "qualifications": [
          "An unsuccessful search at DDS does not establish that no claim exists, that an appointment is invalid, or that no other office holds a record.",
          "The represented-case journey conditions remain unchanged; this example does not establish an appointment, claimant identity or disclosure authority.",
          "This is the paper-record search scenario in DI31005.005C, not the separate known-another-office route in B and not an electronic-folder search rule.",
          "The source notes that regional implementation procedures may vary; no particular regional instruction is supplied here.",
          "No actual search, acknowledgement, record entry, receipt, office transfer, deadline or completed reply is established.",
          "Both existing R19 source-comparison holds remain unchanged; this route does not determine PDE/PDN identity, issue date or incoming representation-document disposition."
        ],
        "existing_record_context_candidate_ids": [
          "FORM_SSA408"
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual forwarding, proper servicing office, receipt and reply remain unverified."
          ]
        },
        "full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
        "timing": "No measured duration, follow-up clock or customer deadline is supplied by this instruction.",
        "source_case_conditions": [
          "Every condition of the full parent paper-record search route applies.",
          "DDS cannot determine the servicing field office."
        ],
        "additional_sources": [],
        "source_provenance": [
          {
            "source_code": "DI31005.005",
            "locator": "C full; original page regional-procedure note retained",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
            "whole_maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
            "start": 2460,
            "end": 3008,
            "offset_unit": "Unicode codepoints in captured rendered-main UTF8 text",
            "exact_text": "C. \nResponding to an inquiry if there is no record of a paper claim\n\nIf, you cannot find a record of the paper claim after a thorough search, inform the inquirer you are sending the inquiry to the FO for reply. If you cannot determine the servicing FO:\n\n•\n\ncomplete an SSA-408, annotated with the remark: “Please respond to inquiry, no record of a claim in our office;”\n\n•\n\nattach the SSA-408 to the inquiry; and\n\n•\n\nsend the inquiry and a copy of the acknowledgement to the parallel FO (in the locality of the DDS) for forwarding to the proper FO.",
            "span_sha256": "d2762d1c092f3a78be281c44c988491aaaabfa7c9944404e0262bd5b7d6c77f8",
            "scope": "New independently read future source context; current R19 applied B route and source/history unchanged. No actual case search or office identity established."
          }
        ],
        "source_instruction_summary": "C: only after a thorough unsuccessful search for the paper claim record, inform the inquirer the inquiry is being sent to FO for reply. Only if servicing FO cannot be determined: SSA408 exact remark; attach SSA408 to inquiry; send inquiry AND acknowledgement copy to parallel FO in DDS locality for forwarding to proper FO. This is not B office-in-possession/reply-copy handling.",
        "source_qualified_branch": {
          "kind": "selected_paper_record_inquiry_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "owner": "DDS staff under the selected paper-inquiry conditions",
        "route": "Inquiry forwarding for field-office reply; completion and return to the usual path unverified",
        "review_status": "Selected public paper-inquiry context; actual search, case facts and internal execution unverified.",
        "systems": [
          "SSA-408 Route Slip"
        ],
        "entity_ids": [],
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
          "snapshot_path": "/service/sources/DI31005.005-r19-main.txt",
          "report": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json"
        }
      },
      "correct-birth-record/automated-enumeration-keying-proof": {
        "id": "automated-enumeration-keying-proof",
        "title": "A keying error arose during automated enumeration",
        "when": "SSA reviews a possible error from an agreed automated enumeration process.",
        "you": "Explain the discrepancy and provide requested supporting information.",
        "ssa": "Verify the keying error with participating-entity documentation showing that the error originated there. A verified keying correction uses NCP in SSNAP without a new iteration or replacement-limit count. If the necessary prior application or entity documentation cannot be reviewed, do not change the current iteration through NCP; use the supported new-iteration application route.",
        "route": "FO evidence comparison → NCP / new Numident iteration",
        "next": "SSA makes the internal keying-error finding.",
        "source": "numident",
        "section": "A.1-2",
        "timing": "No completion duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      }
    },
    "flows": {
      "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-paper-record-not-found-after-thorough-search",
        "full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search",
        "entry_conditions": [
          "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
          "DDS is handling an inquiry concerning a paper claim.",
          "DDS cannot find a record of that paper claim after a thorough search."
        ],
        "steps": [
          {
            "id": "paper-search-condition",
            "title": "The paper-record search condition",
            "kind": "situation",
            "actor": "context",
            "action": "This route concerns a paper claim that DDS cannot find after a thorough search. A missing record in this office does not establish that no claim exists.",
            "next": "If that search condition is not established, this example does not supply a forwarding instruction.",
            "source": "DDS_paper_inquiry005C_selected",
            "section": "DI31005.005 C; regional-procedure note",
            "source_context_refs": [
              "005-C-whole"
            ],
            "qualifications": [
              "This is a source-qualified paper-inquiry example, not evidence that a search, appointment, office action or receipt occurred.",
              "Regional implementation may vary. No measured duration, repair, case decision or automatic rejoin is established."
            ],
            "conditions": [
              "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
              "DDS is handling an inquiry concerning a paper claim.",
              "DDS cannot find a record of that paper claim after a thorough search."
            ]
          },
          {
            "id": "inform-inquirer-FO-reply",
            "title": "Tell the inquirer the field office will handle the reply",
            "kind": "action",
            "actor": "DDS",
            "action": "The instruction tells DDS to inform the inquirer that the inquiry is being sent to the field office for a reply.",
            "next": "If staff cannot determine the servicing field office, the additional unknown-office route applies. This does not establish forwarding, receipt or reply.",
            "source": "DDS_paper_inquiry005C_selected",
            "section": "DI31005.005 C; regional-procedure note",
            "source_context_refs": [
              "005-C-whole"
            ],
            "qualifications": [
              "This is a source-qualified paper-inquiry example, not evidence that a search, appointment, office action or receipt occurred.",
              "Regional implementation may vary. No measured duration, repair, case decision or automatic rejoin is established."
            ],
            "conditions": [
              "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
              "DDS is handling an inquiry concerning a paper claim.",
              "DDS cannot find a record of that paper claim after a thorough search."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual forwarding, proper servicing office, receipt and reply remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-paper-record-servicing-FO-unknown",
        "full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
        "entry_conditions": [
          "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
          "DDS is handling an inquiry concerning a paper claim.",
          "DDS cannot find a record of that paper claim after a thorough search.",
          "Every condition of the full parent paper-record search route applies.",
          "DDS cannot determine the servicing field office."
        ],
        "steps": [
          {
            "id": "complete-route-slip",
            "title": "Complete the route slip",
            "kind": "action",
            "actor": "DDS",
            "action": "Complete an SSA-408 with the source-specified remark: “Please respond to inquiry, no record of a claim in our office;”",
            "next": "This is the unknown-servicing-field-office condition, not a form requirement for every inquiry.",
            "source": "DDS_paper_inquiry005C_selected",
            "section": "DI31005.005 C; regional-procedure note",
            "source_context_refs": [
              "005-C-whole"
            ],
            "qualifications": [
              "This is a source-qualified paper-inquiry example, not evidence that a search, appointment, office action or receipt occurred.",
              "Regional implementation may vary. No measured duration, repair, case decision or automatic rejoin is established."
            ],
            "conditions": [
              "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
              "DDS is handling an inquiry concerning a paper claim.",
              "DDS cannot find a record of that paper claim after a thorough search.",
              "Every condition of the full parent paper-record search route applies.",
              "DDS cannot determine the servicing field office."
            ]
          },
          {
            "id": "attach-route-slip",
            "title": "Attach it to the inquiry",
            "kind": "action",
            "actor": "DDS",
            "action": "Attach the completed SSA-408 to the inquiry.",
            "next": "The inquiry and acknowledgement copy have their own routing instruction.",
            "source": "DDS_paper_inquiry005C_selected",
            "section": "DI31005.005 C; regional-procedure note",
            "source_context_refs": [
              "005-C-whole"
            ],
            "qualifications": [
              "This is a source-qualified paper-inquiry example, not evidence that a search, appointment, office action or receipt occurred.",
              "Regional implementation may vary. No measured duration, repair, case decision or automatic rejoin is established."
            ],
            "conditions": [
              "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
              "DDS is handling an inquiry concerning a paper claim.",
              "DDS cannot find a record of that paper claim after a thorough search.",
              "Every condition of the full parent paper-record search route applies.",
              "DDS cannot determine the servicing field office."
            ]
          },
          {
            "id": "send-inquiry-ack-copy",
            "title": "Send the inquiry and acknowledgement copy",
            "kind": "action",
            "actor": "DDS",
            "action": "Send the inquiry and a copy of the acknowledgement to the parallel field office in the locality of the DDS for forwarding to the proper field office.",
            "next": "The proper office is the prescribed destination. This example does not establish that forwarding, receipt or a final reply occurred.",
            "source": "DDS_paper_inquiry005C_selected",
            "section": "DI31005.005 C; regional-procedure note",
            "source_context_refs": [
              "005-C-whole"
            ],
            "qualifications": [
              "This is a source-qualified paper-inquiry example, not evidence that a search, appointment, office action or receipt occurred.",
              "Regional implementation may vary. No measured duration, repair, case decision or automatic rejoin is established."
            ],
            "conditions": [
              "The unchanged represented-case journey conditions apply; actual appointment and contact facts are not established by choosing this example.",
              "DDS is handling an inquiry concerning a paper claim.",
              "DDS cannot find a record of that paper claim after a thorough search.",
              "Every condition of the full parent paper-record search route applies.",
              "DDS cannot determine the servicing field office."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual forwarding, proper servicing office, receipt and reply remain unverified."
          ]
        }
      },
      "correct-birth-record/automated-enumeration-keying-proof": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "automated-enumeration-keying-proof",
        "full_route": "correct-birth-record/automated-enumeration-keying-proof",
        "entry_conditions": [
          "A possible keying error concerns an automated enumeration process with an established SSA data-exchange agreement.",
          "Participating-entity documentation must clearly demonstrate that the error originated with that entity before that source-specific keying correction is established.",
          "SSA establishes the actual evidence and correction route. Selecting the example or a dropdown does not establish a documented error."
        ],
        "alternative_groups": [
          {
            "id": "source-review-disposition",
            "label": "Alternative instructions after the source-document review",
            "logic": "source_conditions_determine_branch",
            "note": "These are alternatives, not consecutive NCP and fallback actions. Neither outcome is established by choosing this example. If the necessary facts are unknown or neither predicate applies, this flow does not choose an outcome."
          }
        ],
        "steps": [
          {
            "id": "review-automated-enumeration-source",
            "title": "Review the participating entity’s documentation",
            "kind": "action",
            "actor": "SSA staff",
            "action": "For the automated-enumeration circumstance, verify the reported keying error with participating-entity documentation that clearly shows the error originated there. General keying-error review may compare the paper SS-5 or microprint with Numident; that does not remove the automated-entity documentation requirement.",
            "conditions": [
              "A possible keying error concerns an automated enumeration process with an established SSA data-exchange agreement.",
              "Participating-entity documentation must clearly demonstrate that the error originated with that entity before that source-specific keying correction is established.",
              "SSA establishes the actual evidence and correction route. Selecting the example or a dropdown does not establish a documented error."
            ],
            "source": "numident",
            "section": "A.1",
            "source_context_refs": [
              "RM10212.200-A"
            ],
            "qualifications": [
              "Source RM10212.200 A.1 automated-enumeration evidence authority is distinct from a claimant allegation.",
              "No identity, error, completed correction, benefit change or successful rejoin is established.",
              "DOB-specific evidence rules in linked RM10210.295 and other linked processing targets are not newly reviewed by this flow."
            ],
            "next": "The established review result determines which alternative instruction may apply."
          },
          {
            "id": "verified-keying-NCP",
            "title": "If the keying error is documented",
            "kind": "action",
            "actor": "SSA staff",
            "action": "After the required review establishes a keying error, correct the incorrect Numident information using NCP in SSNAP. The source says this correction adds no Numident iteration and does not count against the annual or lifetime card limits.",
            "conditions": [
              "The applicable source documentation has been reviewed.",
              "SSA determines that a keying error occurred; in the automated-enumeration case, participating-entity documentation clearly demonstrates its origin."
            ],
            "source": "numident",
            "section": "A.1",
            "source_context_refs": [
              "RM10212.200-A"
            ],
            "qualifications": [
              "Source RM10212.200 A.1 automated-enumeration evidence authority is distinct from a claimant allegation.",
              "No identity, error, completed correction, benefit change or successful rejoin is established.",
              "DOB-specific evidence rules in linked RM10210.295 and other linked processing targets are not newly reviewed by this flow."
            ],
            "next": "This is the documented-keying-error alternative. The separate unavailable-document instruction is not a required next action.",
            "alternative_group": "source-review-disposition"
          },
          {
            "id": "unavailable-documents-new-iteration",
            "title": "If the needed documentation cannot be reviewed",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When the necessary SS-5, microprint or participating-entity documentation cannot be reviewed for any reason, do not use NCP or change the current Numident iteration. Follow the new-iteration application route: a completed SSN application, identity evidence and supporting update evidence when required. The linked DOB-specific evidence rules remain a separate dependency.",
            "conditions": [
              "SSA cannot review the necessary SS-5, microprint or participating-entity documentation.",
              "The new-iteration route requires its own application and evidence conditions; this example does not establish that they have been satisfied."
            ],
            "source": "numident",
            "section": "A.1–A.2; B.1–B.2 DOB reference",
            "source_context_refs": [
              "RM10212.200-A",
              "RM10212.200-B"
            ],
            "qualifications": [
              "Source RM10212.200 A.1 automated-enumeration evidence authority is distinct from a claimant allegation.",
              "No identity, error, completed correction, benefit change or successful rejoin is established.",
              "DOB-specific evidence rules in linked RM10210.295 and other linked processing targets are not newly reviewed by this flow."
            ],
            "next": "A new iteration preserves the prior record. This does not establish that an application, evidence review or update has been completed.",
            "alternative_group": "source-review-disposition"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual document availability, error finding, identity, required update evidence and processing outcome are unverified.",
            "Available documentation that does not clearly demonstrate the automated-entity error does not automatically establish either displayed alternative. The broader A/A.2 update instruction requires its own review."
          ]
        }
      }
    },
    "source_contexts": {
      "005-C-whole": {
        "source_code": "DI31005.005",
        "locator": "C full; original page regional-procedure note retained",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
        "whole_maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
        "start": 2460,
        "end": 3008,
        "offset_unit": "Unicode codepoints in captured rendered-main UTF8 text",
        "exact_text": "C. \nResponding to an inquiry if there is no record of a paper claim\n\nIf, you cannot find a record of the paper claim after a thorough search, inform the inquirer you are sending the inquiry to the FO for reply. If you cannot determine the servicing FO:\n\n•\n\ncomplete an SSA-408, annotated with the remark: “Please respond to inquiry, no record of a claim in our office;”\n\n•\n\nattach the SSA-408 to the inquiry; and\n\n•\n\nsend the inquiry and a copy of the acknowledgement to the parallel FO (in the locality of the DDS) for forwarding to the proper FO.",
        "span_sha256": "d2762d1c092f3a78be281c44c988491aaaabfa7c9944404e0262bd5b7d6c77f8",
        "scope": "New independently read future source context; current R19 applied B route and source/history unchanged. No actual case search or office identity established."
      },
      "RM10212.200-A": {
        "source_code": "RM10212.200",
        "locator": "A full including all substeps",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110212200",
        "start": 141,
        "end": 3078,
        "exact_text": "A. \nWhy we change NUMIDENT data\n\nThe NUMIDENT contains specific information for each number holder (NH). We only correct or change information on an existing NUMIDENT iteration when there is a documented keying error by reviewing the prior Social Security number (SSN) application (SS-5).\n\nHowever, when an applicant wishes to update information previously submitted, or to correct information when we cannot document a keying error, we update the NUMIDENT by creating a new iteration appended to the previous iteration. The applicant must submit a new application and provide supporting documentation (e.g., a birth certificate to correct the NH's date of birth information).\n\n1. \nWhen there is a keying error\n\nA keying error occurs when the data on the paper application for a Social Security card (SS-5) does not match the data on the NUMIDENT. To identify whether a keying error has occurred, compare the information on the paper SS-5 or SS-5 microprint with the NUMIDENT. Paper SS-5 and SS-5 microprints are available in the Image Retrieval Online (IRON) system and through SS-5 Reprints. Links are available to these programs in SSNAP.\n\nNOTE: \n\nThe agency will also consider keying errors that occur as part of the automated enumeration processes where we have an established data exchange agreement, such as Enumeration at Birth. In these cases, keying errors must be verified with documentation from the participating entity (e.g., hospital documentation) that clearly demonstrates the error originated with that entity.\n\nIf, after reviewing the paper SS-5, SS-5 microprint, or documentation from a participating entity, you determine that a keying error occurred, correct the incorrect NUMIDENT record information using Numident Correction Processing (NCP) in the Social Security Number Application Processing (SSNAP). This action does not add to the number of NUMIDENT iterations and will not count against the annual or lifetime SSN card limits.\n\nHowever, when, for any reason, you are unable to review the SS-5, SS-5 microprint, or documentation from a participating entity, we do not use the NCP process. Do not correct or change the current NUMIDENT iteration. Instead, update the information on the NUMIDENT by creating a new iteration as provided in RM 10212.200A.2.\n\nKeying Errors: For instructions see details\n\n•\n\nRM 10215.051 Correcting Keying Errors in Fields Other than \"Name on Card\" Field\n\n•\n\nRM 10210.295 Date of Birth Change on the NUMIDENT\n\n•\n\nRM 10215.055 Correct a Coding Error that Resulted in an Incorrect Employment Legend on the SSN Card\n\n•\n\nRM 10220.415 Numident Correction Processing (NCP)\n\n•\n\nRM 00702.006 How to Correct Keying Errors\n\n2. \nUpdating NUMIDENT data by creating a new iteration\n\nThe applicant must submit a completed SSN application accompanied by evidence of identity and evidence to support the update. Create a new NUMIDENT iteration with the new information, following RM 10212.200B.\n\n",
        "span_sha256": "5c3b1e5d6014dce3f80d1b526b36590faae2861b9c599913abdf97065e1f4b66",
        "maintext_sha256": "fdae9bad104a1019d56b3c743ed03737234dc309e681680c257a36bad9d3a59a"
      },
      "RM10212.200-B": {
        "source_code": "RM10212.200",
        "locator": "B full including all substeps",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110212200",
        "start": 3078,
        "end": 8544,
        "exact_text": "B. \nHow do you create a new NUMIDENT iteration to update data on the NUMIDENT\n1. \nRequest evidence\n\nApplicants requesting an update of information on the NUMIDENT record must submit:\n\n•\n\nAn application for a replacement SSN card; and\n\n•\n\nEvidence of identity to establish that the NH for whom the SS-5 is submitted is the same person to whom SSA assigned the SSN as provided in RM 10210.420; and\n\n•\n\nEvidence to support the update, if required in RM 10212.200B.2.\n\n2. \nObtain documentation\n\nUse this table to determine when supporting evidence is required for the update and additional actions needed.\n\nFor this update\n\n\t\n\nObtain this supporting documentation, when required, and follow any additional instructions\n\n\n\n\nSex field\n\n\t\n\nThe agency is only correcting or changing the sex field on the NUMIDENT to reflect the NH’s sex at birth.\n\nEvidence of sex:\n\n•\n\nU.S. Born:\n\n–\n\na birth certificate (BC) established by a State or local bureau of vital statistics (BVS) that reflects the NH's sex at birth.\n\n–\n\nThe NUMIDENT sex field established through enumeration at birth (EAB).\n\n•\n\nForeign born:\n\n–\n\nA foreign BC or Consular Report of Birth Abroad that lists the NH's sex at birth.\n\nNOTE: Do not accept an amended, corrected (GN 00302.510), or delayed BC (GN 00302.540) as proof to correct the sex field unless accompanied by an amendment affidavit or supporting documentation that clearly indicates the reason for the amendment.\n\n\n\n\nDate of birth (DOB) field\n\n\t\n\nSee Date of Birth Change on the NUMIDENT in RM 10210.295.\n\n\n\n\nPlace of birth (PLB) field\n\n\t\n\nEvidence of place of birth:\n\n•\n\nU.S. born:\n\n–\n\na BC established before age five and issued by a state or local bureau of vital statistics (BVS) for an individual born within its jurisdiction; or another acceptable proof of age document listed in RM 10210.265, provided the document also lists the NH's PLB.\n\n•\n\nForeign born:\n\n–\n\nan acceptable document such as a foreign BC or another acceptable proof of age document listed in RM 10210.265, provided the document also list the individual’s PLB.\n\nSee RM 10212.200B.3.b. for additional processing information.\n\n\n\n\nCitizenship field\n\n\t\n\nEvidence of U.S. citizenship:\n\n•\n\nU.S. public birth record showing birth in one of the 50 U.S. states, the District of Columbia, American Samoa, Puerto Rico, Guam, the Virgin Islands of the U.S. (on or after 01/17/1917), or the Northern Mariana Islands (on or after 11/04/1986, NMI Local time),\n\n•\n\nU.S. passport,\n\n–\n\nU.S. passports may be current or expired but must meet the criteria in RM 10210.505 to be acceptable evidence of U.S. citizenship.\n\n•\n\nCertificate of Naturalization,\n\n•\n\nCertificate of Citizenship, or\n\n•\n\nOther documents listed in RM 10210.505, RM 10210.510, RM 10210.520, and RM 10210.525.\n\nInterviewers should request and obtain the U.S. citizenship document with the highest probative value available to the applicant (\"available\" means the applicant either possesses the document or can obtain it within 10 working days) before accepting a document of a lower probative level.\n\nYou may use primary, secondary, third-level, or fourth-level evidence to change the citizenship data on a NUMIDENT record.\n\nEXAMPLE: If primary evidence of U.S. citizenship is not available then the interviewer may accept secondary evidence to update the citizenship data on the NUMIDENT record.\n\n\n\n\nParent's name field\n\n\t\n\nEvidence of parent's name:\n\n•\n\nU.S. born:\n\n–\n\nOriginal or amended BC, or\n\n–\n\nFinal adoption decree issue by the court or court determination of paternity\n\n•\n\nForeign Born:\n\n–\n\nan acceptable document such as a BC or another acceptable proof of age document listed in RM 10210.265 , provided the document also list the NH’s parent’s name.\n\nFor additional processing information, see RM 10212.200B.3.b.\n\n3. \nProcess the request\n\nIn the \"Remarks\" field on the Social Security Number Application Process (SSNAP) Summary screen, list any evidence documents the applicant submitted to support the change to the NUMIDENT, if not previously captured in SSNAP.\n\na. \n\nIf you update the sex code on the NUMIDENT, update the MBR, SSR, RPS or any other SSA record with the new sex designation.\n\nb. \n\nIf you update the parent's name field on a child’s NUMIDENT record, ask if the parent is a title II beneficiary, an SSI recipient, or a representative payee. If so, review the MBR, SSR, or RPS record and initiate or complete actions necessary to update the record (for example, correcting a parent’s name on the SSR record or ensuring that actions are taken to complete a new representative payee application).\n\n4. \nWhen to suppress an SSN card\n\nProcess the requested change but suppress the issuance of a replacement SSN card when the correction will not affect any data on the face of the SSN card (as with a change of the sex, DOB, PLB, or parent’s name fields on the NUMIDENT) unless the applicant is requesting a replacement card. (See RM 10205.400 for information on replacement card limits.)\n\n5. \nWhen to send written notice\n\nSend a written notice if you are unable to update the record or to provide the individual with a replacement card. Follow these instructions:\n\n•\n\nRM 00299.020 Form SSA-L676 – Refusal to Process SSN Application, or\n\n•\n\nRM 10205.090 Form SS-5 Received, and Additional Documentation is Needed, or\n\n•\n\nRM 10215.110 Policy on Providing Written Notice and Second Review When SSN or Card May Not Be Issued, or\n\n•\n\nRM 10215.115 Procedures for Providing Written Notice to an SSN Applicant.\n\n",
        "span_sha256": "21b55a35eee09f58807fb77374fca4db4e431ad72493f86414b8818b19b2cfe8",
        "maintext_sha256": "fdae9bad104a1019d56b3c743ed03737234dc309e681680c257a36bad9d3a59a"
      }
    },
    "source_page": {
      "source_code": "DI31005.005",
      "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
      "captured_utc": "2026-10-31T13:48:09.682Z",
      "checked_on": "2026-10-31",
      "capture_type": "IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP",
      "main_characters": 3995,
      "maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
      "browser_snapshot_sha256": "b8bff24f878a250b5c620c6b72ac2c8350bade8d967415ac31c328c7917523ba",
      "capture_metadata_sha256": "139825e74deed61e7f75fadcd3e6b01ca3527397aad1ce4e406a011788da1e45",
      "header_footer_labels": [
        "Effective Dates: 04/15/2013 - Present",
        "Basic (04-13)",
        "Batch run: 09/01/2026",
        "Rev:04/15/2013"
      ],
      "maintext_url": "/service/sources/DI31005.005-r19-main.txt",
      "snapshot_url": "/service/sources/DI31005.005-r19-DOM-snapshot.txt",
      "review_scope": "C whole and regional-procedure note only; existing B and comparison histories retained.",
      "applied_workflow_claims": true,
      "source_comparison_hold": false,
      "whole_page_or_native_acceptance": false,
      "selected_source_id": "DDS_paper_inquiry005C_selected"
    },
    "conditions_qualifiers_and_source_claims_not_removed": true,
    "no_uniform_four_card_requirement": true,
    "customer_action_cards_not_invented": true,
    "native_source_acceptance": false,
    "activation": false,
    "revision_provenance": {
      "parent_package_sha256": "195cf9f15519004ee640f510c180683ba7a0021ff9cb50bff6eb42afc562e1d5",
      "change": "Independent whole-source role precision: RM10212.200 binds generic agency/staff instructions, not a narrower FO assignment. Only three new-flow actor labels change.",
      "source_actions_conditions_alternatives_original_records_and_DDS_flows_unchanged": true
    },
    "source_pages": {
      "DI31005.005": {
        "source_code": "DI31005.005",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
        "captured_utc": "2026-10-31T13:48:09.682Z",
        "checked_on": "2026-10-31",
        "capture_type": "IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP",
        "main_characters": 3995,
        "maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b",
        "browser_snapshot_sha256": "b8bff24f878a250b5c620c6b72ac2c8350bade8d967415ac31c328c7917523ba",
        "capture_metadata_sha256": "139825e74deed61e7f75fadcd3e6b01ca3527397aad1ce4e406a011788da1e45",
        "header_footer_labels": [
          "Effective Dates: 04/15/2013 - Present",
          "Basic (04-13)",
          "Batch run: 09/01/2026",
          "Rev:04/15/2013"
        ],
        "maintext_url": "/service/sources/DI31005.005-r19-main.txt",
        "snapshot_url": "/service/sources/DI31005.005-r19-DOM-snapshot.txt",
        "review_scope": "C whole and regional-procedure note only; existing B and comparison histories retained.",
        "applied_workflow_claims": true,
        "source_comparison_hold": false,
        "whole_page_or_native_acceptance": false,
        "selected_source_id": "DDS_paper_inquiry005C_selected"
      },
      "RM10212.200": {
        "source_code": "RM10212.200",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110212200",
        "captured_utc": "2026-10-31T16:40:40.589Z",
        "capture_type": "Actual IAB rendered #content and DOM snapshot",
        "maintext_sha256": "fdae9bad104a1019d56b3c743ed03737234dc309e681680c257a36bad9d3a59a",
        "DOM_snapshot_sha256": "56866acd9b713f351889ef2731ef171bade4c16f48aa1cda8687f17a1a21be2a",
        "capture_metadata_sha256": "b1811f4289571d46291eb12b95025f343f48027a7cb436d877782e1c4f36a7eb",
        "whole_main_characters": 9518,
        "publisher_labels": [
          "Effective Dates: 06/05/2026 - Present",
          "TN 36 (06-26)",
          "Batch run: 07/31/2026",
          "Rev:06/05/2026"
        ],
        "native_source_acceptance": false
      }
    },
    "appending_flow_requires_exact_approved_record_projection": "Compare each exact complete approved exception_flow; strip only that field from only the three explicitly approved full-path records, requiring the complete original record, global journey fields, source objects and all ancestors exact. No other record or guard is weakened."
  },
  "new38": {
    "schema": "securitystat.source-bound-exception-flow-package/1",
    "status": "INDEPENDENT_SOURCE_REVIEW_BOUND_UI_INTEGRATION_AND_ROOT_GATES_REQUIRED",
    "baseline_frozen_R21_data_sha256": "1c70473cbe297b520d2b8fa11a7d7c0e5a0335c8009e9d790b7c819d49a76a10",
    "new_record_candidate_data_sha256": "53760a3392c42a4fc6940d0decd27f685d60c0137c115e7a15cb72350cebb1b1",
    "new_record_source_draft_sha256": "aa2eea6e712ba8952f381ece485e4007a03ff41da809c95b85c09542217cbae6",
    "independent_review": {
      "sha256": "f07cb6e5de0add882f251975ead09a38413a9c2e6c2c12a70a82869c265fa234",
      "artifact_name": "independent-R4-source-review.json"
    },
    "original_records_semantics": "These are exact NEW R4 candidate records without only exception_flow; they are not asserted to exist in frozen R21 or the live release.",
    "original_records": {
      "provide-claim-evidence/wsu-third-party-not-yet-valid": {
        "id": "wsu-third-party-not-yet-valid",
        "title": "The WSU has not yet obtained a valid third-party application",
        "when": "Staff establish that the third-party WSU claim does not yet have a valid application.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Use the signed-application-and-proofs or only-proofs instruction according to what the claimant actually provides.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "C; C.1",
        "additional_sources": [],
        "owner": "FO",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope."
        ],
        "source_context_refs": [
          "GN01070.781-C"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "C whole, all substeps retained",
            "start": 4807,
            "end": 7452,
            "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
            "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
        },
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid"
      },
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs": {
        "id": "wsu-signed-application-and-proofs",
        "title": "The FO receives the signed application and proofs",
        "when": "Both the signed application and proofs reach the FO in the source C circumstance.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Call or email the WSU and ask it to transfer claim jurisdiction in MCS. Use number 7 Claims Movement on the MCS menu to receipt the claim. Annotate the ATTEST issue on MCS DW01 to show receipt of the witnessed signed application; this does not replace signature validity requirements. Receipt all proofs on MCS DW01 under the applicable evidence rules. Return the signed application with the witnessed-signature cover notice referenced in GN00201.015. Take the action appropriate to the actual claim, such as adjudication or transfer to DDS. The example does not establish entitlement or a completed transfer.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "C.1.a",
        "additional_sources": [],
        "owner": "FO",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Both the signed application and proofs are provided to the FO."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Both the signed application and proofs are provided to the FO."
        ],
        "source_context_refs": [
          "GN01070.781-C"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "C whole, all substeps retained",
            "start": 4807,
            "end": 7452,
            "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
            "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "parent_full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid",
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs"
      },
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation": {
        "id": "wsu-only-proofs-before-attestation",
        "title": "The FO receives only the proofs before the WSU completes the application",
        "when": "The claimant provides proofs while the WSU has not yet attested and receipted the application.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "The source directs an offer to reprint the application and complete claim handling; this is not a promise that a benefit decision can be completed without its other requirements. Contact the WSU immediately to request jurisdiction transfer, and receipt the claim using number 7 Claims Movement in MCS. Obtain a wet signature under the witnessed-signature instruction or complete verbal attestation with the proper applicant under GN00201.015; actual signature validity is not established here. Annotate the ATTEST issue on MCS DW01 as the source instructs. Receipt the claim and all proofs on MCS DW01 under the applicable evidence rules. Return the signed application with the source-referenced witnessed-signature cover notice. Take the action appropriate to the established claim, such as adjudication or transfer to DDS, after all applicable requirements.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "C.1.b",
        "additional_sources": [],
        "owner": "FO",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
        ],
        "source_context_refs": [
          "GN01070.781-C"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "C whole, all substeps retained",
            "start": 4807,
            "end": 7452,
            "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
            "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "The source uses immediately for contact/handling; no guaranteed benefit-decision completion is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "parent_full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid",
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation"
      },
      "provide-claim-evidence/wsu-EVID-unavailable-evidence-route": {
        "id": "wsu-EVID-unavailable-evidence-route",
        "title": "The evidence cannot be recorded in EVID",
        "when": "An authorized FO employee handles WSU claimant evidence that cannot be recorded in EVID.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Certify a photocopy of the evidence under the applicable document rules. Fax or send the certified photocopies into Evidence Portal OR eView; both are not required. Establish REMARK and the associated remark with a next-day tickle in MCS DW01 or the CCE Development Worksheet. Annotate MCS DW03 or the CCE Development Worksheet with the FO code, employee name and direct phone number. Call or email the WSU immediately about the recorded or faxed proofs. Verify that the evidence is properly stored in the Certified Electronic Folder (CEF). For the EP OR eView copy, verify that it is stored and viewed for legible content. The linked retention/return rules remain separate; this is not authority to destroy every original document.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "B.2.a–b",
        "additional_sources": [],
        "owner": "FO",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
          "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
          "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
        ],
        "source_context_refs": [
          "GN01070.781-B"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "B whole, all substeps retained",
            "start": 875,
            "end": 4807,
            "exact_text": "B. \nClaims attested or receipted in by the WSU\n\nThese instructions pertain to both First Party and Third Party internet claims (iClaims).\n\nFirst party iClaims are signed by the Number Holder (NH) using the “click and sign” process and the word “Internet” propagates to the appropriate application, (e.g., DIB, RIB, Aux Spouse) on the Development Worksheet in MCS or CCE to indicate that an internet claim was filed using “click and sign”, see GN 00201.015.\n\nThird party iClaims cannot be signed using click and sign. However, follow instructions in this section if the WSU has already obtained a valid application by completing one of the following actions as documented on the DW01:\n\n•\n\nContacted the proper applicant and verbally attested the application, or\n\n•\n\nReceived a wet-signed SSA-1 or SSA-16 (or MCS and CCE output equivalent)\n\nNOTE:The Number Holder (NH) might contact the FO before the FO or WSU completes the ATTEST issue. Treat all first party iClaims the same for the purposes of the instructions in this section regardless of whether the FO or WSU has entered a receipt date in the ATTEST line of the MCS DW01 or CCE Development Worksheet.\n\n1. \nClaimants requiring action by the FO or WSU\n\nTechnicians will assist claimants with scheduling, rescheduling, or cancelling appointments in the Enterprise Scheduling System (ESS) and the Enhance Leads and Appointments System (eLAS) to support the Appointmetn Focused Service Delivery Model (AFS) for FOs.\n\na. \n\nFor Enumeration purposes: Technicians will utilized ESS to schedule appointments and will refer individuals to use the Online Social Security Number Application (oSNAP) when applicable.\n\nb. \n\nFor Initial Claims and Post-entitlement (PE) appointments: Technicians will utilize eLAS to schedule initial claim appointments, and ESS for PE appointments.\n\nc. \n\nTechnicians should annotate in the remarks that there is a pending iClaim.\n\n2. \nAssist claimants who provide evidence to the FO\na. \n\nRecord evidence received in the FO\n\nWhen a WSU claimant submits their proofs to the FO, an FO employee authorized to examine and certify documents takes the actions in this section. For more information about who we authorize to certify documents, see GN 00301.090.\n\n•\n\nExamine and evaluate the evidence document(s) for authenticity you may refer to our sensitive POMS; Evaluating the Validity of Documents and Records.\n\n•\n\nAccess Shared Process and enter the evidence document(s) on the Evidence (EVID) screen, unless you should not record the document(s) or form(s) on the EVID screen per GN 00301.286E.3.\n\n•\n\nIf the evidence cannot be recorded in EVID, certify a photocopy of the evidence document(s) and fax/send the certified photocopies into the Evidence Portal(EP) or eView.\n\n•\n\nEstablish the issue “REMARK” and an associated remark with a next day tickle on the MCS DW01 screen or on the CCE Development Worksheet to alert the WSU that you certified the document(s) via the Shared Process or faxed them into EP or eView.\n\n•\n\nAnnotate the MCS DW03 screen or CCE Development Worksheet with the FO code, the name, and the direct phone number of the FO employee who established the EVID or faxed the evidence into EP or eView.\n\n•\n\nCall or email the WSU immediately to notify them that you recorded proofs on the EVID screen or faxed proofs into EP or eView. This prevents processing delays and unnecessary re-contacts with the claimant.\n\n•\n\nComplete the Social Security Number Application Process (SSNAP) actions when enumeration updates are necessary.\n\nb. \n\nFO does not retain evidence faxed into EP, or eView\n\nFO technicians should verify that the evidence is properly stored in the Certified Electronic Folder (CEF).\n\nOnce the document has been recorded in EVID or stored and viewed for legible content in either EP or eView, the document does not need to be retained, per GN 00301.322. For information on the Retention or Return of Documents, see GN 00301.275.\n\n",
            "span_sha256": "ba7530d405d93262f91d35404eb11b7e9b0d4e141dc4fd068419cbed6494d886",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "Immediate WSU notification and a source-worded next-day internal tickle; no calendar/business conversion or customer completion promise.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "provide-claim-evidence/wsu-EVID-unavailable-evidence-route"
      },
      "provide-claim-evidence/wsu-first-party-ATTEST-date-not-entered": {
        "id": "wsu-first-party-ATTEST-date-not-entered",
        "title": "A first-party iClaim has no ATTEST receipt date yet",
        "when": "The source B first-party signed-iClaim circumstance applies even before the ATTEST receipt date is entered.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Do not classify this first-party case as the source C not-yet-valid third-party circumstance solely because that receipt date is absent. Actual evidence processing and identity checks retain their own instructions.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "B note",
        "additional_sources": [],
        "owner": "FO",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is an actual first-party click-and-sign iClaim.",
          "The ATTEST receipt date has not yet been entered; other identity/authentication and proper-application requirements remain distinct."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is an actual first-party click-and-sign iClaim.",
          "The ATTEST receipt date has not yet been entered; other identity/authentication and proper-application requirements remain distinct."
        ],
        "source_context_refs": [
          "GN01070.781-B"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "B whole, all substeps retained",
            "start": 875,
            "end": 4807,
            "exact_text": "B. \nClaims attested or receipted in by the WSU\n\nThese instructions pertain to both First Party and Third Party internet claims (iClaims).\n\nFirst party iClaims are signed by the Number Holder (NH) using the “click and sign” process and the word “Internet” propagates to the appropriate application, (e.g., DIB, RIB, Aux Spouse) on the Development Worksheet in MCS or CCE to indicate that an internet claim was filed using “click and sign”, see GN 00201.015.\n\nThird party iClaims cannot be signed using click and sign. However, follow instructions in this section if the WSU has already obtained a valid application by completing one of the following actions as documented on the DW01:\n\n•\n\nContacted the proper applicant and verbally attested the application, or\n\n•\n\nReceived a wet-signed SSA-1 or SSA-16 (or MCS and CCE output equivalent)\n\nNOTE:The Number Holder (NH) might contact the FO before the FO or WSU completes the ATTEST issue. Treat all first party iClaims the same for the purposes of the instructions in this section regardless of whether the FO or WSU has entered a receipt date in the ATTEST line of the MCS DW01 or CCE Development Worksheet.\n\n1. \nClaimants requiring action by the FO or WSU\n\nTechnicians will assist claimants with scheduling, rescheduling, or cancelling appointments in the Enterprise Scheduling System (ESS) and the Enhance Leads and Appointments System (eLAS) to support the Appointmetn Focused Service Delivery Model (AFS) for FOs.\n\na. \n\nFor Enumeration purposes: Technicians will utilized ESS to schedule appointments and will refer individuals to use the Online Social Security Number Application (oSNAP) when applicable.\n\nb. \n\nFor Initial Claims and Post-entitlement (PE) appointments: Technicians will utilize eLAS to schedule initial claim appointments, and ESS for PE appointments.\n\nc. \n\nTechnicians should annotate in the remarks that there is a pending iClaim.\n\n2. \nAssist claimants who provide evidence to the FO\na. \n\nRecord evidence received in the FO\n\nWhen a WSU claimant submits their proofs to the FO, an FO employee authorized to examine and certify documents takes the actions in this section. For more information about who we authorize to certify documents, see GN 00301.090.\n\n•\n\nExamine and evaluate the evidence document(s) for authenticity you may refer to our sensitive POMS; Evaluating the Validity of Documents and Records.\n\n•\n\nAccess Shared Process and enter the evidence document(s) on the Evidence (EVID) screen, unless you should not record the document(s) or form(s) on the EVID screen per GN 00301.286E.3.\n\n•\n\nIf the evidence cannot be recorded in EVID, certify a photocopy of the evidence document(s) and fax/send the certified photocopies into the Evidence Portal(EP) or eView.\n\n•\n\nEstablish the issue “REMARK” and an associated remark with a next day tickle on the MCS DW01 screen or on the CCE Development Worksheet to alert the WSU that you certified the document(s) via the Shared Process or faxed them into EP or eView.\n\n•\n\nAnnotate the MCS DW03 screen or CCE Development Worksheet with the FO code, the name, and the direct phone number of the FO employee who established the EVID or faxed the evidence into EP or eView.\n\n•\n\nCall or email the WSU immediately to notify them that you recorded proofs on the EVID screen or faxed proofs into EP or eView. This prevents processing delays and unnecessary re-contacts with the claimant.\n\n•\n\nComplete the Social Security Number Application Process (SSNAP) actions when enumeration updates are necessary.\n\nb. \n\nFO does not retain evidence faxed into EP, or eView\n\nFO technicians should verify that the evidence is properly stored in the Certified Electronic Folder (CEF).\n\nOnce the document has been recorded in EVID or stored and viewed for legible content in either EP or eView, the document does not need to be retained, per GN 00301.322. For information on the Retention or Return of Documents, see GN 00301.275.\n\n",
            "span_sha256": "ba7530d405d93262f91d35404eb11b7e9b0d4e141dc4fd068419cbed6494d886",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "provide-claim-evidence/wsu-first-party-ATTEST-date-not-entered"
      },
      "provide-claim-evidence/wsu-appointment-cancellation-not-agreed": {
        "id": "wsu-appointment-cancellation-not-agreed",
        "title": "The claimant does not agree to cancel the FO appointment",
        "when": "The WSU reaches the claimant, but the claimant does not agree to cancel the pending FO appointment.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Document the discussion in the claim remarks. Transfer the iClaim to the FO as the source directs; successful transfer and the appointment outcome are not established by this example.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "D",
        "additional_sources": [],
        "owner": "WSU",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "Contact is successful and the claimant does not agree to cancel the appointment."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "Contact is successful and the claimant does not agree to cancel the appointment."
        ],
        "source_context_refs": [
          "GN01070.781-D"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "D whole, all substeps retained",
            "start": 7452,
            "end": 8249,
            "exact_text": "D. \nWSU procedures to handle iClaims with appointments\n\nThe WSU assigned the claim assumes jurisdiction and adjudicates the iClaim application. When reviewing assigned iClaims, use the MCS DW01, CCE Claims Summary, or eLAS screens to determine if there is a pending appointment in an FO. For all pending appointments:\n\n•\n\nThe WSU contacts the claimant to advise that the WSU will process their claim and will cancel the appointment with the FO.\n\n•\n\nIf contact is successful and the claimant does not agree to cancel the appointment, document the discussion in remarks and transfer the iClaim to the FO.\n\n•\n\nIf the WSU is unable to reach the claimant after at least two attempts before the scheduled FO appointment, document the contact attempts in the remarks and cancel the pending appointment.\n\n",
            "span_sha256": "b476eb09507dcf98b3846365c7c149d45a35da851784110c0714ef2f257f69c4",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "provide-claim-evidence/wsu-appointment-cancellation-not-agreed"
      },
      "provide-claim-evidence/wsu-two-unsuccessful-appointment-contacts": {
        "id": "wsu-two-unsuccessful-appointment-contacts",
        "title": "The WSU cannot reach the claimant before the appointment",
        "when": "The WSU cannot reach the claimant after at least two attempts before the scheduled FO appointment.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Document the unsuccessful contact attempts in the remarks. The source directs cancellation of the pending appointment under these exact conditions; it does not direct denial of the claim.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "D",
        "additional_sources": [],
        "owner": "WSU",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "The WSU is unable to reach the claimant after at least two attempts before that scheduled appointment."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "The WSU is unable to reach the claimant after at least two attempts before that scheduled appointment."
        ],
        "source_context_refs": [
          "GN01070.781-D"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "D whole, all substeps retained",
            "start": 7452,
            "end": 8249,
            "exact_text": "D. \nWSU procedures to handle iClaims with appointments\n\nThe WSU assigned the claim assumes jurisdiction and adjudicates the iClaim application. When reviewing assigned iClaims, use the MCS DW01, CCE Claims Summary, or eLAS screens to determine if there is a pending appointment in an FO. For all pending appointments:\n\n•\n\nThe WSU contacts the claimant to advise that the WSU will process their claim and will cancel the appointment with the FO.\n\n•\n\nIf contact is successful and the claimant does not agree to cancel the appointment, document the discussion in remarks and transfer the iClaim to the FO.\n\n•\n\nIf the WSU is unable to reach the claimant after at least two attempts before the scheduled FO appointment, document the contact attempts in the remarks and cancel the pending appointment.\n\n",
            "span_sha256": "b476eb09507dcf98b3846365c7c149d45a35da851784110c0714ef2f257f69c4",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "provide-claim-evidence/wsu-two-unsuccessful-appointment-contacts"
      },
      "provide-claim-evidence/wsu-managers-mutual-transfer": {
        "id": "wsu-managers-mutual-transfer",
        "title": "The FO and WSU managers agree to a transfer",
        "when": "FO and WSU managers may transfer an iClaim by mutual agreement for enhanced service delivery.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Contact the other office by phone or email to discuss the situation. Document and facilitate the mutually agreed transfer. No actual jurisdiction change is established by selecting this scenario.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "E",
        "additional_sources": [],
        "owner": "WSU and FO managers",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The case is an iClaim between the FO and WSU.",
          "Both managers mutually agree to the source-defined transfer for enhanced service delivery."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The case is an iClaim between the FO and WSU.",
          "Both managers mutually agree to the source-defined transfer for enhanced service delivery."
        ],
        "source_context_refs": [
          "GN01070.781-E"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "E whole, all substeps retained",
            "start": 8249,
            "end": 8522,
            "exact_text": "E. \nTransfer iClaims with mutual agreement\n\nWSU and FO managers may transfer an iClaim between their offices by mutual agreement for enhanced service delivery. Contact the other office via telephone or email to discuss the situation. Document and facilitate the transfer.\n\n",
            "span_sha256": "f10d60a7acaa84dfbe25b4e1f0057e678920bec1b556ed55867884d8db50ffca",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "provide-claim-evidence/wsu-managers-mutual-transfer"
      },
      "provide-claim-evidence/wsu-signed-application-arrives-after-transfer": {
        "id": "wsu-signed-application-arrives-after-transfer",
        "title": "The signed application reaches the WSU after transfer to the FO",
        "when": "The WSU receives a signed application after it already transferred the claim to the FO for adjudication.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Send the signed application to the FO of jurisdiction. The source does not establish actual delivery or the final adjudication.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUcoord_selected",
        "section": "C.1.b note",
        "additional_sources": [],
        "owner": "WSU",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source C claim was already transferred from the WSU to the FO for adjudication.",
          "The WSU then receives the signed application; this is a later event, not a claim that the application remains unsigned."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source C claim was already transferred from the WSU to the FO for adjudication.",
          "The WSU then receives the signed application; this is a later event, not a claim that the application remains unsigned."
        ],
        "source_context_refs": [
          "GN01070.781-C"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.781",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
            "locator": "C whole, all substeps retained",
            "start": 4807,
            "end": 7452,
            "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
            "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
            "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
          "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
        },
        "full_route": "provide-claim-evidence/wsu-signed-application-arrives-after-transfer"
      },
      "resolve-partial-award/partial-future-event-diary": {
        "id": "partial-future-event-diary",
        "title": "This is a future-event diary, not retained WSU outstanding development",
        "when": "A WSU-established future-event diary matures under the separate source E route.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "At maturity the PC either acts on the future event OR sends a development request to the servicing FO for its required action. Find the servicing FO on MBR or RPOC for the source-defined follow-up. This is not the separate source D instruction to send a WSU-originated outstanding-issue diary back to the WSU.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_WSUdiary_selected",
        "section": "A; B future-events; E",
        "additional_sources": [],
        "owner": "PC",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
          "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
          "The future-event diary has matured; the source supplies no universal maturity date."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
          "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
          "The future-event diary has matured; the source supplies no universal maturity date."
        ],
        "source_context_refs": [
          "GN01070.782-A",
          "GN01070.782-B",
          "GN01070.782-E"
        ],
        "source_provenance": [
          {
            "source_code": "GN01070.782",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
            "locator": "A whole, all substeps retained",
            "start": 162,
            "end": 651,
            "exact_text": "A. \nOverview of the WSUs and their role\n\nThis section outlines the responsibilities of the WSUs in handling initial claim diaries that they establish in partial adjudication cases. These instructions should help ensure consistent handling of claims diaries across all Operations' components.\n\nThe WSUs process first-party English language iClaim Retirement and Medicare-only applications where the claimant provides a domestic residence address and has proven age and citizenship status.\n\n",
            "span_sha256": "bce29e34a54053569e99d2d1d09412fe1b30b5b7f5db969df661d6bb2e138e1f",
            "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
          },
          {
            "source_code": "GN01070.782",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
            "locator": "B whole, all substeps retained",
            "start": 651,
            "end": 2031,
            "exact_text": "B. \nDevelopment responsibilities for partial claims\n\nThe WSUs will initiate all necessary developmental action and requests for proof in the process of adjudicating their claims. If the WSU is not able to fully adjudicate because there is an unresolved issue (for example, involving military service, missing earnings), the WSUs will process the claim as a partial award, if it meets the requirements of GN 01010.110.\n\nThe WSUs will document and maintain control of partial claims until they receive the requested evidence and the outstanding issue(s) are resolved, as described in GN 01010.110D.\n\nThe process for handling diaries established on partial awards is the same process that the field offices (FO) follow.\n\nFor diaries established for future events, such as future Windfall Elimination Provision (WEP) entitlement, annotate the Modernized Claims System (MCS) Report of Contact (RPOC) screen with the reason for the diary and the local FO Code for future follow-up action.\n\nThe WSUs will monitor their Modernized Development Worksheet (MDW) diary alert listings, and follow-up on outstanding requests when needed. When the WSU completes the development, they will take the necessary action to clear the diary and adjust benefit rates, if necessary. The WSU will send an MDW or Request for Assistance form to the Processing Center (PC) to request they cancel the diary.\n\n",
            "span_sha256": "e3c87ba874aa587e8c8647608cfc3559122138c639872bcc32a2e10cb61557f5",
            "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
          },
          {
            "source_code": "GN01070.782",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
            "locator": "E whole, all substeps retained",
            "start": 3421,
            "end": 3980,
            "exact_text": "E. \nPC responsibility when future event diary matures\n\nThe WSUs also establish diaries on future events, such as earnings development, that they cannot develop until the following year and possible future higher entitlement on another Social Security number (SSN). The WSUs will not retain jurisdiction of these diaries. When the future event diary date matures, the PC will either take action on the future event or forward a follow-up development request to the servicing FO for their necessary action. Find the servicing FO on the MBR or the RPOC screen.\n\n",
            "span_sha256": "4143e2f30f0083e86029b67cbfca87c183becf61dec96979de15d992f06040b5",
            "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40",
          "snapshot_path": "/service/sources/GN01070.782-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
        },
        "full_route": "resolve-partial-award/partial-future-event-diary"
      },
      "resolve-partial-award/partial-RPOC-not-available": {
        "id": "partial-RPOC-not-available",
        "title": "The RPOC screen is unavailable for the diary rationale",
        "when": "The source MCS partial-award process needs its diary rationale documented, but RPOC is unavailable.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Prepare a paper RC with the diary information and the exact source remark: “SEE RC IN FILE - PC MUST ADD DIARY REMARKS - RPOC NOT AVAILABLE”. Fax the RC into the paperless unit of the PC with jurisdiction; this does not establish receipt or a new physical-system interface.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_partial_selected",
        "section": "B; C.1.a",
        "additional_sources": [],
        "owner": "Adjudicating component",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is an actual qualifying partial award under the source B entitlement/exclusion rules and the source C1a MCS processing instruction.",
          "RPOC screens are not available for the required diary information/rationale."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is an actual qualifying partial award under the source B entitlement/exclusion rules and the source C1a MCS processing instruction.",
          "RPOC screens are not available for the required diary information/rationale."
        ],
        "source_context_refs": [
          "GN01010.110-B",
          "GN01010.110-C"
        ],
        "source_provenance": [
          {
            "source_code": "GN01010.110",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
            "locator": "B whole, all substeps retained",
            "start": 1554,
            "end": 3583,
            "exact_text": "B. \nPolicy on partial adjudication\n\nThe claims technician is responsible for fully developing and reviewing the claim to ensure that the claimant meets all entitlement factors prior to adjudication. You must properly document any partial award in the Modernized Claims System (MCS) screen or the claims file to ensure proper control of any outstanding issues until they are resolved.\n\n1. \nWhen to partially adjudicate a claim\n\nPartially adjudicate a claim if:\n\na. \n\nAll factors of entitlement are met;\n\nb. \n\nThere is an unresolved issue pending (e.g., Military Service (MS) verification is pending);\n\nc. \n\nImmediate payment is due; and\n\nd. \n\nThe claimant either:\n\n•\n\nFiles an application and there is an issue pending development (e.g., proof of Military Service is being developed); or\n\n•\n\nIs potentially entitled to more than one benefit type or on more than one SSN and only one claim is ready for effectuation.\n\nReminder: It is not a partial award situation when a disability decision is still outstanding and the claimant files for another benefit type (e.g. RIB). The disability (DIB) decision is an outstanding entitlement factor for the DIB claim; adjudicate the RIB application separately from the DIB.\n\n2. \nWhen not to partially adjudicate a claim\n\nDo not adjudicate the following types of claims as partial awards:\n\na. \n\nLump Sum Death Payment (LSDP) claims via MCS while a claim for monthly benefits is pending on the same social security number (SSN) (see GN 01010.250).\n\nb. \n\nA claim with pending development for lag year earnings, in accordance with RS 01404.005. However, if lag earnings are not an entitlement issue (i.e. earnings are not needed for insured status), adjudicate the claim after 10 days. No diary is necessary.\n\nc. \n\nMedicare-only claims involving State buy-ins or not meeting the residency requirement. However, in advance filing cases where the claimant will meet the residency requirement, you can adjudicate the claim and include a diary for verification of the 5-year residency requirement.\n\n",
            "span_sha256": "5df3b4d03a280433220b31b6c2463365bf6cc93c68477a0afe5279e1a9452245",
            "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
          },
          {
            "source_code": "GN01010.110",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
            "locator": "C whole, all substeps retained",
            "start": 3583,
            "end": 6947,
            "exact_text": "C. \nProcedure for adjudicating partial awards\n1. \nDocumenting partial awards\n\nAll adjudicative decisions must reflect the documented facts for the entitlement. We cannot establish an element of entitlement or a factor affecting payment if you do not properly document it in accordance with the Program Operations Manual System (POMS) tolerances, presumptions, or evidentiary standards.\n\na. \nMCS earning computation (EC)\n•\n\nYou must select “DEC STAT 9” for retirement, survivor or Medicare partial claims (RSHI PARTIAL) or 10 (DIB PARTIAL) on the decision (DECI) screen;\n\n•\n\nInitiate the appropriate internal control (e.g., Modernized Development Worksheet (MDW)) and establish a diary on the DECI screen (see MSOM MCS 009.013) The DECI diary entry interfaces with the Processing Center Action Control System (PCACS) and establishes the diary in the processing center (PC).\n\n•\n\nAnnotate the report of contact (RPOC) screen with the applicable diary evidence code and a detailed rationale for all issues under development. If RPOC screens are not available, prepare a paper report of contact (RC) with the diary information including the following remark “SEE RC IN FILE - PC MUST ADD DIARY REMARKS - RPOC NOT AVAILABLE” and fax it into the paperless unit of the PC of jurisdiction. This simplifies and expedites accurate diary inputs in the PC.\n\nb. \nManually processed awards\n•\n\nFor manual awards, you must prepare an internal diary (e.g., MDW) and, request the PC to establish a diary supplying the applicable rationale and evidence Code(s).\n\n•\n\nAnnotate the Automated 101 (A101) or Electronic Form 101 (EF101) Benefit Continuity Remarks/Notice (BCRN) screen with the applicable diary Evidence Code(s) and document all issues under development in detail.\n\n•\n\nThe period for a diary for outstanding development input in the PC is usually 60-days unless conditions warrant a longer or shorter period and a specific date is input.\n\n2. \nPartial award notices\n\nYou must annotate the applicable partial award paragraph(s) on the notice as instructed here.\n\n•\n\nInclude a special paragraph on the appropriate screen for the award notice (e.g., notice (NOT) 2, NOT3, A101 BCRN screen, RPOC, etc.).\n\n•\n\nSelect the dictated paragraphs needed as instructed in MS 03509.010 and NL 00725.005 for the MCS Universal Text Identifiers (UTI) for partial awards (PAYR01).\n\n•\n\nFor Dual Entitlement (DE) claims, include the special paragraph stating that we will make a separate decision on the other claim, when applicable. Use the UTI “CLOR05” for MCS processing (NL 00725.005) and “B56” for manually processed awards.\n\n•\n\nThe notice must include language advising the claimant that we based the determination on currently available evidence and we may revise it based on additional evidence.\n\nNOTE: In most cases, the first notice is not an initial determination on the unresolved issue. The PC will send another notice once the development is complete. This second notice is the final determination on that issue and must include a reconsideration paragraph. However, the first notice may be the final notice in earning record (E/R) revision cases not involving an earnings investigation (see GN 04001.040E.2).\n\n3. \nSpecial Notice Not Required\n\nA special notice is not required if a Primary Insurance Amounts (PIA) discrepancy is resolved prior to adjudication (see GN 01010.100).\n\n",
            "span_sha256": "c5be9ddcd9570de5e4d03426217e371100d0b1c2fad62bd1c5791e4b0bf853e0",
            "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56",
          "snapshot_path": "/service/sources/GN01010.110-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "full_route": "resolve-partial-award/partial-RPOC-not-available"
      },
      "resolve-partial-award/partial-pending-DIB-separate-other-benefit": {
        "id": "partial-pending-DIB-separate-other-benefit",
        "title": "A disability decision is still outstanding for another benefit claim",
        "when": "The claimant files another benefit type while the DIB disability decision is still outstanding.",
        "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
        "ssa": "Adjudicate the other benefit application separately from the DIB claim under its applicable requirements. This is not a partial-award shortcut or an approval finding.",
        "route": "Selected source-defined staff handling; no automatic transition",
        "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
        "source": "r22_partial_selected",
        "section": "B.1 reminder",
        "additional_sources": [],
        "owner": "Adjudicating component",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The DIB disability decision remains an outstanding entitlement factor for that DIB claim.",
          "The claimant files another benefit type, such as RIB; no entitlement or payment for that other claim is established."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The DIB disability decision remains an outstanding entitlement factor for that DIB claim.",
          "The claimant files another benefit type, such as RIB; no entitlement or payment for that other claim is established."
        ],
        "source_context_refs": [
          "GN01010.110-B"
        ],
        "source_provenance": [
          {
            "source_code": "GN01010.110",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
            "locator": "B whole, all substeps retained",
            "start": 1554,
            "end": 3583,
            "exact_text": "B. \nPolicy on partial adjudication\n\nThe claims technician is responsible for fully developing and reviewing the claim to ensure that the claimant meets all entitlement factors prior to adjudication. You must properly document any partial award in the Modernized Claims System (MCS) screen or the claims file to ensure proper control of any outstanding issues until they are resolved.\n\n1. \nWhen to partially adjudicate a claim\n\nPartially adjudicate a claim if:\n\na. \n\nAll factors of entitlement are met;\n\nb. \n\nThere is an unresolved issue pending (e.g., Military Service (MS) verification is pending);\n\nc. \n\nImmediate payment is due; and\n\nd. \n\nThe claimant either:\n\n•\n\nFiles an application and there is an issue pending development (e.g., proof of Military Service is being developed); or\n\n•\n\nIs potentially entitled to more than one benefit type or on more than one SSN and only one claim is ready for effectuation.\n\nReminder: It is not a partial award situation when a disability decision is still outstanding and the claimant files for another benefit type (e.g. RIB). The disability (DIB) decision is an outstanding entitlement factor for the DIB claim; adjudicate the RIB application separately from the DIB.\n\n2. \nWhen not to partially adjudicate a claim\n\nDo not adjudicate the following types of claims as partial awards:\n\na. \n\nLump Sum Death Payment (LSDP) claims via MCS while a claim for monthly benefits is pending on the same social security number (SSN) (see GN 01010.250).\n\nb. \n\nA claim with pending development for lag year earnings, in accordance with RS 01404.005. However, if lag earnings are not an entitlement issue (i.e. earnings are not needed for insured status), adjudicate the claim after 10 days. No diary is necessary.\n\nc. \n\nMedicare-only claims involving State buy-ins or not meeting the residency requirement. However, in advance filing cases where the claimant will meet the residency requirement, you can adjudicate the claim and include a diary for verification of the 5-year residency requirement.\n\n",
            "span_sha256": "5df3b4d03a280433220b31b6c2463365bf6cc93c68477a0afe5279e1a9452245",
            "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
          }
        ],
        "qualifications": [
          "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
          "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
          "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
          "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
        ],
        "timing": "No customer completion duration is established.",
        "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_WSU_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56",
          "snapshot_path": "/service/sources/GN01010.110-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
        },
        "full_route": "resolve-partial-award/partial-pending-DIB-separate-other-benefit"
      },
      "change-name/name-event-document-needs-additional-identity": {
        "id": "name-event-document-needs-additional-identity",
        "title": "The event document cannot establish identity by itself",
        "when": "The name-change event document does not meet the source’s conditions to serve as identity.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Request an identity document in the prior name, or a new-name identity document only when linked RM10212.020 conditions are met. Acceptability priority rules and event-specific conditions remain separate.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_name",
        "section": "D whole",
        "additional_sources": [],
        "owner": "context / SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The name-change event and new-name evidence must satisfy their separate rules.",
          "The event document cannot itself serve as identity under D: it is a birth certificate; OR the event did not occur within the past two years (four years when under age18); OR the required prior-name/biographical linkage to the latest Numident is not met."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The name-change event and new-name evidence must satisfy their separate rules.",
          "The event document cannot itself serve as identity under D: it is a birth certificate; OR the event did not occur within the past two years (four years when under age18); OR the required prior-name/biographical linkage to the latest Numident is not met."
        ],
        "source_context_refs": [
          "RM10212.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10212.015",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 4628,
            "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
            "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
          "snapshot_path": "/service/sources/RM10212.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "change-name/name-event-document-needs-additional-identity",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "change-name/name-expired-prior-name-identity": {
        "id": "name-expired-prior-name-identity",
        "title": "A prior-name identity document is expired",
        "when": "An expired prior-name identity document is submitted in connection with a name change.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source permits the prior-name identity document even if no longer current or expired in this name-change connection. This does not make every expired document acceptable or waive the linked identity rules.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_name",
        "section": "D expiration exceptions",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "Identity must link to the latest Numident and the document must otherwise meet the applicable identity requirements.",
          "The document is in the prior name and is submitted in connection with a name change."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "Identity must link to the latest Numident and the document must otherwise meet the applicable identity requirements.",
          "The document is in the prior name and is submitted in connection with a name change."
        ],
        "source_context_refs": [
          "RM10212.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10212.015",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 4628,
            "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
            "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
          "snapshot_path": "/service/sources/RM10212.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "change-name/name-expired-prior-name-identity",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "change-name/name-surname-component-can-link": {
        "id": "name-surname-component-can-link",
        "title": "A surname component differs but can be linked",
        "when": "An added or missing surname component can be linked to the latest Numident.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source accepts this document for the surname discrepancy if the surname components can be linked to Numident. Other name-change and identity requirements are not waived.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_name",
        "section": "D.1",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The difference is a missing or additional part of the surname on the event or identity document.",
          "SSA establishes linkage to the latest Numident, for example through a parent’s name or name at birth."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The difference is a missing or additional part of the surname on the event or identity document.",
          "SSA establishes linkage to the latest Numident, for example through a parent’s name or name at birth."
        ],
        "source_context_refs": [
          "RM10212.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10212.015",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 4628,
            "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
            "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
          "snapshot_path": "/service/sources/RM10212.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "change-name/name-surname-component-can-link",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "change-name/name-unlinked-surname-prior-event": {
        "id": "name-unlinked-surname-prior-event",
        "title": "A surname component cannot be linked",
        "when": "Surname components cannot be linked and a prior name-change event may explain use of the name.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Resolve the identity question by requesting prior name-change event evidence proving the applicant may have used that name in the past. Specific event-document requirements remain linked and unreviewed.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_name",
        "section": "D.1",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "Parts of the surname cannot be linked to the latest Numident.",
          "The source’s prior-name-change evidence route applies; actual event/document acceptability is not established here."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "Parts of the surname cannot be linked to the latest Numident.",
          "The source’s prior-name-change evidence route applies; actual event/document acceptability is not established here."
        ],
        "source_context_refs": [
          "RM10212.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10212.015",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 4628,
            "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
            "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
          "snapshot_path": "/service/sources/RM10212.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "change-name/name-unlinked-surname-prior-event",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "change-name/name-unlinked-surname-no-event": {
        "id": "name-unlinked-surname-no-event",
        "title": "No name-change event explains the surname difference",
        "when": "The surname cannot be linked and no name-change event has occurred.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Request evidence of the legal name, such as the source’s birth-certificate example, under RM10212.001. This legal-name purpose does not turn a birth certificate into the sole acceptable identity document under D.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_name",
        "section": "D.1",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The D1 surname discrepancy cannot be linked.",
          "No name-change event has occurred."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The D1 surname discrepancy cannot be linked.",
          "No name-change event has occurred."
        ],
        "source_context_refs": [
          "RM10212.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10212.015",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 4628,
            "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
            "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
          "snapshot_path": "/service/sources/RM10212.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "change-name/name-unlinked-surname-no-event",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "apply-extra-help/extra-help-deemed-group": {
        "id": "extra-help-deemed-group",
        "title": "The person is in a source-defined deemed group",
        "when": "The source says these Medicare-related groups should not file a subsidy application.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The page says CMS separately contacts the person about the subsidy and plan selection/change/opt-out instructions. A person who does not want to wait may contact CMS through the source-listed phone or website; actual contact or enrollment is not established.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_extra",
        "section": "B.3 Who Should Not Complete",
        "additional_sources": [],
        "owner": "context / claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "Actual facts establish one of the source groups: SSI plus Medicare; Medicaid prescription-drug coverage plus Medicare; or State payment of Medicare premiums, such as QMB/SLMB/QI."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "Actual facts establish one of the source groups: SSI plus Medicare; Medicaid prescription-drug coverage plus Medicare; or State payment of Medicare premiums, such as QMB/SLMB/QI."
        ],
        "source_context_refs": [
          "HI03010.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "HI03010.035",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6228,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 12/04/2025 - Present\nPrevious | Next\n\nTN 54 (12-25)\n\nHI 03010.035 General Information about the Subsidy Application\n\nCITATIONS:\n\nRegulations—20 CFR 418.3201 and 42 CFR 423.774\nA. \nIntroduction\n\nThe MMA allows individuals to file for the subsidy with either SSA or a State Medicaid office. The law also required that CMS and SSA jointly develop an application for determining eligibility for the subsidy. SSA and CMS considered comments from States, advocacy groups, focus group participants and SSA regional coordinators when developing this application.\n\nStates have the option of using the CMS-SSA form (SSA-1020-OCR), SSA’s Internet application (i1020), or their own application. However, if a State Medicaid office chooses to use an application other than the SSA-1020 or i1020, that State Agency will make the eligibility determinations for those applications. States using the SSA-1020-OCR may forward the application to SSA to process. The instructions in this section apply to applications that will be processed by SSA.\n\nB. \nMethods of filing\n\nThere are several methods of filing the application but the same data is collected whichever method is used. Any of the application methods here can be used by a:\n\n•\n\nsingle individual filing for themselves (see HI 03010.010 for definition of proper applicant);\n\n•\n\nmarried individual filing only for themselves; or\n\n•\n\nmarried couple (living together) who are both filing for the subsidy at the same time.\n\n1. \nScannable Form (SSA-1020-OCR)\n\nThis is a self-help form. It will be mailed to Medicare eligible individuals who appear to meet the income limits based solely on computer matches with other agencies. The form will also be distributed at outreach events and used by State agencies and advocacy groups. It can be completed by the claimant or a personal representative filing on behalf of the claimant (see HI 03010.010B.). When completed, the SSA-1020-OCR is sent to the WBDOC to process as explained in HI 03010.040C.2. See HI 03010.038B.1. if the completed form is received in a field office (FO).\n\nThe SSA-1020-OCR is available in English and Spanish. SSA’s web site will contain facsimiles of the SSA-1020 in 14 languages that an applicant can use to complete the SSA-1020-OCR. The facsimiles are not scannable and should not be completed or forwarded to WBDOC.\n\n2. \nMAPS\n\nSSA FO and Workload Support Unit (WSU) staffs will complete in-person and telephone application interviews asking questions that are presented on a series of screens in the new MAPS. MAPS was developed specifically for the subsidy. Some questions on the MAPS are worded and presented differently than questions on the scannable form, but they elicit the same information.\n\n3. \nInternet Application (i1020)\n\nThe Internet application (i1020) is an interactive self-help form designed to capture all inputs by the claimant (or third party on behalf of the claimant) and subsequently propagate this data to the Medicare Determination process without any intervening action by an adjudicator. The screens are similar to, and elicit the same information as, MAPS screens and the scannable application. However, easy-access Help screens containing additional explanatory information are also available on the i1020 for most questions. The i1020 is available in English and Spanish. It can be accessed via the following website: www.ssa.gov/medicare/part-d-extra-help .\n\nNOTE: \n\nAlthough the screens are similar, the i1020 does not use or interface with MAPS screens to input subsidy application data to the Determination process. However, once accepted, MAPS screens are used to query and/or change data in an application entered via the i1020.\n\nThe following information is being provided solely to help respond to inquiries that may be received about the i1020.\n\nWho Should Complete the Subsidy Application?\n\nClaimants may use the i1020 to apply for the subsidy if:\n\n•\n\nthey have or are eligible for Medicare Part A and/or Part B; and\n\n•\n\nthey live in one of the 50 states or the District of Columbia; and\n\n•\n\ntheir combined savings, investments, and real estate (other than their home) is not worth more than $18,090 ($17,600 in 2025) if they are single, or $36,100 ($35,130 in 2025) if they are married and living together.\n\nNOTE: \n\nEven if the above amounts are exceeded, claimants may still be eligible for the subsidy – but they will have to contact their state Medicaid agency to find out. However, claimants may still enroll with an approved Medicare prescription drug provider for Part D coverage – whether or not they are eligible for the subsidy. To obtain a list of Medicare-approved prescription drug providers in their area, claimants may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nWho Should Not Complete the Subsidy Application\n\nSome claimants will be deemed eligible for the subsidy and should not complete an i1020 (or any other subsidy application). Claimants who should not file include those:\n\n•\n\nwho receive SSI payments and have Medicare;\n\n•\n\nwho receive Medicaid with prescription drug coverage and have Medicare; or\n\n•\n\nwhose state pays for their Medicare premiums (e.g., QMBs, SLMBs and QIs).\n\nThese claimants will be contacted separately by CMS about their subsidy. CMS will also notify them of the plan selection and provide instructions for changing plans or opting out of enrollment. If they don’t want to wait to be contacted, they may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0603010035\n\t\nHI 03010.035 - General Information about the Subsidy Application - 12/04/2025\nBatch run: 12/04/2025\nRev:12/04/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
            "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
          "snapshot_path": "/service/sources/HI03010.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "apply-extra-help/extra-help-deemed-group",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
        }
      },
      "apply-extra-help/extra-help-state-own-application": {
        "id": "extra-help-state-own-application",
        "title": "The State uses its own application",
        "when": "A State Medicaid agency uses an application other than SSA-1020 or i1020.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "For that State application, the source assigns the eligibility determination to the State agency. A State using SSA-1020-OCR may instead forward it to SSA; no automatic forwarding is established. This SSA page does not provide the State’s full filing, development or appeal procedure; no State procedure is modeled here.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_extra",
        "section": "A",
        "additional_sources": [],
        "owner": "context / State Medicaid agency",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The State Medicaid office chooses an application other than SSA-1020 or i1020."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The State Medicaid office chooses an application other than SSA-1020 or i1020."
        ],
        "source_context_refs": [
          "HI03010.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "HI03010.035",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6228,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 12/04/2025 - Present\nPrevious | Next\n\nTN 54 (12-25)\n\nHI 03010.035 General Information about the Subsidy Application\n\nCITATIONS:\n\nRegulations—20 CFR 418.3201 and 42 CFR 423.774\nA. \nIntroduction\n\nThe MMA allows individuals to file for the subsidy with either SSA or a State Medicaid office. The law also required that CMS and SSA jointly develop an application for determining eligibility for the subsidy. SSA and CMS considered comments from States, advocacy groups, focus group participants and SSA regional coordinators when developing this application.\n\nStates have the option of using the CMS-SSA form (SSA-1020-OCR), SSA’s Internet application (i1020), or their own application. However, if a State Medicaid office chooses to use an application other than the SSA-1020 or i1020, that State Agency will make the eligibility determinations for those applications. States using the SSA-1020-OCR may forward the application to SSA to process. The instructions in this section apply to applications that will be processed by SSA.\n\nB. \nMethods of filing\n\nThere are several methods of filing the application but the same data is collected whichever method is used. Any of the application methods here can be used by a:\n\n•\n\nsingle individual filing for themselves (see HI 03010.010 for definition of proper applicant);\n\n•\n\nmarried individual filing only for themselves; or\n\n•\n\nmarried couple (living together) who are both filing for the subsidy at the same time.\n\n1. \nScannable Form (SSA-1020-OCR)\n\nThis is a self-help form. It will be mailed to Medicare eligible individuals who appear to meet the income limits based solely on computer matches with other agencies. The form will also be distributed at outreach events and used by State agencies and advocacy groups. It can be completed by the claimant or a personal representative filing on behalf of the claimant (see HI 03010.010B.). When completed, the SSA-1020-OCR is sent to the WBDOC to process as explained in HI 03010.040C.2. See HI 03010.038B.1. if the completed form is received in a field office (FO).\n\nThe SSA-1020-OCR is available in English and Spanish. SSA’s web site will contain facsimiles of the SSA-1020 in 14 languages that an applicant can use to complete the SSA-1020-OCR. The facsimiles are not scannable and should not be completed or forwarded to WBDOC.\n\n2. \nMAPS\n\nSSA FO and Workload Support Unit (WSU) staffs will complete in-person and telephone application interviews asking questions that are presented on a series of screens in the new MAPS. MAPS was developed specifically for the subsidy. Some questions on the MAPS are worded and presented differently than questions on the scannable form, but they elicit the same information.\n\n3. \nInternet Application (i1020)\n\nThe Internet application (i1020) is an interactive self-help form designed to capture all inputs by the claimant (or third party on behalf of the claimant) and subsequently propagate this data to the Medicare Determination process without any intervening action by an adjudicator. The screens are similar to, and elicit the same information as, MAPS screens and the scannable application. However, easy-access Help screens containing additional explanatory information are also available on the i1020 for most questions. The i1020 is available in English and Spanish. It can be accessed via the following website: www.ssa.gov/medicare/part-d-extra-help .\n\nNOTE: \n\nAlthough the screens are similar, the i1020 does not use or interface with MAPS screens to input subsidy application data to the Determination process. However, once accepted, MAPS screens are used to query and/or change data in an application entered via the i1020.\n\nThe following information is being provided solely to help respond to inquiries that may be received about the i1020.\n\nWho Should Complete the Subsidy Application?\n\nClaimants may use the i1020 to apply for the subsidy if:\n\n•\n\nthey have or are eligible for Medicare Part A and/or Part B; and\n\n•\n\nthey live in one of the 50 states or the District of Columbia; and\n\n•\n\ntheir combined savings, investments, and real estate (other than their home) is not worth more than $18,090 ($17,600 in 2025) if they are single, or $36,100 ($35,130 in 2025) if they are married and living together.\n\nNOTE: \n\nEven if the above amounts are exceeded, claimants may still be eligible for the subsidy – but they will have to contact their state Medicaid agency to find out. However, claimants may still enroll with an approved Medicare prescription drug provider for Part D coverage – whether or not they are eligible for the subsidy. To obtain a list of Medicare-approved prescription drug providers in their area, claimants may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nWho Should Not Complete the Subsidy Application\n\nSome claimants will be deemed eligible for the subsidy and should not complete an i1020 (or any other subsidy application). Claimants who should not file include those:\n\n•\n\nwho receive SSI payments and have Medicare;\n\n•\n\nwho receive Medicaid with prescription drug coverage and have Medicare; or\n\n•\n\nwhose state pays for their Medicare premiums (e.g., QMBs, SLMBs and QIs).\n\nThese claimants will be contacted separately by CMS about their subsidy. CMS will also notify them of the plan selection and provide instructions for changing plans or opting out of enrollment. If they don’t want to wait to be contacted, they may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0603010035\n\t\nHI 03010.035 - General Information about the Subsidy Application - 12/04/2025\nBatch run: 12/04/2025\nRev:12/04/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
            "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
          "snapshot_path": "/service/sources/HI03010.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "apply-extra-help/extra-help-state-own-application",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
        }
      },
      "apply-extra-help/extra-help-language-facsimile": {
        "id": "extra-help-language-facsimile",
        "title": "A translated facsimile is being used as a guide",
        "when": "A facsimile in another language is used to help complete the scannable form.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Use the facsimile to help complete the SSA-1020-OCR; the source says the facsimile is not scannable and should not itself be completed or sent to WBDOC.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_extra",
        "section": "B.1",
        "additional_sources": [],
        "owner": "claimant / context",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The document is one of the source-described language facsimiles rather than the scannable SSA-1020-OCR."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The document is one of the source-described language facsimiles rather than the scannable SSA-1020-OCR."
        ],
        "source_context_refs": [
          "HI03010.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "HI03010.035",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6228,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 12/04/2025 - Present\nPrevious | Next\n\nTN 54 (12-25)\n\nHI 03010.035 General Information about the Subsidy Application\n\nCITATIONS:\n\nRegulations—20 CFR 418.3201 and 42 CFR 423.774\nA. \nIntroduction\n\nThe MMA allows individuals to file for the subsidy with either SSA or a State Medicaid office. The law also required that CMS and SSA jointly develop an application for determining eligibility for the subsidy. SSA and CMS considered comments from States, advocacy groups, focus group participants and SSA regional coordinators when developing this application.\n\nStates have the option of using the CMS-SSA form (SSA-1020-OCR), SSA’s Internet application (i1020), or their own application. However, if a State Medicaid office chooses to use an application other than the SSA-1020 or i1020, that State Agency will make the eligibility determinations for those applications. States using the SSA-1020-OCR may forward the application to SSA to process. The instructions in this section apply to applications that will be processed by SSA.\n\nB. \nMethods of filing\n\nThere are several methods of filing the application but the same data is collected whichever method is used. Any of the application methods here can be used by a:\n\n•\n\nsingle individual filing for themselves (see HI 03010.010 for definition of proper applicant);\n\n•\n\nmarried individual filing only for themselves; or\n\n•\n\nmarried couple (living together) who are both filing for the subsidy at the same time.\n\n1. \nScannable Form (SSA-1020-OCR)\n\nThis is a self-help form. It will be mailed to Medicare eligible individuals who appear to meet the income limits based solely on computer matches with other agencies. The form will also be distributed at outreach events and used by State agencies and advocacy groups. It can be completed by the claimant or a personal representative filing on behalf of the claimant (see HI 03010.010B.). When completed, the SSA-1020-OCR is sent to the WBDOC to process as explained in HI 03010.040C.2. See HI 03010.038B.1. if the completed form is received in a field office (FO).\n\nThe SSA-1020-OCR is available in English and Spanish. SSA’s web site will contain facsimiles of the SSA-1020 in 14 languages that an applicant can use to complete the SSA-1020-OCR. The facsimiles are not scannable and should not be completed or forwarded to WBDOC.\n\n2. \nMAPS\n\nSSA FO and Workload Support Unit (WSU) staffs will complete in-person and telephone application interviews asking questions that are presented on a series of screens in the new MAPS. MAPS was developed specifically for the subsidy. Some questions on the MAPS are worded and presented differently than questions on the scannable form, but they elicit the same information.\n\n3. \nInternet Application (i1020)\n\nThe Internet application (i1020) is an interactive self-help form designed to capture all inputs by the claimant (or third party on behalf of the claimant) and subsequently propagate this data to the Medicare Determination process without any intervening action by an adjudicator. The screens are similar to, and elicit the same information as, MAPS screens and the scannable application. However, easy-access Help screens containing additional explanatory information are also available on the i1020 for most questions. The i1020 is available in English and Spanish. It can be accessed via the following website: www.ssa.gov/medicare/part-d-extra-help .\n\nNOTE: \n\nAlthough the screens are similar, the i1020 does not use or interface with MAPS screens to input subsidy application data to the Determination process. However, once accepted, MAPS screens are used to query and/or change data in an application entered via the i1020.\n\nThe following information is being provided solely to help respond to inquiries that may be received about the i1020.\n\nWho Should Complete the Subsidy Application?\n\nClaimants may use the i1020 to apply for the subsidy if:\n\n•\n\nthey have or are eligible for Medicare Part A and/or Part B; and\n\n•\n\nthey live in one of the 50 states or the District of Columbia; and\n\n•\n\ntheir combined savings, investments, and real estate (other than their home) is not worth more than $18,090 ($17,600 in 2025) if they are single, or $36,100 ($35,130 in 2025) if they are married and living together.\n\nNOTE: \n\nEven if the above amounts are exceeded, claimants may still be eligible for the subsidy – but they will have to contact their state Medicaid agency to find out. However, claimants may still enroll with an approved Medicare prescription drug provider for Part D coverage – whether or not they are eligible for the subsidy. To obtain a list of Medicare-approved prescription drug providers in their area, claimants may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nWho Should Not Complete the Subsidy Application\n\nSome claimants will be deemed eligible for the subsidy and should not complete an i1020 (or any other subsidy application). Claimants who should not file include those:\n\n•\n\nwho receive SSI payments and have Medicare;\n\n•\n\nwho receive Medicaid with prescription drug coverage and have Medicare; or\n\n•\n\nwhose state pays for their Medicare premiums (e.g., QMBs, SLMBs and QIs).\n\nThese claimants will be contacted separately by CMS about their subsidy. CMS will also notify them of the plan selection and provide instructions for changing plans or opting out of enrollment. If they don’t want to wait to be contacted, they may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0603010035\n\t\nHI 03010.035 - General Information about the Subsidy Application - 12/04/2025\nBatch run: 12/04/2025\nRev:12/04/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
            "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
          "snapshot_path": "/service/sources/HI03010.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "apply-extra-help/extra-help-language-facsimile",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "apply-extra-help/extra-help-resources-question-state-route": {
        "id": "extra-help-resources-question-state-route",
        "title": "Resources exceed the page’s listed i1020 amounts",
        "when": "The person asks about the source’s resource-amount boundary.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The page also says a person may enroll with an approved Medicare prescription-drug provider whether or not eligible for subsidy; no enrollment or eligibility result is established.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_extra",
        "section": "B.3 resource note",
        "additional_sources": [],
        "owner": "context / claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source’s listed i1020 resource guidance is relevant; this example does not calculate countable resources, apply exclusions or determine entitlement."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source’s listed i1020 resource guidance is relevant; this example does not calculate countable resources, apply exclusions or determine entitlement."
        ],
        "source_context_refs": [
          "HI03010.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "HI03010.035",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6228,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 12/04/2025 - Present\nPrevious | Next\n\nTN 54 (12-25)\n\nHI 03010.035 General Information about the Subsidy Application\n\nCITATIONS:\n\nRegulations—20 CFR 418.3201 and 42 CFR 423.774\nA. \nIntroduction\n\nThe MMA allows individuals to file for the subsidy with either SSA or a State Medicaid office. The law also required that CMS and SSA jointly develop an application for determining eligibility for the subsidy. SSA and CMS considered comments from States, advocacy groups, focus group participants and SSA regional coordinators when developing this application.\n\nStates have the option of using the CMS-SSA form (SSA-1020-OCR), SSA’s Internet application (i1020), or their own application. However, if a State Medicaid office chooses to use an application other than the SSA-1020 or i1020, that State Agency will make the eligibility determinations for those applications. States using the SSA-1020-OCR may forward the application to SSA to process. The instructions in this section apply to applications that will be processed by SSA.\n\nB. \nMethods of filing\n\nThere are several methods of filing the application but the same data is collected whichever method is used. Any of the application methods here can be used by a:\n\n•\n\nsingle individual filing for themselves (see HI 03010.010 for definition of proper applicant);\n\n•\n\nmarried individual filing only for themselves; or\n\n•\n\nmarried couple (living together) who are both filing for the subsidy at the same time.\n\n1. \nScannable Form (SSA-1020-OCR)\n\nThis is a self-help form. It will be mailed to Medicare eligible individuals who appear to meet the income limits based solely on computer matches with other agencies. The form will also be distributed at outreach events and used by State agencies and advocacy groups. It can be completed by the claimant or a personal representative filing on behalf of the claimant (see HI 03010.010B.). When completed, the SSA-1020-OCR is sent to the WBDOC to process as explained in HI 03010.040C.2. See HI 03010.038B.1. if the completed form is received in a field office (FO).\n\nThe SSA-1020-OCR is available in English and Spanish. SSA’s web site will contain facsimiles of the SSA-1020 in 14 languages that an applicant can use to complete the SSA-1020-OCR. The facsimiles are not scannable and should not be completed or forwarded to WBDOC.\n\n2. \nMAPS\n\nSSA FO and Workload Support Unit (WSU) staffs will complete in-person and telephone application interviews asking questions that are presented on a series of screens in the new MAPS. MAPS was developed specifically for the subsidy. Some questions on the MAPS are worded and presented differently than questions on the scannable form, but they elicit the same information.\n\n3. \nInternet Application (i1020)\n\nThe Internet application (i1020) is an interactive self-help form designed to capture all inputs by the claimant (or third party on behalf of the claimant) and subsequently propagate this data to the Medicare Determination process without any intervening action by an adjudicator. The screens are similar to, and elicit the same information as, MAPS screens and the scannable application. However, easy-access Help screens containing additional explanatory information are also available on the i1020 for most questions. The i1020 is available in English and Spanish. It can be accessed via the following website: www.ssa.gov/medicare/part-d-extra-help .\n\nNOTE: \n\nAlthough the screens are similar, the i1020 does not use or interface with MAPS screens to input subsidy application data to the Determination process. However, once accepted, MAPS screens are used to query and/or change data in an application entered via the i1020.\n\nThe following information is being provided solely to help respond to inquiries that may be received about the i1020.\n\nWho Should Complete the Subsidy Application?\n\nClaimants may use the i1020 to apply for the subsidy if:\n\n•\n\nthey have or are eligible for Medicare Part A and/or Part B; and\n\n•\n\nthey live in one of the 50 states or the District of Columbia; and\n\n•\n\ntheir combined savings, investments, and real estate (other than their home) is not worth more than $18,090 ($17,600 in 2025) if they are single, or $36,100 ($35,130 in 2025) if they are married and living together.\n\nNOTE: \n\nEven if the above amounts are exceeded, claimants may still be eligible for the subsidy – but they will have to contact their state Medicaid agency to find out. However, claimants may still enroll with an approved Medicare prescription drug provider for Part D coverage – whether or not they are eligible for the subsidy. To obtain a list of Medicare-approved prescription drug providers in their area, claimants may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nWho Should Not Complete the Subsidy Application\n\nSome claimants will be deemed eligible for the subsidy and should not complete an i1020 (or any other subsidy application). Claimants who should not file include those:\n\n•\n\nwho receive SSI payments and have Medicare;\n\n•\n\nwho receive Medicaid with prescription drug coverage and have Medicare; or\n\n•\n\nwhose state pays for their Medicare premiums (e.g., QMBs, SLMBs and QIs).\n\nThese claimants will be contacted separately by CMS about their subsidy. CMS will also notify them of the plan selection and provide instructions for changing plans or opting out of enrollment. If they don’t want to wait to be contacted, they may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0603010035\n\t\nHI 03010.035 - General Information about the Subsidy Application - 12/04/2025\nBatch run: 12/04/2025\nRev:12/04/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
            "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
          "snapshot_path": "/service/sources/HI03010.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "apply-extra-help/extra-help-resources-question-state-route",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
        }
      },
      "lower-irmaa/irmaa-amended-return-contact": {
        "id": "irmaa-amended-return-contact",
        "title": "The request concerns an amended tax return",
        "when": "The person had an amended income tax return.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Call the official SSA number shown on the publisher page and tell the representative the request concerns lowering IRMAA after an amended tax return. The page does not specify a complete adjudication or evidence-decision procedure for this branch.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_irmaa",
        "section": "Amended income tax returns",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "An amended income tax return is the source-defined reason for this request; a life-changing event is not inferred."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "An amended income tax return is the source-defined reason for this request; a life-changing event is not inferred."
        ],
        "source_context_refs": [
          "SSA-irmaa-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-irmaa",
            "url": "https://www.ssa.gov/medicare/lower-irmaa",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1871,
            "exact_text": "Breadcrumb\nHome  Medicare  Request to lower IRMAA\nPlan for Medicare\nSign up for Medicare\nRequest to lower IRMAA\nApply for Part D Extra Help\nManage Medicare benefits\nRequest to lower an Income-Related Monthly Adjustment Amount (IRMAA)\n\nIf you've had a life-changing event that reduced your household income, you can ask to lower the additional amount you'll pay for Medicare Part B and Part D.\n\nLife-changing events include marriage, divorce, the death of a spouse, loss of income, and an employer settlement payment.\n\nUpload your request to lower an IRMAA\n\nSign in to fill out and submit Medicare Income-Related Monthly Adjustment Amount-Life Changing Event (SSA-44). \n\nSign In\nCreate account\nAmended income tax returns\n\nCall +1 800-772-1213 and tell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) if you had an amended income tax return.\n\nOther ways to complete this task\n\nFax or mail your request\n\nFill out the Medicare Income-Related Monthly Adjustment Amount – Life-Changing Event (SSA-44) (PDF) form. Fax or mail your completed form and evidence to a Social Security office.\n\nFind your local office\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nFor support completing this task\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) due to a life-changing event.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
            "maintext_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
          "snapshot_path": "/service/sources/SSA-irmaa-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "lower-irmaa/irmaa-amended-return-contact",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "lower-irmaa/irmaa-fax-mail-life-change": {
        "id": "irmaa-fax-mail-life-change",
        "title": "Use the fax or mail life-changing-event option",
        "when": "The person uses the source’s fax/mail alternative for the life-changing-event request.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Complete SSA-44 for the life-changing-event request and the applicable evidence. This example does not decide a qualifying event or required proof. Fax or mail the completed form and evidence to a Social Security office using the publisher’s office-finder route. Actual receipt and the IRMAA result remain unverified.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_irmaa",
        "section": "Fax or mail your request",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is a life-changing event that reduced household income under the source guidance.",
          "The completed SSA-44 and applicable evidence are being submitted using the source’s fax/mail option."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is a life-changing event that reduced household income under the source guidance.",
          "The completed SSA-44 and applicable evidence are being submitted using the source’s fax/mail option."
        ],
        "source_context_refs": [
          "SSA-irmaa-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-irmaa",
            "url": "https://www.ssa.gov/medicare/lower-irmaa",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1871,
            "exact_text": "Breadcrumb\nHome  Medicare  Request to lower IRMAA\nPlan for Medicare\nSign up for Medicare\nRequest to lower IRMAA\nApply for Part D Extra Help\nManage Medicare benefits\nRequest to lower an Income-Related Monthly Adjustment Amount (IRMAA)\n\nIf you've had a life-changing event that reduced your household income, you can ask to lower the additional amount you'll pay for Medicare Part B and Part D.\n\nLife-changing events include marriage, divorce, the death of a spouse, loss of income, and an employer settlement payment.\n\nUpload your request to lower an IRMAA\n\nSign in to fill out and submit Medicare Income-Related Monthly Adjustment Amount-Life Changing Event (SSA-44). \n\nSign In\nCreate account\nAmended income tax returns\n\nCall +1 800-772-1213 and tell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) if you had an amended income tax return.\n\nOther ways to complete this task\n\nFax or mail your request\n\nFill out the Medicare Income-Related Monthly Adjustment Amount – Life-Changing Event (SSA-44) (PDF) form. Fax or mail your completed form and evidence to a Social Security office.\n\nFind your local office\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nFor support completing this task\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) due to a life-changing event.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
            "maintext_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
          "snapshot_path": "/service/sources/SSA-irmaa-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "lower-irmaa/irmaa-fax-mail-life-change",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "lower-irmaa/irmaa-outside-US-appointment": {
        "id": "irmaa-outside-US-appointment",
        "title": "Request an appointment from outside the United States",
        "when": "The person lives outside the United States and wants an appointment for this task.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The page directs contacting a Federal Benefits Unit to request an appointment. This is an appointment-routing instruction, not a change in claim jurisdiction or an eligibility finding.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_irmaa",
        "section": "Make an appointment outside U.S.",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source includes U.S. territories/commonwealths in this outside-U.S. appointment instruction.",
          "An appointment is being requested for the IRMAA task."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source includes U.S. territories/commonwealths in this outside-U.S. appointment instruction.",
          "An appointment is being requested for the IRMAA task."
        ],
        "source_context_refs": [
          "SSA-irmaa-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-irmaa",
            "url": "https://www.ssa.gov/medicare/lower-irmaa",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1871,
            "exact_text": "Breadcrumb\nHome  Medicare  Request to lower IRMAA\nPlan for Medicare\nSign up for Medicare\nRequest to lower IRMAA\nApply for Part D Extra Help\nManage Medicare benefits\nRequest to lower an Income-Related Monthly Adjustment Amount (IRMAA)\n\nIf you've had a life-changing event that reduced your household income, you can ask to lower the additional amount you'll pay for Medicare Part B and Part D.\n\nLife-changing events include marriage, divorce, the death of a spouse, loss of income, and an employer settlement payment.\n\nUpload your request to lower an IRMAA\n\nSign in to fill out and submit Medicare Income-Related Monthly Adjustment Amount-Life Changing Event (SSA-44). \n\nSign In\nCreate account\nAmended income tax returns\n\nCall +1 800-772-1213 and tell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) if you had an amended income tax return.\n\nOther ways to complete this task\n\nFax or mail your request\n\nFill out the Medicare Income-Related Monthly Adjustment Amount – Life-Changing Event (SSA-44) (PDF) form. Fax or mail your completed form and evidence to a Social Security office.\n\nFind your local office\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nFor support completing this task\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) due to a life-changing event.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
            "maintext_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
          "snapshot_path": "/service/sources/SSA-irmaa-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "lower-irmaa/irmaa-outside-US-appointment",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "update-contact/contact-email-account-path": {
        "id": "contact-email-account-path",
        "title": "Update the account email",
        "when": "The person wants to update email through the account.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Sign in to the account and choose My Profile. Choose Security, then Update Email. The page says email can be updated at any time; actual authentication and completion are not established.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_contact",
        "section": "Email updates",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is an email update, not a direct-deposit or universal mailing-address procedure."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is an email update, not a direct-deposit or universal mailing-address procedure."
        ],
        "source_context_refs": [
          "SSA-contact-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-contact",
            "url": "https://www.ssa.gov/life-events/update-contact-information",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1593,
            "exact_text": "Breadcrumb\nHome  Life events  Contact information change\nLife events\nApproaching age 65 (Medicare eligibility)\nApproaching Retirement\nBecoming an adult\nDisability, injury, or illness\nStaying at a medical facility\nNeed help managing money\nImmigration\nIncarceration\nName change\nContact information change\nCommunication preferences\nUpdate contact information\n\nUpdate your mailing address, phone number, or email so we can communicate with you about your benefits.\n\nYou can update your email address any time. You can only update your mailing address and phone number if you're already getting benefits.\n\nSign in to your account\n\nKeep your phone number, email, and mailing address up to date in your account. Depending on your benefit type you may need to call us to complete this task.\n\nFor email updates, sign in to your account and select \"My Profile\" at the top of the page. Next, choose \"Security,\" then \"Update Email.\"\n\nSign in\nCreate account\nOther ways to complete this task\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to update your contact information.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
            "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
          "snapshot_path": "/service/sources/SSA-contact-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "update-contact/contact-email-account-path",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "update-contact/contact-not-already-benefits": {
        "id": "contact-not-already-benefits",
        "title": "The person is not already receiving benefits",
        "when": "The page’s mailing-address/phone update feature is being considered before benefits are being received.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Use the page’s SSA contact option to explain the contact-information request. No telephone-only completion, new account eligibility or pending-claim routing rule is established.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_contact",
        "section": "Update contact information",
        "additional_sources": [],
        "owner": "context / claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The person is not already receiving benefits; no application or entitlement status is inferred from this example."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The person is not already receiving benefits; no application or entitlement status is inferred from this example."
        ],
        "source_context_refs": [
          "SSA-contact-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-contact",
            "url": "https://www.ssa.gov/life-events/update-contact-information",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1593,
            "exact_text": "Breadcrumb\nHome  Life events  Contact information change\nLife events\nApproaching age 65 (Medicare eligibility)\nApproaching Retirement\nBecoming an adult\nDisability, injury, or illness\nStaying at a medical facility\nNeed help managing money\nImmigration\nIncarceration\nName change\nContact information change\nCommunication preferences\nUpdate contact information\n\nUpdate your mailing address, phone number, or email so we can communicate with you about your benefits.\n\nYou can update your email address any time. You can only update your mailing address and phone number if you're already getting benefits.\n\nSign in to your account\n\nKeep your phone number, email, and mailing address up to date in your account. Depending on your benefit type you may need to call us to complete this task.\n\nFor email updates, sign in to your account and select \"My Profile\" at the top of the page. Next, choose \"Security,\" then \"Update Email.\"\n\nSign in\nCreate account\nOther ways to complete this task\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to update your contact information.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
            "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_boundary_question",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_boundary_question",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
          "snapshot_path": "/service/sources/SSA-contact-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "update-contact/contact-not-already-benefits",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "update-contact/contact-paper-check-unable-online": {
        "id": "contact-paper-check-unable-online",
        "title": "A paper-check mailing-address change needs the FAQ’s identity route",
        "when": "The source FAQ’s unable-online/one-time-code context applies to a paper-check recipient seeking an address change.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Under the retained paper-check and surrounding FAQ conditions, the page says to visit a Social Security office before changing the mailing address. No proof of identity, appointment arrangement or completed address change is established.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_identityproof",
        "section": "Does everyone need to prove identity? complete expanded answer",
        "additional_sources": [],
        "owner": "context / claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The person receives payment by paper check and wants to change the mailing address.",
          "The surrounding FAQ condition of inability to use online services or generate the one-time code is retained; this is not a universal rule for every contact-information update."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The person receives payment by paper check and wants to change the mailing address.",
          "The surrounding FAQ condition of inability to use online services or generate the one-time code is retained; this is not a universal rule for every contact-information update."
        ],
        "source_context_refs": [
          "SSA-identityproof-whole",
          "SSA-contact-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-identityproof",
            "url": "https://www.ssa.gov/news/en/identity-proofing.html?tl=0%2C1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6260,
            "exact_text": "What to Know about Proving Your Identity (Subscribe | En español)\n\nWebpage updated April 28, 2025\n\nWhy do I need to prove my identity?\n\nSocial Security is strengthening the process to prove identity related to direct deposit information. This applies to individuals who need to change their direct deposit information on our records. The easiest and most secure way is online with a personal my Social Security account. If someone cannot access their my Social Security account, then they will need to come into a Social Security office to prove their identity.\n\nPeople will continue to receive their benefits on schedule to the bank account information in Social Security’s records without needing to prove identity.\n\nHow do the new identity verification procedures protect me?\n\nBad actors use other people’s personal information, often found on the dark web, to steal people’s money and identity. That information allows bad actors to get past antiquated knowledge-based questions. Social Security’s identity verification procedures prevent bad actors from stealing current and future benefits.\n\nNew – How can I change my direct deposit over the phone?\n\nBeginning April 28, 2025, you can change your direct deposit by calling 1-800-772-1213. Before you call, go to ssa.gov/PIN to get a one-time code that you will give to the Social Security representative. To generate the code, you will need to sign in to or create a personal my Social Security account. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nDoes everyone need to prove their identity with Social Security?\n\nIf you are not applying for benefits or changing direct deposit information for current benefits, there is no need to contact Social Security to prove identity.\n\nPeople will continue to receive their benefits on schedule to the bank account information in Social Security’s records without needing to prove identity.\n\nIf changing direct deposit information for existing benefits, the most convenient and secure way to prove identity is with Social Security’s online services using a personal my Social Security account.\n\nIf unable to use Social Security’s online services, or generate a one-time code on ssa.gov/PIN a person\n\nchanging direct deposit information for any type of benefit must prove their identity in a Social Security office.\nreceiving payment by paper check must visit a Social Security office before changing their mailing address.\nDo I need to visit a Social Security office to prove my identity?\n\nIt depends. You don’t need to visit Social Security:\n\nto prove your identity if you use a personal my Social Security account to change direct deposit information.\nif you are applying for benefits online or over the phone (unless your claim is flagged as a possible fraud risk).\nto continue receiving benefits to the bank account information in Social Security’s records.\nif you do not receive benefits.\n\nYou do need to visit a Social Security office if you need to change direct deposit information and cannot do it online or cannot generate a one-time code at ssa.gov/PIN to complete the direct deposit transaction over the phone. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nDo I need to contact Social Security if I do not receive benefits?\n\nNo. You don’t need to contact Social Security if you don’t receive benefits.\n\nDo I need to contact Social Security to prove my identity to continue my monthly benefits?\n\nNo. You do not need to contact Social Security to continue your monthly benefits at your current bank. If you need to change your direct deposit information in the future, you can change that information online with a personal my Social Security account or automatic enrollment service through your bank, or by generating one-time code to complete the transaction over the phone at ssa.gov/PIN. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nCan I still apply for benefits on the telephone?\n\nYes.\n\nIf I prove my identity online or in an office, do I need to prove my identity if I visit an office again?\n\nOnce you have created a personal my Social Security account, you don’t need to prove your identity online again to continue using Social Security’s convenient online services.\n\nIf you need to prove your identity in a local office for a reason explained on this webpage, and if you need to visit a local office again for assistance when proof of identity is required, you will need to prove your identity at that next visit.\n\nAre there exceptions to proving my identity in person?\n\nYes. You can create a personal my Social Security account to prove your identity one time and continue to use Social Security’s online services without proving your identity in person. Beginning April 28, 2025, you can change your direct deposit by calling 1-800-772-1213. Before you call, go to ssa.gov/PIN to get a one-time code that you will give to the Social Security representative. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nHow do I find a Social Security office if I cannot do my business online?\n\nOur office locator service is available online at Social Security Office Locator. Customers who cannot use our website may call 1-800-772-1213 and we will assist you with finding a local office. Customers do not need an appointment if they are only changing their direct deposit information.\n\nWill Social Security send me a text message about proving my identity?\n\nNo. Social Security will never contact you by a text message to provide or confirm information about your identity. Ignore a text message like this if you receive one.",
            "span_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688",
            "maintext_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688"
          },
          {
            "source_code": "SSA-contact",
            "url": "https://www.ssa.gov/life-events/update-contact-information",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1593,
            "exact_text": "Breadcrumb\nHome  Life events  Contact information change\nLife events\nApproaching age 65 (Medicare eligibility)\nApproaching Retirement\nBecoming an adult\nDisability, injury, or illness\nStaying at a medical facility\nNeed help managing money\nImmigration\nIncarceration\nName change\nContact information change\nCommunication preferences\nUpdate contact information\n\nUpdate your mailing address, phone number, or email so we can communicate with you about your benefits.\n\nYou can update your email address any time. You can only update your mailing address and phone number if you're already getting benefits.\n\nSign in to your account\n\nKeep your phone number, email, and mailing address up to date in your account. Depending on your benefit type you may need to call us to complete this task.\n\nFor email updates, sign in to your account and select \"My Profile\" at the top of the page. Next, choose \"Security,\" then \"Update Email.\"\n\nSign in\nCreate account\nOther ways to complete this task\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to update your contact information.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
            "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688",
          "snapshot_path": "/service/sources/SSA-identityproof-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "update-contact/contact-paper-check-unable-online",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "update-contact/contact-outside-US-appointment": {
        "id": "contact-outside-US-appointment",
        "title": "Request a contact-update appointment outside the United States",
        "when": "The source’s outside-U.S. appointment instruction applies.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Use the source’s Federal Benefits Unit route to request an appointment. This does not assign a new benefit-processing jurisdiction or guarantee an account update.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_contact",
        "section": "Make an appointment outside U.S.",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The person lives outside the United States, including source-described territories/commonwealths, and seeks an appointment for this contact update."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The person lives outside the United States, including source-described territories/commonwealths, and seeks an appointment for this contact update."
        ],
        "source_context_refs": [
          "SSA-contact-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-contact",
            "url": "https://www.ssa.gov/life-events/update-contact-information",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1593,
            "exact_text": "Breadcrumb\nHome  Life events  Contact information change\nLife events\nApproaching age 65 (Medicare eligibility)\nApproaching Retirement\nBecoming an adult\nDisability, injury, or illness\nStaying at a medical facility\nNeed help managing money\nImmigration\nIncarceration\nName change\nContact information change\nCommunication preferences\nUpdate contact information\n\nUpdate your mailing address, phone number, or email so we can communicate with you about your benefits.\n\nYou can update your email address any time. You can only update your mailing address and phone number if you're already getting benefits.\n\nSign in to your account\n\nKeep your phone number, email, and mailing address up to date in your account. Depending on your benefit type you may need to call us to complete this task.\n\nFor email updates, sign in to your account and select \"My Profile\" at the top of the page. Next, choose \"Security,\" then \"Update Email.\"\n\nSign in\nCreate account\nOther ways to complete this task\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to update your contact information.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
            "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
          "snapshot_path": "/service/sources/SSA-contact-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "update-contact/contact-outside-US-appointment",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "get-benefit-letter/benefit-letter-automated-phone": {
        "id": "benefit-letter-automated-phone",
        "title": "Use automated phone assistance for the letter",
        "when": "The person chooses the published automated-phone alternative.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Call the official SSA number shown on the page; the source describes automated assistance in English and Spanish, 24 hours a day, seven days a week. When the service asks how it can help, say “proof of income.” The page does not specify the fulfilment method or delivery duration for this option.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_letter",
        "section": "Other ways; automated phone assistance",
        "additional_sources": [],
        "owner": "claimant",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is a request for a benefit-verification letter, not a tax form or an eligibility determination."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is a request for a benefit-verification letter, not a tax form or an eligibility determination."
        ],
        "source_context_refs": [
          "SSA-letter-whole"
        ],
        "source_provenance": [
          {
            "source_code": "SSA-letter",
            "url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 1301,
            "exact_text": "Breadcrumb\nHome  Manage benefits  Get benefit letter\nPrepare\nApply\nManage benefits\nGet benefit letter\nGet tax form (1099/1042S)\nSubmit forms and upload documents\nUpdate direct deposit\nResolve an overpayment\nRequest to withhold taxes\nView benefit payment schedule\nCommunicate changes to personal situation\nIdentify someone to manage benefits for you\nCancel your benefits application\nPause your Retirement benefit\nMake or change appointment\nGet benefit verification letter\n\nGet a benefit letter to show that you receive benefits, have submitted an application, or don't receive benefits.\n\nThis documentation is often needed for loan applications, housing assistance, and other processes that require verification of your income. It may be referred to as a \"proof of income letter\" or \"benefit letter\" and is personalized based on the status of your Social Security benefits, Supplemental Security Income, and Medicare coverage.\n\nSign in to your account\n\nDownload a PDF to get the letter right away.\n\nSign in\nCreate account\nOther ways to complete this task\nUse our automated phone assistance\nAvailable 24 hours a day, 7 days a week in English and Spanish.\n\nCall +1 800-772-1213\n\nWhen you hear \"How can I help you today?\" say \"proof of income.\"\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
            "span_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655",
            "maintext_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "service_channel_alternative",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "service_channel_alternative",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655",
          "snapshot_path": "/service/sources/SSA-letter-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "get-benefit-letter/benefit-letter-automated-phone",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion": {
        "id": "ssi-EXR-provisional-benefits-fee-exclusion",
        "title": "Representative-fee processing involves provisional benefits",
        "when": "Representative-fee treatment of provisional benefits arises while applying for Title XVI EXR or in a related appeal; a favorable medical decision is not a prerequisite for this fee-specific route.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source excludes provisional benefits when authorizing a fee under the fee-agreement process. Do not use provisional benefits to calculate the past-due-benefit amount for withholding/direct payment under the fee-agreement or fee-petition process. Also do not use provisional benefits to pay a court-authorized fee. Detailed fee rules remain linked; no amount is calculated.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_awardssi",
        "section": "C",
        "additional_sources": [],
        "owner": "SSA fee-processing component",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is Title XVI EXR representative-fee scope while applying for EXR or during a related appeal, not an actual fee authorization, withholding calculation or appointment finding.",
          "Provisional benefits must be distinguished from the relevant past-due-benefit fee basis."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is Title XVI EXR representative-fee scope while applying for EXR or during a related appeal, not an actual fee authorization, withholding calculation or appointment finding.",
          "Provisional benefits must be distinguished from the relevant past-due-benefit fee basis."
        ],
        "source_context_refs": [
          "DI13050.061-whole"
        ],
        "source_provenance": [
          {
            "source_code": "DI13050.061",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 2032,
            "exact_text": "Effective Dates: 12/04/2012 - Present\nPrevious | Next\n\nTN 22 (09-24)\n\nDI 13050.061 Field Office (FO) Procedures for Title XVI Expedited Reinstatement (EXR) Awards\nA. \nOverview for a favorable medical decision\n\nThe Disability Determination Services (DDS) makes a favorable determination regarding entitlement, documents the determination on form SSA-832 and returns the case allowance to the FO via the Electronic Disability Collect System (EDCS) Action Items list. The FO technician must then process the award.\n\nB. \nTitle XVI procedures\n\nWhen DDS issues an EXR allowance, take the following steps:\n\n1. \n\nReview the SSA-832:\n\n•\n\nItem 9A is selected;\n\n•\n\nItem 10 shows “other ”.\n\n•\n\nItem 20 shows WRM code 31; and\n\n•\n\nRemarks show “Expedited Reinstatement MOE MM/DD/YY”.\n\n2. \n\nStop the provisional payments and terminate the current record. Follow the instructions in SM 01701.080D.\n\n3. \n\nStart-date the EXR record per SM 01701.080D.\n\n4. \n\nSend an expedited reinstatement award notice.\n\n5. \n\nClear the EXR event in the DCF as a continuance per DI 13010.620.\n\nC. \nPolicy for payment of representative’s fee\n\nClaimants have the right to representation while applying for EXR and any related appeals. We do not include provisional benefits in authorizing a fee under the fee agreement process. Do not use provisional benefits to calculate the amount of past due benefits to withhold for direct payment of a representative's fee under the fee agreement or fee petition process, or to pay a fee authorized by a court. For more information on representative's fees, see GN 03910.000, GN 03920.000, GN 03930.000 and GN 03940.000..\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0413050061\n\t\nDI 13050.061 - Field Office (FO) Procedures for Title XVI Expedited Reinstatement (EXR) Awards - 12/04/2012\nBatch run: 10/29/2026\nRev:12/04/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15",
            "maintext_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15",
          "snapshot_path": "/service/sources/DI13050.061-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This fee-specific route also applies while applying for Title XVI EXR or during a related appeal. It does not require the usual award story’s favorable medical decision."
        }
      },
      "cdb-marriage-benefit-review/cdb-marriage-spouse-SSI-only": {
        "id": "cdb-marriage-spouse-SSI-only",
        "title": "The spouse receives SSI only",
        "when": "The spouse’s only benefit is SSI under the source’s marriage-exception question.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source says SSI-only is not a Social Security beneficiary for this marriage exception.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_childtermination",
        "section": "A.3.a",
        "additional_sources": [],
        "owner": "SSA staff / context",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "Actual spouse-benefit facts must be established.",
          "The spouse receives SSI only, rather than a qualifying Social Security benefit for A3a."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "Actual spouse-benefit facts must be established.",
          "The spouse receives SSI only, rather than a qualifying Social Security benefit for A3a."
        ],
        "source_context_refs": [
          "RS00203.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RS00203.035",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6833,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 09/06/2023 - Present\nPrevious | Next\n\nTN 47 (04-26)\n\nRS 00203.035 Child's Benefits Termination of Entitlement\nA. \nGeneral information on termination\n\nA child's entitlement ends with the month before the month in which any of the following occurs:\n\n1. \nDeath\n\nThe child dies.\n\n2. \nAttainment of age 18\n\nThe child attains age 18 and is not disabled or a full-time student. A child born on the first day of the month attains age 18 in the previous month based on Agency policy concerning attainment of age.\n\nNOTE: If the child is under a disability, see RS 00203.035B.1. If the child is a full-time student, see RS 00203.035B.2.\n\n3. \nMarriage\n\nThe child marries, with these exceptions:\n\na. \n\nEntitlement does not end if the child is a child disability beneficiary ( CDB ) and the marriage is to a Social Security beneficiary other than:\n\n•\n\na child beneficiary under age 18, or\n\n•\n\na child beneficiary age 18 or 19 entitled because he or she is a full-time student.\n\nAn individual receiving Supplemental Security Income benefits only is not included in the definition of a “Social Security beneficiary.”\n\nb. \n\nAlthough a putative marriage in Louisiana terminates a child's entitlement, a putative marriage in any other state that recognizes such marriages does not. Under the laws of some states, a party to a void marriage may acquire inheritance rights as a spouse. This relationship is a putative marriage. The essential basis of a putative marriage is a good faith belief in the existence of a valid marriage at its inception and a continuous good faith belief (in a life case) or good faith until the worker dies (in a death case). (For information on putative marriages, see GN 00305.085.)\n\nNOTE: For instructions about same-sex marriage, see GN 00210.000.\n\nNOTE: Benefits to a CDB no longer terminate because the benefits of their spouse who is a CDB or disability beneficiary terminate. A CDB whose benefits terminate in or after July 1969 because their spouse's CDB benefits terminated for a reason other than death may have their benefits reinstated.\n\n4. \nNH no longer entitled to disability insurance benefits\n\nEntitlement ends the first month the NH is no longer entitled to a disability insurance benefit, unless the entitlement ended because of their death or entitlement to retirement insurance benefits.\n\nIf the NH is at full retirement age (FRA) when a subsequent disability determination shows that their disability ceased prior to the Disability Insurance Benefits (DIB) to Retirement Insurance Benefits (RIB) conversion, see \"NOTE\" in GN 00201.005B.1.a.\n\n \n\nB. \nSpecial rules\n\nIn addition to the situations listed in child’s benefits termination of entitlement, RS 00203.035A, the following terminating events apply:\n\n1. \nChild disability beneficiary (CDB)\n\nThe entitlement of a CDB ends with the second month following the month he or she ceases to be under a disability, unless in such month he or she is under age 19 and a full-time student.\n\nNOTE: The trial work provision discussed in DI 13010.035 applies to a CDB.\n\n2. \nStudent\n\nThe entitlement of a full-time student age 18-19 ends whenever the following occurs first, unless at such time he or she is entitled to benefits as a CDB:\n\na. \n\nThe month before the month he or she attains age 19, or deemed to have attained age 19.\n\nb. \n\nThe last month he or she is a full-time student. (For information on when student benefits terminate, see RS 00205.325B.)\n\nFor more information on the point at which a particular age is attained, see GN 00302.400.\n\n3. \nLegally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \nStep-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \nPolicy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203035\n\t\nRS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023\nBatch run: 09/10/2026\nRev:09/06/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
            "maintext_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
          "snapshot_path": "/service/sources/RS00203.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "cdb-marriage-benefit-review/cdb-marriage-spouse-SSI-only",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "cdb-marriage-benefit-review/cdb-marriage-spouse-excluded-child-benefit": {
        "id": "cdb-marriage-spouse-excluded-child-benefit",
        "title": "The spouse receives an excluded child-benefit type",
        "when": "The spouse is in one of the two child-benefit categories excluded from A3a.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source’s CDB marriage exception excludes these two spouse-benefit categories. Receiving a payment alone does not establish a qualifying spouse category.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_childtermination",
        "section": "A.3.a",
        "additional_sources": [],
        "owner": "SSA staff / context",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The spouse is a child beneficiary under18 OR an age18/19 child beneficiary entitled as a full-time student.",
          "The claimant’s CDB and actual marriage circumstances require separate establishment."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The spouse is a child beneficiary under18 OR an age18/19 child beneficiary entitled as a full-time student.",
          "The claimant’s CDB and actual marriage circumstances require separate establishment."
        ],
        "source_context_refs": [
          "RS00203.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RS00203.035",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6833,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 09/06/2023 - Present\nPrevious | Next\n\nTN 47 (04-26)\n\nRS 00203.035 Child's Benefits Termination of Entitlement\nA. \nGeneral information on termination\n\nA child's entitlement ends with the month before the month in which any of the following occurs:\n\n1. \nDeath\n\nThe child dies.\n\n2. \nAttainment of age 18\n\nThe child attains age 18 and is not disabled or a full-time student. A child born on the first day of the month attains age 18 in the previous month based on Agency policy concerning attainment of age.\n\nNOTE: If the child is under a disability, see RS 00203.035B.1. If the child is a full-time student, see RS 00203.035B.2.\n\n3. \nMarriage\n\nThe child marries, with these exceptions:\n\na. \n\nEntitlement does not end if the child is a child disability beneficiary ( CDB ) and the marriage is to a Social Security beneficiary other than:\n\n•\n\na child beneficiary under age 18, or\n\n•\n\na child beneficiary age 18 or 19 entitled because he or she is a full-time student.\n\nAn individual receiving Supplemental Security Income benefits only is not included in the definition of a “Social Security beneficiary.”\n\nb. \n\nAlthough a putative marriage in Louisiana terminates a child's entitlement, a putative marriage in any other state that recognizes such marriages does not. Under the laws of some states, a party to a void marriage may acquire inheritance rights as a spouse. This relationship is a putative marriage. The essential basis of a putative marriage is a good faith belief in the existence of a valid marriage at its inception and a continuous good faith belief (in a life case) or good faith until the worker dies (in a death case). (For information on putative marriages, see GN 00305.085.)\n\nNOTE: For instructions about same-sex marriage, see GN 00210.000.\n\nNOTE: Benefits to a CDB no longer terminate because the benefits of their spouse who is a CDB or disability beneficiary terminate. A CDB whose benefits terminate in or after July 1969 because their spouse's CDB benefits terminated for a reason other than death may have their benefits reinstated.\n\n4. \nNH no longer entitled to disability insurance benefits\n\nEntitlement ends the first month the NH is no longer entitled to a disability insurance benefit, unless the entitlement ended because of their death or entitlement to retirement insurance benefits.\n\nIf the NH is at full retirement age (FRA) when a subsequent disability determination shows that their disability ceased prior to the Disability Insurance Benefits (DIB) to Retirement Insurance Benefits (RIB) conversion, see \"NOTE\" in GN 00201.005B.1.a.\n\n \n\nB. \nSpecial rules\n\nIn addition to the situations listed in child’s benefits termination of entitlement, RS 00203.035A, the following terminating events apply:\n\n1. \nChild disability beneficiary (CDB)\n\nThe entitlement of a CDB ends with the second month following the month he or she ceases to be under a disability, unless in such month he or she is under age 19 and a full-time student.\n\nNOTE: The trial work provision discussed in DI 13010.035 applies to a CDB.\n\n2. \nStudent\n\nThe entitlement of a full-time student age 18-19 ends whenever the following occurs first, unless at such time he or she is entitled to benefits as a CDB:\n\na. \n\nThe month before the month he or she attains age 19, or deemed to have attained age 19.\n\nb. \n\nThe last month he or she is a full-time student. (For information on when student benefits terminate, see RS 00205.325B.)\n\nFor more information on the point at which a particular age is attained, see GN 00302.400.\n\n3. \nLegally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \nStep-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \nPolicy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203035\n\t\nRS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023\nBatch run: 09/10/2026\nRev:09/06/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
            "maintext_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
          "snapshot_path": "/service/sources/RS00203.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "cdb-marriage-benefit-review/cdb-marriage-spouse-excluded-child-benefit",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "cdb-marriage-benefit-review/cdb-spouse-disability-benefit-later-terminates": {
        "id": "cdb-spouse-disability-benefit-later-terminates",
        "title": "The spouse’s CDB or disability benefit later ends",
        "when": "The spouse’s CDB or disability benefit terminates after the marriage.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source says a CDB no longer terminates merely because the spouse’s CDB or disability benefit terminates.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_childtermination",
        "section": "A.3 note",
        "additional_sources": [],
        "owner": "SSA staff / context",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is the source’s spouse-CDB/disability-termination circumstance.",
          "Actual later entitlement facts and other possible terminating events are not established."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is the source’s spouse-CDB/disability-termination circumstance.",
          "Actual later entitlement facts and other possible terminating events are not established."
        ],
        "source_context_refs": [
          "RS00203.035-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RS00203.035",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 6833,
            "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 09/06/2023 - Present\nPrevious | Next\n\nTN 47 (04-26)\n\nRS 00203.035 Child's Benefits Termination of Entitlement\nA. \nGeneral information on termination\n\nA child's entitlement ends with the month before the month in which any of the following occurs:\n\n1. \nDeath\n\nThe child dies.\n\n2. \nAttainment of age 18\n\nThe child attains age 18 and is not disabled or a full-time student. A child born on the first day of the month attains age 18 in the previous month based on Agency policy concerning attainment of age.\n\nNOTE: If the child is under a disability, see RS 00203.035B.1. If the child is a full-time student, see RS 00203.035B.2.\n\n3. \nMarriage\n\nThe child marries, with these exceptions:\n\na. \n\nEntitlement does not end if the child is a child disability beneficiary ( CDB ) and the marriage is to a Social Security beneficiary other than:\n\n•\n\na child beneficiary under age 18, or\n\n•\n\na child beneficiary age 18 or 19 entitled because he or she is a full-time student.\n\nAn individual receiving Supplemental Security Income benefits only is not included in the definition of a “Social Security beneficiary.”\n\nb. \n\nAlthough a putative marriage in Louisiana terminates a child's entitlement, a putative marriage in any other state that recognizes such marriages does not. Under the laws of some states, a party to a void marriage may acquire inheritance rights as a spouse. This relationship is a putative marriage. The essential basis of a putative marriage is a good faith belief in the existence of a valid marriage at its inception and a continuous good faith belief (in a life case) or good faith until the worker dies (in a death case). (For information on putative marriages, see GN 00305.085.)\n\nNOTE: For instructions about same-sex marriage, see GN 00210.000.\n\nNOTE: Benefits to a CDB no longer terminate because the benefits of their spouse who is a CDB or disability beneficiary terminate. A CDB whose benefits terminate in or after July 1969 because their spouse's CDB benefits terminated for a reason other than death may have their benefits reinstated.\n\n4. \nNH no longer entitled to disability insurance benefits\n\nEntitlement ends the first month the NH is no longer entitled to a disability insurance benefit, unless the entitlement ended because of their death or entitlement to retirement insurance benefits.\n\nIf the NH is at full retirement age (FRA) when a subsequent disability determination shows that their disability ceased prior to the Disability Insurance Benefits (DIB) to Retirement Insurance Benefits (RIB) conversion, see \"NOTE\" in GN 00201.005B.1.a.\n\n \n\nB. \nSpecial rules\n\nIn addition to the situations listed in child’s benefits termination of entitlement, RS 00203.035A, the following terminating events apply:\n\n1. \nChild disability beneficiary (CDB)\n\nThe entitlement of a CDB ends with the second month following the month he or she ceases to be under a disability, unless in such month he or she is under age 19 and a full-time student.\n\nNOTE: The trial work provision discussed in DI 13010.035 applies to a CDB.\n\n2. \nStudent\n\nThe entitlement of a full-time student age 18-19 ends whenever the following occurs first, unless at such time he or she is entitled to benefits as a CDB:\n\na. \n\nThe month before the month he or she attains age 19, or deemed to have attained age 19.\n\nb. \n\nThe last month he or she is a full-time student. (For information on when student benefits terminate, see RS 00205.325B.)\n\nFor more information on the point at which a particular age is attained, see GN 00302.400.\n\n3. \nLegally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \nStep-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \nPolicy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203035\n\t\nRS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023\nBatch run: 09/10/2026\nRev:09/06/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
            "maintext_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
          "snapshot_path": "/service/sources/RS00203.035-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "cdb-marriage-benefit-review/cdb-spouse-disability-benefit-later-terminates",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-benefit-agency-evidence-help": {
        "id": "ssn-benefit-agency-evidence-help",
        "title": "An SSN is needed for another benefit",
        "when": "The individual needs an SSN for a benefit and cannot supply required data or evidence.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source directs contacting the agency requiring the SSN to find out what evidence it used to establish eligibility to that benefit.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_ssnassist",
        "section": "A agency-benefit bullet",
        "additional_sources": [],
        "owner": "SSA staff / context",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source’s SSN-evidence assistance scope applies; no waiver of required data or acceptable evidence is established.",
          "An agency requires the SSN for a benefit."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source’s SSN-evidence assistance scope applies; no waiver of required data or acceptable evidence is established.",
          "An agency requires the SSN for a benefit."
        ],
        "source_context_refs": [
          "RM10210.120-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10210.120",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 2741,
            "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
            "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
          "snapshot_path": "/service/sources/RM10210.120-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "ssn-evidence-hard-to-obtain/ssn-benefit-agency-evidence-help",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-parallel-FO-evidence-help": {
        "id": "ssn-parallel-FO-evidence-help",
        "title": "A parallel field office can help pursue a lead",
        "when": "Staff establish that assistance from a parallel FO is appropriate for an evidence lead.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Request assistance from a parallel field office when appropriate. The source does not supply the office-selection mechanism or a completed evidence handoff.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_ssnassist",
        "section": "A parallel-FO bullet",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The required SSN data/evidence cannot be supplied under the source assistance scope.",
          "Parallel-FO assistance is appropriate for pursuing an actual lead; the example does not invent an office or source."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The required SSN data/evidence cannot be supplied under the source assistance scope.",
          "Parallel-FO assistance is appropriate for pursuing an actual lead; the example does not invent an office or source."
        ],
        "source_context_refs": [
          "RM10210.120-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10210.120",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 2741,
            "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
            "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
          "snapshot_path": "/service/sources/RM10210.120-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "ssn-evidence-hard-to-obtain/ssn-parallel-FO-evidence-help",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed": {
        "id": "ssn-evidence-efforts-failed",
        "title": "Evidence efforts have failed",
        "when": "All efforts to produce the required SSN evidence have failed.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "Contact the Regional Office for guidance. This does not waive the required information or evidence or establish what the Regional Office will advise.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_ssnassist",
        "section": "A final bullet and note",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The source assistance scope applies and efforts to produce the required evidence have failed."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The source assistance scope applies and efforts to produce the required evidence have failed."
        ],
        "source_context_refs": [
          "RM10210.120-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10210.120",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 2741,
            "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
            "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
          "snapshot_path": "/service/sources/RM10210.120-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed/ssn-all-leads-data-evidence-unattainable": {
        "id": "ssn-all-leads-data-evidence-unattainable",
        "title": "All leads are exhausted and requirements remain unmet",
        "when": "After all leads are explored, the source’s required data/evidence remain unattainable.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "The source says not to process the SSN application under these conditions. This is not a benefit-entitlement denial or a case outcome established by choosing the example. Provide the written notice required by RM10215.110. Its detailed second-review, notice and processing instructions are not newly read or invented here.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_ssnassist",
        "section": "A final note",
        "additional_sources": [],
        "owner": "SSA staff",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "The parent failed-evidence effort scope applies.",
          "All leads have been explored and required SS-5 data and evidence remain unattainable under the source note."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "The parent failed-evidence effort scope applies.",
          "All leads have been explored and required SS-5 data and evidence remain unattainable under the source note."
        ],
        "source_context_refs": [
          "RM10210.120-whole"
        ],
        "source_provenance": [
          {
            "source_code": "RM10210.120",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 2741,
            "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
            "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
          "snapshot_path": "/service/sources/RM10210.120-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed/ssn-all-leads-data-evidence-unattainable",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "parent_full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed"
      },
      "benefit-upload-signature/uploaded-firstparty-CPAS-application": {
        "id": "uploaded-firstparty-CPAS-application",
        "title": "The uploaded application uses CPAS",
        "when": "The source’s first-party eligible CPAS benefit application is submitted through Upload Documents.",
        "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
        "ssa": "For CPAS benefit applications SSA-16, SSA-8000 and SSA-8001, establish the proper applicant and check that the signer’s name is in the form’s signature area. The signing date and signing time must each be in the form’s signature area OR on an appended signature certificate page. Linked DI11005.017 eligibility details remain separately unreviewed for this draft; these fields alone are not a complete validity assessment. Review for missing information. The source’s CPAS instruction says a claimant-contact validity call is unnecessary when the application was submitted through Upload Documents; this does not resolve actual contrary evidence. Load MCS or CCE, receipt ATTEST and record CPAS as the actual method. Automatic ATTEST text alone does not mean verbal attestation occurred. Add a CPAS issue and receipt it with the date the CPAS document was received; do not silently substitute the source C4 uploaded-submission date instruction. Provide the application summary, reporting responsibilities and claim receipt; no delivery method is added beyond this C5 instruction. Adjudicate only after all required proofs and development are complete. This example does not establish those facts or an award. After the required actions, upload the application copy and appended signature certificate if included to Evidence Portal OR eView. A prior Upload Documents submission does not prove this later storage occurred.",
        "route": "Selected published condition or service option; no automatic transition",
        "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
        "source": "r22_missing_signaturemethods",
        "section": "B; C.4; C.5",
        "additional_sources": [],
        "owner": "SSA technician",
        "systems": [],
        "entity_ids": [],
        "conditions": [
          "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
          "This pilot excludes the separately linked third-party iClaim procedure.",
          "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
        ],
        "condition_logic": "all",
        "source_case_conditions": [
          "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
          "This pilot excludes the separately linked third-party iClaim procedure.",
          "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
        ],
        "source_context_refs": [
          "GN00201.015-whole"
        ],
        "source_provenance": [
          {
            "source_code": "GN00201.015",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0200201015",
            "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
            "start": 0,
            "end": 17432,
            "exact_text": "Effective Dates: 07/22/2026 - Present\nPrevious | Next\n\nTN 46 (07-26)\n\nGN 00201.015 Signature Methods for Benefit Applications\nA. \nBackground\n\nIn 2004, SSA adopted alternative signature methods to the traditional pen-and-ink signature (also known as wet signature) for benefit applications (e.g., SSA-1, SSA-16, SSA-8000) and related benefit application forms to simplify work processes.\n\nB. \nPolicy\n\nSSA accepts the following signature methods for benefit applications:\n\n•\n\nWet signature,\n\n•\n\nAttestation,\n\n•\n\nElectronic signature via Click-and-sign,\n\n•\n\nElectronic signature using Upload Documents, and\n\n•\n\nCommercial Product Alternative Signature (CPAS)\n\nOnly certain individuals can sign benefit applications (e.g., SSA-1, SSA-16, SSA-8000. See Proper Applicant GN 00204.003.\n\nFor non-benefit application forms, follow the applicable guidelines for each specific form to ensure signature compliance.\n\nFor example, refer to the specific signature policy related to Form SSA-827 (Authorization to Disclose Information to the Social Security Administration), DI 11005.056.\n\nNOTE: For SSI redetermination (RZ) signature methods, refer to SI 02305.003.\n\nC. \nSignature methods\n1. \n\nWet signature: A wet signature is a handwritten name or mark made with pen-and-ink on a physical document.\n\na. \n\nWet signature policies and procedures apply when:\n\n•\n\nProper applicant or claimant signs with pen-and-ink.\n\nIMPORTANT: For teleclaims and for proper applicants or claimants who prefer to sign with pen-and-ink, mail the application for signature using the Title II cover notice in GN 00204.014, which includes protective filing closeout language. Always ensure that the cover notice reflects the correct closeout date, based on the earlier of either the appointment date or the application date.\n\n•\n\nWe receive a paper application, signed by a proper applicant, that was not generated from Modernized Claims System (MCS) or Consolidated Claims Experience (CCE). For example, the proper applicant may have printed, completed, and signed an SSA-1 retirement application from SSAs list of forms available on the website.\n\nb. \n\nWet signature procedure and documentation\n\nWhen a paper application or application printout from telephone claims is received and signed with a wet signature (i.e., paper benefit applications mailed or dropped into Dropbox at a field office), the SSA technician follow instructions:\n\nPaper applications\n\n•\n\nReview the signed paper application to ensure that a signature is present in the designated box. Then, contact the claimant to verify the validity of the application by confirming that the claimant is alive, in accordance with GN 00204.001C1d, Valid Application.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue, and add a remark of wet signature to indicate that the application was signed with a wet (pen-and-ink) signature.\n\nApplication printout from telephone claims\n\n•\n\nReview the signed application printout to ensure that a signature is present in the designated area.\n\n•\n\nReceipt in the ATTEST issue and add a remark of \"wet signature\" to indicate that the application was signed with a wet (pen-and-ink) signature.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\nFor a paper application or an application printout from telephone claims, technicians take these actions:\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n•\n\nAdjudicate the application if all required proofs have been received and all determinations have been completed. If additional evidence is needed, follow the procedures in GN 00301.150 and SI 00601.100 for obtaining Title II and Title XVI evidence respectively. Also, see GN 00301.286 for recording evidence electronically and retaining evidentiary documents, when required.\n\n•\n\nReturn the signed paper application using the witnessed signature cover notice in Document Processing Systems (DPS), which informs the proper applicant or claimant that the paper application will not be retained by SSA.\n\n2. \n\nAttestation\n\na. \n\nAttestation is the action taken by an SSA employee of confirming and annotating the claimant or proper applicants:\n\n•\n\nIntent to file or complete a claims-related form,\n\n•\n\nAffirmation under penalty of perjury that the information provided is correct, and\n\n•\n\nAgreement to sign the application, amendment, or SSA forms that are completed with the claim/amendment by attestation.\n\nb. \n\nProcedure during the interview\n\n•\n\nVerify the identity of the individual according to relevant procedures for in-person or telephone interviewing, refer to GN 00203.020.\n\n•\n\nInform the individual that SSA has an alternative method to collect a signature in lieu of a wet signature on the application for benefits or claim related forms approved for attestation.\n\n•\n\nAt the start of the interview, read the following scripted language:\n\nDuring this interview, we will ask you questions that will be used to process your/or name of claimant's (application/amendment/ name of form) for (benefits/Medicare). At the end of the interview, we will ask you to confirm the truthfulness of your answers under penalty of perjury and we will record your response. You should be aware that you can be held legally responsible for giving us false information.\n\n•\n\nConfirm the individuals intent to file and sign the application for benefits or claim related forms approved for attestation.\n\n•\n\nComplete the application or claim related forms approved for attestation by obtaining and recording the individuals responses.\n\n•\n\nAt the end of the interview, to obtain the individuals affirmation of intent to file and understanding of the penalty clause, read the following scripted language:\n\n1. Attestation - script for in-person interviews:\n\nHere is a printed copy of the information that will be used to process your/or name of claimant's (application/amendment/name of form). Please review all the information carefully and let us know right away if anything needs to be corrected OR if any of the information changes.\n\nOnce the individual finishes reviewing the document and indicates that the information is accurate, read the following:\n\nDo you understand that the information you gave us and examined will be used to process your/or name of claimants (application/amendment/ name of form) for (benefits/Medicare)? Do you declare under penalty of perjury that this information is true and correct to the best of your knowledge?\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n2. Attestation - script for telephone interviews:\n\nYou will receive a printed copy of the information being used to process your/or name of claimant's (application/amendment/name of form) to retain for your records. Do you understand that you must review all of this information carefully and let us know right away if anything needs to be corrected OR if any of the information changes?\n\nOnce the individual acknowledges that they will receive a copy and understanding that they need to let us know of any changes, read the following:\n\nDo you understand that the information you have provided will be used to process your/or name of claimant's (application /amendment/ name of form)? Do you declare under penalty of perjury that this information is true and correct to the best of your knowledge?\n\nIMPORTANT: The individual must answer YES to all the required statements above (i.e., intent to provide information, truthfulness of it, and agreement to sign it under penalty of perjury) in order to accept the application for benefits or claim related forms approved for attestation, as a signed form. Individuals answering NO to any of the requirements will need to submit the form with a wet signature or another acceptable signature method for the application.\n\n•\n\nPrint the MCS or CCE claim and mail it to the claimant for his or her review and retention, along with the reporting responsibilities and claim receipt. Advise the claimant to review the material and contact SSA within 10 days if he or she needs to make any corrections. Any corrections received post-adjudication will be handled following current procedures. A copy of the claim will be placed in the Online Retrieval System (ORS).\n\n•\n\nAdjudicate the application if all required proofs have been received and all determinations have been completed.\n\nc. \n\nDocumenting attestation\n\nFollow the procedure here to document your attestation:\n\n•\n\nFor claims and amendments in MCS or CCE, the ATTEST issue automatically propagates to the DW01. Document that all requirements for attestation have been met by typing the receipt date for the ATTEST issue.\n\n•\n\nWhen the issue ATTEST is displayed in the Issue field and a date is entered in the receipt field, MCS propagates the interviewers three position office code, a space, up to six letters of the interviewers last name, a comma, and the first initial to the Remarks field. The comma following the last name is a floating comma. If the last name contains fewer than six characters, the comma should immediately follow the last character of the last name (e.g., 216 Cox, N). The ATTEST issue(s) and interviewers name will be retained electronically and deemed equivalent to the signature for the application or amendment.\n\nNOTE: For CCE, the attestation date and interviewer's name will automatically propagate.\n\n3. \n\nClick and sign Internet claim (iClaim)\n\na. \n\nClick and Sign is the means by which the claimant can sign their application electronically using an approved signing process by selecting the check box that indicates they are signing electronically (e.g., I agree with the Electronic Signature Agreement above and then clicking the Submit now (for RIB and Medicare claims), or Accept & Continue (for DIB claims) buttons in the Summary page at the conclusion of the online application). The Electronic Signature Agreement contains his or her affirmation under penalty of perjury that the information provided is true and correct to the best of their knowledge, and the applicant's intent to file and electronically sign and submit application data to SSA.\n\nb. \n\nProcedure and Documentation for Click and Sign\n\n•\n\nIndividuals completing and submitting their own application (i.e., first party applicants) are first routed to mySSA to be authenticated and verify their identity. Therefore, if the iClaim is marked as authenticated, you do not need to contact the claimant to verify identity. However, if the iClaim is flagged as unauthenticated, you must contact the claimant to verify their identity following GN 00203.020.\n\nNOTE:Third party iClaims will continue to follow the procedures outlined in GN 00204.055H2b and EM-18043.\n\n•\n\nThe word Internet propagates to the appropriate application, i.e., DIB, RIB, Aux Spouse on the MCS DW01 to indicate that an Internet claim was signed electronically and filed using click and sign.\n\n•\n\nReceipt in the ATTEST issue with the date the claimant submitted the iClaim, refer to GN 00204.007B4 for additional information.\n\nNOTE: Some additional forms within iClaim are approved for electronic signature by click and sign (e.g., SSA-827). The technician will add an ATTEST issue specific to that form on the development worksheet and receipt date.\n\n•\n\nAfter downloading the online application data from iClaim into MCS, ORS is automatically updated with a copy of the Internet application summary as submitted by the claimant. This secures the integrity of the information the beneficiary provided on the Internet application.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n4. \n\nUpload documents\n\nAfter authenticating through mySSA, individuals can complete and submit a PDF or webform version of certain agency forms and benefit applications using Upload Documents. If the application or form requires a signature, an electronic signature section will be presented on the Review and Submit page. In that section, individuals review the signature statement and apply their electronic signature to the uploaded or completed form by selecting the check box (a required field) and then selecting the Submit button. The form or application is considered signed upon submission. An appended page containing the electronic signature information will accompany the submitted PDF.\n\nNOTE: Although these forms are submitted electronically, technicians must process them as if they were paper applications and enter the information into our SSA systems by following the procedures outlined below.\n\na. \n\nProcedure and documentation for benefit applications\n\n•\n\nReview the signed PDF or webform version for any missing information.\n\nNOTE: The mySSA authentication verifies the claimant's identity and that they are alive meeting requirements in GN 00204.001C1d; unless there is evidence to the contrary.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue and add a remark of \"upload docs\" to indicate that the application was signed using Upload Documents.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\n•\n\nReceipt in the issue with the date the uploaded document was submitted by the individual.\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt by mail.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n5. \n\nCommercial product alternative signature (CPAS)\n\nIndividuals may use a commercial software product (commercial product) to affix their signatures to certain forms and writings in accordance with DI 11005.017, Commercial Product Alternative Signature Process for Certain Forms and Writings.\n\nIf there is a CPAS on the benefit application forms (SSA-16 (including the summary sent to the claimant after a third-party completes an internet claim), SSA-8000, and SSA-8001), SSA technicians must ensure the proper applicant has signed the benefit application forms using a commercial product that:\n\n•\n\nAffixes a signers name in the signature area of the form,\n\n•\n\nAffixes the date the document was signed in the signature area of the form or on an appended signature certificate page, and,\n\n•\n\nAffixes the time the document was signed in the signature area of the form or on an appended signature certificate page.\n\nOnce the technician ensures that the CPAS meets the above requirements for benefit applications SSA-16, SSA-8000, and SSA-8001 the technician must do the following:\n\n•\n\nReview the signed paper application for any missing information and contact the claimant to verify the validity of the application by confirming that the claimant is alive, in accordance with GN 00204.001C1d, Valid Application. If the application was submitted via Upload Documents, there is no need to contact claimant.\n\nNOTE: For third party iClaims with a submitted benefit application using CPAS, follow the procedures outlined in GN 00204.055H2b.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue, and add a remark of \"CPAS\" to indicate that the application was signed using CPAS.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\n•\n\nAdd a CPAS issue on the MCS DW01 screen or the Development Worksheet in CCE and receipt the issue with the date the CPAS document was received.\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n•\n\nOnce the above actions are completed, upload a copy of the application and the appended signature certificate page, if included, to Evidence Portal or eView.\n\nNOTE: For more information on CPAS and other approved forms, refer to DI 11005.017.\n\nD. \nReferences\n•\n\nDI 11005.017 Commercial Product Alternative Signature Process for Certain Forms and Writings\n\n•\n\nDI 11005.056 Signature Requirements for Form SSA-827\n\n•\n\nGN 00204.001 Valid Application\n\n•\n\nGN 00204.003 Proper Applicant\n\n•\n\nGN 00204.007 Application Filing Date\n\n•\n\nGN 00204.014 The SSA-L566-U2 Title II Application Cover Notice\n\n•\n\nGN 00301.150 Evidence of Mail Development\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nSI 00601.100 General Guidance for Information or Evidence\n\n•\n\nSI 02305.003 Alternative Signature Methods: Attestation and Witnessed Signature\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0200201015\n\t\nGN 00201.015 - Signature Methods for Benefit Applications - 07/22/2026\nBatch run: 10/21/2026\nRev:07/22/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb",
            "maintext_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb"
          }
        ],
        "qualifications": [
          "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
          "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
          "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
          "No new native system identity, alias, graph edge or operational acceptance is asserted."
        ],
        "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
        "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
        "source_qualified_branch": {
          "kind": "source_qualified_condition",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "scenario_kind": "source_qualified_condition",
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb",
          "snapshot_path": "/service/sources/GN00201.015-r22-main.txt",
          "report": "/service/r22-missing-exception-selected-claims.json"
        },
        "full_route": "benefit-upload-signature/uploaded-firstparty-CPAS-application",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source conditions, execution and case outcome remain unverified."
          ]
        },
        "entry_exception_scope": {
          "usual_path_premise_not_inherited": true,
          "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
        }
      }
    },
    "flows": {
      "provide-claim-evidence/wsu-third-party-not-yet-valid": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-third-party-not-yet-valid",
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid",
        "entry_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope."
        ],
        "steps": [
          {
            "id": "wsu-third-party-not-yet-valid-step-1",
            "title": "Check which application circumstance applies",
            "kind": "situation",
            "actor": "context",
            "action": "This is the source C third-party circumstance, not an assumption that every absent ATTEST date means an invalid application.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C; C.1",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-third-party-not-yet-valid-step-2",
            "title": "Coordinate the FO and WSU handling",
            "kind": "action",
            "actor": "FO",
            "action": "Use the signed-application-and-proofs or only-proofs instruction according to what the claimant actually provides.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C; C.1",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-signed-application-and-proofs",
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs",
        "entry_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Both the signed application and proofs are provided to the FO."
        ],
        "steps": [
          {
            "id": "wsu-signed-application-and-proofs-step-1",
            "title": "Ask the WSU to transfer jurisdiction",
            "kind": "action",
            "actor": "FO",
            "action": "Call or email the WSU and ask it to transfer claim jurisdiction in MCS.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-signed-application-and-proofs-step-2",
            "title": "Receipt the claim",
            "kind": "action",
            "actor": "FO",
            "action": "Use number 7 Claims Movement on the MCS menu to receipt the claim.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-signed-application-and-proofs-step-3",
            "title": "Record the witnessed signature",
            "kind": "action",
            "actor": "FO",
            "action": "Annotate the ATTEST issue on MCS DW01 to show receipt of the witnessed signed application; this does not replace signature validity requirements.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-signed-application-and-proofs-step-4",
            "title": "Receipt the proofs",
            "kind": "action",
            "actor": "FO",
            "action": "Receipt all proofs on MCS DW01 under the applicable evidence rules.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-signed-application-and-proofs-step-5",
            "title": "Return the signed application",
            "kind": "action",
            "actor": "FO",
            "action": "Return the signed application with the witnessed-signature cover notice referenced in GN00201.015.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-signed-application-and-proofs-step-6",
            "title": "Take the appropriate claim action",
            "kind": "action",
            "actor": "FO",
            "action": "Take the action appropriate to the actual claim, such as adjudication or transfer to DDS. The example does not establish entitlement or a completed transfer.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Both the signed application and proofs are provided to the FO."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.a",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-only-proofs-before-attestation",
        "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation",
        "entry_conditions": [
          "A third-party iClaim is assigned to a WSU.",
          "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
          "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
          "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
        ],
        "steps": [
          {
            "id": "wsu-only-proofs-before-attestation-step-1",
            "title": "Offer the reprinted-application route",
            "kind": "action",
            "actor": "FO",
            "action": "The source directs an offer to reprint the application and complete claim handling; this is not a promise that a benefit decision can be completed without its other requirements.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-2",
            "title": "Request transfer and receipt the claim",
            "kind": "action",
            "actor": "FO",
            "action": "Contact the WSU immediately to request jurisdiction transfer, and receipt the claim using number 7 Claims Movement in MCS.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-3",
            "title": "Obtain the applicable signature",
            "kind": "action",
            "actor": "FO",
            "action": "Obtain a wet signature under the witnessed-signature instruction or complete verbal attestation with the proper applicant under GN00201.015; actual signature validity is not established here.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-4",
            "title": "Record signature receipt",
            "kind": "action",
            "actor": "FO",
            "action": "Annotate the ATTEST issue on MCS DW01 as the source instructs.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-5",
            "title": "Receipt the claim and proofs",
            "kind": "action",
            "actor": "FO",
            "action": "Receipt the claim and all proofs on MCS DW01 under the applicable evidence rules.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-6",
            "title": "Return the signed application",
            "kind": "action",
            "actor": "FO",
            "action": "Return the signed application with the source-referenced witnessed-signature cover notice.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-only-proofs-before-attestation-step-7",
            "title": "Take the appropriate claim action",
            "kind": "action",
            "actor": "FO",
            "action": "Take the action appropriate to the established claim, such as adjudication or transfer to DDS, after all applicable requirements.",
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope.",
              "Only proofs are provided before WSU attestation and application receipt; whether an application was already mailed does not change this source predicate."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-EVID-unavailable-evidence-route": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-EVID-unavailable-evidence-route",
        "full_route": "provide-claim-evidence/wsu-EVID-unavailable-evidence-route",
        "entry_conditions": [
          "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
          "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
        ],
        "steps": [
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-1",
            "title": "Certify a photocopy",
            "kind": "action",
            "actor": "FO",
            "action": "Certify a photocopy of the evidence under the applicable document rules.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-2",
            "title": "Send the certified copy",
            "kind": "action",
            "actor": "FO",
            "action": "Fax or send the certified photocopies into Evidence Portal OR eView; both are not required.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-3",
            "title": "Set the source-defined reminder",
            "kind": "action",
            "actor": "FO",
            "action": "Establish REMARK and the associated remark with a next-day tickle in MCS DW01 or the CCE Development Worksheet.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-4",
            "title": "Record the employee contact details",
            "kind": "action",
            "actor": "FO",
            "action": "Annotate MCS DW03 or the CCE Development Worksheet with the FO code, employee name and direct phone number.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-5",
            "title": "Notify the WSU",
            "kind": "action",
            "actor": "FO",
            "action": "Call or email the WSU immediately about the recorded or faxed proofs.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-EVID-unavailable-evidence-route-step-6",
            "title": "Verify storage and legibility",
            "kind": "action",
            "actor": "FO",
            "action": "Verify that the evidence is properly stored in the Certified Electronic Folder (CEF). For the EP OR eView copy, verify that it is stored and viewed for legible content. The linked retention/return rules remain separate; this is not authority to destroy every original document.",
            "conditions": [
              "The usual source B first-party or already-valid third-party WSU claim conditions apply.",
              "An employee authorized to examine and certify the documents establishes that the evidence cannot be recorded in EVID under the linked recording rules."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B.2.a–b",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-first-party-ATTEST-date-not-entered": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-first-party-ATTEST-date-not-entered",
        "full_route": "provide-claim-evidence/wsu-first-party-ATTEST-date-not-entered",
        "entry_conditions": [
          "This is an actual first-party click-and-sign iClaim.",
          "The ATTEST receipt date has not yet been entered; other identity/authentication and proper-application requirements remain distinct."
        ],
        "steps": [
          {
            "id": "wsu-first-party-ATTEST-date-not-entered-step-1",
            "title": "Keep the first-party scope distinct",
            "kind": "situation",
            "actor": "context",
            "action": "The source treats all first-party iClaims the same for its B coordination instructions regardless of whether an ATTEST-line receipt date has been entered.",
            "conditions": [
              "This is an actual first-party click-and-sign iClaim.",
              "The ATTEST receipt date has not yet been entered; other identity/authentication and proper-application requirements remain distinct."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B note",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-first-party-ATTEST-date-not-entered-step-2",
            "title": "Use the applicable B coordination instruction",
            "kind": "action",
            "actor": "FO",
            "action": "Do not classify this first-party case as the source C not-yet-valid third-party circumstance solely because that receipt date is absent. Actual evidence processing and identity checks retain their own instructions.",
            "conditions": [
              "This is an actual first-party click-and-sign iClaim.",
              "The ATTEST receipt date has not yet been entered; other identity/authentication and proper-application requirements remain distinct."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "B note",
            "source_context_refs": [
              "GN01070.781-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-appointment-cancellation-not-agreed": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-appointment-cancellation-not-agreed",
        "full_route": "provide-claim-evidence/wsu-appointment-cancellation-not-agreed",
        "entry_conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "Contact is successful and the claimant does not agree to cancel the appointment."
        ],
        "steps": [
          {
            "id": "wsu-appointment-cancellation-not-agreed-step-1",
            "title": "Document the discussion",
            "kind": "action",
            "actor": "WSU",
            "action": "Document the discussion in the claim remarks.",
            "conditions": [
              "An assigned WSU iClaim has a pending FO appointment.",
              "Contact is successful and the claimant does not agree to cancel the appointment."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "D",
            "source_context_refs": [
              "GN01070.781-D"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-appointment-cancellation-not-agreed-step-2",
            "title": "Transfer the iClaim to the FO",
            "kind": "action",
            "actor": "WSU",
            "action": "Transfer the iClaim to the FO as the source directs; successful transfer and the appointment outcome are not established by this example.",
            "conditions": [
              "An assigned WSU iClaim has a pending FO appointment.",
              "Contact is successful and the claimant does not agree to cancel the appointment."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "D",
            "source_context_refs": [
              "GN01070.781-D"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-two-unsuccessful-appointment-contacts": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-two-unsuccessful-appointment-contacts",
        "full_route": "provide-claim-evidence/wsu-two-unsuccessful-appointment-contacts",
        "entry_conditions": [
          "An assigned WSU iClaim has a pending FO appointment.",
          "The WSU is unable to reach the claimant after at least two attempts before that scheduled appointment."
        ],
        "steps": [
          {
            "id": "wsu-two-unsuccessful-appointment-contacts-step-1",
            "title": "Document the contact attempts",
            "kind": "action",
            "actor": "WSU",
            "action": "Document the unsuccessful contact attempts in the remarks.",
            "conditions": [
              "An assigned WSU iClaim has a pending FO appointment.",
              "The WSU is unable to reach the claimant after at least two attempts before that scheduled appointment."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "D",
            "source_context_refs": [
              "GN01070.781-D"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-two-unsuccessful-appointment-contacts-step-2",
            "title": "Cancel the pending appointment",
            "kind": "action",
            "actor": "WSU",
            "action": "The source directs cancellation of the pending appointment under these exact conditions; it does not direct denial of the claim.",
            "conditions": [
              "An assigned WSU iClaim has a pending FO appointment.",
              "The WSU is unable to reach the claimant after at least two attempts before that scheduled appointment."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "D",
            "source_context_refs": [
              "GN01070.781-D"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-managers-mutual-transfer": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-managers-mutual-transfer",
        "full_route": "provide-claim-evidence/wsu-managers-mutual-transfer",
        "entry_conditions": [
          "The case is an iClaim between the FO and WSU.",
          "Both managers mutually agree to the source-defined transfer for enhanced service delivery."
        ],
        "steps": [
          {
            "id": "wsu-managers-mutual-transfer-step-1",
            "title": "Discuss the circumstances",
            "kind": "action",
            "actor": "WSU and FO managers",
            "action": "Contact the other office by phone or email to discuss the situation.",
            "conditions": [
              "The case is an iClaim between the FO and WSU.",
              "Both managers mutually agree to the source-defined transfer for enhanced service delivery."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "E",
            "source_context_refs": [
              "GN01070.781-E"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "wsu-managers-mutual-transfer-step-2",
            "title": "Document and facilitate the transfer",
            "kind": "action",
            "actor": "WSU and FO managers",
            "action": "Document and facilitate the mutually agreed transfer. No actual jurisdiction change is established by selecting this scenario.",
            "conditions": [
              "The case is an iClaim between the FO and WSU.",
              "Both managers mutually agree to the source-defined transfer for enhanced service delivery."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "E",
            "source_context_refs": [
              "GN01070.781-E"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "provide-claim-evidence/wsu-signed-application-arrives-after-transfer": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wsu-signed-application-arrives-after-transfer",
        "full_route": "provide-claim-evidence/wsu-signed-application-arrives-after-transfer",
        "entry_conditions": [
          "The source C claim was already transferred from the WSU to the FO for adjudication.",
          "The WSU then receives the signed application; this is a later event, not a claim that the application remains unsigned."
        ],
        "steps": [
          {
            "id": "wsu-signed-application-arrives-after-transfer-step-1",
            "title": "Send it to the FO with jurisdiction",
            "kind": "action",
            "actor": "WSU",
            "action": "Send the signed application to the FO of jurisdiction. The source does not establish actual delivery or the final adjudication.",
            "conditions": [
              "The source C claim was already transferred from the WSU to the FO for adjudication.",
              "The WSU then receives the signed application; this is a later event, not a claim that the application remains unsigned."
            ],
            "source": "r22_WSUcoord_selected",
            "section": "C.1.b note",
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "resolve-partial-award/partial-future-event-diary": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "partial-future-event-diary",
        "full_route": "resolve-partial-award/partial-future-event-diary",
        "entry_conditions": [
          "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
          "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
          "The future-event diary has matured; the source supplies no universal maturity date."
        ],
        "steps": [
          {
            "id": "partial-future-event-diary-step-1",
            "title": "Keep the diary ownership distinct",
            "kind": "situation",
            "actor": "context",
            "action": "The source says the WSU does not retain jurisdiction of future-event diaries. This does not decide benefit entitlement or apply its WEP example as a current-law outcome.",
            "conditions": [
              "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
              "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
              "The future-event diary has matured; the source supplies no universal maturity date."
            ],
            "source": "r22_WSUdiary_selected",
            "section": "A; B future-events; E",
            "source_context_refs": [
              "GN01070.782-A",
              "GN01070.782-B",
              "GN01070.782-E"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "partial-future-event-diary-step-2",
            "title": "Use the PC future-event instruction",
            "kind": "action",
            "actor": "PC",
            "action": "At maturity the PC either acts on the future event OR sends a development request to the servicing FO for its required action.",
            "conditions": [
              "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
              "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
              "The future-event diary has matured; the source supplies no universal maturity date."
            ],
            "source": "r22_WSUdiary_selected",
            "section": "A; B future-events; E",
            "source_context_refs": [
              "GN01070.782-A",
              "GN01070.782-B",
              "GN01070.782-E"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "partial-future-event-diary-step-3",
            "title": "Identify the servicing FO when needed",
            "kind": "action",
            "actor": "PC",
            "action": "Find the servicing FO on MBR or RPOC for the source-defined follow-up. This is not the separate source D instruction to send a WSU-originated outstanding-issue diary back to the WSU.",
            "conditions": [
              "The source-defined WSU workload applies: first-party English-language Retirement or Medicare-only iClaim, domestic residence and proven age/citizenship.",
              "The diary concerns a future event the WSU cannot develop until later, rather than its retained outstanding-issue partial-award development.",
              "The future-event diary has matured; the source supplies no universal maturity date."
            ],
            "source": "r22_WSUdiary_selected",
            "section": "A; B future-events; E",
            "source_context_refs": [
              "GN01070.782-A",
              "GN01070.782-B",
              "GN01070.782-E"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "resolve-partial-award/partial-RPOC-not-available": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "partial-RPOC-not-available",
        "full_route": "resolve-partial-award/partial-RPOC-not-available",
        "entry_conditions": [
          "This is an actual qualifying partial award under the source B entitlement/exclusion rules and the source C1a MCS processing instruction.",
          "RPOC screens are not available for the required diary information/rationale."
        ],
        "steps": [
          {
            "id": "partial-RPOC-not-available-step-1",
            "title": "Prepare a paper report of contact",
            "kind": "action",
            "actor": "Adjudicating component",
            "action": "Prepare a paper RC with the diary information and the exact source remark: “SEE RC IN FILE - PC MUST ADD DIARY REMARKS - RPOC NOT AVAILABLE”.",
            "conditions": [
              "This is an actual qualifying partial award under the source B entitlement/exclusion rules and the source C1a MCS processing instruction.",
              "RPOC screens are not available for the required diary information/rationale."
            ],
            "source": "r22_partial_selected",
            "section": "B; C.1.a",
            "source_context_refs": [
              "GN01010.110-B",
              "GN01010.110-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "partial-RPOC-not-available-step-2",
            "title": "Fax it to the PC paperless unit",
            "kind": "action",
            "actor": "Adjudicating component",
            "action": "Fax the RC into the paperless unit of the PC with jurisdiction; this does not establish receipt or a new physical-system interface.",
            "conditions": [
              "This is an actual qualifying partial award under the source B entitlement/exclusion rules and the source C1a MCS processing instruction.",
              "RPOC screens are not available for the required diary information/rationale."
            ],
            "source": "r22_partial_selected",
            "section": "B; C.1.a",
            "source_context_refs": [
              "GN01010.110-B",
              "GN01010.110-C"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "resolve-partial-award/partial-pending-DIB-separate-other-benefit": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "partial-pending-DIB-separate-other-benefit",
        "full_route": "resolve-partial-award/partial-pending-DIB-separate-other-benefit",
        "entry_conditions": [
          "The DIB disability decision remains an outstanding entitlement factor for that DIB claim.",
          "The claimant files another benefit type, such as RIB; no entitlement or payment for that other claim is established."
        ],
        "steps": [
          {
            "id": "partial-pending-DIB-separate-other-benefit-step-1",
            "title": "Recognize the entitlement-factor boundary",
            "kind": "situation",
            "actor": "context",
            "action": "The source says this is not a partial-award situation for the still-undecided DIB entitlement.",
            "conditions": [
              "The DIB disability decision remains an outstanding entitlement factor for that DIB claim.",
              "The claimant files another benefit type, such as RIB; no entitlement or payment for that other claim is established."
            ],
            "source": "r22_partial_selected",
            "section": "B.1 reminder",
            "source_context_refs": [
              "GN01010.110-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Continue only under the established source conditions; no completed action is assumed."
          },
          {
            "id": "partial-pending-DIB-separate-other-benefit-step-2",
            "title": "Handle the other application separately",
            "kind": "action",
            "actor": "Adjudicating component",
            "action": "Adjudicate the other benefit application separately from the DIB claim under its applicable requirements. This is not a partial-award shortcut or an approval finding.",
            "conditions": [
              "The DIB disability decision remains an outstanding entitlement factor for that DIB claim.",
              "The claimant files another benefit type, such as RIB; no entitlement or payment for that other claim is established."
            ],
            "source": "r22_partial_selected",
            "section": "B.1 reminder",
            "source_context_refs": [
              "GN01010.110-B"
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual handoff, completion and return to the usual path are unverified."
          ]
        }
      },
      "change-name/name-event-document-needs-additional-identity": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "name-event-document-needs-additional-identity",
        "full_route": "change-name/name-event-document-needs-additional-identity",
        "entry_conditions": [
          "The name-change event and new-name evidence must satisfy their separate rules.",
          "The event document cannot itself serve as identity under D: it is a birth certificate; OR the event did not occur within the past two years (four years when under age18); OR the required prior-name/biographical linkage to the latest Numident is not met."
        ],
        "steps": [
          {
            "id": "name-event-document-needs-additional-identity-step-1",
            "title": "Identify the additional identity requirement",
            "kind": "situation",
            "actor": "context",
            "action": "The source requires identity linkage in the prior and new names. It does not permit a birth certificate alone to serve as the name-change identity document.",
            "conditions": [
              "The name-change event and new-name evidence must satisfy their separate rules.",
              "The event document cannot itself serve as identity under D: it is a birth certificate; OR the event did not occur within the past two years (four years when under age18); OR the required prior-name/biographical linkage to the latest Numident is not met."
            ],
            "source": "r22_missing_name",
            "section": "D whole",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "name-event-document-needs-additional-identity-step-2",
            "title": "Use an applicable identity-document alternative",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Request an identity document in the prior name, or a new-name identity document only when linked RM10212.020 conditions are met. Acceptability priority rules and event-specific conditions remain separate.",
            "conditions": [
              "The name-change event and new-name evidence must satisfy their separate rules.",
              "The event document cannot itself serve as identity under D: it is a birth certificate; OR the event did not occur within the past two years (four years when under age18); OR the required prior-name/biographical linkage to the latest Numident is not met."
            ],
            "source": "r22_missing_name",
            "section": "D whole",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "change-name/name-expired-prior-name-identity": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "name-expired-prior-name-identity",
        "full_route": "change-name/name-expired-prior-name-identity",
        "entry_conditions": [
          "Identity must link to the latest Numident and the document must otherwise meet the applicable identity requirements.",
          "The document is in the prior name and is submitted in connection with a name change."
        ],
        "steps": [
          {
            "id": "name-expired-prior-name-identity-step-1",
            "title": "Keep the expiration exception narrow",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source permits the prior-name identity document even if no longer current or expired in this name-change connection. This does not make every expired document acceptable or waive the linked identity rules.",
            "conditions": [
              "Identity must link to the latest Numident and the document must otherwise meet the applicable identity requirements.",
              "The document is in the prior name and is submitted in connection with a name change."
            ],
            "source": "r22_missing_name",
            "section": "D expiration exceptions",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "change-name/name-surname-component-can-link": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "name-surname-component-can-link",
        "full_route": "change-name/name-surname-component-can-link",
        "entry_conditions": [
          "The difference is a missing or additional part of the surname on the event or identity document.",
          "SSA establishes linkage to the latest Numident, for example through a parent’s name or name at birth."
        ],
        "steps": [
          {
            "id": "name-surname-component-can-link-step-1",
            "title": "Assess the actual linkage",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source accepts this document for the surname discrepancy if the surname components can be linked to Numident. Other name-change and identity requirements are not waived.",
            "conditions": [
              "The difference is a missing or additional part of the surname on the event or identity document.",
              "SSA establishes linkage to the latest Numident, for example through a parent’s name or name at birth."
            ],
            "source": "r22_missing_name",
            "section": "D.1",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "change-name/name-unlinked-surname-prior-event": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "name-unlinked-surname-prior-event",
        "full_route": "change-name/name-unlinked-surname-prior-event",
        "entry_conditions": [
          "Parts of the surname cannot be linked to the latest Numident.",
          "The source’s prior-name-change evidence route applies; actual event/document acceptability is not established here."
        ],
        "steps": [
          {
            "id": "name-unlinked-surname-prior-event-step-1",
            "title": "Request prior event evidence",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Resolve the identity question by requesting prior name-change event evidence proving the applicant may have used that name in the past. Specific event-document requirements remain linked and unreviewed.",
            "conditions": [
              "Parts of the surname cannot be linked to the latest Numident.",
              "The source’s prior-name-change evidence route applies; actual event/document acceptability is not established here."
            ],
            "source": "r22_missing_name",
            "section": "D.1",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "change-name/name-unlinked-surname-no-event": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "name-unlinked-surname-no-event",
        "full_route": "change-name/name-unlinked-surname-no-event",
        "entry_conditions": [
          "The D1 surname discrepancy cannot be linked.",
          "No name-change event has occurred."
        ],
        "steps": [
          {
            "id": "name-unlinked-surname-no-event-step-1",
            "title": "Request legal-name evidence",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Request evidence of the legal name, such as the source’s birth-certificate example, under RM10212.001. This legal-name purpose does not turn a birth certificate into the sole acceptable identity document under D.",
            "conditions": [
              "The D1 surname discrepancy cannot be linked.",
              "No name-change event has occurred."
            ],
            "source": "r22_missing_name",
            "section": "D.1",
            "source_context_refs": [
              "RM10212.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "apply-extra-help/extra-help-deemed-group": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "extra-help-deemed-group",
        "full_route": "apply-extra-help/extra-help-deemed-group",
        "entry_conditions": [
          "Actual facts establish one of the source groups: SSI plus Medicare; Medicaid prescription-drug coverage plus Medicare; or State payment of Medicare premiums, such as QMB/SLMB/QI."
        ],
        "steps": [
          {
            "id": "extra-help-deemed-group-step-1",
            "title": "Keep the application distinction",
            "kind": "situation",
            "actor": "context",
            "action": "For these source-defined deemed groups, the page says not to complete i1020 or another subsidy application. This example does not determine that any person actually belongs to a group.",
            "conditions": [
              "Actual facts establish one of the source groups: SSI plus Medicare; Medicaid prescription-drug coverage plus Medicare; or State payment of Medicare premiums, such as QMB/SLMB/QI."
            ],
            "source": "r22_missing_extra",
            "section": "B.3 Who Should Not Complete",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "extra-help-deemed-group-step-2",
            "title": "Use the CMS information route",
            "kind": "action",
            "actor": "claimant",
            "action": "The page says CMS separately contacts the person about the subsidy and plan selection/change/opt-out instructions. A person who does not want to wait may contact CMS through the source-listed phone or website; actual contact or enrollment is not established.",
            "conditions": [
              "Actual facts establish one of the source groups: SSI plus Medicare; Medicaid prescription-drug coverage plus Medicare; or State payment of Medicare premiums, such as QMB/SLMB/QI."
            ],
            "source": "r22_missing_extra",
            "section": "B.3 Who Should Not Complete",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "apply-extra-help/extra-help-state-own-application": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "extra-help-state-own-application",
        "full_route": "apply-extra-help/extra-help-state-own-application",
        "entry_conditions": [
          "The State Medicaid office chooses an application other than SSA-1020 or i1020."
        ],
        "steps": [
          {
            "id": "extra-help-state-own-application-step-1",
            "title": "Identify who makes the determination",
            "kind": "situation",
            "actor": "context",
            "action": "For that State application, the source assigns the eligibility determination to the State agency. A State using SSA-1020-OCR may instead forward it to SSA; no automatic forwarding is established. This SSA page does not provide the State’s full filing, development or appeal procedure; no State procedure is modeled here.",
            "conditions": [
              "The State Medicaid office chooses an application other than SSA-1020 or i1020."
            ],
            "source": "r22_missing_extra",
            "section": "A",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "apply-extra-help/extra-help-language-facsimile": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "extra-help-language-facsimile",
        "full_route": "apply-extra-help/extra-help-language-facsimile",
        "entry_conditions": [
          "The document is one of the source-described language facsimiles rather than the scannable SSA-1020-OCR."
        ],
        "steps": [
          {
            "id": "extra-help-language-facsimile-step-1",
            "title": "Use the guide for the actual form",
            "kind": "action",
            "actor": "claimant",
            "action": "Use the facsimile to help complete the SSA-1020-OCR; the source says the facsimile is not scannable and should not itself be completed or sent to WBDOC.",
            "conditions": [
              "The document is one of the source-described language facsimiles rather than the scannable SSA-1020-OCR."
            ],
            "source": "r22_missing_extra",
            "section": "B.1",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "extra-help-language-facsimile-step-2",
            "title": "Keep the destination condition",
            "kind": "situation",
            "actor": "context",
            "action": "Completed SSA-1020-OCR processing and a form received by an FO have separately linked procedures; this does not invent the FO intake steps.",
            "conditions": [
              "The document is one of the source-described language facsimiles rather than the scannable SSA-1020-OCR."
            ],
            "source": "r22_missing_extra",
            "section": "B.1",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "apply-extra-help/extra-help-resources-question-state-route": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "extra-help-resources-question-state-route",
        "full_route": "apply-extra-help/extra-help-resources-question-state-route",
        "entry_conditions": [
          "The source’s listed i1020 resource guidance is relevant; this example does not calculate countable resources, apply exclusions or determine entitlement."
        ],
        "steps": [
          {
            "id": "extra-help-resources-question-state-route-step-1",
            "title": "Do not equate the threshold with universal ineligibility",
            "kind": "situation",
            "actor": "context",
            "action": "The page says a person above its listed amounts may still be eligible for the subsidy and should contact the State Medicaid agency to find out. Amounts and case facts are not hardcoded here.",
            "conditions": [
              "The source’s listed i1020 resource guidance is relevant; this example does not calculate countable resources, apply exclusions or determine entitlement."
            ],
            "source": "r22_missing_extra",
            "section": "B.3 resource note",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "extra-help-resources-question-state-route-step-2",
            "title": "Keep Part D coverage separate",
            "kind": "action",
            "actor": "claimant",
            "action": "The page also says a person may enroll with an approved Medicare prescription-drug provider whether or not eligible for subsidy; no enrollment or eligibility result is established.",
            "conditions": [
              "The source’s listed i1020 resource guidance is relevant; this example does not calculate countable resources, apply exclusions or determine entitlement."
            ],
            "source": "r22_missing_extra",
            "section": "B.3 resource note",
            "source_context_refs": [
              "HI03010.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "lower-irmaa/irmaa-amended-return-contact": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "irmaa-amended-return-contact",
        "full_route": "lower-irmaa/irmaa-amended-return-contact",
        "entry_conditions": [
          "An amended income tax return is the source-defined reason for this request; a life-changing event is not inferred."
        ],
        "steps": [
          {
            "id": "irmaa-amended-return-contact-step-1",
            "title": "Contact SSA about the amended return",
            "kind": "action",
            "actor": "claimant",
            "action": "Call the official SSA number shown on the publisher page and tell the representative the request concerns lowering IRMAA after an amended tax return. The page does not specify a complete adjudication or evidence-decision procedure for this branch.",
            "conditions": [
              "An amended income tax return is the source-defined reason for this request; a life-changing event is not inferred."
            ],
            "source": "r22_missing_irmaa",
            "section": "Amended income tax returns",
            "source_context_refs": [
              "SSA-irmaa-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "lower-irmaa/irmaa-fax-mail-life-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "irmaa-fax-mail-life-change",
        "full_route": "lower-irmaa/irmaa-fax-mail-life-change",
        "entry_conditions": [
          "This is a life-changing event that reduced household income under the source guidance.",
          "The completed SSA-44 and applicable evidence are being submitted using the source’s fax/mail option."
        ],
        "steps": [
          {
            "id": "irmaa-fax-mail-life-change-step-1",
            "title": "Prepare the source-specific request",
            "kind": "action",
            "actor": "claimant",
            "action": "Complete SSA-44 for the life-changing-event request and the applicable evidence. This example does not decide a qualifying event or required proof.",
            "conditions": [
              "This is a life-changing event that reduced household income under the source guidance.",
              "The completed SSA-44 and applicable evidence are being submitted using the source’s fax/mail option."
            ],
            "source": "r22_missing_irmaa",
            "section": "Fax or mail your request",
            "source_context_refs": [
              "SSA-irmaa-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "irmaa-fax-mail-life-change-step-2",
            "title": "Use the published office route",
            "kind": "action",
            "actor": "claimant",
            "action": "Fax or mail the completed form and evidence to a Social Security office using the publisher’s office-finder route. Actual receipt and the IRMAA result remain unverified.",
            "conditions": [
              "This is a life-changing event that reduced household income under the source guidance.",
              "The completed SSA-44 and applicable evidence are being submitted using the source’s fax/mail option."
            ],
            "source": "r22_missing_irmaa",
            "section": "Fax or mail your request",
            "source_context_refs": [
              "SSA-irmaa-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "lower-irmaa/irmaa-outside-US-appointment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "irmaa-outside-US-appointment",
        "full_route": "lower-irmaa/irmaa-outside-US-appointment",
        "entry_conditions": [
          "The source includes U.S. territories/commonwealths in this outside-U.S. appointment instruction.",
          "An appointment is being requested for the IRMAA task."
        ],
        "steps": [
          {
            "id": "irmaa-outside-US-appointment-step-1",
            "title": "Contact a Federal Benefits Unit",
            "kind": "action",
            "actor": "claimant",
            "action": "The page directs contacting a Federal Benefits Unit to request an appointment. This is an appointment-routing instruction, not a change in claim jurisdiction or an eligibility finding.",
            "conditions": [
              "The source includes U.S. territories/commonwealths in this outside-U.S. appointment instruction.",
              "An appointment is being requested for the IRMAA task."
            ],
            "source": "r22_missing_irmaa",
            "section": "Make an appointment outside U.S.",
            "source_context_refs": [
              "SSA-irmaa-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "update-contact/contact-email-account-path": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "contact-email-account-path",
        "full_route": "update-contact/contact-email-account-path",
        "entry_conditions": [
          "This is an email update, not a direct-deposit or universal mailing-address procedure."
        ],
        "steps": [
          {
            "id": "contact-email-account-path-step-1",
            "title": "Sign in and open the profile",
            "kind": "action",
            "actor": "claimant",
            "action": "Sign in to the account and choose My Profile.",
            "conditions": [
              "This is an email update, not a direct-deposit or universal mailing-address procedure."
            ],
            "source": "r22_missing_contact",
            "section": "Email updates",
            "source_context_refs": [
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "contact-email-account-path-step-2",
            "title": "Use the published email path",
            "kind": "action",
            "actor": "claimant",
            "action": "Choose Security, then Update Email. The page says email can be updated at any time; actual authentication and completion are not established.",
            "conditions": [
              "This is an email update, not a direct-deposit or universal mailing-address procedure."
            ],
            "source": "r22_missing_contact",
            "section": "Email updates",
            "source_context_refs": [
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "update-contact/contact-not-already-benefits": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "contact-not-already-benefits",
        "full_route": "update-contact/contact-not-already-benefits",
        "entry_conditions": [
          "The person is not already receiving benefits; no application or entitlement status is inferred from this example."
        ],
        "steps": [
          {
            "id": "contact-not-already-benefits-step-1",
            "title": "Keep the feature restriction narrow",
            "kind": "situation",
            "actor": "context",
            "action": "The page limits its mailing-address and phone-number update feature to people already receiving benefits while allowing email updates at any time. This does not supply the full procedure for a pending claim’s address record.",
            "conditions": [
              "The person is not already receiving benefits; no application or entitlement status is inferred from this example."
            ],
            "source": "r22_missing_contact",
            "section": "Update contact information",
            "source_context_refs": [
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "contact-not-already-benefits-step-2",
            "title": "Ask about the needed update",
            "kind": "action",
            "actor": "claimant",
            "action": "Use the page’s SSA contact option to explain the contact-information request. No telephone-only completion, new account eligibility or pending-claim routing rule is established.",
            "conditions": [
              "The person is not already receiving benefits; no application or entitlement status is inferred from this example."
            ],
            "source": "r22_missing_contact",
            "section": "Update contact information",
            "source_context_refs": [
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "update-contact/contact-paper-check-unable-online": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "contact-paper-check-unable-online",
        "full_route": "update-contact/contact-paper-check-unable-online",
        "entry_conditions": [
          "The person receives payment by paper check and wants to change the mailing address.",
          "The surrounding FAQ condition of inability to use online services or generate the one-time code is retained; this is not a universal rule for every contact-information update."
        ],
        "steps": [
          {
            "id": "contact-paper-check-unable-online-step-1",
            "title": "Keep the FAQ scope",
            "kind": "situation",
            "actor": "context",
            "action": "The identity FAQ distinguishes direct-deposit identity procedures from continued payments and other contacts. It does not require everyone to contact SSA to continue benefits.",
            "conditions": [
              "The person receives payment by paper check and wants to change the mailing address.",
              "The surrounding FAQ condition of inability to use online services or generate the one-time code is retained; this is not a universal rule for every contact-information update."
            ],
            "source": "r22_missing_identityproof",
            "section": "Does everyone need to prove identity? complete expanded answer",
            "source_context_refs": [
              "SSA-identityproof-whole",
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "contact-paper-check-unable-online-step-2",
            "title": "Use the stated office instruction",
            "kind": "action",
            "actor": "claimant",
            "action": "Under the retained paper-check and surrounding FAQ conditions, the page says to visit a Social Security office before changing the mailing address. No proof of identity, appointment arrangement or completed address change is established.",
            "conditions": [
              "The person receives payment by paper check and wants to change the mailing address.",
              "The surrounding FAQ condition of inability to use online services or generate the one-time code is retained; this is not a universal rule for every contact-information update."
            ],
            "source": "r22_missing_identityproof",
            "section": "Does everyone need to prove identity? complete expanded answer",
            "source_context_refs": [
              "SSA-identityproof-whole",
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "update-contact/contact-outside-US-appointment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "contact-outside-US-appointment",
        "full_route": "update-contact/contact-outside-US-appointment",
        "entry_conditions": [
          "The person lives outside the United States, including source-described territories/commonwealths, and seeks an appointment for this contact update."
        ],
        "steps": [
          {
            "id": "contact-outside-US-appointment-step-1",
            "title": "Contact a Federal Benefits Unit",
            "kind": "action",
            "actor": "claimant",
            "action": "Use the source’s Federal Benefits Unit route to request an appointment. This does not assign a new benefit-processing jurisdiction or guarantee an account update.",
            "conditions": [
              "The person lives outside the United States, including source-described territories/commonwealths, and seeks an appointment for this contact update."
            ],
            "source": "r22_missing_contact",
            "section": "Make an appointment outside U.S.",
            "source_context_refs": [
              "SSA-contact-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "get-benefit-letter/benefit-letter-automated-phone": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "benefit-letter-automated-phone",
        "full_route": "get-benefit-letter/benefit-letter-automated-phone",
        "entry_conditions": [
          "This is a request for a benefit-verification letter, not a tax form or an eligibility determination."
        ],
        "steps": [
          {
            "id": "benefit-letter-automated-phone-step-1",
            "title": "Call the published automated service",
            "kind": "action",
            "actor": "claimant",
            "action": "Call the official SSA number shown on the page; the source describes automated assistance in English and Spanish, 24 hours a day, seven days a week.",
            "conditions": [
              "This is a request for a benefit-verification letter, not a tax form or an eligibility determination."
            ],
            "source": "r22_missing_letter",
            "section": "Other ways; automated phone assistance",
            "source_context_refs": [
              "SSA-letter-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "benefit-letter-automated-phone-step-2",
            "title": "Use the source’s request phrase",
            "kind": "action",
            "actor": "claimant",
            "action": "When the service asks how it can help, say “proof of income.” The page does not specify the fulfilment method or delivery duration for this option.",
            "conditions": [
              "This is a request for a benefit-verification letter, not a tax form or an eligibility determination."
            ],
            "source": "r22_missing_letter",
            "section": "Other ways; automated phone assistance",
            "source_context_refs": [
              "SSA-letter-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-EXR-provisional-benefits-fee-exclusion",
        "full_route": "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion",
        "entry_conditions": [
          "This is Title XVI EXR representative-fee scope while applying for EXR or during a related appeal, not an actual fee authorization, withholding calculation or appointment finding.",
          "Provisional benefits must be distinguished from the relevant past-due-benefit fee basis."
        ],
        "steps": [
          {
            "id": "ssi-EXR-provisional-benefits-fee-exclusion-step-1",
            "title": "Keep fee authorization distinct",
            "kind": "action",
            "actor": "SSA fee-processing component",
            "action": "The source excludes provisional benefits when authorizing a fee under the fee-agreement process.",
            "conditions": [
              "This is Title XVI EXR representative-fee scope while applying for EXR or during a related appeal, not an actual fee authorization, withholding calculation or appointment finding.",
              "Provisional benefits must be distinguished from the relevant past-due-benefit fee basis."
            ],
            "source": "r22_missing_awardssi",
            "section": "C",
            "source_context_refs": [
              "DI13050.061-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "ssi-EXR-provisional-benefits-fee-exclusion-step-2",
            "title": "Keep withholding/direct-payment calculations distinct",
            "kind": "action",
            "actor": "SSA fee-processing component",
            "action": "Do not use provisional benefits to calculate the past-due-benefit amount for withholding/direct payment under the fee-agreement or fee-petition process. Also do not use provisional benefits to pay a court-authorized fee. Detailed fee rules remain linked; no amount is calculated.",
            "conditions": [
              "This is Title XVI EXR representative-fee scope while applying for EXR or during a related appeal, not an actual fee authorization, withholding calculation or appointment finding.",
              "Provisional benefits must be distinguished from the relevant past-due-benefit fee basis."
            ],
            "source": "r22_missing_awardssi",
            "section": "C",
            "source_context_refs": [
              "DI13050.061-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "cdb-marriage-benefit-review/cdb-marriage-spouse-SSI-only": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdb-marriage-spouse-SSI-only",
        "full_route": "cdb-marriage-benefit-review/cdb-marriage-spouse-SSI-only",
        "entry_conditions": [
          "Actual spouse-benefit facts must be established.",
          "The spouse receives SSI only, rather than a qualifying Social Security benefit for A3a."
        ],
        "steps": [
          {
            "id": "cdb-marriage-spouse-SSI-only-step-1",
            "title": "Classify the benefit for this exception",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source says SSI-only is not a Social Security beneficiary for this marriage exception.",
            "conditions": [
              "Actual spouse-benefit facts must be established.",
              "The spouse receives SSI only, rather than a qualifying Social Security benefit for A3a."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3.a",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "cdb-marriage-spouse-SSI-only-step-2",
            "title": "Keep other case and marriage questions separate",
            "kind": "situation",
            "actor": "context",
            "action": "This does not itself make a complete termination decision. Other marriage facts, lawful relationship questions, effectuation and notices remain outside this selected comparison.",
            "conditions": [
              "Actual spouse-benefit facts must be established.",
              "The spouse receives SSI only, rather than a qualifying Social Security benefit for A3a."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3.a",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "cdb-marriage-benefit-review/cdb-marriage-spouse-excluded-child-benefit": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdb-marriage-spouse-excluded-child-benefit",
        "full_route": "cdb-marriage-benefit-review/cdb-marriage-spouse-excluded-child-benefit",
        "entry_conditions": [
          "The spouse is a child beneficiary under18 OR an age18/19 child beneficiary entitled as a full-time student.",
          "The claimant’s CDB and actual marriage circumstances require separate establishment."
        ],
        "steps": [
          {
            "id": "cdb-marriage-spouse-excluded-child-benefit-step-1",
            "title": "Apply the specific benefit-type boundary",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source’s CDB marriage exception excludes these two spouse-benefit categories. Receiving a payment alone does not establish a qualifying spouse category.",
            "conditions": [
              "The spouse is a child beneficiary under18 OR an age18/19 child beneficiary entitled as a full-time student.",
              "The claimant’s CDB and actual marriage circumstances require separate establishment."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3.a",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "cdb-marriage-spouse-excluded-child-benefit-step-2",
            "title": "Leave the actual outcome unassigned",
            "kind": "situation",
            "actor": "context",
            "action": "This source comparison does not adjudicate marriage validity, entitlement or notices; it is not a blanket rule for every marriage or benefit type.",
            "conditions": [
              "The spouse is a child beneficiary under18 OR an age18/19 child beneficiary entitled as a full-time student.",
              "The claimant’s CDB and actual marriage circumstances require separate establishment."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3.a",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "cdb-marriage-benefit-review/cdb-spouse-disability-benefit-later-terminates": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdb-spouse-disability-benefit-later-terminates",
        "full_route": "cdb-marriage-benefit-review/cdb-spouse-disability-benefit-later-terminates",
        "entry_conditions": [
          "This is the source’s spouse-CDB/disability-termination circumstance.",
          "Actual later entitlement facts and other possible terminating events are not established."
        ],
        "steps": [
          {
            "id": "cdb-spouse-disability-benefit-later-terminates-step-1",
            "title": "Keep the later termination distinct",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source says a CDB no longer terminates merely because the spouse’s CDB or disability benefit terminates.",
            "conditions": [
              "This is the source’s spouse-CDB/disability-termination circumstance.",
              "Actual later entitlement facts and other possible terminating events are not established."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3 note",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "cdb-spouse-disability-benefit-later-terminates-step-2",
            "title": "Keep historical reinstatement separate",
            "kind": "situation",
            "actor": "context",
            "action": "The source separately describes a historical July1969-related reinstatement circumstance. This flow does not determine historical reinstatement, other termination grounds or current entitlement.",
            "conditions": [
              "This is the source’s spouse-CDB/disability-termination circumstance.",
              "Actual later entitlement facts and other possible terminating events are not established."
            ],
            "source": "r22_missing_childtermination",
            "section": "A.3 note",
            "source_context_refs": [
              "RS00203.035-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-benefit-agency-evidence-help": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssn-benefit-agency-evidence-help",
        "full_route": "ssn-evidence-hard-to-obtain/ssn-benefit-agency-evidence-help",
        "entry_conditions": [
          "The source’s SSN-evidence assistance scope applies; no waiver of required data or acceptable evidence is established.",
          "An agency requires the SSN for a benefit."
        ],
        "steps": [
          {
            "id": "ssn-benefit-agency-evidence-help-step-1",
            "title": "Contact the agency about its evidence",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source directs contacting the agency requiring the SSN to find out what evidence it used to establish eligibility to that benefit.",
            "conditions": [
              "The source’s SSN-evidence assistance scope applies; no waiver of required data or acceptable evidence is established.",
              "An agency requires the SSN for a benefit."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A agency-benefit bullet",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "ssn-benefit-agency-evidence-help-step-2",
            "title": "Keep the evidence standard",
            "kind": "situation",
            "actor": "context",
            "action": "An agency’s prior benefit decision does not automatically establish acceptable SSN evidence or SSN eligibility.",
            "conditions": [
              "The source’s SSN-evidence assistance scope applies; no waiver of required data or acceptable evidence is established.",
              "An agency requires the SSN for a benefit."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A agency-benefit bullet",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-parallel-FO-evidence-help": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssn-parallel-FO-evidence-help",
        "full_route": "ssn-evidence-hard-to-obtain/ssn-parallel-FO-evidence-help",
        "entry_conditions": [
          "The required SSN data/evidence cannot be supplied under the source assistance scope.",
          "Parallel-FO assistance is appropriate for pursuing an actual lead; the example does not invent an office or source."
        ],
        "steps": [
          {
            "id": "ssn-parallel-FO-evidence-help-step-1",
            "title": "Request help pursuing the lead",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Request assistance from a parallel field office when appropriate. The source does not supply the office-selection mechanism or a completed evidence handoff.",
            "conditions": [
              "The required SSN data/evidence cannot be supplied under the source assistance scope.",
              "Parallel-FO assistance is appropriate for pursuing an actual lead; the example does not invent an office or source."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A parallel-FO bullet",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssn-evidence-efforts-failed",
        "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed",
        "entry_conditions": [
          "The source assistance scope applies and efforts to produce the required evidence have failed."
        ],
        "steps": [
          {
            "id": "ssn-evidence-efforts-failed-step-1",
            "title": "Seek regional guidance",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Contact the Regional Office for guidance. This does not waive the required information or evidence or establish what the Regional Office will advise.",
            "conditions": [
              "The source assistance scope applies and efforts to produce the required evidence have failed."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A final bullet and note",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed/ssn-all-leads-data-evidence-unattainable": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssn-all-leads-data-evidence-unattainable",
        "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed/ssn-all-leads-data-evidence-unattainable",
        "entry_conditions": [
          "The parent failed-evidence effort scope applies.",
          "All leads have been explored and required SS-5 data and evidence remain unattainable under the source note."
        ],
        "steps": [
          {
            "id": "ssn-all-leads-data-evidence-unattainable-step-1",
            "title": "Do not process under the stated condition",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source says not to process the SSN application under these conditions. This is not a benefit-entitlement denial or a case outcome established by choosing the example.",
            "conditions": [
              "The parent failed-evidence effort scope applies.",
              "All leads have been explored and required SS-5 data and evidence remain unattainable under the source note."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A final note",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "ssn-all-leads-data-evidence-unattainable-step-2",
            "title": "Provide the source-referenced written notice",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Provide the written notice required by RM10215.110. Its detailed second-review, notice and processing instructions are not newly read or invented here.",
            "conditions": [
              "The parent failed-evidence effort scope applies.",
              "All leads have been explored and required SS-5 data and evidence remain unattainable under the source note."
            ],
            "source": "r22_missing_ssnassist",
            "section": "A final note",
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      },
      "benefit-upload-signature/uploaded-firstparty-CPAS-application": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "uploaded-firstparty-CPAS-application",
        "full_route": "benefit-upload-signature/uploaded-firstparty-CPAS-application",
        "entry_conditions": [
          "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
          "This pilot excludes the separately linked third-party iClaim procedure.",
          "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
        ],
        "steps": [
          {
            "id": "uploaded-firstparty-CPAS-application-step-1",
            "title": "Check the actual method and form conditions",
            "kind": "action",
            "actor": "SSA technician",
            "action": "For CPAS benefit applications SSA-16, SSA-8000 and SSA-8001, establish the proper applicant and check that the signer’s name is in the form’s signature area. The signing date and signing time must each be in the form’s signature area OR on an appended signature certificate page. Linked DI11005.017 eligibility details remain separately unreviewed for this draft; these fields alone are not a complete validity assessment.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-2",
            "title": "Review the application",
            "kind": "action",
            "actor": "SSA technician",
            "action": "Review for missing information. The source’s CPAS instruction says a claimant-contact validity call is unnecessary when the application was submitted through Upload Documents; this does not resolve actual contrary evidence.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-3",
            "title": "Record the actual signature method",
            "kind": "action",
            "actor": "SSA technician",
            "action": "Load MCS or CCE, receipt ATTEST and record CPAS as the actual method. Automatic ATTEST text alone does not mean verbal attestation occurred.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-4",
            "title": "Record the CPAS receipt issue",
            "kind": "action",
            "actor": "SSA technician",
            "action": "Add a CPAS issue and receipt it with the date the CPAS document was received; do not silently substitute the source C4 uploaded-submission date instruction.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-5",
            "title": "Provide the claim documents",
            "kind": "action",
            "actor": "SSA technician",
            "action": "Provide the application summary, reporting responsibilities and claim receipt; no delivery method is added beyond this C5 instruction.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-6",
            "title": "Complete adjudication only when ready",
            "kind": "action",
            "actor": "SSA technician",
            "action": "Adjudicate only after all required proofs and development are complete. This example does not establish those facts or an award.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Continue only under the source-defined conditions; this does not establish execution."
          },
          {
            "id": "uploaded-firstparty-CPAS-application-step-7",
            "title": "Store the post-processing copy",
            "kind": "action",
            "actor": "SSA technician",
            "action": "After the required actions, upload the application copy and appended signature certificate if included to Evidence Portal OR eView. A prior Upload Documents submission does not prove this later storage occurred.",
            "conditions": [
              "This is a source-approved CPAS application on SSA-16, SSA-8000 or SSA-8001, with the proper applicant independently established; this is not every uploaded document.",
              "This pilot excludes the separately linked third-party iClaim procedure.",
              "The application is submitted through Upload Documents; no contradictory identity/living-status facts are established or resolved by this example."
            ],
            "source": "r22_missing_signaturemethods",
            "section": "B; C.4; C.5",
            "source_context_refs": [
              "GN00201.015-whole"
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified."
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No verified completion or automatic return to another route."
          ]
        }
      }
    },
    "source_contexts": {
      "GN01070.781-A": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "A whole, all substeps retained",
        "start": 167,
        "end": 875,
        "exact_text": "A. \nHow to identify the WSU assigned to the claim\n\nUse the number holder’s (NH) Social Security number (SSN) to query the Modernized Claims System (MCS) Development Worksheet (DW01) screen or the Consolidated Claims Experience (CCE) screens.\n\nThe FO code on the MCS DW01 or CCE Claims Summary screen shows which WSU is assigned to the claim. For a list of WSU office codes, see GN 01070.782D.\n\nREMINDER: Technicians should also review the WMS History Query (WMHH) to check for recent case movement, see MS 03802.006.\n\nTo locate the WSU address, telephone number, or email address, use the Detailed Office/Organization Resource System (DOORS). FOs use the administrative telephone number to contact the WSU.\n\n",
        "span_sha256": "1b6421f7ad2e5ea2689a280bf33b900698ee2b4316f875a384e0dfd0eb05b4ba",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.781-B": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "B whole, all substeps retained",
        "start": 875,
        "end": 4807,
        "exact_text": "B. \nClaims attested or receipted in by the WSU\n\nThese instructions pertain to both First Party and Third Party internet claims (iClaims).\n\nFirst party iClaims are signed by the Number Holder (NH) using the “click and sign” process and the word “Internet” propagates to the appropriate application, (e.g., DIB, RIB, Aux Spouse) on the Development Worksheet in MCS or CCE to indicate that an internet claim was filed using “click and sign”, see GN 00201.015.\n\nThird party iClaims cannot be signed using click and sign. However, follow instructions in this section if the WSU has already obtained a valid application by completing one of the following actions as documented on the DW01:\n\n•\n\nContacted the proper applicant and verbally attested the application, or\n\n•\n\nReceived a wet-signed SSA-1 or SSA-16 (or MCS and CCE output equivalent)\n\nNOTE:The Number Holder (NH) might contact the FO before the FO or WSU completes the ATTEST issue. Treat all first party iClaims the same for the purposes of the instructions in this section regardless of whether the FO or WSU has entered a receipt date in the ATTEST line of the MCS DW01 or CCE Development Worksheet.\n\n1. \nClaimants requiring action by the FO or WSU\n\nTechnicians will assist claimants with scheduling, rescheduling, or cancelling appointments in the Enterprise Scheduling System (ESS) and the Enhance Leads and Appointments System (eLAS) to support the Appointmetn Focused Service Delivery Model (AFS) for FOs.\n\na. \n\nFor Enumeration purposes: Technicians will utilized ESS to schedule appointments and will refer individuals to use the Online Social Security Number Application (oSNAP) when applicable.\n\nb. \n\nFor Initial Claims and Post-entitlement (PE) appointments: Technicians will utilize eLAS to schedule initial claim appointments, and ESS for PE appointments.\n\nc. \n\nTechnicians should annotate in the remarks that there is a pending iClaim.\n\n2. \nAssist claimants who provide evidence to the FO\na. \n\nRecord evidence received in the FO\n\nWhen a WSU claimant submits their proofs to the FO, an FO employee authorized to examine and certify documents takes the actions in this section. For more information about who we authorize to certify documents, see GN 00301.090.\n\n•\n\nExamine and evaluate the evidence document(s) for authenticity you may refer to our sensitive POMS; Evaluating the Validity of Documents and Records.\n\n•\n\nAccess Shared Process and enter the evidence document(s) on the Evidence (EVID) screen, unless you should not record the document(s) or form(s) on the EVID screen per GN 00301.286E.3.\n\n•\n\nIf the evidence cannot be recorded in EVID, certify a photocopy of the evidence document(s) and fax/send the certified photocopies into the Evidence Portal(EP) or eView.\n\n•\n\nEstablish the issue “REMARK” and an associated remark with a next day tickle on the MCS DW01 screen or on the CCE Development Worksheet to alert the WSU that you certified the document(s) via the Shared Process or faxed them into EP or eView.\n\n•\n\nAnnotate the MCS DW03 screen or CCE Development Worksheet with the FO code, the name, and the direct phone number of the FO employee who established the EVID or faxed the evidence into EP or eView.\n\n•\n\nCall or email the WSU immediately to notify them that you recorded proofs on the EVID screen or faxed proofs into EP or eView. This prevents processing delays and unnecessary re-contacts with the claimant.\n\n•\n\nComplete the Social Security Number Application Process (SSNAP) actions when enumeration updates are necessary.\n\nb. \n\nFO does not retain evidence faxed into EP, or eView\n\nFO technicians should verify that the evidence is properly stored in the Certified Electronic Folder (CEF).\n\nOnce the document has been recorded in EVID or stored and viewed for legible content in either EP or eView, the document does not need to be retained, per GN 00301.322. For information on the Retention or Return of Documents, see GN 00301.275.\n\n",
        "span_sha256": "ba7530d405d93262f91d35404eb11b7e9b0d4e141dc4fd068419cbed6494d886",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.781-C": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "C whole, all substeps retained",
        "start": 4807,
        "end": 7452,
        "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
        "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.781-D": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "D whole, all substeps retained",
        "start": 7452,
        "end": 8249,
        "exact_text": "D. \nWSU procedures to handle iClaims with appointments\n\nThe WSU assigned the claim assumes jurisdiction and adjudicates the iClaim application. When reviewing assigned iClaims, use the MCS DW01, CCE Claims Summary, or eLAS screens to determine if there is a pending appointment in an FO. For all pending appointments:\n\n•\n\nThe WSU contacts the claimant to advise that the WSU will process their claim and will cancel the appointment with the FO.\n\n•\n\nIf contact is successful and the claimant does not agree to cancel the appointment, document the discussion in remarks and transfer the iClaim to the FO.\n\n•\n\nIf the WSU is unable to reach the claimant after at least two attempts before the scheduled FO appointment, document the contact attempts in the remarks and cancel the pending appointment.\n\n",
        "span_sha256": "b476eb09507dcf98b3846365c7c149d45a35da851784110c0714ef2f257f69c4",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.781-E": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "E whole, all substeps retained",
        "start": 8249,
        "end": 8522,
        "exact_text": "E. \nTransfer iClaims with mutual agreement\n\nWSU and FO managers may transfer an iClaim between their offices by mutual agreement for enhanced service delivery. Contact the other office via telephone or email to discuss the situation. Document and facilitate the transfer.\n\n",
        "span_sha256": "f10d60a7acaa84dfbe25b4e1f0057e678920bec1b556ed55867884d8db50ffca",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.781-F": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "locator": "F whole, all substeps retained",
        "start": 8522,
        "end": 8624,
        "exact_text": "F. \nReferences\n•\n\nGN 01050.075 Claims Routing Guide\n\n•\n\nGN 03910.040 Appointment of a Representative\n\n",
        "span_sha256": "56b0cc446da7b18a1d792d4d5ea459d213339bf6b9126335684f93561cf693c9",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
      },
      "GN01070.782-A": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "locator": "A whole, all substeps retained",
        "start": 162,
        "end": 651,
        "exact_text": "A. \nOverview of the WSUs and their role\n\nThis section outlines the responsibilities of the WSUs in handling initial claim diaries that they establish in partial adjudication cases. These instructions should help ensure consistent handling of claims diaries across all Operations' components.\n\nThe WSUs process first-party English language iClaim Retirement and Medicare-only applications where the claimant provides a domestic residence address and has proven age and citizenship status.\n\n",
        "span_sha256": "bce29e34a54053569e99d2d1d09412fe1b30b5b7f5db969df661d6bb2e138e1f",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
      },
      "GN01070.782-B": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "locator": "B whole, all substeps retained",
        "start": 651,
        "end": 2031,
        "exact_text": "B. \nDevelopment responsibilities for partial claims\n\nThe WSUs will initiate all necessary developmental action and requests for proof in the process of adjudicating their claims. If the WSU is not able to fully adjudicate because there is an unresolved issue (for example, involving military service, missing earnings), the WSUs will process the claim as a partial award, if it meets the requirements of GN 01010.110.\n\nThe WSUs will document and maintain control of partial claims until they receive the requested evidence and the outstanding issue(s) are resolved, as described in GN 01010.110D.\n\nThe process for handling diaries established on partial awards is the same process that the field offices (FO) follow.\n\nFor diaries established for future events, such as future Windfall Elimination Provision (WEP) entitlement, annotate the Modernized Claims System (MCS) Report of Contact (RPOC) screen with the reason for the diary and the local FO Code for future follow-up action.\n\nThe WSUs will monitor their Modernized Development Worksheet (MDW) diary alert listings, and follow-up on outstanding requests when needed. When the WSU completes the development, they will take the necessary action to clear the diary and adjust benefit rates, if necessary. The WSU will send an MDW or Request for Assistance form to the Processing Center (PC) to request they cancel the diary.\n\n",
        "span_sha256": "e3c87ba874aa587e8c8647608cfc3559122138c639872bcc32a2e10cb61557f5",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
      },
      "GN01070.782-C": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "locator": "C whole, all substeps retained",
        "start": 2031,
        "end": 2628,
        "exact_text": "C. \nFO responsibility when partial diary development received (WSU processed original claim)\n\nIf the claimant brings in their documentation for the outstanding issue into the local FO instead of sending it to the WSU, the FO should take the necessary action and update any proofs they receive on the evidence screen. Review the MDW or original claim Development Worksheet (DW01) for other outstanding issues that may be pertinent to the diary. The FO must contact the WSU so they can close out their controls on the partial claim development. The WSU will also notify the PC to cancel its diary.\n\n",
        "span_sha256": "2b050edde627f3bf21678f8cc13da865cd610a979b3139bfb3b6daac86e159bb",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
      },
      "GN01070.782-D": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "locator": "D whole, all substeps retained",
        "start": 2628,
        "end": 3421,
        "exact_text": "D. \nPC responsibility when partial award diary matures\n\nWhen the diary for an outstanding issue on a partially adjudicated claim matures, the PC will first review the Workload Management System (WMS) query to ascertain which office originated the diary. If a WSU FO code is present, the PC will forward the follow up to the WSU rather than the servicing FO shown on the Master Beneficiary Record (MBR).\n\nHere is a list of the office codes for the WSUs:\n\nBoston WSU\n\n\t\n\nC98\n\n\n\n\nNEPSC WSU\n\n\t\n\nC25\n\n\n\n\nMATPSC WSU\n\n\t\n\nC12\n\n\n\n\nSEPSC WSU\n\n\t\n\nC34\n\n\n\n\nTampa WSU\n\n\t\n\n319\n\n\n\n\nGLPSC WSU\n\n\t\n\nC02\n\n\n\n\nAlbuquerque WSU\n\n\t\n\nA54\n\n\n\n\nMAMPSC WSU\n\n\t\n\nC33\n\n\n\n\nGolden WSU\n\n\t\n\nC88\n\n\n\n\nWNPSC WSU\n\n\t\n\nC87\n\n\n\n\nSalinas WSU\n\n\t\n\n165\n\n\n\n\nAuburn WSU\n\n\t\n\nC84\n\n\n\n\nOCO WSU\n\n\t\n\nC61\n\n\n\n\nOCO WBDOC\n\n\t\n\n00A\n\n\n\n\nDurham WSU\n\n\t\n\n01B\n\n",
        "span_sha256": "b71168f3a00814f7f2fe3b5555fe4e27d98171d9d3d4e180034e67f86c595ed9",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
      },
      "GN01070.782-E": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "locator": "E whole, all substeps retained",
        "start": 3421,
        "end": 3980,
        "exact_text": "E. \nPC responsibility when future event diary matures\n\nThe WSUs also establish diaries on future events, such as earnings development, that they cannot develop until the following year and possible future higher entitlement on another Social Security number (SSN). The WSUs will not retain jurisdiction of these diaries. When the future event diary date matures, the PC will either take action on the future event or forward a follow-up development request to the servicing FO for their necessary action. Find the servicing FO on the MBR or the RPOC screen.\n\n",
        "span_sha256": "4143e2f30f0083e86029b67cbfca87c183becf61dec96979de15d992f06040b5",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40"
      },
      "GN01010.110-A": {
        "source_code": "GN01010.110",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "locator": "A whole, all substeps retained",
        "start": 104,
        "end": 1554,
        "exact_text": "A. \nTypes of adjudication and related terms\n1. \nAdjudication\n\nAdjudication is the application of the law to the facts and an authoritative declaration of the result (i.e. a signed determination or decision). Consider a claim adjudicated when an employee with adjudicative authority delegated from the Commissioner of the Social Security Administration completes\n\n•\n\nthe appropriate electronic adjudicative decision screen,\n\n•\n\nthe equivalent direct input screen, or,\n\n•\n\nsigns a paper adjudicative form\n\n2. \nPartial adjudication\n\nPartial adjudication is a method of awarding benefits to a claimant before all development is complete. It is the initial determination of all issues except those still being developed.\n\n3. \nImmediate payment\n\nImmediate payment means that payment is due for the current operating month (COM) in which the claim is being adjudicated (or earlier); or Hospital Insurance / Supplementary Medical Insurance (HI/SMI) entitlement exists in a monthly benefit claim.\n\nExample 1:\n\nA claimant is entitled to retirement insurance benefits (RIB) effective 10/2010. The first payment is due 11/03/2010 for the COM of the 10 /2010.\n\nExample 2:\n\nA claimant is in full work deduction status. Immediate payment does not exist unless the Number Holder (NH) is entitled to HI/SMI.\n\nException: The immediate payment criteria do not apply to Terminal Illness (TERI) or Compassionate Allowance (CAL) claims pending disability determinations.\n\n",
        "span_sha256": "44a3d27d7a209c32b38cf6d3cc19544c49cccef5eab30c97ada1932b8f9c293d",
        "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
      },
      "GN01010.110-B": {
        "source_code": "GN01010.110",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "locator": "B whole, all substeps retained",
        "start": 1554,
        "end": 3583,
        "exact_text": "B. \nPolicy on partial adjudication\n\nThe claims technician is responsible for fully developing and reviewing the claim to ensure that the claimant meets all entitlement factors prior to adjudication. You must properly document any partial award in the Modernized Claims System (MCS) screen or the claims file to ensure proper control of any outstanding issues until they are resolved.\n\n1. \nWhen to partially adjudicate a claim\n\nPartially adjudicate a claim if:\n\na. \n\nAll factors of entitlement are met;\n\nb. \n\nThere is an unresolved issue pending (e.g., Military Service (MS) verification is pending);\n\nc. \n\nImmediate payment is due; and\n\nd. \n\nThe claimant either:\n\n•\n\nFiles an application and there is an issue pending development (e.g., proof of Military Service is being developed); or\n\n•\n\nIs potentially entitled to more than one benefit type or on more than one SSN and only one claim is ready for effectuation.\n\nReminder: It is not a partial award situation when a disability decision is still outstanding and the claimant files for another benefit type (e.g. RIB). The disability (DIB) decision is an outstanding entitlement factor for the DIB claim; adjudicate the RIB application separately from the DIB.\n\n2. \nWhen not to partially adjudicate a claim\n\nDo not adjudicate the following types of claims as partial awards:\n\na. \n\nLump Sum Death Payment (LSDP) claims via MCS while a claim for monthly benefits is pending on the same social security number (SSN) (see GN 01010.250).\n\nb. \n\nA claim with pending development for lag year earnings, in accordance with RS 01404.005. However, if lag earnings are not an entitlement issue (i.e. earnings are not needed for insured status), adjudicate the claim after 10 days. No diary is necessary.\n\nc. \n\nMedicare-only claims involving State buy-ins or not meeting the residency requirement. However, in advance filing cases where the claimant will meet the residency requirement, you can adjudicate the claim and include a diary for verification of the 5-year residency requirement.\n\n",
        "span_sha256": "5df3b4d03a280433220b31b6c2463365bf6cc93c68477a0afe5279e1a9452245",
        "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
      },
      "GN01010.110-C": {
        "source_code": "GN01010.110",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "locator": "C whole, all substeps retained",
        "start": 3583,
        "end": 6947,
        "exact_text": "C. \nProcedure for adjudicating partial awards\n1. \nDocumenting partial awards\n\nAll adjudicative decisions must reflect the documented facts for the entitlement. We cannot establish an element of entitlement or a factor affecting payment if you do not properly document it in accordance with the Program Operations Manual System (POMS) tolerances, presumptions, or evidentiary standards.\n\na. \nMCS earning computation (EC)\n•\n\nYou must select “DEC STAT 9” for retirement, survivor or Medicare partial claims (RSHI PARTIAL) or 10 (DIB PARTIAL) on the decision (DECI) screen;\n\n•\n\nInitiate the appropriate internal control (e.g., Modernized Development Worksheet (MDW)) and establish a diary on the DECI screen (see MSOM MCS 009.013) The DECI diary entry interfaces with the Processing Center Action Control System (PCACS) and establishes the diary in the processing center (PC).\n\n•\n\nAnnotate the report of contact (RPOC) screen with the applicable diary evidence code and a detailed rationale for all issues under development. If RPOC screens are not available, prepare a paper report of contact (RC) with the diary information including the following remark “SEE RC IN FILE - PC MUST ADD DIARY REMARKS - RPOC NOT AVAILABLE” and fax it into the paperless unit of the PC of jurisdiction. This simplifies and expedites accurate diary inputs in the PC.\n\nb. \nManually processed awards\n•\n\nFor manual awards, you must prepare an internal diary (e.g., MDW) and, request the PC to establish a diary supplying the applicable rationale and evidence Code(s).\n\n•\n\nAnnotate the Automated 101 (A101) or Electronic Form 101 (EF101) Benefit Continuity Remarks/Notice (BCRN) screen with the applicable diary Evidence Code(s) and document all issues under development in detail.\n\n•\n\nThe period for a diary for outstanding development input in the PC is usually 60-days unless conditions warrant a longer or shorter period and a specific date is input.\n\n2. \nPartial award notices\n\nYou must annotate the applicable partial award paragraph(s) on the notice as instructed here.\n\n•\n\nInclude a special paragraph on the appropriate screen for the award notice (e.g., notice (NOT) 2, NOT3, A101 BCRN screen, RPOC, etc.).\n\n•\n\nSelect the dictated paragraphs needed as instructed in MS 03509.010 and NL 00725.005 for the MCS Universal Text Identifiers (UTI) for partial awards (PAYR01).\n\n•\n\nFor Dual Entitlement (DE) claims, include the special paragraph stating that we will make a separate decision on the other claim, when applicable. Use the UTI “CLOR05” for MCS processing (NL 00725.005) and “B56” for manually processed awards.\n\n•\n\nThe notice must include language advising the claimant that we based the determination on currently available evidence and we may revise it based on additional evidence.\n\nNOTE: In most cases, the first notice is not an initial determination on the unresolved issue. The PC will send another notice once the development is complete. This second notice is the final determination on that issue and must include a reconsideration paragraph. However, the first notice may be the final notice in earning record (E/R) revision cases not involving an earnings investigation (see GN 04001.040E.2).\n\n3. \nSpecial Notice Not Required\n\nA special notice is not required if a Primary Insurance Amounts (PIA) discrepancy is resolved prior to adjudication (see GN 01010.100).\n\n",
        "span_sha256": "c5be9ddcd9570de5e4d03426217e371100d0b1c2fad62bd1c5791e4b0bf853e0",
        "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
      },
      "GN01010.110-D": {
        "source_code": "GN01010.110",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "locator": "D whole, all substeps retained",
        "start": 6947,
        "end": 7221,
        "exact_text": "D. \nReferences\n•\n\nGN 01010.100 Subsequent Title II Claims and FO Adjudication\n\n•\n\nGN 01010.250 Processing Claims in the FO – Special Considerations\n\n•\n\nGN 04001.040 Role of Notice in Reopening\n\n•\n\nRS 01404.005 Lag Period – and Lag Earnings\n\n•\n\nMS 03509.010 Notice 3 (NOT3)\n\n",
        "span_sha256": "d9a778332d58d352464de78e2d8000b500e253cb3349e479164c741f6cd4de0a",
        "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56"
      },
      "RM10212.015-whole": {
        "source_code": "RM10212.015",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 4628,
        "exact_text": "Effective Dates: 04/16/2012 - Present\nPrevious | Next\n\nTN 17 (01-24)\n\nRM 10212.015 Evidence Requirements to Process a Name Change on the SSN\nA. \nGeneral Evidence Requirements\n\nTo process a name change on the SSN you must obtain evidence of the:\n\n1. \n\nname change event that complies with the evidence requirements detailed for each event in RM 10212.010;\n\n2. \n\nnew name; and\n\n3. \n\nnumber holder’s identity as shown on the latest Numident record.\n\nB. \nEvidence of Name Change Event\n\nConsider an acceptable name change document evidence of the name change event. To determine what is acceptable evidence of a name change refer to RM 10212.010.\n\nNOTE: When a legal opinion precedent is required to determine whether the document submitted is acceptable for a name change, SSA does not follow common law. SSA generally follows statutory law in these situations.\n\nC. \nEvidence of new name\n\nThe new name to be shown on the SSN card is obtained from the name change document, except when the name change is based on the following events:\n\nName Change Events\n\n\t\n\nReference\n\n\n\n\nNew name based on Marriage, Civil Union, and Domestic Partnership\n\n\t\n\nRM 10212.055B\n\n\n\n\nNew name based on Divorce, Dissolution, or Annulment\n\n\t\n\nRM 10212.065B\n\nD. \nEvidence of identity\n\nEvidence of identity in the new name to be shown on the SSN card and in the prior name on the latest Numident record must always be established in order to link the new name to the Numident record and to establish that the person applying for the name change and the number holder are the same person.\n\nThe name change document can also serve as an acceptable identity document for a name change if it is not a birth certificate and:\n\n•\n\nthe name change event occurred within the past two years (if under age 18, within the past 4 years), and\n\n•\n\nthe document has the number holder’s prior name and biographical information such as age, date of birth, or parents’ names, which matches the data on the latest Numident record.\n\nEXCEPTION: See exception in RM 10212.015 D.1, in this section.\n\nIf the name change event document does not meet both criteria the applicant must submit an identity document in addition to the name change document. The applicant must submit either:\n\n•\n\none identity document in the prior name as shown on the latest Numident record. The identity document in the old name is acceptable even if no longer current or is expired. (See exception in RM 10212.015D.1, in this section), or\n\n•\n\none identity document in the new name (to be shown on SSN card) when the requirements described in RM 10212.020 are met.\n\nNOTE: Use the priority lists of acceptable identity documents when requesting identity documents following RM 10210.420.\n\nEXCEPTION: Accept expired identity documents in the prior name if submitted in connection with a name change.\n\n1. \nWhen surname(s) on name change or identity document does not match the latest Numident\n\nWhen establishing identity in the name on the latest Numident through the name change or identity document and the surname shown on the document(s) does not exactly agree with the surname on the latest Numident record due to the lack or addition of part of the surname, the document is acceptable if the surname(s) shown on the name change or identity document can be linked to the Numident record (e.g., parent’s name, name at birth). Parts of a surname shown on the name change or identity document that cannot be linked to the Numident raise questions regarding the applicant’s identity and must be resolved by requesting prior evidence of a name change event proving the applicant may have used the name in the past. If no name change event has occurred, request evidence of the person’s legal name (e.g., birth certificate) per RM 10212.001.\n\nNOTE: Special circumstances regarding evidence of identity for name change events may be provided in the following sections referring to specific types of name change events.\n\nE. \nReference\n•\n\nRM 10212.010, Evidence of a Name Change on the SSN card.\n\n•\n\nRM 10212.020, Evidence Required to Process a Name Change when Evidence of Identity in the New Name Only is Submitted.\n\n•\n\nRM 10225.058, How to Process an SSN Replacement Card Request When an Adopted Child is Changing Their Name.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110212015\n\t\nRM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012\nBatch run: 07/31/2026\nRev:04/16/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
        "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0"
      },
      "HI03010.035-whole": {
        "source_code": "HI03010.035",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 6228,
        "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 12/04/2025 - Present\nPrevious | Next\n\nTN 54 (12-25)\n\nHI 03010.035 General Information about the Subsidy Application\n\nCITATIONS:\n\nRegulations—20 CFR 418.3201 and 42 CFR 423.774\nA. \nIntroduction\n\nThe MMA allows individuals to file for the subsidy with either SSA or a State Medicaid office. The law also required that CMS and SSA jointly develop an application for determining eligibility for the subsidy. SSA and CMS considered comments from States, advocacy groups, focus group participants and SSA regional coordinators when developing this application.\n\nStates have the option of using the CMS-SSA form (SSA-1020-OCR), SSA’s Internet application (i1020), or their own application. However, if a State Medicaid office chooses to use an application other than the SSA-1020 or i1020, that State Agency will make the eligibility determinations for those applications. States using the SSA-1020-OCR may forward the application to SSA to process. The instructions in this section apply to applications that will be processed by SSA.\n\nB. \nMethods of filing\n\nThere are several methods of filing the application but the same data is collected whichever method is used. Any of the application methods here can be used by a:\n\n•\n\nsingle individual filing for themselves (see HI 03010.010 for definition of proper applicant);\n\n•\n\nmarried individual filing only for themselves; or\n\n•\n\nmarried couple (living together) who are both filing for the subsidy at the same time.\n\n1. \nScannable Form (SSA-1020-OCR)\n\nThis is a self-help form. It will be mailed to Medicare eligible individuals who appear to meet the income limits based solely on computer matches with other agencies. The form will also be distributed at outreach events and used by State agencies and advocacy groups. It can be completed by the claimant or a personal representative filing on behalf of the claimant (see HI 03010.010B.). When completed, the SSA-1020-OCR is sent to the WBDOC to process as explained in HI 03010.040C.2. See HI 03010.038B.1. if the completed form is received in a field office (FO).\n\nThe SSA-1020-OCR is available in English and Spanish. SSA’s web site will contain facsimiles of the SSA-1020 in 14 languages that an applicant can use to complete the SSA-1020-OCR. The facsimiles are not scannable and should not be completed or forwarded to WBDOC.\n\n2. \nMAPS\n\nSSA FO and Workload Support Unit (WSU) staffs will complete in-person and telephone application interviews asking questions that are presented on a series of screens in the new MAPS. MAPS was developed specifically for the subsidy. Some questions on the MAPS are worded and presented differently than questions on the scannable form, but they elicit the same information.\n\n3. \nInternet Application (i1020)\n\nThe Internet application (i1020) is an interactive self-help form designed to capture all inputs by the claimant (or third party on behalf of the claimant) and subsequently propagate this data to the Medicare Determination process without any intervening action by an adjudicator. The screens are similar to, and elicit the same information as, MAPS screens and the scannable application. However, easy-access Help screens containing additional explanatory information are also available on the i1020 for most questions. The i1020 is available in English and Spanish. It can be accessed via the following website: www.ssa.gov/medicare/part-d-extra-help .\n\nNOTE: \n\nAlthough the screens are similar, the i1020 does not use or interface with MAPS screens to input subsidy application data to the Determination process. However, once accepted, MAPS screens are used to query and/or change data in an application entered via the i1020.\n\nThe following information is being provided solely to help respond to inquiries that may be received about the i1020.\n\nWho Should Complete the Subsidy Application?\n\nClaimants may use the i1020 to apply for the subsidy if:\n\n•\n\nthey have or are eligible for Medicare Part A and/or Part B; and\n\n•\n\nthey live in one of the 50 states or the District of Columbia; and\n\n•\n\ntheir combined savings, investments, and real estate (other than their home) is not worth more than $18,090 ($17,600 in 2025) if they are single, or $36,100 ($35,130 in 2025) if they are married and living together.\n\nNOTE: \n\nEven if the above amounts are exceeded, claimants may still be eligible for the subsidy – but they will have to contact their state Medicaid agency to find out. However, claimants may still enroll with an approved Medicare prescription drug provider for Part D coverage – whether or not they are eligible for the subsidy. To obtain a list of Medicare-approved prescription drug providers in their area, claimants may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nWho Should Not Complete the Subsidy Application\n\nSome claimants will be deemed eligible for the subsidy and should not complete an i1020 (or any other subsidy application). Claimants who should not file include those:\n\n•\n\nwho receive SSI payments and have Medicare;\n\n•\n\nwho receive Medicaid with prescription drug coverage and have Medicare; or\n\n•\n\nwhose state pays for their Medicare premiums (e.g., QMBs, SLMBs and QIs).\n\nThese claimants will be contacted separately by CMS about their subsidy. CMS will also notify them of the plan selection and provide instructions for changing plans or opting out of enrollment. If they don’t want to wait to be contacted, they may call CMS toll-free at 1-800-MEDICARE (1-800-633-4227) or visit www.medicare.gov. If they are deaf or hard of hearing, they may call the Medicare TTY number toll-free at 1-877-486-2048.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0603010035\n\t\nHI 03010.035 - General Information about the Subsidy Application - 12/04/2025\nBatch run: 12/04/2025\nRev:12/04/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
        "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb"
      },
      "SSA-irmaa-whole": {
        "source_code": "SSA-irmaa",
        "url": "https://www.ssa.gov/medicare/lower-irmaa",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 1871,
        "exact_text": "Breadcrumb\nHome  Medicare  Request to lower IRMAA\nPlan for Medicare\nSign up for Medicare\nRequest to lower IRMAA\nApply for Part D Extra Help\nManage Medicare benefits\nRequest to lower an Income-Related Monthly Adjustment Amount (IRMAA)\n\nIf you've had a life-changing event that reduced your household income, you can ask to lower the additional amount you'll pay for Medicare Part B and Part D.\n\nLife-changing events include marriage, divorce, the death of a spouse, loss of income, and an employer settlement payment.\n\nUpload your request to lower an IRMAA\n\nSign in to fill out and submit Medicare Income-Related Monthly Adjustment Amount-Life Changing Event (SSA-44). \n\nSign In\nCreate account\nAmended income tax returns\n\nCall +1 800-772-1213 and tell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) if you had an amended income tax return.\n\nOther ways to complete this task\n\nFax or mail your request\n\nFill out the Medicare Income-Related Monthly Adjustment Amount – Life-Changing Event (SSA-44) (PDF) form. Fax or mail your completed form and evidence to a Social Security office.\n\nFind your local office\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nFor support completing this task\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to lower your Medicare Income-Related Monthly Adjustment Amount (IRMAA) due to a life-changing event.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
        "span_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
        "maintext_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5"
      },
      "SSA-contact-whole": {
        "source_code": "SSA-contact",
        "url": "https://www.ssa.gov/life-events/update-contact-information",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 1593,
        "exact_text": "Breadcrumb\nHome  Life events  Contact information change\nLife events\nApproaching age 65 (Medicare eligibility)\nApproaching Retirement\nBecoming an adult\nDisability, injury, or illness\nStaying at a medical facility\nNeed help managing money\nImmigration\nIncarceration\nName change\nContact information change\nCommunication preferences\nUpdate contact information\n\nUpdate your mailing address, phone number, or email so we can communicate with you about your benefits.\n\nYou can update your email address any time. You can only update your mailing address and phone number if you're already getting benefits.\n\nSign in to your account\n\nKeep your phone number, email, and mailing address up to date in your account. Depending on your benefit type you may need to call us to complete this task.\n\nFor email updates, sign in to your account and select \"My Profile\" at the top of the page. Next, choose \"Security,\" then \"Update Email.\"\n\nSign in\nCreate account\nOther ways to complete this task\nMake an appointment\n\nYou’ll need to create an account if you don’t have one. After you sign in, we’ll help you schedule an appointment to complete this task.\n\nSchedule an appointment\n\nIf you live outside of the U.S., including U.S. territories or commonwealths, you’ll need to contact a Federal Benefits Unit to request an appointment. \n\nCall us\nAvailable in most U.S. time zones Monday through Friday, 8 a.m. to 7 p.m., in English, Spanish, and other languages.\n\nCall +1 800-772-1213\n\nTell the representative you want to update your contact information.\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
        "span_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
        "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9"
      },
      "SSA-identityproof-whole": {
        "source_code": "SSA-identityproof",
        "url": "https://www.ssa.gov/news/en/identity-proofing.html?tl=0%2C1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 6260,
        "exact_text": "What to Know about Proving Your Identity (Subscribe | En español)\n\nWebpage updated April 28, 2025\n\nWhy do I need to prove my identity?\n\nSocial Security is strengthening the process to prove identity related to direct deposit information. This applies to individuals who need to change their direct deposit information on our records. The easiest and most secure way is online with a personal my Social Security account. If someone cannot access their my Social Security account, then they will need to come into a Social Security office to prove their identity.\n\nPeople will continue to receive their benefits on schedule to the bank account information in Social Security’s records without needing to prove identity.\n\nHow do the new identity verification procedures protect me?\n\nBad actors use other people’s personal information, often found on the dark web, to steal people’s money and identity. That information allows bad actors to get past antiquated knowledge-based questions. Social Security’s identity verification procedures prevent bad actors from stealing current and future benefits.\n\nNew – How can I change my direct deposit over the phone?\n\nBeginning April 28, 2025, you can change your direct deposit by calling 1-800-772-1213. Before you call, go to ssa.gov/PIN to get a one-time code that you will give to the Social Security representative. To generate the code, you will need to sign in to or create a personal my Social Security account. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nDoes everyone need to prove their identity with Social Security?\n\nIf you are not applying for benefits or changing direct deposit information for current benefits, there is no need to contact Social Security to prove identity.\n\nPeople will continue to receive their benefits on schedule to the bank account information in Social Security’s records without needing to prove identity.\n\nIf changing direct deposit information for existing benefits, the most convenient and secure way to prove identity is with Social Security’s online services using a personal my Social Security account.\n\nIf unable to use Social Security’s online services, or generate a one-time code on ssa.gov/PIN a person\n\nchanging direct deposit information for any type of benefit must prove their identity in a Social Security office.\nreceiving payment by paper check must visit a Social Security office before changing their mailing address.\nDo I need to visit a Social Security office to prove my identity?\n\nIt depends. You don’t need to visit Social Security:\n\nto prove your identity if you use a personal my Social Security account to change direct deposit information.\nif you are applying for benefits online or over the phone (unless your claim is flagged as a possible fraud risk).\nto continue receiving benefits to the bank account information in Social Security’s records.\nif you do not receive benefits.\n\nYou do need to visit a Social Security office if you need to change direct deposit information and cannot do it online or cannot generate a one-time code at ssa.gov/PIN to complete the direct deposit transaction over the phone. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nDo I need to contact Social Security if I do not receive benefits?\n\nNo. You don’t need to contact Social Security if you don’t receive benefits.\n\nDo I need to contact Social Security to prove my identity to continue my monthly benefits?\n\nNo. You do not need to contact Social Security to continue your monthly benefits at your current bank. If you need to change your direct deposit information in the future, you can change that information online with a personal my Social Security account or automatic enrollment service through your bank, or by generating one-time code to complete the transaction over the phone at ssa.gov/PIN. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nCan I still apply for benefits on the telephone?\n\nYes.\n\nIf I prove my identity online or in an office, do I need to prove my identity if I visit an office again?\n\nOnce you have created a personal my Social Security account, you don’t need to prove your identity online again to continue using Social Security’s convenient online services.\n\nIf you need to prove your identity in a local office for a reason explained on this webpage, and if you need to visit a local office again for assistance when proof of identity is required, you will need to prove your identity at that next visit.\n\nAre there exceptions to proving my identity in person?\n\nYes. You can create a personal my Social Security account to prove your identity one time and continue to use Social Security’s online services without proving your identity in person. Beginning April 28, 2025, you can change your direct deposit by calling 1-800-772-1213. Before you call, go to ssa.gov/PIN to get a one-time code that you will give to the Social Security representative. You will be redirected to sign in to or create a personal my Social Security account to generate the code. If you are unable to create an account, you will need to come into a local Social Security office or arrange for direct deposit through your bank.\n\nHow do I find a Social Security office if I cannot do my business online?\n\nOur office locator service is available online at Social Security Office Locator. Customers who cannot use our website may call 1-800-772-1213 and we will assist you with finding a local office. Customers do not need an appointment if they are only changing their direct deposit information.\n\nWill Social Security send me a text message about proving my identity?\n\nNo. Social Security will never contact you by a text message to provide or confirm information about your identity. Ignore a text message like this if you receive one.",
        "span_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688",
        "maintext_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688"
      },
      "SSA-letter-whole": {
        "source_code": "SSA-letter",
        "url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 1301,
        "exact_text": "Breadcrumb\nHome  Manage benefits  Get benefit letter\nPrepare\nApply\nManage benefits\nGet benefit letter\nGet tax form (1099/1042S)\nSubmit forms and upload documents\nUpdate direct deposit\nResolve an overpayment\nRequest to withhold taxes\nView benefit payment schedule\nCommunicate changes to personal situation\nIdentify someone to manage benefits for you\nCancel your benefits application\nPause your Retirement benefit\nMake or change appointment\nGet benefit verification letter\n\nGet a benefit letter to show that you receive benefits, have submitted an application, or don't receive benefits.\n\nThis documentation is often needed for loan applications, housing assistance, and other processes that require verification of your income. It may be referred to as a \"proof of income letter\" or \"benefit letter\" and is personalized based on the status of your Social Security benefits, Supplemental Security Income, and Medicare coverage.\n\nSign in to your account\n\nDownload a PDF to get the letter right away.\n\nSign in\nCreate account\nOther ways to complete this task\nUse our automated phone assistance\nAvailable 24 hours a day, 7 days a week in English and Spanish.\n\nCall +1 800-772-1213\n\nWhen you hear \"How can I help you today?\" say \"proof of income.\"\n\nCall TTY +1 800-325-0778 if you're deaf or hard of hearing.",
        "span_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655",
        "maintext_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655"
      },
      "DI13050.061-whole": {
        "source_code": "DI13050.061",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 2032,
        "exact_text": "Effective Dates: 12/04/2012 - Present\nPrevious | Next\n\nTN 22 (09-24)\n\nDI 13050.061 Field Office (FO) Procedures for Title XVI Expedited Reinstatement (EXR) Awards\nA. \nOverview for a favorable medical decision\n\nThe Disability Determination Services (DDS) makes a favorable determination regarding entitlement, documents the determination on form SSA-832 and returns the case allowance to the FO via the Electronic Disability Collect System (EDCS) Action Items list. The FO technician must then process the award.\n\nB. \nTitle XVI procedures\n\nWhen DDS issues an EXR allowance, take the following steps:\n\n1. \n\nReview the SSA-832:\n\n•\n\nItem 9A is selected;\n\n•\n\nItem 10 shows “other ”.\n\n•\n\nItem 20 shows WRM code 31; and\n\n•\n\nRemarks show “Expedited Reinstatement MOE MM/DD/YY”.\n\n2. \n\nStop the provisional payments and terminate the current record. Follow the instructions in SM 01701.080D.\n\n3. \n\nStart-date the EXR record per SM 01701.080D.\n\n4. \n\nSend an expedited reinstatement award notice.\n\n5. \n\nClear the EXR event in the DCF as a continuance per DI 13010.620.\n\nC. \nPolicy for payment of representative’s fee\n\nClaimants have the right to representation while applying for EXR and any related appeals. We do not include provisional benefits in authorizing a fee under the fee agreement process. Do not use provisional benefits to calculate the amount of past due benefits to withhold for direct payment of a representative's fee under the fee agreement or fee petition process, or to pay a fee authorized by a court. For more information on representative's fees, see GN 03910.000, GN 03920.000, GN 03930.000 and GN 03940.000..\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0413050061\n\t\nDI 13050.061 - Field Office (FO) Procedures for Title XVI Expedited Reinstatement (EXR) Awards - 12/04/2012\nBatch run: 10/29/2026\nRev:12/04/2012\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15",
        "maintext_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15"
      },
      "RS00203.035-whole": {
        "source_code": "RS00203.035",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 6833,
        "exact_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 09/06/2023 - Present\nPrevious | Next\n\nTN 47 (04-26)\n\nRS 00203.035 Child's Benefits Termination of Entitlement\nA. \nGeneral information on termination\n\nA child's entitlement ends with the month before the month in which any of the following occurs:\n\n1. \nDeath\n\nThe child dies.\n\n2. \nAttainment of age 18\n\nThe child attains age 18 and is not disabled or a full-time student. A child born on the first day of the month attains age 18 in the previous month based on Agency policy concerning attainment of age.\n\nNOTE: If the child is under a disability, see RS 00203.035B.1. If the child is a full-time student, see RS 00203.035B.2.\n\n3. \nMarriage\n\nThe child marries, with these exceptions:\n\na. \n\nEntitlement does not end if the child is a child disability beneficiary ( CDB ) and the marriage is to a Social Security beneficiary other than:\n\n•\n\na child beneficiary under age 18, or\n\n•\n\na child beneficiary age 18 or 19 entitled because he or she is a full-time student.\n\nAn individual receiving Supplemental Security Income benefits only is not included in the definition of a “Social Security beneficiary.”\n\nb. \n\nAlthough a putative marriage in Louisiana terminates a child's entitlement, a putative marriage in any other state that recognizes such marriages does not. Under the laws of some states, a party to a void marriage may acquire inheritance rights as a spouse. This relationship is a putative marriage. The essential basis of a putative marriage is a good faith belief in the existence of a valid marriage at its inception and a continuous good faith belief (in a life case) or good faith until the worker dies (in a death case). (For information on putative marriages, see GN 00305.085.)\n\nNOTE: For instructions about same-sex marriage, see GN 00210.000.\n\nNOTE: Benefits to a CDB no longer terminate because the benefits of their spouse who is a CDB or disability beneficiary terminate. A CDB whose benefits terminate in or after July 1969 because their spouse's CDB benefits terminated for a reason other than death may have their benefits reinstated.\n\n4. \nNH no longer entitled to disability insurance benefits\n\nEntitlement ends the first month the NH is no longer entitled to a disability insurance benefit, unless the entitlement ended because of their death or entitlement to retirement insurance benefits.\n\nIf the NH is at full retirement age (FRA) when a subsequent disability determination shows that their disability ceased prior to the Disability Insurance Benefits (DIB) to Retirement Insurance Benefits (RIB) conversion, see \"NOTE\" in GN 00201.005B.1.a.\n\n \n\nB. \nSpecial rules\n\nIn addition to the situations listed in child’s benefits termination of entitlement, RS 00203.035A, the following terminating events apply:\n\n1. \nChild disability beneficiary (CDB)\n\nThe entitlement of a CDB ends with the second month following the month he or she ceases to be under a disability, unless in such month he or she is under age 19 and a full-time student.\n\nNOTE: The trial work provision discussed in DI 13010.035 applies to a CDB.\n\n2. \nStudent\n\nThe entitlement of a full-time student age 18-19 ends whenever the following occurs first, unless at such time he or she is entitled to benefits as a CDB:\n\na. \n\nThe month before the month he or she attains age 19, or deemed to have attained age 19.\n\nb. \n\nThe last month he or she is a full-time student. (For information on when student benefits terminate, see RS 00205.325B.)\n\nFor more information on the point at which a particular age is attained, see GN 00302.400.\n\n3. \nLegally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \nStep-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \nPolicy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203035\n\t\nRS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023\nBatch run: 09/10/2026\nRev:09/06/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
        "maintext_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad"
      },
      "RM10210.120-whole": {
        "source_code": "RM10210.120",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 2741,
        "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
        "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
      },
      "GN00201.015-whole": {
        "source_code": "GN00201.015",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0200201015",
        "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
        "start": 0,
        "end": 17432,
        "exact_text": "Effective Dates: 07/22/2026 - Present\nPrevious | Next\n\nTN 46 (07-26)\n\nGN 00201.015 Signature Methods for Benefit Applications\nA. \nBackground\n\nIn 2004, SSA adopted alternative signature methods to the traditional pen-and-ink signature (also known as wet signature) for benefit applications (e.g., SSA-1, SSA-16, SSA-8000) and related benefit application forms to simplify work processes.\n\nB. \nPolicy\n\nSSA accepts the following signature methods for benefit applications:\n\n•\n\nWet signature,\n\n•\n\nAttestation,\n\n•\n\nElectronic signature via Click-and-sign,\n\n•\n\nElectronic signature using Upload Documents, and\n\n•\n\nCommercial Product Alternative Signature (CPAS)\n\nOnly certain individuals can sign benefit applications (e.g., SSA-1, SSA-16, SSA-8000. See Proper Applicant GN 00204.003.\n\nFor non-benefit application forms, follow the applicable guidelines for each specific form to ensure signature compliance.\n\nFor example, refer to the specific signature policy related to Form SSA-827 (Authorization to Disclose Information to the Social Security Administration), DI 11005.056.\n\nNOTE: For SSI redetermination (RZ) signature methods, refer to SI 02305.003.\n\nC. \nSignature methods\n1. \n\nWet signature: A wet signature is a handwritten name or mark made with pen-and-ink on a physical document.\n\na. \n\nWet signature policies and procedures apply when:\n\n•\n\nProper applicant or claimant signs with pen-and-ink.\n\nIMPORTANT: For teleclaims and for proper applicants or claimants who prefer to sign with pen-and-ink, mail the application for signature using the Title II cover notice in GN 00204.014, which includes protective filing closeout language. Always ensure that the cover notice reflects the correct closeout date, based on the earlier of either the appointment date or the application date.\n\n•\n\nWe receive a paper application, signed by a proper applicant, that was not generated from Modernized Claims System (MCS) or Consolidated Claims Experience (CCE). For example, the proper applicant may have printed, completed, and signed an SSA-1 retirement application from SSAs list of forms available on the website.\n\nb. \n\nWet signature procedure and documentation\n\nWhen a paper application or application printout from telephone claims is received and signed with a wet signature (i.e., paper benefit applications mailed or dropped into Dropbox at a field office), the SSA technician follow instructions:\n\nPaper applications\n\n•\n\nReview the signed paper application to ensure that a signature is present in the designated box. Then, contact the claimant to verify the validity of the application by confirming that the claimant is alive, in accordance with GN 00204.001C1d, Valid Application.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue, and add a remark of wet signature to indicate that the application was signed with a wet (pen-and-ink) signature.\n\nApplication printout from telephone claims\n\n•\n\nReview the signed application printout to ensure that a signature is present in the designated area.\n\n•\n\nReceipt in the ATTEST issue and add a remark of \"wet signature\" to indicate that the application was signed with a wet (pen-and-ink) signature.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\nFor a paper application or an application printout from telephone claims, technicians take these actions:\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n•\n\nAdjudicate the application if all required proofs have been received and all determinations have been completed. If additional evidence is needed, follow the procedures in GN 00301.150 and SI 00601.100 for obtaining Title II and Title XVI evidence respectively. Also, see GN 00301.286 for recording evidence electronically and retaining evidentiary documents, when required.\n\n•\n\nReturn the signed paper application using the witnessed signature cover notice in Document Processing Systems (DPS), which informs the proper applicant or claimant that the paper application will not be retained by SSA.\n\n2. \n\nAttestation\n\na. \n\nAttestation is the action taken by an SSA employee of confirming and annotating the claimant or proper applicants:\n\n•\n\nIntent to file or complete a claims-related form,\n\n•\n\nAffirmation under penalty of perjury that the information provided is correct, and\n\n•\n\nAgreement to sign the application, amendment, or SSA forms that are completed with the claim/amendment by attestation.\n\nb. \n\nProcedure during the interview\n\n•\n\nVerify the identity of the individual according to relevant procedures for in-person or telephone interviewing, refer to GN 00203.020.\n\n•\n\nInform the individual that SSA has an alternative method to collect a signature in lieu of a wet signature on the application for benefits or claim related forms approved for attestation.\n\n•\n\nAt the start of the interview, read the following scripted language:\n\nDuring this interview, we will ask you questions that will be used to process your/or name of claimant's (application/amendment/ name of form) for (benefits/Medicare). At the end of the interview, we will ask you to confirm the truthfulness of your answers under penalty of perjury and we will record your response. You should be aware that you can be held legally responsible for giving us false information.\n\n•\n\nConfirm the individuals intent to file and sign the application for benefits or claim related forms approved for attestation.\n\n•\n\nComplete the application or claim related forms approved for attestation by obtaining and recording the individuals responses.\n\n•\n\nAt the end of the interview, to obtain the individuals affirmation of intent to file and understanding of the penalty clause, read the following scripted language:\n\n1. Attestation - script for in-person interviews:\n\nHere is a printed copy of the information that will be used to process your/or name of claimant's (application/amendment/name of form). Please review all the information carefully and let us know right away if anything needs to be corrected OR if any of the information changes.\n\nOnce the individual finishes reviewing the document and indicates that the information is accurate, read the following:\n\nDo you understand that the information you gave us and examined will be used to process your/or name of claimants (application/amendment/ name of form) for (benefits/Medicare)? Do you declare under penalty of perjury that this information is true and correct to the best of your knowledge?\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n2. Attestation - script for telephone interviews:\n\nYou will receive a printed copy of the information being used to process your/or name of claimant's (application/amendment/name of form) to retain for your records. Do you understand that you must review all of this information carefully and let us know right away if anything needs to be corrected OR if any of the information changes?\n\nOnce the individual acknowledges that they will receive a copy and understanding that they need to let us know of any changes, read the following:\n\nDo you understand that the information you have provided will be used to process your/or name of claimant's (application /amendment/ name of form)? Do you declare under penalty of perjury that this information is true and correct to the best of your knowledge?\n\nIMPORTANT: The individual must answer YES to all the required statements above (i.e., intent to provide information, truthfulness of it, and agreement to sign it under penalty of perjury) in order to accept the application for benefits or claim related forms approved for attestation, as a signed form. Individuals answering NO to any of the requirements will need to submit the form with a wet signature or another acceptable signature method for the application.\n\n•\n\nPrint the MCS or CCE claim and mail it to the claimant for his or her review and retention, along with the reporting responsibilities and claim receipt. Advise the claimant to review the material and contact SSA within 10 days if he or she needs to make any corrections. Any corrections received post-adjudication will be handled following current procedures. A copy of the claim will be placed in the Online Retrieval System (ORS).\n\n•\n\nAdjudicate the application if all required proofs have been received and all determinations have been completed.\n\nc. \n\nDocumenting attestation\n\nFollow the procedure here to document your attestation:\n\n•\n\nFor claims and amendments in MCS or CCE, the ATTEST issue automatically propagates to the DW01. Document that all requirements for attestation have been met by typing the receipt date for the ATTEST issue.\n\n•\n\nWhen the issue ATTEST is displayed in the Issue field and a date is entered in the receipt field, MCS propagates the interviewers three position office code, a space, up to six letters of the interviewers last name, a comma, and the first initial to the Remarks field. The comma following the last name is a floating comma. If the last name contains fewer than six characters, the comma should immediately follow the last character of the last name (e.g., 216 Cox, N). The ATTEST issue(s) and interviewers name will be retained electronically and deemed equivalent to the signature for the application or amendment.\n\nNOTE: For CCE, the attestation date and interviewer's name will automatically propagate.\n\n3. \n\nClick and sign Internet claim (iClaim)\n\na. \n\nClick and Sign is the means by which the claimant can sign their application electronically using an approved signing process by selecting the check box that indicates they are signing electronically (e.g., I agree with the Electronic Signature Agreement above and then clicking the Submit now (for RIB and Medicare claims), or Accept & Continue (for DIB claims) buttons in the Summary page at the conclusion of the online application). The Electronic Signature Agreement contains his or her affirmation under penalty of perjury that the information provided is true and correct to the best of their knowledge, and the applicant's intent to file and electronically sign and submit application data to SSA.\n\nb. \n\nProcedure and Documentation for Click and Sign\n\n•\n\nIndividuals completing and submitting their own application (i.e., first party applicants) are first routed to mySSA to be authenticated and verify their identity. Therefore, if the iClaim is marked as authenticated, you do not need to contact the claimant to verify identity. However, if the iClaim is flagged as unauthenticated, you must contact the claimant to verify their identity following GN 00203.020.\n\nNOTE:Third party iClaims will continue to follow the procedures outlined in GN 00204.055H2b and EM-18043.\n\n•\n\nThe word Internet propagates to the appropriate application, i.e., DIB, RIB, Aux Spouse on the MCS DW01 to indicate that an Internet claim was signed electronically and filed using click and sign.\n\n•\n\nReceipt in the ATTEST issue with the date the claimant submitted the iClaim, refer to GN 00204.007B4 for additional information.\n\nNOTE: Some additional forms within iClaim are approved for electronic signature by click and sign (e.g., SSA-827). The technician will add an ATTEST issue specific to that form on the development worksheet and receipt date.\n\n•\n\nAfter downloading the online application data from iClaim into MCS, ORS is automatically updated with a copy of the Internet application summary as submitted by the claimant. This secures the integrity of the information the beneficiary provided on the Internet application.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n4. \n\nUpload documents\n\nAfter authenticating through mySSA, individuals can complete and submit a PDF or webform version of certain agency forms and benefit applications using Upload Documents. If the application or form requires a signature, an electronic signature section will be presented on the Review and Submit page. In that section, individuals review the signature statement and apply their electronic signature to the uploaded or completed form by selecting the check box (a required field) and then selecting the Submit button. The form or application is considered signed upon submission. An appended page containing the electronic signature information will accompany the submitted PDF.\n\nNOTE: Although these forms are submitted electronically, technicians must process them as if they were paper applications and enter the information into our SSA systems by following the procedures outlined below.\n\na. \n\nProcedure and documentation for benefit applications\n\n•\n\nReview the signed PDF or webform version for any missing information.\n\nNOTE: The mySSA authentication verifies the claimant's identity and that they are alive meeting requirements in GN 00204.001C1d; unless there is evidence to the contrary.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue and add a remark of \"upload docs\" to indicate that the application was signed using Upload Documents.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\n•\n\nReceipt in the issue with the date the uploaded document was submitted by the individual.\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt by mail.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n5. \n\nCommercial product alternative signature (CPAS)\n\nIndividuals may use a commercial software product (commercial product) to affix their signatures to certain forms and writings in accordance with DI 11005.017, Commercial Product Alternative Signature Process for Certain Forms and Writings.\n\nIf there is a CPAS on the benefit application forms (SSA-16 (including the summary sent to the claimant after a third-party completes an internet claim), SSA-8000, and SSA-8001), SSA technicians must ensure the proper applicant has signed the benefit application forms using a commercial product that:\n\n•\n\nAffixes a signers name in the signature area of the form,\n\n•\n\nAffixes the date the document was signed in the signature area of the form or on an appended signature certificate page, and,\n\n•\n\nAffixes the time the document was signed in the signature area of the form or on an appended signature certificate page.\n\nOnce the technician ensures that the CPAS meets the above requirements for benefit applications SSA-16, SSA-8000, and SSA-8001 the technician must do the following:\n\n•\n\nReview the signed paper application for any missing information and contact the claimant to verify the validity of the application by confirming that the claimant is alive, in accordance with GN 00204.001C1d, Valid Application. If the application was submitted via Upload Documents, there is no need to contact claimant.\n\nNOTE: For third party iClaims with a submitted benefit application using CPAS, follow the procedures outlined in GN 00204.055H2b.\n\n•\n\nLoad the application into MCS or CCE, receipt in the ATTEST issue, and add a remark of \"CPAS\" to indicate that the application was signed using CPAS.\n\nNOTE: Because the MCS system automatically propagates \"ATTEST\" to the DW01, even when attestation is not the actual signature method, technicians must add a remark specifying the correct signature method used (e.g., wet signature, upload docs, CPAS).\n\n•\n\nAdd a CPAS issue on the MCS DW01 screen or the Development Worksheet in CCE and receipt the issue with the date the CPAS document was received.\n\n•\n\nProvide the claimant with a copy of the application summary, reporting responsibilities and claim receipt.\n\n•\n\nAdjudicate the application after all required proofs have been received and all developmental actions have been completed.\n\n•\n\nOnce the above actions are completed, upload a copy of the application and the appended signature certificate page, if included, to Evidence Portal or eView.\n\nNOTE: For more information on CPAS and other approved forms, refer to DI 11005.017.\n\nD. \nReferences\n•\n\nDI 11005.017 Commercial Product Alternative Signature Process for Certain Forms and Writings\n\n•\n\nDI 11005.056 Signature Requirements for Form SSA-827\n\n•\n\nGN 00204.001 Valid Application\n\n•\n\nGN 00204.003 Proper Applicant\n\n•\n\nGN 00204.007 Application Filing Date\n\n•\n\nGN 00204.014 The SSA-L566-U2 Title II Application Cover Notice\n\n•\n\nGN 00301.150 Evidence of Mail Development\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nSI 00601.100 General Guidance for Information or Evidence\n\n•\n\nSI 02305.003 Alternative Signature Methods: Attestation and Witnessed Signature\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0200201015\n\t\nGN 00201.015 - Signature Methods for Benefit Applications - 07/22/2026\nBatch run: 10/21/2026\nRev:07/22/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "span_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb",
        "maintext_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb"
      }
    },
    "source_pages": {
      "GN01070.781": {
        "source_code": "GN01070.781",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "captured_utc": "2026-10-31T16:40:35.167Z",
        "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
        "DOM_snapshot_sha256": "8c19db72a2052cc54a7c498680ad802e8c7132565edc6de630991c2cb0a5a18b",
        "capture_metadata_sha256": "4bfce92899c50424838ee47bd06cbc86eea5b09cfcfbe14e769637f36e79b0a4",
        "main_characters": 9033,
        "publisher_labels": [
          "Effective Dates: 05/04/2022 - Present",
          "TN 64 (03-26)",
          "Batch run: 10/02/2026",
          "Rev:05/04/2022"
        ],
        "capture_type": "Actual IAB rendered #content and DOM snapshot",
        "maintext_url": "/service/sources/GN01070.781-r22-main.txt",
        "snapshot_url": "/service/sources/GN01070.781-r22-DOM-snapshot.txt",
        "whole_page_or_native_acceptance": false
      },
      "GN01070.782": {
        "source_code": "GN01070.782",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "captured_utc": "2026-10-31T16:40:35.509Z",
        "maintext_sha256": "8e7d124d8bf72ca3b6db9b9f945c0f2d334cf585fccd02eb8b051bdd1903ab40",
        "DOM_snapshot_sha256": "e60aa9c48429ab0861d5b111375164c111cf9403292a26a697c55fd70cc0ac0d",
        "capture_metadata_sha256": "99d1fc52e015481ee89c8bd7d249b63c55dbc4943857e1ee6698a9ab6c086b54",
        "main_characters": 4384,
        "publisher_labels": [
          "Effective Dates: 09/09/2025 - Present",
          "TN 63 (09-25)",
          "Batch run: 09/09/2025",
          "Rev:09/09/2025"
        ],
        "capture_type": "Actual IAB rendered #content and DOM snapshot",
        "maintext_url": "/service/sources/GN01070.782-r22-main.txt",
        "snapshot_url": "/service/sources/GN01070.782-r22-DOM-snapshot.txt",
        "whole_page_or_native_acceptance": false
      },
      "GN01010.110": {
        "source_code": "GN01010.110",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "captured_utc": "2026-10-31T16:40:35.817Z",
        "maintext_sha256": "39206a67c4468c355dabf3e79f184616a8e2557a2ef027d20da09f0645d0ee56",
        "DOM_snapshot_sha256": "87594c2bd441d58486eed035981c63596db84f78478c16e364aafbd3df471206",
        "capture_metadata_sha256": "0b035dcc1b49e039f667846e3bae4e5711a44066c4da9a1c540158027a5a8390",
        "main_characters": 7567,
        "publisher_labels": [
          "Effective Dates: 06/22/2023 - Present",
          "TN 58 (06-23)",
          "Batch run: 06/22/2023",
          "Rev:06/22/2023"
        ],
        "capture_type": "Actual IAB rendered #content and DOM snapshot",
        "maintext_url": "/service/sources/GN01010.110-r22-main.txt",
        "snapshot_url": "/service/sources/GN01010.110-r22-DOM-snapshot.txt",
        "whole_page_or_native_acceptance": false
      },
      "RM10212.015": {
        "source_code": "RM10212.015",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
        "captured_utc": "2026-10-31T16:53:21.435Z",
        "capture_metadata": {
          "requested_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
          "actual_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
          "title": "SSA - POMS: RM 10212.015 - Evidence Requirements to Process a Name Change on the SSN - 04/16/2012",
          "source_id": "name",
          "selector": "#content",
          "captured_utc": "2026-10-31T16:53:21.435Z",
          "characters": 4628,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015"
        },
        "maintext_sha256": "9728a6b21517f09b8e1e158a533be8a73f42a5d247981ca68157935c3c7185c0",
        "DOM_snapshot_sha256": "5ca1763d3f9ead8e580c95f72318bd3c250205ef8bdb779bd0d78cf8ee87cbbe",
        "capture_metadata_sha256": "8e1f202d195fd713f242836c428cf313685de6e679efb18ac2e539559ed98a3f",
        "main_characters": 4628,
        "maintext_url": "/service/sources/RM10212.015-r22-main.txt",
        "snapshot_url": "/service/sources/RM10212.015-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "HI03010.035": {
        "source_code": "HI03010.035",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
        "captured_utc": "2026-10-31T16:53:21.730Z",
        "capture_metadata": {
          "requested_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
          "actual_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
          "title": "SSA - POMS: HI 03010.035 - General Information about the Subsidy Application - 12/04/2025",
          "source_id": "extra",
          "selector": "body",
          "captured_utc": "2026-10-31T16:53:21.730Z",
          "characters": 6228,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035"
        },
        "maintext_sha256": "61aac7c504727987770a37f38c91acc4ba7ef2a750da88ef5cb7f2e8222b20cb",
        "DOM_snapshot_sha256": "56866acd9b713f351889ef2731ef171bade4c16f48aa1cda8687f17a1a21be2a",
        "capture_metadata_sha256": "46d88b0524973c9f526c02a237766d7735b49fd3103ed82325a5a74e3b65355e",
        "main_characters": 6228,
        "maintext_url": "/service/sources/HI03010.035-r22-main.txt",
        "snapshot_url": "/service/sources/HI03010.035-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "SSA-irmaa": {
        "source_code": "SSA-irmaa",
        "url": "https://www.ssa.gov/medicare/lower-irmaa",
        "captured_utc": "2026-10-31T16:53:29.155Z",
        "capture_metadata": {
          "requested_url": "https://www.ssa.gov/medicare/lower-irmaa",
          "actual_url": "https://www.ssa.gov/medicare/lower-irmaa",
          "title": "Request to lower an Income-Related Monthly Adjustment Amount (IRMAA) | SSA",
          "source_id": "irmaa",
          "selector": "main",
          "captured_utc": "2026-10-31T16:53:29.155Z",
          "characters": 1871,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://www.ssa.gov/medicare/lower-irmaa"
        },
        "maintext_sha256": "6316a2247e48e3f176256aa8d5a47f8cbf1a004bbfe00abd29bb13ed8cc11da5",
        "DOM_snapshot_sha256": "1ff28448eff8fca5222abcf62c1104f800b3205c18fbf55a2573acd78c3f846e",
        "capture_metadata_sha256": "7ba4173a82f0865be346bb24e18b633fe96a66bee56abad46af626b086012f8c",
        "main_characters": 1871,
        "maintext_url": "/service/sources/SSA-irmaa-r22-main.txt",
        "snapshot_url": "/service/sources/SSA-irmaa-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "SSA-contact": {
        "source_code": "SSA-contact",
        "url": "https://www.ssa.gov/life-events/update-contact-information",
        "captured_utc": "2026-10-31T16:53:29.454Z",
        "capture_metadata": {
          "requested_url": "https://www.ssa.gov/life-events/update-contact-information",
          "actual_url": "https://www.ssa.gov/life-events/update-contact-information",
          "title": "Update contact information | SSA",
          "source_id": "contact",
          "selector": "main",
          "captured_utc": "2026-10-31T16:53:29.454Z",
          "characters": 1593,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://www.ssa.gov/life-events/update-contact-information"
        },
        "maintext_sha256": "8c5e6e760dbcf5b04be84e326797bef86ae0d52800f0f0ff2a6130b52b0455e9",
        "DOM_snapshot_sha256": "810f0e4605e48e8562f6bd68f644d2d2243d5741c998270baeb172dab684c32d",
        "capture_metadata_sha256": "a3b89adb8d6ed66074f75651da1d58c6b5416760cf906581cb2a1aafba4c4081",
        "main_characters": 1593,
        "maintext_url": "/service/sources/SSA-contact-r22-main.txt",
        "snapshot_url": "/service/sources/SSA-contact-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "SSA-identityproof": {
        "source_code": "SSA-identityproof",
        "url": "https://www.ssa.gov/news/en/identity-proofing.html?tl=0%2C1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11",
        "captured_utc": "2026-10-31T16:54:01.435Z",
        "capture_metadata": {
          "captured_utc": "2026-10-31T16:54:01.435Z",
          "url": "https://www.ssa.gov/news/en/identity-proofing.html?tl=0%2C1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11",
          "title": "What to Know about Proving Your Identity | News | SSA",
          "mechanism": "Actual IAB main.innerText after twelve normal disclosure clicks",
          "FAQ_states": [
            {
              "expanded": "true",
              "id": "js-tl0",
              "question": "Why do I need to prove my identity?"
            },
            {
              "expanded": "true",
              "id": "js-tl1",
              "question": "How do the new identity verification procedures protect me?"
            },
            {
              "expanded": "true",
              "id": "js-tl2",
              "question": "New – How can I change my direct deposit over the phone?"
            },
            {
              "expanded": "true",
              "id": "js-tl3",
              "question": "Does everyone need to prove their identity with Social Security?"
            },
            {
              "expanded": "true",
              "id": "js-tl4",
              "question": "Do I need to visit a Social Security office to prove my identity?"
            },
            {
              "expanded": "true",
              "id": "js-tl5",
              "question": "Do I need to contact Social Security if I do not receive benefits?"
            },
            {
              "expanded": "true",
              "id": "js-tl6",
              "question": "Do I need to contact Social Security to prove my identity to continue my monthly benefits?"
            },
            {
              "expanded": "true",
              "id": "js-tl7",
              "question": "Can I still apply for benefits on the telephone?"
            },
            {
              "expanded": "true",
              "id": "js-tl8",
              "question": "If I prove my identity online or in an office, do I need to prove my identity if I visit an office again?"
            },
            {
              "expanded": "true",
              "id": "js-tl9",
              "question": "Are there exceptions to proving my identity in person?"
            },
            {
              "expanded": "true",
              "id": "js-tl10",
              "question": "How do I find a Social Security office if I cannot do my business online?"
            },
            {
              "expanded": "true",
              "id": "js-tl11",
              "question": "Will Social Security send me a text message about proving my identity?"
            }
          ],
          "all12_expanded": true,
          "characters": 6260,
          "collapsed_first_observation_preserved": true,
          "source_native_acceptance": false,
          "workflow_adoption": false
        },
        "maintext_sha256": "3ce3411c0904e9caf27803a20799aa6eee3f60531a574c16ed6438a84ca3f688",
        "DOM_snapshot_sha256": "64b8fa03866ac8d0c728430f9231f1e9be624694c55b9cf3603172315c03a0fe",
        "capture_metadata_sha256": "33e6bd95e40c2aafc3f0ad32a6aa18d446c6bb0017935e39dced119716f34808",
        "main_characters": 6260,
        "maintext_url": "/service/sources/SSA-identityproof-r22-main.txt",
        "snapshot_url": "/service/sources/SSA-identityproof-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "SSA-letter": {
        "source_code": "SSA-letter",
        "url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
        "captured_utc": "2026-10-31T16:56:09.556Z",
        "capture_metadata": {
          "requested_url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
          "actual_url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
          "title": "Get benefit verification letter | SSA",
          "source_id": "letter",
          "selector": "main",
          "captured_utc": "2026-10-31T16:56:09.556Z",
          "characters": 1301,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://www.ssa.gov/manage-benefits/get-benefit-letter"
        },
        "maintext_sha256": "3888ac5894887869496d6b9ff1a7357374c1243b4f4143f6db2336e192f9b655",
        "DOM_snapshot_sha256": "4d11dd86ff23d28560e3300053ed423a675e848b4d84a41d799baedb7821de78",
        "capture_metadata_sha256": "dff88d32d44779fce8477fca075656421e7e9674c9cca6484883b0bb4455b1c4",
        "main_characters": 1301,
        "maintext_url": "/service/sources/SSA-letter-r22-main.txt",
        "snapshot_url": "/service/sources/SSA-letter-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "DI13050.061": {
        "source_code": "DI13050.061",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
        "captured_utc": "2026-10-31T16:56:09.880Z",
        "capture_metadata": {
          "requested_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
          "actual_url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
          "title": "SSA - POMS: DI 13050.061 - Field Office (FO) Procedures for Title XVI Expedited Reinstatement (EXR) Awards - 12/04/2012",
          "source_id": "awardssi",
          "selector": "#content",
          "captured_utc": "2026-10-31T16:56:09.880Z",
          "characters": 2032,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061"
        },
        "maintext_sha256": "74f3137dfcac4ba769d63d9915a4cc03424e1a8dfbaa178a6ebe623bd556da15",
        "DOM_snapshot_sha256": "69edb5ffb07fd4fa3c029f881f63a709ad0e4ba8301913cab1c283f53adb02ce",
        "capture_metadata_sha256": "f885d621a775780db861949d54a59dfb05861c6f7c26703df1da0f4a573859e3",
        "main_characters": 2032,
        "maintext_url": "/service/sources/DI13050.061-r22-main.txt",
        "snapshot_url": "/service/sources/DI13050.061-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "RS00203.035": {
        "source_code": "RS00203.035",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
        "captured_utc": "2026-10-31T16:56:10.210Z",
        "capture_metadata": {
          "requested_url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
          "actual_url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
          "title": "SSA - POMS: RS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023",
          "source_id": "childtermination",
          "selector": "body",
          "captured_utc": "2026-10-31T16:56:10.210Z",
          "characters": 6833,
          "expanded_disclosures": [],
          "source_native_acceptance": false,
          "workflow_adoption": false,
          "contents_reviewed_as_workflow": false,
          "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035"
        },
        "maintext_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
        "DOM_snapshot_sha256": "56866acd9b713f351889ef2731ef171bade4c16f48aa1cda8687f17a1a21be2a",
        "capture_metadata_sha256": "1680989185d0dbeb04c53e652874a03413f50756f6434fe4d83ca8967c595463",
        "main_characters": 6833,
        "maintext_url": "/service/sources/RS00203.035-r22-main.txt",
        "snapshot_url": "/service/sources/RS00203.035-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "RM10210.120": {
        "source_code": "RM10210.120",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
        "captured_utc": "2026-10-31T16:40:40.175Z",
        "capture_metadata": {
          "captured_utc": "2026-10-31T16:40:40.175Z",
          "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
          "title": "SSA - POMS: RM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023",
          "mechanism": "Actual IAB rendered #content and DOM snapshot",
          "source_native_acceptance": false,
          "workflow_adoption": false
        },
        "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
        "DOM_snapshot_sha256": "56866acd9b713f351889ef2731ef171bade4c16f48aa1cda8687f17a1a21be2a",
        "capture_metadata_sha256": "cf09ddef497b1350291ad0eccb94c15ee73fd61d8ee87b12b6325e5e600da892",
        "main_characters": 2741,
        "maintext_url": "/service/sources/RM10210.120-r22-main.txt",
        "snapshot_url": "/service/sources/RM10210.120-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      },
      "GN00201.015": {
        "source_code": "GN00201.015",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0200201015",
        "captured_utc": "2026-10-31T16:40:39.860Z",
        "capture_metadata": {
          "captured_utc": "2026-10-31T16:40:39.860Z",
          "url": "https://secure.ssa.gov/poms.nsf/lnx/0200201015",
          "title": "SSA - POMS: GN 00201.015 - Signature Methods for Benefit Applications - 07/22/2026",
          "mechanism": "Actual IAB rendered #content and DOM snapshot",
          "source_native_acceptance": false,
          "workflow_adoption": false
        },
        "maintext_sha256": "8ad4b198abd95e3df3ce2912ff5ca2ff7e99de3c0266c61cae08b2fbd9b76afb",
        "DOM_snapshot_sha256": "2d528ae5dceff74434a3b851a3e2dab9be04e3065a501dff407c12f68908611c",
        "capture_metadata_sha256": "54e3e7c8817ab8c7b5763fefeddf210514f75cb65559067ad3b99dde7a03332b",
        "main_characters": 17432,
        "maintext_url": "/service/sources/GN00201.015-r22-main.txt",
        "snapshot_url": "/service/sources/GN00201.015-r22-DOM-snapshot.txt",
        "capture_scope": "Retain actual capture metadata: expanded FAQ or whole-visible-body fallback where stated; not raw HTTP or unexpanded FAQ completeness.",
        "whole_page_or_native_acceptance": false
      }
    },
    "source_objects": {
      "r22_WSUcoord_selected": {
        "code": "GN 01070.781",
        "title": "Selected WSU coordination exceptions",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
        "revision": "05/04/2022 - Present",
        "transmittal": "TN 64 (03-26)",
        "kind": "Captured official POMS — selected source-bound draft exceptions",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the draft exception conditions/actions in the separate ledger; no whole-case, operational or native acceptance."
      },
      "r22_WSUdiary_selected": {
        "code": "GN 01070.782",
        "title": "Selected WSU diary-routing exceptions",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070782",
        "revision": "09/09/2025 - Present",
        "transmittal": "TN 63 (09-25)",
        "kind": "Captured official POMS — selected source-bound draft exceptions",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the draft exception conditions/actions in the separate ledger; no whole-case, operational or native acceptance."
      },
      "r22_missing_awardssi": {
        "code": "DI 13050.061",
        "title": "Additional selected scenarios: FO Procedures for Title XVI EXR Awards",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413050061",
        "revision": "2012-12-04; TN 22 (09-24)",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_childtermination": {
        "code": "RS 00203.035",
        "title": "Additional selected scenarios: Child’s Benefits Termination of Entitlement",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
        "revision": "2023-09-06; TN 47 (04-26)",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_contact": {
        "code": "SSA guidance",
        "title": "Additional selected scenarios: Update contact information",
        "url": "https://www.ssa.gov/life-events/update-contact-information",
        "revision": "Public page; no revision date asserted",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_extra": {
        "code": "HI 03010.035",
        "title": "Additional selected scenarios: General Information about the Subsidy Application",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0603010035",
        "revision": "2025-12-04",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_identityproof": {
        "code": "SSA guidance",
        "title": "Additional selected scenarios: What to Know about Proving Your Identity",
        "url": "https://www.ssa.gov/news/en/identity-proofing.html",
        "revision": "Public page; no revision date asserted",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_irmaa": {
        "code": "SSA guidance",
        "title": "Additional selected scenarios: Request to lower IRMAA",
        "url": "https://www.ssa.gov/medicare/lower-irmaa",
        "revision": "Public page; no revision date asserted",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_letter": {
        "code": "SSA guidance",
        "title": "Additional selected scenarios: Get benefit verification letter",
        "url": "https://www.ssa.gov/manage-benefits/get-benefit-letter",
        "revision": "Public page; no revision date asserted",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_name": {
        "code": "RM 10212.015",
        "title": "Additional selected scenarios: Evidence Requirements to Process a Name Change on the SSN",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0110212015",
        "revision": "2012-04-16; TN 17 (01-24) displayed",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_signaturemethods": {
        "code": "GN 00201.015",
        "title": "Additional selected scenarios: Signature Methods for Benefit Applications",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0200201015",
        "revision": "2026-07-22",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_missing_ssnassist": {
        "code": "RM 10210.120",
        "title": "Additional selected scenarios: Assisting Applicants When the SSN Application Cannot Be Filed",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
        "revision": "2023-12-28",
        "kind": "Captured official source — selected conditional/channel scenarios only",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the explicit new scenario predicates/actions; detailed linked targets, actual cases and operational execution remain unverified."
      },
      "r22_partial_selected": {
        "code": "GN 01010.110",
        "title": "Selected partial-award control and scope exceptions",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201010110",
        "revision": "06/22/2023 - Present",
        "transmittal": "TN 58 (06-23)",
        "kind": "Captured official POMS — selected source-bound draft exceptions",
        "checked_on": "2026-10-31",
        "verification_scope": "Only the draft exception conditions/actions in the separate ledger; no whole-case, operational or native acceptance."
      }
    },
    "all_ancestor_bindings": {
      "provide-claim-evidence/wsu-third-party-not-yet-valid": [],
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs": [
        {
          "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid",
          "exact_record_without_flow": {
            "id": "wsu-third-party-not-yet-valid",
            "title": "The WSU has not yet obtained a valid third-party application",
            "when": "Staff establish that the third-party WSU claim does not yet have a valid application.",
            "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
            "ssa": "Use the signed-application-and-proofs or only-proofs instruction according to what the claimant actually provides.",
            "route": "Selected source-defined staff handling; no automatic transition",
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
            "source": "r22_WSUcoord_selected",
            "section": "C; C.1",
            "additional_sources": [],
            "owner": "FO",
            "systems": [],
            "entity_ids": [],
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "condition_logic": "all",
            "source_case_conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "source_provenance": [
              {
                "source_code": "GN01070.781",
                "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
                "locator": "C whole, all substeps retained",
                "start": 4807,
                "end": 7452,
                "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
                "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
                "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
              }
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "timing": "No customer completion duration is established.",
            "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_WSU_scenario",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
              "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
              "report": "/service/r22-missing-exception-selected-claims.json"
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
              ]
            },
            "entry_exception_scope": {
              "usual_path_premise_not_inherited": true,
              "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
            },
            "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid"
          }
        }
      ],
      "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation": [
        {
          "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid",
          "exact_record_without_flow": {
            "id": "wsu-third-party-not-yet-valid",
            "title": "The WSU has not yet obtained a valid third-party application",
            "when": "Staff establish that the third-party WSU claim does not yet have a valid application.",
            "you": "Keep your application, proofs and any notices; staff must establish the conditions for this route.",
            "ssa": "Use the signed-application-and-proofs or only-proofs instruction according to what the claimant actually provides.",
            "route": "Selected source-defined staff handling; no automatic transition",
            "next": "Actual completion, receipt and return to the usual path are not established by this illustration.",
            "source": "r22_WSUcoord_selected",
            "section": "C; C.1",
            "additional_sources": [],
            "owner": "FO",
            "systems": [],
            "entity_ids": [],
            "conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "condition_logic": "all",
            "source_case_conditions": [
              "A third-party iClaim is assigned to a WSU.",
              "At the source-defined FO contact, the WSU has not yet obtained a valid application; staff establish this fact rather than infer it from a missing ATTEST date alone.",
              "Proofs or the signed application are provided to the FO under the source C1 contact scope."
            ],
            "source_context_refs": [
              "GN01070.781-C"
            ],
            "source_provenance": [
              {
                "source_code": "GN01070.781",
                "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0201070781",
                "locator": "C whole, all substeps retained",
                "start": 4807,
                "end": 7452,
                "exact_text": "C. \nClaims not attested or receipted in by the WSU\n\nThese instructions pertain to Third Party filed iClaims where the WSU has not yet obtained a valid application by completing one of the actions listed in the above subsection B.\n\nThe FO coordinates with the WSU when a WSU claimant provides their proofs or wet-signed application to the FO, in-person, instead of sending them directly to the WSU.\n\n1. \nAssist claimants who provide their proofs or applications to the FO in-person or by mail\na. \n\nClaimant provides both the application and proofs to the FO\n\nIf the claimant provides both the signed application and proofs to the FO, the FO claims specialist will take jurisdiction of claim by following these steps in this subsection:\n\n•\n\nCall or email the WSU and ask them to transfer jurisdiction of the claim in MCS.\n\n•\n\nReceipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate claim, transfer to DDS).\n\nb. \n\nClaimant provides only the proofs to the local FO before the WSU attests and receipts the application\n\nIf the claimant provides only the proofs to the local FO before the WSU attests and receipts the application (whether the claimant mailed the application yet), offer to reprint the application and complete the adjudication of the claim immediately. The FO claim technician will take jurisdiction and complete the adjudication of the claim by following the steps below\n\n•\n\nCall or email the WSU immediately and ask them to transfer jurisdiction of the claim to the FO. Receipt in the claim by accessing #7 Claims Movement on the MCS Menu.\n\n•\n\nObtain a wet signature on the reprinted application, per the witnessed signature procedures in GN 00201.015 or complete a verbal attestation with the claimant.\n\n•\n\nAnnotate the ATTEST issue on the MCS DW01 screen to indicate that we received a signed application (witnessed signature).\n\n•\n\nReceipt in the claim and all proofs on the MCS DW01 screen.\n\n•\n\nReturn the signed application to the claimant. Include the witnessed signature cover notice in GN 00201.015.\n\n•\n\nTake appropriate action as necessary, (i.e. adjudicate the claim, transfer to DDS).\n\nNOTE: If a WSU receives a signed application after transferring jurisdiction to the FO for adjudication, the WSU should send the signed application to the FO of jurisdiction.\n\n",
                "span_sha256": "aae7376bf0294041d3592935705f6bd15cd9e7e7b5c413b8180b0b4511737a77",
                "maintext_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b"
              }
            ],
            "qualifications": [
              "Choosing this source-qualified example does not establish actual case facts, applicant authority, signature validity, evidence acceptance, completed transfer or adjudication.",
              "Timing instructions and internal diary periods are not measured benefit-processing times or customer decision deadlines.",
              "Named MCS/CCE/WSU/PC/MDW records are source context only; no new native identity, alias, relationship or current interface is asserted.",
              "Linked evidentiary, proper-applicant, signature, notice and system-manual details are not silently expanded."
            ],
            "timing": "No customer completion duration is established.",
            "review_status": "Selected published WSU scenario; actual case facts and internal execution unverified.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_WSU_scenario",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "8cf413c8593953745cf1f1958790748973407779d8552ba072c6440896eb563b",
              "snapshot_path": "/service/sources/GN01070.781-r22-main.txt",
              "report": "/service/r22-missing-exception-selected-claims.json"
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual signature/evidence/claim action, recipient receipt and case outcome remain unverified."
              ]
            },
            "entry_exception_scope": {
              "usual_path_premise_not_inherited": true,
              "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
            },
            "full_route": "provide-claim-evidence/wsu-third-party-not-yet-valid"
          }
        }
      ],
      "provide-claim-evidence/wsu-EVID-unavailable-evidence-route": [],
      "provide-claim-evidence/wsu-first-party-ATTEST-date-not-entered": [],
      "provide-claim-evidence/wsu-appointment-cancellation-not-agreed": [],
      "provide-claim-evidence/wsu-two-unsuccessful-appointment-contacts": [],
      "provide-claim-evidence/wsu-managers-mutual-transfer": [],
      "provide-claim-evidence/wsu-signed-application-arrives-after-transfer": [],
      "resolve-partial-award/partial-future-event-diary": [],
      "resolve-partial-award/partial-RPOC-not-available": [],
      "resolve-partial-award/partial-pending-DIB-separate-other-benefit": [],
      "change-name/name-event-document-needs-additional-identity": [],
      "change-name/name-expired-prior-name-identity": [],
      "change-name/name-surname-component-can-link": [],
      "change-name/name-unlinked-surname-prior-event": [],
      "change-name/name-unlinked-surname-no-event": [],
      "apply-extra-help/extra-help-deemed-group": [],
      "apply-extra-help/extra-help-state-own-application": [],
      "apply-extra-help/extra-help-language-facsimile": [],
      "apply-extra-help/extra-help-resources-question-state-route": [],
      "lower-irmaa/irmaa-amended-return-contact": [],
      "lower-irmaa/irmaa-fax-mail-life-change": [],
      "lower-irmaa/irmaa-outside-US-appointment": [],
      "update-contact/contact-email-account-path": [],
      "update-contact/contact-not-already-benefits": [],
      "update-contact/contact-paper-check-unable-online": [],
      "update-contact/contact-outside-US-appointment": [],
      "get-benefit-letter/benefit-letter-automated-phone": [],
      "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion": [],
      "cdb-marriage-benefit-review/cdb-marriage-spouse-SSI-only": [],
      "cdb-marriage-benefit-review/cdb-marriage-spouse-excluded-child-benefit": [],
      "cdb-marriage-benefit-review/cdb-spouse-disability-benefit-later-terminates": [],
      "ssn-evidence-hard-to-obtain/ssn-benefit-agency-evidence-help": [],
      "ssn-evidence-hard-to-obtain/ssn-parallel-FO-evidence-help": [],
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed": [],
      "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed/ssn-all-leads-data-evidence-unattainable": [
        {
          "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed",
          "exact_record_without_flow": {
            "id": "ssn-evidence-efforts-failed",
            "title": "Evidence efforts have failed",
            "when": "All efforts to produce the required SSN evidence have failed.",
            "you": "Keep the relevant request, notice and documents; this example does not establish the conditions for your case.",
            "ssa": "Contact the Regional Office for guidance. This does not waive the required information or evidence or establish what the Regional Office will advise.",
            "route": "Selected published condition or service option; no automatic transition",
            "next": "Actual completion, response, benefit or record outcome and return to the usual path remain unverified.",
            "source": "r22_missing_ssnassist",
            "section": "A final bullet and note",
            "additional_sources": [],
            "owner": "SSA staff",
            "systems": [],
            "entity_ids": [],
            "conditions": [
              "The source assistance scope applies and efforts to produce the required evidence have failed."
            ],
            "condition_logic": "all",
            "source_case_conditions": [
              "The source assistance scope applies and efforts to produce the required evidence have failed."
            ],
            "source_context_refs": [
              "RM10210.120-whole"
            ],
            "source_provenance": [
              {
                "source_code": "RM10210.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
                "locator": "Whole captured expanded main/visible-body text; conditions and references retained",
                "start": 0,
                "end": 2741,
                "exact_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
                "span_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
                "maintext_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c"
              }
            ],
            "qualifications": [
              "Selecting a route does not establish its facts, evidence acceptability, successful submission, benefit entitlement, completed record action or recipient receipt.",
              "These are selected published instructions or service options, not complete eligibility, identity, signature, legal-status, fee or notice decisions.",
              "Linked target procedures remain separately unreviewed unless explicitly supplied; no invented fallback, deadline or automatic rejoin.",
              "No new native system identity, alias, graph edge or operational acceptance is asserted."
            ],
            "timing": "No measured end-to-end completion duration or automatic date calculation is supplied.",
            "review_status": "Selected source-qualified scenario; detailed dependencies and actual case execution unverified.",
            "source_qualified_branch": {
              "kind": "source_qualified_condition",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "scenario_kind": "source_qualified_condition",
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
              "snapshot_path": "/service/sources/RM10210.120-r22-main.txt",
              "report": "/service/r22-missing-exception-selected-claims.json"
            },
            "full_route": "ssn-evidence-hard-to-obtain/ssn-evidence-efforts-failed",
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual source conditions, execution and case outcome remain unverified."
              ]
            }
          }
        }
      ],
      "benefit-upload-signature/uploaded-firstparty-CPAS-application": []
    },
    "entry_exception_scopes": {
      "provide-claim-evidence/wsu-third-party-not-yet-valid": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
      },
      "provide-claim-evidence/wsu-signed-application-arrives-after-transfer": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
      },
      "resolve-partial-award/partial-future-event-diary": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
      },
      "resolve-partial-award/partial-pending-DIB-separate-other-benefit": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a related source-defined entry exception. The usual-path story does not establish its validity, partial-award status or case stage. Only this route’s actual conditions apply."
      },
      "apply-extra-help/extra-help-deemed-group": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
      },
      "apply-extra-help/extra-help-state-own-application": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
      },
      "apply-extra-help/extra-help-resources-question-state-route": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
      },
      "exr-award-ssi/ssi-EXR-provisional-benefits-fee-exclusion": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This fee-specific route also applies while applying for Title XVI EXR or during a related appeal. It does not require the usual award story’s favorable medical decision."
      },
      "benefit-upload-signature/uploaded-firstparty-CPAS-application": {
        "usual_path_premise_not_inherited": true,
        "mandatory_visible_note": "This is a separate source-defined method or condition. The usual-path story does not establish this route’s case facts or completed actions."
      }
    },
    "source_C_legacy_gate_requirement": {
      "affected_full_routes": [
        "provide-claim-evidence/wsu-third-party-not-yet-valid",
        "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-signed-application-and-proofs",
        "provide-claim-evidence/wsu-third-party-not-yet-valid/wsu-only-proofs-before-attestation",
        "provide-claim-evidence/wsu-signed-application-arrives-after-transfer"
      ],
      "override_only_if_complete_record_flow_journey_sources_and_all_ancestors_exact": true,
      "default_decision_is_not_case_truth": true,
      "mismatched_or_unreviewed_flow_preserves_legacy_fallback": true,
      "case_facts_not_automatically_selected_or_changed": true
    },
    "no_uniform_card_count": true,
    "preserve_all_prior_records_and_forks": true,
    "no_native_alias_edge_or_acceptance": true,
    "activation": false
  },
  "selected_flow_count": 274,
  "complete_policy_review": false,
  "activation": false,
  "legacy_work_report16": {
    "schema": "securitystat.source-bound-exception-flow-package/1",
    "status": "SELECTED_WORK_REPORT_SEQUENCE_SOURCE_REVIEW",
    "baseline_frozen_R22_data_sha256": "6a283390aff1728ab2d92cf5ae7b8538f8257b4b4116fc09e37258a6df623674",
    "ranked_cluster_input_sha256": "3fc59056ba28ba22494c1a08540fd87f3f1322d1da9edc0bca7e501b58890dcf",
    "source_capture": {
      "manifest_sha256": "30b72542b0d2f47d922fc569200ecae31be294e8e2046cee7a18b2a4a70f22da",
      "metadata": {
        "code": "DI13010.020",
        "title": "SSA - POMS: DI 13010.020 - Work Reports and Receipts - 06/14/2024",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010020",
        "captured_utc": "2026-10-31T18:06:40.701Z",
        "characters": 10383,
        "scope": "Whole actual rendered source capture for future legacy16 route migration; no source acceptance or current candidate changes."
      },
      "maintext_sha256": "2a6a7fdc649930b204a43924ba46f3c7b5b57223ce5ad50ef2009e095a3350ea",
      "snapshot_sha256": "c5996204dca45ac5d8ac8a6f09baa2d2fd38bc6e4cb586cb08db0d62a035f833",
      "capture_type": "Whole actual Browser rendered content and DOM/accessibility snapshot; not raw HTTP"
    },
    "fresh_vs_R16_source_diff": {
      "fresh_main_sha256": "2a6a7fdc649930b204a43924ba46f3c7b5b57223ce5ad50ef2009e095a3350ea",
      "prior_main_sha256": "2a6a7fdc649930b204a43924ba46f3c7b5b57223ce5ad50ef2009e095a3350ea",
      "byteexact": true,
      "bytes": 10523,
      "characters": 10383,
      "no_date_based_priority": true
    },
    "source_contexts": {
      "DI13010.020-whole": {
        "source_code": "DI13010.020",
        "start": 0,
        "end": 10383,
        "exact_text": "Effective Dates: 06/14/2024 - Present\nPrevious | Next\n\nTN 84 (01-25)\n\nDI 13010.020 Work Reports and Receipts\nA. \nDescription of a work report\n\nA work report is a report of a change in work activity or earnings for a beneficiary receiving title II or title XVI disability benefits. We receive work reports by phone, fax, mail, or in person.\n\nThe report may include documentation of earnings, such as:\n\n•\n\npay stubs,\n\n•\n\na W2,\n\n•\n\na tax return, or\n\n•\n\na written or verbal statement that work activity has started, stopped, or changed in some way (i.e., a reduction, or increase in pay or hours).\n\nB. \nExplaining reporting responsibilities\n\nTake every opportunity to tell beneficiaries or their representative payees to promptly report any changes in work activity. Remind them that work activity and earnings may affect benefits, and they must tell us right away if:\n\n•\n\nwork starts or stops;\n\n•\n\nduties, hours, or pay changes; or\n\n•\n\nthey stop paying for items or services needed for work due to the disability.\n\nRemind title XVI and concurrent beneficiaries, deemors, and representative payees to report monthly earnings as soon as possible. For more information on SSI monthly wage reporting, see SI 00820.143.\n\nSee also:\n\nDI 10505.005 Determining and Verifying Gross Earnings from Employment\n\nC. \nReceipts for work reports\n1. \nMandatory issuance of receipts for reports of a change in work activity or earnings\n\nSection 202 of the Social Security Act of 2004 requires us to issue a receipt when we receive a report of a change in work activity or earnings status from a disabled beneficiary, or their representative. The receipt acknowledges that the beneficiary (or representative) gave us information about a change in their work or earnings, and documents the date that we received the report.\n\n \n\nIf you receive a work report from one of the following\n\n\t\n\nThen send the receipt to one of the following:\n\n\n\n•\n\nbeneficiary;\n\n•\n\nrepresentative payee;\n\n•\n\nappointed representative; or\n\n•\n\ntitle XVI deemor.\n\n\t\n•\n\nbeneficiary;\n\n•\n\nrepresentative payee; or\n\n•\n\nappointed representative.\n\nTo establish a work report in the appropriate system and issue a receipt follow the instructions in this section. For in-person and telephone reports from the beneficiary or payee, give or mail the receipt to the reporter immediately. For mailed or faxed reports, or reports dropped off in the field office (FO), establish the work report and mail the receipt within five days of receipt of the information.\n\nIf eWork is unavailable, or the case is an Supplemental Security Income (SSI) Monthly Wage Verification (SSIMWV) exclusion, issue a SSA-724 (Work Report Receipt) to the reporter through the Document Processing System (DPS). For more information on the DPS, go to the Boston Regional Site.\n\nSee also:\n\n•\n\nGN 03910.020 Who Is a Representative\n\n•\n\nSI 01320.001 Deeming of Income-Background\n\n•\n\nSI 00820.143 Monthly Wage Reporting\n\n2. \nWhen receipts are not mandatory\n\nReceipts are not mandatory when one of the following happens:\n\n•\n\nyou receive a report from someone other than the beneficiary, payee, appointed representative, or deemor (for example, a sheltered workshop that reports the income of all employees);\n\n•\n\nthe monthly reported earnings are less than $65 for a title XVI beneficiary who consistently earns less than the $65 earned income exclusion; or\n\n•\n\nyou receive a SSA-821-BK or SSA-820-BK (Work Activity Report) in response to a work review established in eWork resulting from a CDREO alert; or\n\n•\n\nyou receive work information from a CDR mailer, and the work has already been developed.\n\nIf a third party requests a receipt (e.g., deemor), inform them that you will mail the receipt to the beneficiary or the representative payee. Do not issue a receipt directly to the reporter because the receipt contains the beneficiary’s personally identifiable information (PII).\n\nD. \nEstablishing a work report in eWork\n\nEstablish a work report in eWork when you receive information that work and earnings has started, stopped, or changed for a title II or title XVI beneficiary who receives benefits based on disability.\n\nFrom the eWork main menu:\n\n1. \n\nSelect Initiate/Update Work Report.\n\n2. \n\nReview the Development Summary block. If there is a pending work review, go to DI 13010.020F in this section.\n\n3. \n\nReview the list of employers. If the work report is from an employer already listed, select “Add” beside the employer to update the work activity information. CAUTION: Do not select “Edit” or this will bring in prior work reports showing the earlier initiation date for the same employer.\n\n4. \n\nIf eWork does not list the employer, select “New Employer” at the bottom of the list.\n\n5. \n\nComplete the Employment Input Screen with as much information as the beneficiary can provide about the work activity. Select “Submit and Close.”\n\n6. \n\nFor title XVI and concurrent cases, the “PushT16WrkRpt” screen appears next. Complete the screen with the additional information requested, and to establish a modernized development worksheet (MDW) or development worksheet (DWO1) issue, select one of the following:\n\n•\n\n“READY”: Send to PCOM”\n\n•\n\n“SKIP”: No MDW, or MSSICCS input needed\n\nYou cannot enter a work report for a title XVI deemor into eWork. If a title XVI deemor is reporting their own monthly earnings, follow SI 00820.143.\n\nUse SSI Monthly Wage Verification (SSIMWV) to record the deemor’s wages and issue a receipt to the beneficiary or the beneficiary’s representative payee as appropriate.\n\nIf the title XVI deemor reports that they will soon start working and does not yet have paystubs, or the case is an SSIMWV exclusion, use DPS to issue a SSA-L724 (Work Report Receipt) to the beneficiary or representative payee. For the fill-in information, provide a brief, one sentence summary of the work report information.\n\nE. \nWork report pending\n\nIf a work report for the same employer is pending in eWork:\n\n1. \n\nDetermine if the current report will change the information from the prior report, or is a report for a new period of employment. If the report:\n\n•\n\nis for a new period of employment, select “Add”; or\n\n•\n\ninvolves work from the same period of employment that is already shown, select “Edit.”\n\n2. \n\nIssue a new receipt if the reporter is the beneficiary, the representative payee, or appointed representative.\n\nF. \nWork review pending\n\nIf the Development Summary block shows that a work review is pending, establish the work report. eWork automatically assigns the work report to the office with jurisdiction of the pending work review.\n\nIMPORTANT: If the beneficiary indicates that they have moved, or wants your office to handle the work review, contact the office with jurisdiction and ask them to transfer the work review to you. After you transfer jurisdiction in eWork, the system automatically transfers the work review in the disability control file (DCF).\n\nG. \nPay stub reports and receipts\n\nWhen a technician has already established the employer in eWork with a work report, the “Pay Stub Report” feature is only available to input earnings for title II beneficiaries. The pay stub report does not evaluate the affect that earnings have on benefits or provide controls similar to the work report.\n\nTo avoid incorrect payments for both title II and title XVI, make sure you evaluate regular, ongoing pay stub reports for a change that could affect the beneficiary’s eligibility to disability.\n\n1. \nProcessing title II pay stub reports\n\nIf you receive pay stubs from a title II beneficiary, check the Development Worksheet in eWork to determine if there is a pending work review. Take the following actions if:\n\n•\n\nThere is a pending work review, send the pay stubs to the FO responsible for the work review. If the work review belongs to another jurisdiction, alert them of the pay stub input, and establish a one-day tickle on the developmental worksheet (DW) in eWork; or\n\n•\n\nA work review is not pending, click on the “View/Update Pay Stub Report” link from the eWork main menu. If the employer has not been established in the Pay Stub Report listing, return to the eWork main menu to establish a Work Report, and issue a receipt, per DI 13010.020B in this section. Then input the paystub information.\n\n•\n\nIf the current employer is present in the Pay Stub Report listing, input the information in the Pay Stub Report input screen.\n\n•\n\nIssue a receipt to the reporter if they meet the conditions as stated in DI 13010.020C.1. in this section.\n\nIMPORTANT: If you are unable to use eWork, fax the pay stubs into Evidence Portal (EP) and issue the SSA-L724 through DPS. Alert the technician who is responsible for evaluating the work activity according to local procedures. If you verified paystubs in eWork, you can return the paystubs to the beneficiary. You do not need to fax the paystubs into eView or Evidence Portal (EP).\n\n2. \nProcessing concurrent monthly pay stub reports\n\nUse the SSIMWV system to record pay stubs for a concurrent regular earnings reporter. For policy on monthly wage reporting, see SI 00820.143. If the paystubs are for a first time report of work or change of work:\n\n•\n\nestablish a work report in eWork, and\n\n•\n\nsend the paystubs to the technician who is responsible for evaluating the earnings, following local procedures.\n\n3. \nProcessing pay stubs for concurrent cases that involve work incentives\n\nIf the case is in MSSICS, you cannot enter pay stubs for concurrent cases involving blind work expenses (BWEs) or impairment-related work expenses (IRWEs) into the SSIMWV program. To process monthly pay stubs in concurrent cases that involve BWEs or IRWEs, see SI 00820.144. Make sure the person responsible for the title II decision is aware of any IRWEs.\n\n4. \nProcessing title XVI only monthly pay stub reports\n\nTo process title XVI only pay stub reports, follow SI 00820.143 and SI 00820.144\n\nIt is mandatory to attempt to recruit beneficiaries to report monthly wages via the SSITWR system. For more information on the SSITWR system, see SI 00820.144.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0413010020\n\t\nDI 13010.020 - Work Reports and Receipts - 06/14/2024\nBatch run: 03/25/2025\nRev:06/14/2024\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "text_sha256": "2a6a7fdc649930b204a43924ba46f3c7b5b57223ce5ad50ef2009e095a3350ea"
      }
    },
    "original_records": {
      "report-ssi-wages/ssi-deemor-starting-work-no-paystubs-receipt": {
        "id": "ssi-deemor-starting-work-no-paystubs-receipt",
        "title": "Someone whose income affects SSI will start work but has no pay stubs yet",
        "when": "A Title XVI deemor reports that they will soon start working and does not yet have pay stubs. A deemor is someone whose income may count toward another person’s SSI. This branch concerns that upcoming-work report, not routine monthly wages already supported by pay stubs.",
        "you": "Tell SSA who will start work, when the work is expected to start, and which SSI recipient the report concerns. Explain that pay stubs are not yet available and keep your report details. Ask how the recipient or representative payee will receive the acknowledgement.",
        "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. For the selected soon-to-start/no-paystub condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence report summary. D separately routes the deemor’s own monthly earnings through SI00820.143 and SSIMWV. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
        "owner": "SSA technician receiving the deemor work report",
        "systems": [
          "Document Processing System (DPS)",
          "SSA-L724 Work Report Receipt"
        ],
        "route": "Upcoming-work report from deemor without pay stubs -> staff DPS receipt -> beneficiary or representative payee",
        "next": "Ask SSA whether further wage reporting or evidence will be needed when work begins. A receipt acknowledges the report and does not decide the SSI payment or deeming result.",
        "source": "workreceipt",
        "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
        "timing": "D supplies no separate deadline for the selected upcoming-work receipt. C.1 timing depends on the stated reporter/channel conditions;its immediate beneficiary/payee instruction is not extended to the deemor. No benefit-decision or payment-adjustment deadline is established.",
        "review_status": "Selected whole official DI13010.020D checked2026-10-26 with C.1-C.2 receipt/privacy context. Soon-to-start work/no paystub condition retained;no deemor eWork input,SSA-L724 through DPS to beneficiary/payee. Routine monthly earnings and excluded SSIMWV cases remain separate. Customer definition/explanation and staff-role label editorial;no completed deeming determination or runtime certification.",
        "source_receipt": {
          "report": "service-deemor020D-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-ssi-wages/ssi-consistent-under65-receipt-exception": {
        "id": "ssi-consistent-under65-receipt-exception",
        "title": "Your SSI earnings report meets a narrow receipt exception",
        "when": "You are a Title XVI beneficiary reporting monthly earnings below $65 and you consistently earn below the $65 earned-income exclusion. Both the current monthly amount and the consistent earnings pattern must fit this specified receipt rule.",
        "you": "Continue reporting earnings and work changes as required. Keep your own record of what you reported and ask SSA whether this particular receipt exception applies. Do not treat a missing receipt as a decision about the amount of SSI due.",
        "ssa": "DI13010.020C.2 says a work-report receipt is not mandatory when monthly reported earnings are less than $65 for a Title XVI beneficiary who consistently earns less than the $65 earned-income exclusion. This is a receipt-issuance exception only. B still instructs staff to explain prompt work-change reporting and monthly earnings reporting. C.1 reporter,recipient and channel rules and the other C.2 exceptions remain separate.",
        "owner": "SSA technician receiving the SSI earnings report",
        "systems": [],
        "route": "SSI monthly earnings report -> staff checks both stated low-earnings conditions -> receipt requirement reviewed separately from earnings evaluation",
        "next": "Ask what further reporting or evidence SSA needs. The receipt exception does not by itself establish countable income, an SSI payment amount, eligibility or a work incentive.",
        "source": "workreceipt",
        "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
        "timing": "C.2 gives no separate completion deadline for this exception. The C.1 immediate/five-day receipt rules remain subject to their own conditions; this branch creates no benefit-decision deadline or new mailing guarantee.",
        "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Current monthly amount AND consistent pattern retained. Customer explanation editorial; receipt not mandatory does not mean reporting is optional or a receipt is prohibited. Benefit computation and other reporting exceptions remain separately held.",
        "source_receipt": {
          "report": "service-ssi-low65-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-ssi-wages/ssi-deemor-ssimwv-exclusion-receipt": {
        "id": "ssi-deemor-ssimwv-exclusion-receipt",
        "title": "A report about someone whose income affects SSI is excluded from SSIMWV",
        "when": "SSA identifies a Title XVI deemor report as an SSIMWV exclusion. A deemor is someone whose income may count toward another person’s SSI. This branch does not determine which cases meet an exclusion.",
        "you": "Explain which SSI recipient the report concerns and keep the details you gave SSA. Ask how the recipient or representative payee will receive the work-report acknowledgement.",
        "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. Under the selected SSIMWV-exclusion condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence summary of the work report. The separate routine monthly-wage route and soon-to-start/no-paystub condition remain distinct. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
        "owner": "SSA technician handling the deemor work report and receipt",
        "systems": [
          "Document Processing System (DPS)",
          "SSA-L724 Work Report Receipt"
        ],
        "route": "Deemor report identified by SSA as an SSIMWV exclusion -> staff DPS receipt -> beneficiary or representative payee",
        "next": "Keep the report details and ask SSA which wage information or follow-up is still needed. This receipt acknowledges the report;it does not establish a wage-input fallback, decide the exclusion or determine the SSI payment.",
        "source": "workreceipt",
        "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
        "timing": "D supplies no separate deadline for this selected receipt route. C.1 timing remains subject to the stated reporter andchannel conditions;its immediate beneficiary/payee instruction is not generalized to a deemor. No payment-adjustment or benefit-decision deadline is established.",
        "review_status": "Whole official DI13010.020D with C.1-C.2 checked2026-10-26. Selected TitleXVI deemor SSIMWV-exclusion receipt route only;SSA identifies the exclusion. No new exclusion criteria,alternative wage input orpayment decision. Existing soon-to-start/no-paystub andconcurrentG3 branches remain separate. Channel/reporter timing andprivacy qualifications retained;customer explanation/staff-role label editorial;no internal execution certified.",
        "source_receipt": {
          "report": "service-deemor-ssimwv-exclusion-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/workreview-owner": {
        "id": "workreview-owner",
        "title": "A review is already pending",
        "when": "eWork shows a pending review.",
        "you": "Tell SSA about a move or a request to change office.",
        "ssa": "Contact the existing owner for transfer if needed.",
        "route": "Existing owner → agreed receiving office",
        "next": "Jurisdiction transfer in eWork also transfers the DCF review.",
        "source": "workreceipt",
        "section": "F",
        "timing": "No branch completion time established",
        "review_status": "Selected public branch checked; remaining cross-references open"
      },
      "report-disability-work/receipt-exception": {
        "id": "receipt-exception",
        "title": "A routine review form was requested",
        "when": "The form responds to a CDREO-triggered eWork review.",
        "you": "Retain your submission record.",
        "ssa": "Apply the receipt exception in C.2.",
        "route": "Existing review",
        "next": "A new receipt is not mandatory for this specified situation.",
        "source": "workreceipt",
        "section": "C.2",
        "timing": "No branch completion time established",
        "review_status": "Selected public branch checked; remaining cross-references open"
      },
      "report-disability-work/titleii-paystubs-pending-work-review": {
        "source": "workreceipt",
        "section": "G opening; G.1",
        "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
        "source_receipt": {
          "report": "service-batch14-workreport-preparation.json",
          "snapshot_path": "sources\\workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-25"
        },
        "id": "titleii-paystubs-pending-work-review",
        "title": "Your pay stubs belong to a pending disability work review",
        "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
        "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
        "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
        "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
        "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
        "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
      },
      "report-disability-work/titleii-paystubs-ework-unavailable": {
        "source": "workreceipt",
        "section": "G opening; G.1",
        "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
        "source_receipt": {
          "report": "service-batch14-workreport-preparation.json",
          "snapshot_path": "sources\\workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-25"
        },
        "id": "titleii-paystubs-ework-unavailable",
        "title": "SSA cannot use eWork for your TitleII pay stubs",
        "when": "The technician is unable to use eWork when handling the TitleII pay-stub report.",
        "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
        "ssa": "Fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. When stubs were verified in eWork, staff may return them; no additional fax into eView or EP is required.",
        "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
        "next": "Receipt issuance and evidence storage do not themselves determine the effect on benefits.",
        "timing": "This fallback paragraph gives no overall evaluation or payment-adjustment deadline."
      },
      "report-disability-work/concurrent-first-work-report-paystubs": {
        "id": "concurrent-first-work-report-paystubs",
        "title": "You receive both SSI and disability benefits and report new or changed work",
        "when": "You receive concurrent Title II disability and SSI benefits, and the submitted pay stubs are for a first report of work or a change in work, rather than only a regular monthly earnings report. This selected branch does not cover concurrent cases involving blind work expenses or impairment-related work expenses.",
        "you": "Tell SSA that you receive both benefits and whether work has just started or changed. Provide the pay stubs SSA requests, keep the report receipt, and ask which technician is evaluating the earnings.",
        "ssa": "DI13010.020G.2 directs staff to establish a work report in eWork and send the pay stubs to the technician responsible for evaluating earnings under local procedures when the pay stubs concern first-time work or a change. Its regular concurrent monthly-report route uses SSIMWV; the first-work/change condition must be identified before applying that routine route.",
        "owner": "SSA intake technician and technician responsible for evaluating the earnings",
        "systems": [
          "eWork",
          "SSIMWV (regular concurrent wage-report context only)"
        ],
        "route": "Concurrent first-work/change report -> eWork work report -> responsible earnings evaluator under local procedures",
        "next": "Ask SSA what follow-up is needed for each benefit. Recording a wage report or issuing a receipt does not itself determine the effect on either benefit. Tell SSA about any disability-related work expenses; their special processing instructions are outside this selected branch.",
        "source": "workreceipt",
        "section": "G.2; C.1 receipt conditions; G.3 held exception context",
        "timing": "G.2 establishes no case-completion deadline. C.1 gives or mails covered beneficiary/payee in-person or telephone report receipts immediately; covered mailed/faxed/dropped-off reports are established and mailed within five days of receipt. These are receipt instructions, not benefit-adjustment deadlines.",
        "review_status": "Selected official G.2/C.1 checked2026-10-26 with G.3 and SI00820.143F.1 context. First-work/change condition retained; BWE/IRWE cases excluded from this selected branch while linked SI00820.144 retrieval remains404. Customer explanation editorial; no whole-page, runtime or benefit-decision certification.",
        "source_receipt": {
          "report": "service-concurrent020-integration-gate.json",
          "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/work-report-same-employer-period-update": {
        "id": "work-report-same-employer-period-update",
        "title": "A report for the same employer is already pending",
        "when": "A work report for the same employer is already pending in eWork,and you provide information that changes that report or concerns a new period of employment. This concerns a pending work report,not by itself a pending work review.",
        "you": "Tell SSA when you previously reported the employer and which dates the new information covers. Explain whether you are correcting the earlier period or reporting a new period of employment. Keep the new receipt and your earlier submission records.",
        "ssa": "DI13010.020E directs staff to determine whether the information concerns a new employment period or the same period already shown. For a new period select Add;for the same period select Edit. Issue a new receipt when the reporter is the beneficiary,representative payee or appointed representative. D separately cautions against using Edit during its initial-report employer-update procedure;F separately governs a pending work review.",
        "owner": "SSA work-report intake technician",
        "systems": [
          "eWork",
          "Work-report receipt"
        ],
        "route": "Identify pending report and employment period -> applicable staff Add/Edit action -> new receipt for the listed reporter",
        "next": "Check that SSA understands the employment period and keep the acknowledgement. Updating the report or issuing a receipt does not decide how work affects benefits.",
        "source": "workreceipt",
        "section": "E whole steps1-2;D/F context only",
        "timing": "E states no case-completion duration or special receipt deadline. Receipt issuance documents the report;it does not establish an earnings decision or payment-adjustment date.",
        "review_status": "Selected official DI13010.020E checked2026-10-26 with D/F context. Same-employer pending-report trigger,new versus same employment period,and beneficiary/payee/appointed-representative receipt list retained. Initial D and pending-review F procedures remain separate. Customer explanation editorial;no benefits determination or runtime certification.",
        "source_receipt": {
          "report": "service-work-report020E-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/titleii-paystubs-employer-not-established": {
        "id": "titleii-paystubs-employer-not-established",
        "title": "SSA needs to establish an employer before recording your pay stubs",
        "when": "You receive Title II disability benefits, no work review is pending, and SSA finds that the employer for the pay stubs you report has not been established in its Pay Stub Report listing.",
        "you": "Provide the employer and work information SSA requests along with your pay stubs. Ask whether your work report and pay-stub information were recorded and whether you should receive a receipt. Keep copies for your records.",
        "ssa": "DI13010.020G.1 directs staff, when no work review is pending and the employer is missing from the Pay Stub Report listing, to establish a Work Report and issue a receipt under the referenced reporting instructions, then input the pay-stub information. G.1 also retains the C.1 reporter conditions for receipts. A pending work review instead follows its responsible-office route; inability to use eWork follows the separate Evidence Portal/DPS route.",
        "owner": "SSA technician receiving the Title II pay-stub report;responsible work-review office only if a review is actually pending",
        "systems": [
          "eWork Work Report and Pay Stub Report (staff use)"
        ],
        "route": "No pending work review -> missing-employer Work Report establishment -> pay-stub entry and applicable receipt",
        "next": "Ask SSA what follow-up is needed for evaluating your work. Recording a report or issuing a receipt does not determine how the work affects benefit entitlement.",
        "source": "workreceipt",
        "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
        "timing": "G.1 gives no customer processing or benefit-decision deadline for this missing-employer route. Its one-day tickle applies to the separate pending-review/other-jurisdiction condition.",
        "review_status": "Selected whole G.1 checked2026-10-26 against revision2024-06-14/TN84(01-25)/batch2025-03-25;C.1/C.2 reporter/privacy conditions retained. Customer explanation editorial;internal execution not independently tested.",
        "source_receipt": {
          "report": "service-work020G1-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/third-party-work-report-receipt-privacy": {
        "id": "third-party-work-report-receipt-privacy",
        "title": "A workplace reports work and asks for a receipt",
        "when": "A sheltered workshop or another reporter outside the beneficiary,representative payee,appointed representative or deemor roles reports work and requests a receipt. This branch concerns the specified third-party reporting situation,not a request by a listed C.1 reporter.",
        "you": "Keep a record of what was submitted and ask SSA about the applicable acknowledgement. If you made the report for someone else,do not expect SSA to send you a receipt containing that person’s private information.",
        "ssa": "C.2 says a receipt is not mandatory for a report from someone outside the listed beneficiary,payee,appointed representative or deemor roles. If a third party requests a receipt,inform them that SSA will mail it to the beneficiary or representative payee. Do not issue the receipt directly to that reporter because it contains the beneficiary’s personally identifiable information. The C.1 mandatory-receipt table and its listed recipient roles remain separate.",
        "route": "Outside third-party work report andreceipt request to SSA;receipt mailed to beneficiary orrepresentative payee ratherthan directly tooutside reporter",
        "next": "Confirm which reporting or follow-up steps still apply. The receipt route protects information;it does not decide the effect of work on benefits or give the reporter access to the beneficiary’s record.",
        "source": "workreceipt",
        "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
        "timing": "C.2 gives no separate completion duration for this selected third-party receipt request. C.1 timing remains subject to its stated reporter/channel conditions;no benefit-decision deadline is established.",
        "review_status": "Whole C.1-C.2 checked2026-10-26 againstretainedofficialDI13010.020. Outside-reporter trigger distinctfrommandatoryC.1reporters andDdeemor soon-to-start/no-paystub route. Customer follow-up explanation editorial;no internal execution orrecord-access right certified.",
        "owner": "SSA technician handling the work report andreceipt request",
        "systems": [],
        "source_receipt": {
          "report": "service-work020C2-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/cdr-mailer-already-developed-receipt-exception": {
        "id": "cdr-mailer-already-developed-receipt-exception",
        "title": "The work in your CDR mailer was already developed",
        "when": "SSA receives work information from a CDR mailer and that work has already been developed. Both the mailer origin and prior work development must apply.",
        "you": "Keep a copy or other submission record. Ask SSA whether the work information was already developed and whether any new or changed work still needs to be reported. Continue reporting work changes as required.",
        "ssa": "DI13010.020C.2 makes a work-report receipt nonmandatory when work information comes from a CDR mailer and the work has already been developed. This selected receipt exception does not determine the medical review outcome or the effect of earnings on benefits. B reporting duties and C.1 reporter, recipient and channel conditions remain separate.",
        "owner": "SSA technician receiving the CDR mailer work information",
        "systems": [],
        "route": "CDR mailer work information -> staff confirms the work was already developed -> receipt requirement considered separately from any benefit or medical review decision",
        "next": "Ask which work information SSA has already developed and whether it needs anything further. A missing receipt alone does not show that the medical review is complete, benefits continue, or additional work information can be omitted.",
        "source": "workreceipt",
        "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
        "timing": "C.2 gives no separate completion deadline for this exception. C.1 immediate/five-day receipt rules retain their own conditions; this branch creates no review-completion or benefit-decision deadline.",
        "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Mailer origin AND already-developed work required. Nonmandatory does not mean receipt issuance is prohibited or reporting is optional. The CDREO-triggered SSA-821-BK/SSA-820-BK exception and other C.2 exceptions remain distinct.",
        "source_receipt": {
          "report": "service-cdr-mailer-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/concurrent-work-expense-ssimwv-exclusion": {
        "id": "concurrent-work-expense-ssimwv-exclusion",
        "title": "You receive both benefits and report disability-related work expenses",
        "when": "You receive concurrent Title II disability and SSI benefits, the case is in MSSICS, and monthly pay stubs involve blind work expenses (BWEs) or impairment-related work expenses (IRWEs). This selected branch concerns the stated input exclusion; it does not decide whether an expense qualifies.",
        "you": "Tell SSA that you receive both benefits and describe the work expenses with your wage report. Ask what evidence and follow-up SSA needs, and ask whether the person handling your Title II decision has been told about any IRWEs. Keep the acknowledgement of your report.",
        "ssa": "DI 13010.020 G.3 says pay stubs for concurrent MSSICS cases involving BWEs or IRWEs cannot be entered into SSIMWV. It refers detailed monthly pay-stub processing to SI 00820.144 and directs staff to make the person responsible for the Title II decision aware of any IRWEs. G.2 regular-report and first-work/change routes remain distinct. The G opening warns that recording pay stubs does not itself evaluate effects on benefits.",
        "owner": "SSA wage-report technician and person responsible for the Title II decision, for the specified IRWE awareness handoff",
        "systems": [
          "MSSICS, stated case condition",
          "SSIMWV, excluded input path for this condition"
        ],
        "route": "Concurrent MSSICS case with BWE or IRWE -> identify SSIMWV input exclusion -> separately obtain applicable wage-processing instructions; notify Title II decision owner of IRWEs",
        "next": "Ask SSA which evidence remains needed for each benefit. This illustration does not determine an allowable expense, a benefit amount or the correct alternative input screen. Detailed SI 00820.144 processing remains an open source gap here.",
        "source": "workreceipt",
        "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
        "timing": "G.3 supplies no deadline for expense development, the staff handoff or a benefit decision. C.1 receipt timing depends on the stated reporter and channel conditions and is not a completion deadline.",
        "review_status": "Whole selected DI 13010.020 G.3 with G opening, G.2 and C.1 checked 2026-10-26; page revision 2024-06-14, TN84 (01-25), batch 2025-03-25. Concurrent MSSICS and BWE/IRWE conditions retained. Title II awareness instruction applies to IRWEs. Linked SI 00820.144 detail remains unverified after preserved404; no fallback screen, expense allowance, physical interface or runtime inferred. Customer explanation editorial.",
        "source_receipt": {
          "report": "service-concurrent-g3-exclusion-integration-gate.json",
          "snapshot_path": "sources/workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-26"
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction": {
        "source": "workreceipt",
        "section": "G opening; G.1",
        "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
        "source_receipt": {
          "report": "service-batch14-workreport-preparation.json",
          "snapshot_path": "sources\\workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-25"
        },
        "id": "another-review-jurisdiction",
        "title": "Another field office owns the pending review",
        "when": "The TitleII pay-stub report belongs to a pending review in another jurisdiction. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
        "you": "Identify the office already reviewing your work and keep your receipt.",
        "ssa": "Send the pay stubs to the responsible review office. Alert that office to the input and establish the stated one-day eWork development-worksheet tickle when using this procedure.",
        "route": "Pay-stub intake → responsible review office in another jurisdiction",
        "next": "The reviewing office evaluates the earnings effect; the tickle is a staff control, not a decision deadline.",
        "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
      },
      "report-disability-work/titleii-paystubs-pending-work-review/ework-not-available": {
        "source": "workreceipt",
        "section": "G opening; G.1",
        "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
        "source_receipt": {
          "report": "service-batch14-workreport-preparation.json",
          "snapshot_path": "sources\\workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-25"
        },
        "id": "ework-not-available",
        "title": "SSA cannot use eWork for your TitleII pay stubs",
        "when": "The parent pending TitleII pay-stub review situation applies and staff are unable to use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
        "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
        "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
        "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
        "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
        "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
        "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction/ework-not-available": {
        "source": "workreceipt",
        "section": "G opening; G.1",
        "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
        "source_receipt": {
          "report": "service-batch14-workreport-preparation.json",
          "snapshot_path": "sources\\workreports020-current-20261025.html",
          "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
          "checked_on": "2026-10-25"
        },
        "id": "ework-not-available",
        "title": "SSA cannot use eWork for your TitleII pay stubs",
        "when": "Another office owns the pending TitleII work review and the intake technician cannot use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
        "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
        "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
        "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
        "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
        "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
        "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
      }
    },
    "flows": {
      "report-ssi-wages/ssi-deemor-starting-work-no-paystubs-receipt": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-deemor-starting-work-no-paystubs-receipt",
        "full_route": "report-ssi-wages/ssi-deemor-starting-work-no-paystubs-receipt",
        "entry_conditions": [
          "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
          "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
        ],
        "steps": [
          {
            "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-1",
            "title": "Keep the deemor input route distinct",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Do not enter the Title XVI deemor work report into eWork. The separate monthly-wage instruction refers to SI00820.143 and SSIMWV.",
            "conditions": [
              "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
              "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
            ],
            "source": "workreceipt",
            "section": "D",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
            ]
          },
          {
            "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-2",
            "title": "Issue the source-specific acknowledgement",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Use DPS to issue SSA-L724 to the beneficiary or representative payee for this soon-to-start/no-pay-stub condition.",
            "conditions": [
              "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
              "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
            ],
            "source": "workreceipt",
            "section": "D",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
            ]
          },
          {
            "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-3",
            "title": "Summarize the report without changing the recipient",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Provide the brief one-sentence work-report summary for the receipt fill-in. Do not give the beneficiary’s private receipt directly to a third-party requester; preserve the source’s beneficiary/payee recipient instruction.",
            "conditions": [
              "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
              "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
            ],
            "source": "workreceipt",
            "section": "D; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-ssi-wages/ssi-consistent-under65-receipt-exception": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-consistent-under65-receipt-exception",
        "full_route": "report-ssi-wages/ssi-consistent-under65-receipt-exception",
        "entry_conditions": [
          "The report is for a Title XVI beneficiary with monthly reported earnings less than $65.",
          "The beneficiary consistently earns less than the source’s $65 earned-income exclusion; both predicates must apply."
        ],
        "steps": [
          {
            "id": "ssi-consistent-under65-receipt-exception-source-step-1",
            "title": "Apply only the narrow receipt exception",
            "kind": "action",
            "actor": "SSA staff",
            "action": "C2 makes the work-report receipt nonmandatory under these two conditions. Reporting duties in B and other receipt/privacy conditions remain; no countable-income or payment conclusion follows.",
            "conditions": [
              "The report is for a Title XVI beneficiary with monthly reported earnings less than $65.",
              "The beneficiary consistently earns less than the source’s $65 earned-income exclusion; both predicates must apply."
            ],
            "source": "workreceipt",
            "section": "C2; B; C1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-ssi-wages/ssi-deemor-ssimwv-exclusion-receipt": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-deemor-ssimwv-exclusion-receipt",
        "full_route": "report-ssi-wages/ssi-deemor-ssimwv-exclusion-receipt",
        "entry_conditions": [
          "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
          "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
        ],
        "steps": [
          {
            "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-1",
            "title": "Keep the deemor report out of eWork",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The source says a Title XVI deemor work report cannot be entered into eWork; the separate routine monthly-wage procedure remains linked.",
            "conditions": [
              "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
              "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
            ],
            "source": "workreceipt",
            "section": "D",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-2",
            "title": "Issue the acknowledgement to its stated recipient",
            "kind": "action",
            "actor": "SSA staff",
            "action": "For the SSIMWV-exclusion condition, use DPS to issue SSA-L724 to the beneficiary or representative payee.",
            "conditions": [
              "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
              "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
            ],
            "source": "workreceipt",
            "section": "D",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-3",
            "title": "Keep the summary and privacy scopes",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Provide the brief one-sentence work-report summary. Do not give the beneficiary’s private receipt directly to a third-party requester; preserve the source’s beneficiary/payee recipient instruction.",
            "conditions": [
              "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
              "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
            ],
            "source": "workreceipt",
            "section": "D; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/workreview-owner": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "workreview-owner",
        "full_route": "report-disability-work/workreview-owner",
        "entry_conditions": [
          "The eWork Development Summary block shows a pending work review.",
          "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
        ],
        "steps": [
          {
            "id": "workreview-owner-source-step-1",
            "title": "Establish the work report",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Establish the work report under F. The published instruction says eWork automatically assigns it to the office with jurisdiction of the pending review; this is a source-described logical function, not current runtime verification.",
            "conditions": [
              "The eWork Development Summary block shows a pending work review.",
              "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
            ],
            "source": "workreceipt",
            "section": "F",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
            ]
          },
          {
            "id": "workreview-owner-source-step-2",
            "title": "Request a transfer only under its condition",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If the beneficiary indicates a move or wants this office to handle the review, contact the office with jurisdiction and ask it to transfer the review. The request is not a completed transfer.",
            "conditions": [
              "The eWork Development Summary block shows a pending work review.",
              "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
            ],
            "source": "workreceipt",
            "section": "F IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
            ]
          },
          {
            "id": "workreview-owner-source-step-3",
            "title": "Keep the DCF consequence conditional",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Only after jurisdiction is transferred in eWork does F describe automatic transfer of the work review in the DCF. This example does not establish that either transfer occurred.",
            "conditions": [
              "The eWork Development Summary block shows a pending work review.",
              "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
            ],
            "source": "workreceipt",
            "section": "F IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/receipt-exception": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "receipt-exception",
        "full_route": "report-disability-work/receipt-exception",
        "entry_conditions": [
          "The received form is SSA-821-BK OR SSA-820-BK.",
          "It responds to a work review established in eWork resulting from a CDREO alert; all parts of this condition apply."
        ],
        "steps": [
          {
            "id": "receipt-exception-source-step-1",
            "title": "Keep the receipt exception within that exact form-and-review condition",
            "kind": "action",
            "actor": "SSA staff",
            "action": "C2 makes a new work-report receipt nonmandatory for this specified response. This is not a waiver of work reporting, due process, evaluation or every receipt.",
            "conditions": [
              "The received form is SSA-821-BK OR SSA-820-BK.",
              "It responds to a work review established in eWork resulting from a CDREO alert; all parts of this condition apply."
            ],
            "source": "workreceipt",
            "section": "C2; B; C1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "titleii-paystubs-pending-work-review",
        "full_route": "report-disability-work/titleii-paystubs-pending-work-review",
        "entry_conditions": [
          "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
          "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
          "The technician checks the eWork Development Worksheet and a work review is pending."
        ],
        "steps": [
          {
            "id": "titleii-paystubs-pending-work-review-source-step-1",
            "title": "Check the pending-review information",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Check the eWork Development Worksheet to identify the pending work review; do not substitute the separate E pending-work-report condition.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The technician checks the eWork Development Worksheet and a work review is pending."
            ],
            "source": "workreceipt",
            "section": "G opening; G1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "The one-day eWork tickle belongs only to the other-jurisdiction condition, not every pay-stub report."
            ]
          },
          {
            "id": "titleii-paystubs-pending-work-review-source-step-2",
            "title": "Send the pay stubs to the responsible office",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Send the pay stubs to the FO responsible for the pending work review. Other-jurisdiction alert/tickle handling is a separately conditional follow-up.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The technician checks the eWork Development Worksheet and a work review is pending."
            ],
            "source": "workreceipt",
            "section": "G1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "The one-day eWork tickle belongs only to the other-jurisdiction condition, not every pay-stub report."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/titleii-paystubs-ework-unavailable": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "titleii-paystubs-ework-unavailable",
        "full_route": "report-disability-work/titleii-paystubs-ework-unavailable",
        "entry_conditions": [
          "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
          "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
          "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
        ],
        "steps": [
          {
            "id": "titleii-paystubs-ework-unavailable-source-step-1",
            "title": "Store the pay stubs under the stated fallback",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "titleii-paystubs-ework-unavailable-source-step-2",
            "title": "Issue the fallback receipt",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "titleii-paystubs-ework-unavailable-source-step-3",
            "title": "Alert the evaluating technician",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/concurrent-first-work-report-paystubs": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "concurrent-first-work-report-paystubs",
        "full_route": "report-disability-work/concurrent-first-work-report-paystubs",
        "entry_conditions": [
          "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
          "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
          "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
        ],
        "steps": [
          {
            "id": "concurrent-first-work-report-paystubs-source-step-1",
            "title": "Establish the work report for the first or changed work",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Under G2, establish a work report in eWork for this first-work/change condition. The regular concurrent reporter’s SSIMWV instruction is separate.",
            "conditions": [
              "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
              "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
              "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
            ],
            "source": "workreceipt",
            "section": "G2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "concurrent-first-work-report-paystubs-source-step-2",
            "title": "Send the pay stubs to the evaluating technician",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Send the pay stubs to the technician responsible for evaluating earnings, following local procedures. Recording or acknowledging information is not a benefit decision.",
            "conditions": [
              "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
              "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
              "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
            ],
            "source": "workreceipt",
            "section": "G2; G opening",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/work-report-same-employer-period-update": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "work-report-same-employer-period-update",
        "full_route": "report-disability-work/work-report-same-employer-period-update",
        "entry_conditions": [
          "A work report for the same employer is already pending in eWork.",
          "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review."
        ],
        "steps": [
          {
            "id": "work-report-same-employer-period-update-source-step-1",
            "title": "For a new employment period: Add",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If the report is for a new period of employment, select Add. This is not the same-period Edit instruction.",
            "conditions": [
              "A work report for the same employer is already pending in eWork.",
              "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
              "The report concerns a NEW period of employment."
            ],
            "source": "workreceipt",
            "section": "E1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ],
            "alternative_group": "employment-period"
          },
          {
            "id": "work-report-same-employer-period-update-source-step-2",
            "title": "For the same employment period: Edit",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If the report involves work from the same employment period already shown, select Edit. Do not import D’s initial-report employer-update caution as a prohibition on this E instruction.",
            "conditions": [
              "A work report for the same employer is already pending in eWork.",
              "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
              "The report concerns the SAME period of employment already shown."
            ],
            "source": "workreceipt",
            "section": "E1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ],
            "alternative_group": "employment-period"
          },
          {
            "id": "work-report-same-employer-period-update-source-step-3",
            "title": "Issue a new receipt to the listed reporter",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Issue a new receipt if the reporter is the beneficiary, representative payee or appointed representative. Receipt issuance does not establish an earnings decision.",
            "conditions": [
              "A work report for the same employer is already pending in eWork.",
              "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
              "The reporter is the beneficiary, representative payee OR appointed representative."
            ],
            "source": "workreceipt",
            "section": "E2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "employment-period",
            "label": "Choose the source instruction for the actual employment period",
            "logic": "source_conditions_determine_branch",
            "note": "Add and Edit are alternatives based on the actual period; both are not sequential actions. Unknown or unclear period information establishes neither choice."
          }
        ]
      },
      "report-disability-work/titleii-paystubs-employer-not-established": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "titleii-paystubs-employer-not-established",
        "full_route": "report-disability-work/titleii-paystubs-employer-not-established",
        "entry_conditions": [
          "A Title II beneficiary submits pay stubs and no work review is pending.",
          "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
        ],
        "steps": [
          {
            "id": "titleii-paystubs-employer-not-established-source-step-1",
            "title": "Establish the missing employer’s work report",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Return to the eWork main menu and establish a Work Report under G1’s missing-employer condition.",
            "conditions": [
              "A Title II beneficiary submits pay stubs and no work review is pending.",
              "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
            ],
            "source": "workreceipt",
            "section": "G1; G opening",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "titleii-paystubs-employer-not-established-source-step-2",
            "title": "Apply the stated receipt condition",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Issue the receipt under the referenced work-report and C1 receipt instructions; reporter, recipient, channel and exceptions retain their own conditions.",
            "conditions": [
              "A Title II beneficiary submits pay stubs and no work review is pending.",
              "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
            ],
            "source": "workreceipt",
            "section": "G1; B; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "titleii-paystubs-employer-not-established-source-step-3",
            "title": "Input the pay-stub information",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Then input the pay-stub information. This input does not evaluate its benefit effect or create the work report’s controls.",
            "conditions": [
              "A Title II beneficiary submits pay stubs and no work review is pending.",
              "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
            ],
            "source": "workreceipt",
            "section": "G1; G opening",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/third-party-work-report-receipt-privacy": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "third-party-work-report-receipt-privacy",
        "full_route": "report-disability-work/third-party-work-report-receipt-privacy",
        "entry_conditions": [
          "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
          "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
        ],
        "steps": [
          {
            "id": "third-party-work-report-receipt-privacy-source-step-1",
            "title": "Keep mandatory-receipt and requester rules distinct",
            "kind": "action",
            "actor": "SSA staff",
            "action": "C2 does not make a receipt mandatory for this outside-reporter condition. Do not generalize this exception to listed reporters.",
            "conditions": [
              "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
              "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
            ],
            "source": "workreceipt",
            "section": "C2; C1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "third-party-work-report-receipt-privacy-source-step-2",
            "title": "Protect the receipt’s recipient",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Inform the requester that the receipt will be mailed to the beneficiary or representative payee; do not issue it directly to the reporter because it contains beneficiary PII. No completed mailing or disclosure authority is established.",
            "conditions": [
              "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
              "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
            ],
            "source": "workreceipt",
            "section": "C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/cdr-mailer-already-developed-receipt-exception": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdr-mailer-already-developed-receipt-exception",
        "full_route": "report-disability-work/cdr-mailer-already-developed-receipt-exception",
        "entry_conditions": [
          "The work information comes from a CDR mailer.",
          "That work has already been developed; both source conditions must apply."
        ],
        "steps": [
          {
            "id": "cdr-mailer-already-developed-receipt-exception-source-step-1",
            "title": "Apply only the stated receipt exception",
            "kind": "action",
            "actor": "SSA staff",
            "action": "C2 makes a receipt nonmandatory for work information from a CDR mailer when that work was already developed. B reporting duties remain; this does not complete the medical review or evaluate new work.",
            "conditions": [
              "The work information comes from a CDR mailer.",
              "That work has already been developed; both source conditions must apply."
            ],
            "source": "workreceipt",
            "section": "C2; B; C1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/concurrent-work-expense-ssimwv-exclusion": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "concurrent-work-expense-ssimwv-exclusion",
        "full_route": "report-disability-work/concurrent-work-expense-ssimwv-exclusion",
        "entry_conditions": [
          "The case is concurrent Title II/Title XVI and is in the source-named MSSICS context.",
          "The pay stubs involve BWEs OR IRWEs. This proposal does not determine which expenses qualify or supply the linked alternative input procedure."
        ],
        "steps": [
          {
            "id": "concurrent-work-expense-ssimwv-exclusion-source-step-1",
            "title": "Keep the input exclusion in its exact scope",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Do not enter these concurrent MSSICS-case pay stubs involving BWEs or IRWEs into SSIMWV. Detailed monthly-pay-stub processing is referred to SI00820.144 and remains held here.",
            "conditions": [
              "The case is concurrent Title II/Title XVI and is in the source-named MSSICS context.",
              "The pay stubs involve BWEs OR IRWEs. This proposal does not determine which expenses qualify or supply the linked alternative input procedure."
            ],
            "source": "workreceipt",
            "section": "G3",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "MSSICS is the published system name in this source; no automatic CCE or SSIMWV alias is created. SI00820.144 remains a source gap, not a guessed fallback."
            ]
          },
          {
            "id": "concurrent-work-expense-ssimwv-exclusion-source-step-2",
            "title": "Keep the IRWE notice condition separate",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If IRWEs are involved, make sure the person responsible for the Title II decision is aware of them. Do not broaden this IRWE-specific instruction to every BWE-only case or treat it as a completed handoff.",
            "conditions": [
              "All concurrent MSSICS/work-expense parent conditions apply.",
              "IRWEs are involved; BWE-only involvement does not itself satisfy this step condition."
            ],
            "source": "workreceipt",
            "section": "G3",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "MSSICS is the published system name in this source; no automatic CCE or SSIMWV alias is created. SI00820.144 remains a source gap, not a guessed fallback."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "another-review-jurisdiction",
        "full_route": "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction",
        "entry_conditions": [
          "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
          "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
          "The employer is already established in eWork with a work report.",
          "The Title II work review is pending in ANOTHER jurisdiction."
        ],
        "steps": [
          {
            "id": "another-review-jurisdiction-source-step-1",
            "title": "Send the pay stubs to the responsible review office",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Send the pay stubs to the FO responsible for the pending work review.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The employer is already established in eWork with a work report.",
              "The Title II work review is pending in ANOTHER jurisdiction."
            ],
            "source": "workreceipt",
            "section": "G opening; G1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "another-review-jurisdiction-source-step-2",
            "title": "Alert the other jurisdiction",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Alert the other jurisdiction about the pay-stub input; no completed alert or receipt is established.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The employer is already established in eWork with a work report.",
              "The Title II work review is pending in ANOTHER jurisdiction."
            ],
            "source": "workreceipt",
            "section": "G1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          },
          {
            "id": "another-review-jurisdiction-source-step-3",
            "title": "Establish only the stated staff reminder",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Establish the one-day tickle on the eWork developmental worksheet under this other-jurisdiction condition. It is not a one-day decision deadline, and an unavailable-eWork fallback supplies no invented substitute.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The employer is already established in eWork with a work report.",
              "The Title II work review is pending in ANOTHER jurisdiction."
            ],
            "source": "workreceipt",
            "section": "G1",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/ework-not-available": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ework-not-available",
        "full_route": "report-disability-work/titleii-paystubs-pending-work-review/ework-not-available",
        "entry_conditions": [
          "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
          "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
          "The parent pending Title II pay-stub work-review condition applies.",
          "The employer was already established in eWork with a work report.",
          "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
        ],
        "steps": [
          {
            "id": "ework-not-available-source-step-1",
            "title": "Store the pay stubs under the stated fallback",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The parent pending Title II pay-stub work-review condition applies.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "ework-not-available-source-step-2",
            "title": "Issue the fallback receipt",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The parent pending Title II pay-stub work-review condition applies.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "ework-not-available-source-step-3",
            "title": "Alert the evaluating technician",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The parent pending Title II pay-stub work-review condition applies.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction/ework-not-available": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ework-not-available",
        "full_route": "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction/ework-not-available",
        "entry_conditions": [
          "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
          "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
          "The Title II work review is pending in another office’s jurisdiction.",
          "The employer was already established in eWork with a work report.",
          "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
        ],
        "steps": [
          {
            "id": "ework-not-available-source-step-1",
            "title": "Store the pay stubs under the stated fallback",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The Title II work review is pending in another office’s jurisdiction.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "ework-not-available-source-step-2",
            "title": "Issue the fallback receipt",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The Title II work review is pending in another office’s jurisdiction.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT; C1-C2",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          },
          {
            "id": "ework-not-available-source-step-3",
            "title": "Alert the evaluating technician",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
            "conditions": [
              "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
              "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
              "The Title II work review is pending in another office’s jurisdiction.",
              "The employer was already established in eWork with a work report.",
              "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
            ],
            "source": "workreceipt",
            "section": "G1 IMPORTANT",
            "source_context_refs": [
              "DI13010.020-whole"
            ],
            "qualifications": [
              "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
              "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
              "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
              "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
              "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
              "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
          ]
        }
      }
    },
    "candidate_bindings": {
      "report-ssi-wages/ssi-deemor-starting-work-no-paystubs-receipt": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "ssi-deemor-starting-work-no-paystubs-receipt",
          "full_route": "report-ssi-wages/ssi-deemor-starting-work-no-paystubs-receipt",
          "entry_conditions": [
            "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
            "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
          ],
          "steps": [
            {
              "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-1",
              "title": "Keep the deemor input route distinct",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Do not enter the Title XVI deemor work report into eWork. The separate monthly-wage instruction refers to SI00820.143 and SSIMWV.",
              "conditions": [
                "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
                "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
              ],
              "source": "workreceipt",
              "section": "D",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
              ]
            },
            {
              "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-2",
              "title": "Issue the source-specific acknowledgement",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Use DPS to issue SSA-L724 to the beneficiary or representative payee for this soon-to-start/no-pay-stub condition.",
              "conditions": [
                "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
                "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
              ],
              "source": "workreceipt",
              "section": "D",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
              ]
            },
            {
              "id": "ssi-deemor-starting-work-no-paystubs-receipt-source-step-3",
              "title": "Summarize the report without changing the recipient",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Provide the brief one-sentence work-report summary for the receipt fill-in. Do not give the beneficiary’s private receipt directly to a third-party requester; preserve the source’s beneficiary/payee recipient instruction.",
              "conditions": [
                "The report concerns a Title XVI deemor who will soon start work and does not yet have pay stubs.",
                "This is the D upcoming-work report condition, not routine monthly wages; actual deeming, benefit and privacy facts are not determined."
              ],
              "source": "workreceipt",
              "section": "D; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "The C1 immediate beneficiary/payee rule is not generalized to the deemor. Linked monthly-wage procedures remain unreviewed."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "ssi-deemor-starting-work-no-paystubs-receipt",
          "title": "Someone whose income affects SSI will start work but has no pay stubs yet",
          "when": "A Title XVI deemor reports that they will soon start working and does not yet have pay stubs. A deemor is someone whose income may count toward another person’s SSI. This branch concerns that upcoming-work report, not routine monthly wages already supported by pay stubs.",
          "you": "Tell SSA who will start work, when the work is expected to start, and which SSI recipient the report concerns. Explain that pay stubs are not yet available and keep your report details. Ask how the recipient or representative payee will receive the acknowledgement.",
          "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. For the selected soon-to-start/no-paystub condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence report summary. D separately routes the deemor’s own monthly earnings through SI00820.143 and SSIMWV. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
          "owner": "SSA technician receiving the deemor work report",
          "systems": [
            "Document Processing System (DPS)",
            "SSA-L724 Work Report Receipt"
          ],
          "route": "Upcoming-work report from deemor without pay stubs -> staff DPS receipt -> beneficiary or representative payee",
          "next": "Ask SSA whether further wage reporting or evidence will be needed when work begins. A receipt acknowledges the report and does not decide the SSI payment or deeming result.",
          "source": "workreceipt",
          "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
          "timing": "D supplies no separate deadline for the selected upcoming-work receipt. C.1 timing depends on the stated reporter/channel conditions;its immediate beneficiary/payee instruction is not extended to the deemor. No benefit-decision or payment-adjustment deadline is established.",
          "review_status": "Selected whole official DI13010.020D checked2026-10-26 with C.1-C.2 receipt/privacy context. Soon-to-start work/no paystub condition retained;no deemor eWork input,SSA-L724 through DPS to beneficiary/payee. Routine monthly earnings and excluded SSIMWV cases remain separate. Customer definition/explanation and staff-role label editorial;no completed deeming determination or runtime certification.",
          "source_receipt": {
            "report": "service-deemor020D-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-ssi-wages",
          "category": "SSI",
          "title": "Report monthly SSI wages",
          "short": "Use the reporting route and distinguish reporting dates.",
          "story": "Jane works while receiving SSI and needs to report the month’s wages.",
          "level": "Customer overview",
          "review_status": "Cited core steps checked; exceptions incomplete",
          "scope": "Source-backed core path. Case-specific eligibility, every exception, and internal execution are not fully modeled.",
          "path": [
            "You",
            "Wage-reporting service",
            "SSA income record"
          ],
          "channels": {
            "office": "Contact the local office about job changes or reporting problems.",
            "phone": "SSA lists an automated monthly wage-reporting telephone service.",
            "online": "SSA lists online and mobile reporting options; method availability depends on the record."
          },
          "checklist": [
            "Identify monthly wages separately from other income changes.",
            "Choose an official wage-reporting route.",
            "Check the different reporting rules for job changes and other income."
          ],
          "steps": [
            {
              "id": "report-ssi-wages-1",
              "title": "Identify reportable income",
              "you": "Identify wages and other changes that need reporting.",
              "ssa": "SSA distinguishes monthly wages from self-employment and other income changes.",
              "source": "wages",
              "section": "Income you need to report",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Customer → reporting method appropriate to income category",
              "next": "Identify income and changes that need reporting, including spouse income when living together. The public page does not establish internal staff assignment or adjudication screens."
            },
            {
              "id": "report-ssi-wages-2",
              "title": "Report monthly wages",
              "you": "Use the listed online, mobile-app or automated telephone option.",
              "ssa": "The wage-reporting page describes the available reporting methods.",
              "source": "wages",
              "section": "Report wages each month",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Monthly wage report → listed online, app or automated telephone service",
              "next": "SSA’s public guidance says to report monthly wages by the sixth day of the following month. Notify the local office of job changes to keep reporting online. This reporting date is not a processing-time promise."
            },
            {
              "id": "report-ssi-wages-3",
              "title": "Report other changes separately",
              "you": "Notify SSA about job changes and other income changes.",
              "ssa": "Different reporting instructions apply to self-employment and other income.",
              "source": "wages",
              "section": "Report changes in income",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Self-employment or other income change → listed SSA contact",
              "next": "The public page says to report these changes by the tenth day of the month after the change. Annual self-employment reporting has a separate January 10 instruction. Staff processing and any payment effect need separate review."
            }
          ],
          "decision": null,
          "timing": "The wage-reporting page asks for monthly wages by day 6 of the following month and other income changes by day 10. General SSI reporting guidance uses a separate 10-day rule. These are reporting instructions, not a payment-adjustment turnaround promise.",
          "timing_type": "Reporting dates",
          "outcome": "SSA receives a wage report; other income and job changes may require a separate report.",
          "gaps": [
            "Remaining exceptions and cross-references still need expanded workflows.",
            "This explains published instructions; actual processing and internal system behavior were not tested."
          ],
          "source_ids": [
            "wages",
            "ssichanges",
            "ssiwageevidence",
            "ssimonthlywageprocessing",
            "ssiwageestimates",
            "ssiwageverificationcompanies",
            "ssicafeteriaplans",
            "ssireportingresponsibilities",
            "ssinesedetermination",
            "ssineseverification",
            "ssinesecurrentestimate",
            "ssimefmatch",
            "ssialertdevelopment",
            "ssitaxinterview",
            "ssitaxdisclosure",
            "ssiirslimited",
            "irsfulldevelopment",
            "ssipayroll",
            "payrollauthorization",
            "workreceipt",
            "ssiwage135run72"
          ]
        },
        "ancestor_records": [
          {
            "id": "ssi-deemor-starting-work-no-paystubs-receipt",
            "title": "Someone whose income affects SSI will start work but has no pay stubs yet",
            "when": "A Title XVI deemor reports that they will soon start working and does not yet have pay stubs. A deemor is someone whose income may count toward another person’s SSI. This branch concerns that upcoming-work report, not routine monthly wages already supported by pay stubs.",
            "you": "Tell SSA who will start work, when the work is expected to start, and which SSI recipient the report concerns. Explain that pay stubs are not yet available and keep your report details. Ask how the recipient or representative payee will receive the acknowledgement.",
            "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. For the selected soon-to-start/no-paystub condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence report summary. D separately routes the deemor’s own monthly earnings through SI00820.143 and SSIMWV. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
            "owner": "SSA technician receiving the deemor work report",
            "systems": [
              "Document Processing System (DPS)",
              "SSA-L724 Work Report Receipt"
            ],
            "route": "Upcoming-work report from deemor without pay stubs -> staff DPS receipt -> beneficiary or representative payee",
            "next": "Ask SSA whether further wage reporting or evidence will be needed when work begins. A receipt acknowledges the report and does not decide the SSI payment or deeming result.",
            "source": "workreceipt",
            "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
            "timing": "D supplies no separate deadline for the selected upcoming-work receipt. C.1 timing depends on the stated reporter/channel conditions;its immediate beneficiary/payee instruction is not extended to the deemor. No benefit-decision or payment-adjustment deadline is established.",
            "review_status": "Selected whole official DI13010.020D checked2026-10-26 with C.1-C.2 receipt/privacy context. Soon-to-start work/no paystub condition retained;no deemor eWork input,SSA-L724 through DPS to beneficiary/payee. Routine monthly earnings and excluded SSIMWV cases remain separate. Customer definition/explanation and staff-role label editorial;no completed deeming determination or runtime certification.",
            "source_receipt": {
              "report": "service-deemor020D-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-ssi-wages/ssi-consistent-under65-receipt-exception": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "ssi-consistent-under65-receipt-exception",
          "full_route": "report-ssi-wages/ssi-consistent-under65-receipt-exception",
          "entry_conditions": [
            "The report is for a Title XVI beneficiary with monthly reported earnings less than $65.",
            "The beneficiary consistently earns less than the source’s $65 earned-income exclusion; both predicates must apply."
          ],
          "steps": [
            {
              "id": "ssi-consistent-under65-receipt-exception-source-step-1",
              "title": "Apply only the narrow receipt exception",
              "kind": "action",
              "actor": "SSA staff",
              "action": "C2 makes the work-report receipt nonmandatory under these two conditions. Reporting duties in B and other receipt/privacy conditions remain; no countable-income or payment conclusion follows.",
              "conditions": [
                "The report is for a Title XVI beneficiary with monthly reported earnings less than $65.",
                "The beneficiary consistently earns less than the source’s $65 earned-income exclusion; both predicates must apply."
              ],
              "source": "workreceipt",
              "section": "C2; B; C1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "ssi-consistent-under65-receipt-exception",
          "title": "Your SSI earnings report meets a narrow receipt exception",
          "when": "You are a Title XVI beneficiary reporting monthly earnings below $65 and you consistently earn below the $65 earned-income exclusion. Both the current monthly amount and the consistent earnings pattern must fit this specified receipt rule.",
          "you": "Continue reporting earnings and work changes as required. Keep your own record of what you reported and ask SSA whether this particular receipt exception applies. Do not treat a missing receipt as a decision about the amount of SSI due.",
          "ssa": "DI13010.020C.2 says a work-report receipt is not mandatory when monthly reported earnings are less than $65 for a Title XVI beneficiary who consistently earns less than the $65 earned-income exclusion. This is a receipt-issuance exception only. B still instructs staff to explain prompt work-change reporting and monthly earnings reporting. C.1 reporter,recipient and channel rules and the other C.2 exceptions remain separate.",
          "owner": "SSA technician receiving the SSI earnings report",
          "systems": [],
          "route": "SSI monthly earnings report -> staff checks both stated low-earnings conditions -> receipt requirement reviewed separately from earnings evaluation",
          "next": "Ask what further reporting or evidence SSA needs. The receipt exception does not by itself establish countable income, an SSI payment amount, eligibility or a work incentive.",
          "source": "workreceipt",
          "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
          "timing": "C.2 gives no separate completion deadline for this exception. The C.1 immediate/five-day receipt rules remain subject to their own conditions; this branch creates no benefit-decision deadline or new mailing guarantee.",
          "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Current monthly amount AND consistent pattern retained. Customer explanation editorial; receipt not mandatory does not mean reporting is optional or a receipt is prohibited. Benefit computation and other reporting exceptions remain separately held.",
          "source_receipt": {
            "report": "service-ssi-low65-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-ssi-wages",
          "category": "SSI",
          "title": "Report monthly SSI wages",
          "short": "Use the reporting route and distinguish reporting dates.",
          "story": "Jane works while receiving SSI and needs to report the month’s wages.",
          "level": "Customer overview",
          "review_status": "Cited core steps checked; exceptions incomplete",
          "scope": "Source-backed core path. Case-specific eligibility, every exception, and internal execution are not fully modeled.",
          "path": [
            "You",
            "Wage-reporting service",
            "SSA income record"
          ],
          "channels": {
            "office": "Contact the local office about job changes or reporting problems.",
            "phone": "SSA lists an automated monthly wage-reporting telephone service.",
            "online": "SSA lists online and mobile reporting options; method availability depends on the record."
          },
          "checklist": [
            "Identify monthly wages separately from other income changes.",
            "Choose an official wage-reporting route.",
            "Check the different reporting rules for job changes and other income."
          ],
          "steps": [
            {
              "id": "report-ssi-wages-1",
              "title": "Identify reportable income",
              "you": "Identify wages and other changes that need reporting.",
              "ssa": "SSA distinguishes monthly wages from self-employment and other income changes.",
              "source": "wages",
              "section": "Income you need to report",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Customer → reporting method appropriate to income category",
              "next": "Identify income and changes that need reporting, including spouse income when living together. The public page does not establish internal staff assignment or adjudication screens."
            },
            {
              "id": "report-ssi-wages-2",
              "title": "Report monthly wages",
              "you": "Use the listed online, mobile-app or automated telephone option.",
              "ssa": "The wage-reporting page describes the available reporting methods.",
              "source": "wages",
              "section": "Report wages each month",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Monthly wage report → listed online, app or automated telephone service",
              "next": "SSA’s public guidance says to report monthly wages by the sixth day of the following month. Notify the local office of job changes to keep reporting online. This reporting date is not a processing-time promise."
            },
            {
              "id": "report-ssi-wages-3",
              "title": "Report other changes separately",
              "you": "Notify SSA about job changes and other income changes.",
              "ssa": "Different reporting instructions apply to self-employment and other income.",
              "source": "wages",
              "section": "Report changes in income",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Self-employment or other income change → listed SSA contact",
              "next": "The public page says to report these changes by the tenth day of the month after the change. Annual self-employment reporting has a separate January 10 instruction. Staff processing and any payment effect need separate review."
            }
          ],
          "decision": null,
          "timing": "The wage-reporting page asks for monthly wages by day 6 of the following month and other income changes by day 10. General SSI reporting guidance uses a separate 10-day rule. These are reporting instructions, not a payment-adjustment turnaround promise.",
          "timing_type": "Reporting dates",
          "outcome": "SSA receives a wage report; other income and job changes may require a separate report.",
          "gaps": [
            "Remaining exceptions and cross-references still need expanded workflows.",
            "This explains published instructions; actual processing and internal system behavior were not tested."
          ],
          "source_ids": [
            "wages",
            "ssichanges",
            "ssiwageevidence",
            "ssimonthlywageprocessing",
            "ssiwageestimates",
            "ssiwageverificationcompanies",
            "ssicafeteriaplans",
            "ssireportingresponsibilities",
            "ssinesedetermination",
            "ssineseverification",
            "ssinesecurrentestimate",
            "ssimefmatch",
            "ssialertdevelopment",
            "ssitaxinterview",
            "ssitaxdisclosure",
            "ssiirslimited",
            "irsfulldevelopment",
            "ssipayroll",
            "payrollauthorization",
            "workreceipt",
            "ssiwage135run72"
          ]
        },
        "ancestor_records": [
          {
            "id": "ssi-consistent-under65-receipt-exception",
            "title": "Your SSI earnings report meets a narrow receipt exception",
            "when": "You are a Title XVI beneficiary reporting monthly earnings below $65 and you consistently earn below the $65 earned-income exclusion. Both the current monthly amount and the consistent earnings pattern must fit this specified receipt rule.",
            "you": "Continue reporting earnings and work changes as required. Keep your own record of what you reported and ask SSA whether this particular receipt exception applies. Do not treat a missing receipt as a decision about the amount of SSI due.",
            "ssa": "DI13010.020C.2 says a work-report receipt is not mandatory when monthly reported earnings are less than $65 for a Title XVI beneficiary who consistently earns less than the $65 earned-income exclusion. This is a receipt-issuance exception only. B still instructs staff to explain prompt work-change reporting and monthly earnings reporting. C.1 reporter,recipient and channel rules and the other C.2 exceptions remain separate.",
            "owner": "SSA technician receiving the SSI earnings report",
            "systems": [],
            "route": "SSI monthly earnings report -> staff checks both stated low-earnings conditions -> receipt requirement reviewed separately from earnings evaluation",
            "next": "Ask what further reporting or evidence SSA needs. The receipt exception does not by itself establish countable income, an SSI payment amount, eligibility or a work incentive.",
            "source": "workreceipt",
            "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
            "timing": "C.2 gives no separate completion deadline for this exception. The C.1 immediate/five-day receipt rules remain subject to their own conditions; this branch creates no benefit-decision deadline or new mailing guarantee.",
            "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Current monthly amount AND consistent pattern retained. Customer explanation editorial; receipt not mandatory does not mean reporting is optional or a receipt is prohibited. Benefit computation and other reporting exceptions remain separately held.",
            "source_receipt": {
              "report": "service-ssi-low65-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-ssi-wages/ssi-deemor-ssimwv-exclusion-receipt": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "ssi-deemor-ssimwv-exclusion-receipt",
          "full_route": "report-ssi-wages/ssi-deemor-ssimwv-exclusion-receipt",
          "entry_conditions": [
            "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
            "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
          ],
          "steps": [
            {
              "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-1",
              "title": "Keep the deemor report out of eWork",
              "kind": "action",
              "actor": "SSA staff",
              "action": "The source says a Title XVI deemor work report cannot be entered into eWork; the separate routine monthly-wage procedure remains linked.",
              "conditions": [
                "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
                "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
              ],
              "source": "workreceipt",
              "section": "D",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-2",
              "title": "Issue the acknowledgement to its stated recipient",
              "kind": "action",
              "actor": "SSA staff",
              "action": "For the SSIMWV-exclusion condition, use DPS to issue SSA-L724 to the beneficiary or representative payee.",
              "conditions": [
                "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
                "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
              ],
              "source": "workreceipt",
              "section": "D",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "ssi-deemor-ssimwv-exclusion-receipt-source-step-3",
              "title": "Keep the summary and privacy scopes",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Provide the brief one-sentence work-report summary. Do not give the beneficiary’s private receipt directly to a third-party requester; preserve the source’s beneficiary/payee recipient instruction.",
              "conditions": [
                "The work report concerns a Title XVI deemor and the case meets the source’s SSIMWV-exclusion condition.",
                "This proposal does not determine exclusion criteria or an alternative wage-input procedure."
              ],
              "source": "workreceipt",
              "section": "D; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "ssi-deemor-ssimwv-exclusion-receipt",
          "title": "A report about someone whose income affects SSI is excluded from SSIMWV",
          "when": "SSA identifies a Title XVI deemor report as an SSIMWV exclusion. A deemor is someone whose income may count toward another person’s SSI. This branch does not determine which cases meet an exclusion.",
          "you": "Explain which SSI recipient the report concerns and keep the details you gave SSA. Ask how the recipient or representative payee will receive the work-report acknowledgement.",
          "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. Under the selected SSIMWV-exclusion condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence summary of the work report. The separate routine monthly-wage route and soon-to-start/no-paystub condition remain distinct. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
          "owner": "SSA technician handling the deemor work report and receipt",
          "systems": [
            "Document Processing System (DPS)",
            "SSA-L724 Work Report Receipt"
          ],
          "route": "Deemor report identified by SSA as an SSIMWV exclusion -> staff DPS receipt -> beneficiary or representative payee",
          "next": "Keep the report details and ask SSA which wage information or follow-up is still needed. This receipt acknowledges the report;it does not establish a wage-input fallback, decide the exclusion or determine the SSI payment.",
          "source": "workreceipt",
          "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
          "timing": "D supplies no separate deadline for this selected receipt route. C.1 timing remains subject to the stated reporter andchannel conditions;its immediate beneficiary/payee instruction is not generalized to a deemor. No payment-adjustment or benefit-decision deadline is established.",
          "review_status": "Whole official DI13010.020D with C.1-C.2 checked2026-10-26. Selected TitleXVI deemor SSIMWV-exclusion receipt route only;SSA identifies the exclusion. No new exclusion criteria,alternative wage input orpayment decision. Existing soon-to-start/no-paystub andconcurrentG3 branches remain separate. Channel/reporter timing andprivacy qualifications retained;customer explanation/staff-role label editorial;no internal execution certified.",
          "source_receipt": {
            "report": "service-deemor-ssimwv-exclusion-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-ssi-wages",
          "category": "SSI",
          "title": "Report monthly SSI wages",
          "short": "Use the reporting route and distinguish reporting dates.",
          "story": "Jane works while receiving SSI and needs to report the month’s wages.",
          "level": "Customer overview",
          "review_status": "Cited core steps checked; exceptions incomplete",
          "scope": "Source-backed core path. Case-specific eligibility, every exception, and internal execution are not fully modeled.",
          "path": [
            "You",
            "Wage-reporting service",
            "SSA income record"
          ],
          "channels": {
            "office": "Contact the local office about job changes or reporting problems.",
            "phone": "SSA lists an automated monthly wage-reporting telephone service.",
            "online": "SSA lists online and mobile reporting options; method availability depends on the record."
          },
          "checklist": [
            "Identify monthly wages separately from other income changes.",
            "Choose an official wage-reporting route.",
            "Check the different reporting rules for job changes and other income."
          ],
          "steps": [
            {
              "id": "report-ssi-wages-1",
              "title": "Identify reportable income",
              "you": "Identify wages and other changes that need reporting.",
              "ssa": "SSA distinguishes monthly wages from self-employment and other income changes.",
              "source": "wages",
              "section": "Income you need to report",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Customer → reporting method appropriate to income category",
              "next": "Identify income and changes that need reporting, including spouse income when living together. The public page does not establish internal staff assignment or adjudication screens."
            },
            {
              "id": "report-ssi-wages-2",
              "title": "Report monthly wages",
              "you": "Use the listed online, mobile-app or automated telephone option.",
              "ssa": "The wage-reporting page describes the available reporting methods.",
              "source": "wages",
              "section": "Report wages each month",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Monthly wage report → listed online, app or automated telephone service",
              "next": "SSA’s public guidance says to report monthly wages by the sixth day of the following month. Notify the local office of job changes to keep reporting online. This reporting date is not a processing-time promise."
            },
            {
              "id": "report-ssi-wages-3",
              "title": "Report other changes separately",
              "you": "Notify SSA about job changes and other income changes.",
              "ssa": "Different reporting instructions apply to self-employment and other income.",
              "source": "wages",
              "section": "Report changes in income",
              "owner": "SSA; exact internal assignment not established",
              "systems": [],
              "timing": "No duration specified for this step",
              "verification": "Cited public text checked 2026-10-16; not an independent operational review",
              "route": "Self-employment or other income change → listed SSA contact",
              "next": "The public page says to report these changes by the tenth day of the month after the change. Annual self-employment reporting has a separate January 10 instruction. Staff processing and any payment effect need separate review."
            }
          ],
          "decision": null,
          "timing": "The wage-reporting page asks for monthly wages by day 6 of the following month and other income changes by day 10. General SSI reporting guidance uses a separate 10-day rule. These are reporting instructions, not a payment-adjustment turnaround promise.",
          "timing_type": "Reporting dates",
          "outcome": "SSA receives a wage report; other income and job changes may require a separate report.",
          "gaps": [
            "Remaining exceptions and cross-references still need expanded workflows.",
            "This explains published instructions; actual processing and internal system behavior were not tested."
          ],
          "source_ids": [
            "wages",
            "ssichanges",
            "ssiwageevidence",
            "ssimonthlywageprocessing",
            "ssiwageestimates",
            "ssiwageverificationcompanies",
            "ssicafeteriaplans",
            "ssireportingresponsibilities",
            "ssinesedetermination",
            "ssineseverification",
            "ssinesecurrentestimate",
            "ssimefmatch",
            "ssialertdevelopment",
            "ssitaxinterview",
            "ssitaxdisclosure",
            "ssiirslimited",
            "irsfulldevelopment",
            "ssipayroll",
            "payrollauthorization",
            "workreceipt",
            "ssiwage135run72"
          ]
        },
        "ancestor_records": [
          {
            "id": "ssi-deemor-ssimwv-exclusion-receipt",
            "title": "A report about someone whose income affects SSI is excluded from SSIMWV",
            "when": "SSA identifies a Title XVI deemor report as an SSIMWV exclusion. A deemor is someone whose income may count toward another person’s SSI. This branch does not determine which cases meet an exclusion.",
            "you": "Explain which SSI recipient the report concerns and keep the details you gave SSA. Ask how the recipient or representative payee will receive the work-report acknowledgement.",
            "ssa": "DI13010.020D says a Title XVI deemor work report cannot be entered into eWork. Under the selected SSIMWV-exclusion condition, use DPS to issue SSA-L724 to the beneficiary or representative payee, with a brief one-sentence summary of the work report. The separate routine monthly-wage route and soon-to-start/no-paystub condition remain distinct. C.2 directs that a third-party requester does not receive the beneficiary’s receipt directly because it contains personal information.",
            "owner": "SSA technician handling the deemor work report and receipt",
            "systems": [
              "Document Processing System (DPS)",
              "SSA-L724 Work Report Receipt"
            ],
            "route": "Deemor report identified by SSA as an SSIMWV exclusion -> staff DPS receipt -> beneficiary or representative payee",
            "next": "Keep the report details and ask SSA which wage information or follow-up is still needed. This receipt acknowledges the report;it does not establish a wage-input fallback, decide the exclusion or determine the SSI payment.",
            "source": "workreceipt",
            "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
            "timing": "D supplies no separate deadline for this selected receipt route. C.1 timing remains subject to the stated reporter andchannel conditions;its immediate beneficiary/payee instruction is not generalized to a deemor. No payment-adjustment or benefit-decision deadline is established.",
            "review_status": "Whole official DI13010.020D with C.1-C.2 checked2026-10-26. Selected TitleXVI deemor SSIMWV-exclusion receipt route only;SSA identifies the exclusion. No new exclusion criteria,alternative wage input orpayment decision. Existing soon-to-start/no-paystub andconcurrentG3 branches remain separate. Channel/reporter timing andprivacy qualifications retained;customer explanation/staff-role label editorial;no internal execution certified.",
            "source_receipt": {
              "report": "service-deemor-ssimwv-exclusion-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/workreview-owner": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "workreview-owner",
          "full_route": "report-disability-work/workreview-owner",
          "entry_conditions": [
            "The eWork Development Summary block shows a pending work review.",
            "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
          ],
          "steps": [
            {
              "id": "workreview-owner-source-step-1",
              "title": "Establish the work report",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Establish the work report under F. The published instruction says eWork automatically assigns it to the office with jurisdiction of the pending review; this is a source-described logical function, not current runtime verification.",
              "conditions": [
                "The eWork Development Summary block shows a pending work review.",
                "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
              ],
              "source": "workreceipt",
              "section": "F",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
              ]
            },
            {
              "id": "workreview-owner-source-step-2",
              "title": "Request a transfer only under its condition",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If the beneficiary indicates a move or wants this office to handle the review, contact the office with jurisdiction and ask it to transfer the review. The request is not a completed transfer.",
              "conditions": [
                "The eWork Development Summary block shows a pending work review.",
                "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
              ],
              "source": "workreceipt",
              "section": "F IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
              ]
            },
            {
              "id": "workreview-owner-source-step-3",
              "title": "Keep the DCF consequence conditional",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Only after jurisdiction is transferred in eWork does F describe automatic transfer of the work review in the DCF. This example does not establish that either transfer occurred.",
              "conditions": [
                "The eWork Development Summary block shows a pending work review.",
                "A request for jurisdiction transfer is conditional on the beneficiary indicating a move or wanting the intake office to handle the review; no transfer is presumed."
              ],
              "source": "workreceipt",
              "section": "F IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "F work-report assignment and transfer must not be imported as automatic pay-stub routing under G."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "workreview-owner",
          "title": "A review is already pending",
          "when": "eWork shows a pending review.",
          "you": "Tell SSA about a move or a request to change office.",
          "ssa": "Contact the existing owner for transfer if needed.",
          "route": "Existing owner → agreed receiving office",
          "next": "Jurisdiction transfer in eWork also transfers the DCF review.",
          "source": "workreceipt",
          "section": "F",
          "timing": "No branch completion time established",
          "review_status": "Selected public branch checked; remaining cross-references open"
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "workreview-owner",
            "title": "A review is already pending",
            "when": "eWork shows a pending review.",
            "you": "Tell SSA about a move or a request to change office.",
            "ssa": "Contact the existing owner for transfer if needed.",
            "route": "Existing owner → agreed receiving office",
            "next": "Jurisdiction transfer in eWork also transfers the DCF review.",
            "source": "workreceipt",
            "section": "F",
            "timing": "No branch completion time established",
            "review_status": "Selected public branch checked; remaining cross-references open"
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/receipt-exception": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "receipt-exception",
          "full_route": "report-disability-work/receipt-exception",
          "entry_conditions": [
            "The received form is SSA-821-BK OR SSA-820-BK.",
            "It responds to a work review established in eWork resulting from a CDREO alert; all parts of this condition apply."
          ],
          "steps": [
            {
              "id": "receipt-exception-source-step-1",
              "title": "Keep the receipt exception within that exact form-and-review condition",
              "kind": "action",
              "actor": "SSA staff",
              "action": "C2 makes a new work-report receipt nonmandatory for this specified response. This is not a waiver of work reporting, due process, evaluation or every receipt.",
              "conditions": [
                "The received form is SSA-821-BK OR SSA-820-BK.",
                "It responds to a work review established in eWork resulting from a CDREO alert; all parts of this condition apply."
              ],
              "source": "workreceipt",
              "section": "C2; B; C1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "receipt-exception",
          "title": "A routine review form was requested",
          "when": "The form responds to a CDREO-triggered eWork review.",
          "you": "Retain your submission record.",
          "ssa": "Apply the receipt exception in C.2.",
          "route": "Existing review",
          "next": "A new receipt is not mandatory for this specified situation.",
          "source": "workreceipt",
          "section": "C.2",
          "timing": "No branch completion time established",
          "review_status": "Selected public branch checked; remaining cross-references open"
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "receipt-exception",
            "title": "A routine review form was requested",
            "when": "The form responds to a CDREO-triggered eWork review.",
            "you": "Retain your submission record.",
            "ssa": "Apply the receipt exception in C.2.",
            "route": "Existing review",
            "next": "A new receipt is not mandatory for this specified situation.",
            "source": "workreceipt",
            "section": "C.2",
            "timing": "No branch completion time established",
            "review_status": "Selected public branch checked; remaining cross-references open"
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "titleii-paystubs-pending-work-review",
          "full_route": "report-disability-work/titleii-paystubs-pending-work-review",
          "entry_conditions": [
            "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
            "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
            "The technician checks the eWork Development Worksheet and a work review is pending."
          ],
          "steps": [
            {
              "id": "titleii-paystubs-pending-work-review-source-step-1",
              "title": "Check the pending-review information",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Check the eWork Development Worksheet to identify the pending work review; do not substitute the separate E pending-work-report condition.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The technician checks the eWork Development Worksheet and a work review is pending."
              ],
              "source": "workreceipt",
              "section": "G opening; G1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "The one-day eWork tickle belongs only to the other-jurisdiction condition, not every pay-stub report."
              ]
            },
            {
              "id": "titleii-paystubs-pending-work-review-source-step-2",
              "title": "Send the pay stubs to the responsible office",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Send the pay stubs to the FO responsible for the pending work review. Other-jurisdiction alert/tickle handling is a separately conditional follow-up.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The technician checks the eWork Development Worksheet and a work review is pending."
              ],
              "source": "workreceipt",
              "section": "G1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "The one-day eWork tickle belongs only to the other-jurisdiction condition, not every pay-stub report."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "source": "workreceipt",
          "section": "G opening; G.1",
          "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
          "source_receipt": {
            "report": "service-batch14-workreport-preparation.json",
            "snapshot_path": "sources\\workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-25"
          },
          "id": "titleii-paystubs-pending-work-review",
          "title": "Your pay stubs belong to a pending disability work review",
          "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
          "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
          "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
          "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
          "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
          "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "titleii-paystubs-pending-work-review",
            "title": "Your pay stubs belong to a pending disability work review",
            "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
            "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
            "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
            "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
            "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-ework-unavailable": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "titleii-paystubs-ework-unavailable",
          "full_route": "report-disability-work/titleii-paystubs-ework-unavailable",
          "entry_conditions": [
            "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
            "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
            "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
          ],
          "steps": [
            {
              "id": "titleii-paystubs-ework-unavailable-source-step-1",
              "title": "Store the pay stubs under the stated fallback",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "titleii-paystubs-ework-unavailable-source-step-2",
              "title": "Issue the fallback receipt",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "titleii-paystubs-ework-unavailable-source-step-3",
              "title": "Alert the evaluating technician",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "source": "workreceipt",
          "section": "G opening; G.1",
          "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
          "source_receipt": {
            "report": "service-batch14-workreport-preparation.json",
            "snapshot_path": "sources\\workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-25"
          },
          "id": "titleii-paystubs-ework-unavailable",
          "title": "SSA cannot use eWork for your TitleII pay stubs",
          "when": "The technician is unable to use eWork when handling the TitleII pay-stub report.",
          "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
          "ssa": "Fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. When stubs were verified in eWork, staff may return them; no additional fax into eView or EP is required.",
          "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
          "next": "Receipt issuance and evidence storage do not themselves determine the effect on benefits.",
          "timing": "This fallback paragraph gives no overall evaluation or payment-adjustment deadline."
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "titleii-paystubs-ework-unavailable",
            "title": "SSA cannot use eWork for your TitleII pay stubs",
            "when": "The technician is unable to use eWork when handling the TitleII pay-stub report.",
            "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
            "ssa": "Fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. When stubs were verified in eWork, staff may return them; no additional fax into eView or EP is required.",
            "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
            "next": "Receipt issuance and evidence storage do not themselves determine the effect on benefits.",
            "timing": "This fallback paragraph gives no overall evaluation or payment-adjustment deadline."
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/concurrent-first-work-report-paystubs": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "concurrent-first-work-report-paystubs",
          "full_route": "report-disability-work/concurrent-first-work-report-paystubs",
          "entry_conditions": [
            "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
            "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
            "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
          ],
          "steps": [
            {
              "id": "concurrent-first-work-report-paystubs-source-step-1",
              "title": "Establish the work report for the first or changed work",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Under G2, establish a work report in eWork for this first-work/change condition. The regular concurrent reporter’s SSIMWV instruction is separate.",
              "conditions": [
                "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
                "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
                "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
              ],
              "source": "workreceipt",
              "section": "G2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "concurrent-first-work-report-paystubs-source-step-2",
              "title": "Send the pay stubs to the evaluating technician",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Send the pay stubs to the technician responsible for evaluating earnings, following local procedures. Recording or acknowledging information is not a benefit decision.",
              "conditions": [
                "The beneficiary receives concurrent Title II disability and Title XVI benefits.",
                "The submitted pay stubs concern a first report of work OR a change in work, rather than only routine monthly earnings.",
                "This selected original record excludes the separate concurrent BWE/IRWE processing case; no expense eligibility is determined."
              ],
              "source": "workreceipt",
              "section": "G2; G opening",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "concurrent-first-work-report-paystubs",
          "title": "You receive both SSI and disability benefits and report new or changed work",
          "when": "You receive concurrent Title II disability and SSI benefits, and the submitted pay stubs are for a first report of work or a change in work, rather than only a regular monthly earnings report. This selected branch does not cover concurrent cases involving blind work expenses or impairment-related work expenses.",
          "you": "Tell SSA that you receive both benefits and whether work has just started or changed. Provide the pay stubs SSA requests, keep the report receipt, and ask which technician is evaluating the earnings.",
          "ssa": "DI13010.020G.2 directs staff to establish a work report in eWork and send the pay stubs to the technician responsible for evaluating earnings under local procedures when the pay stubs concern first-time work or a change. Its regular concurrent monthly-report route uses SSIMWV; the first-work/change condition must be identified before applying that routine route.",
          "owner": "SSA intake technician and technician responsible for evaluating the earnings",
          "systems": [
            "eWork",
            "SSIMWV (regular concurrent wage-report context only)"
          ],
          "route": "Concurrent first-work/change report -> eWork work report -> responsible earnings evaluator under local procedures",
          "next": "Ask SSA what follow-up is needed for each benefit. Recording a wage report or issuing a receipt does not itself determine the effect on either benefit. Tell SSA about any disability-related work expenses; their special processing instructions are outside this selected branch.",
          "source": "workreceipt",
          "section": "G.2; C.1 receipt conditions; G.3 held exception context",
          "timing": "G.2 establishes no case-completion deadline. C.1 gives or mails covered beneficiary/payee in-person or telephone report receipts immediately; covered mailed/faxed/dropped-off reports are established and mailed within five days of receipt. These are receipt instructions, not benefit-adjustment deadlines.",
          "review_status": "Selected official G.2/C.1 checked2026-10-26 with G.3 and SI00820.143F.1 context. First-work/change condition retained; BWE/IRWE cases excluded from this selected branch while linked SI00820.144 retrieval remains404. Customer explanation editorial; no whole-page, runtime or benefit-decision certification.",
          "source_receipt": {
            "report": "service-concurrent020-integration-gate.json",
            "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "concurrent-first-work-report-paystubs",
            "title": "You receive both SSI and disability benefits and report new or changed work",
            "when": "You receive concurrent Title II disability and SSI benefits, and the submitted pay stubs are for a first report of work or a change in work, rather than only a regular monthly earnings report. This selected branch does not cover concurrent cases involving blind work expenses or impairment-related work expenses.",
            "you": "Tell SSA that you receive both benefits and whether work has just started or changed. Provide the pay stubs SSA requests, keep the report receipt, and ask which technician is evaluating the earnings.",
            "ssa": "DI13010.020G.2 directs staff to establish a work report in eWork and send the pay stubs to the technician responsible for evaluating earnings under local procedures when the pay stubs concern first-time work or a change. Its regular concurrent monthly-report route uses SSIMWV; the first-work/change condition must be identified before applying that routine route.",
            "owner": "SSA intake technician and technician responsible for evaluating the earnings",
            "systems": [
              "eWork",
              "SSIMWV (regular concurrent wage-report context only)"
            ],
            "route": "Concurrent first-work/change report -> eWork work report -> responsible earnings evaluator under local procedures",
            "next": "Ask SSA what follow-up is needed for each benefit. Recording a wage report or issuing a receipt does not itself determine the effect on either benefit. Tell SSA about any disability-related work expenses; their special processing instructions are outside this selected branch.",
            "source": "workreceipt",
            "section": "G.2; C.1 receipt conditions; G.3 held exception context",
            "timing": "G.2 establishes no case-completion deadline. C.1 gives or mails covered beneficiary/payee in-person or telephone report receipts immediately; covered mailed/faxed/dropped-off reports are established and mailed within five days of receipt. These are receipt instructions, not benefit-adjustment deadlines.",
            "review_status": "Selected official G.2/C.1 checked2026-10-26 with G.3 and SI00820.143F.1 context. First-work/change condition retained; BWE/IRWE cases excluded from this selected branch while linked SI00820.144 retrieval remains404. Customer explanation editorial; no whole-page, runtime or benefit-decision certification.",
            "source_receipt": {
              "report": "service-concurrent020-integration-gate.json",
              "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/work-report-same-employer-period-update": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "work-report-same-employer-period-update",
          "full_route": "report-disability-work/work-report-same-employer-period-update",
          "entry_conditions": [
            "A work report for the same employer is already pending in eWork.",
            "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review."
          ],
          "steps": [
            {
              "id": "work-report-same-employer-period-update-source-step-1",
              "title": "For a new employment period: Add",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If the report is for a new period of employment, select Add. This is not the same-period Edit instruction.",
              "conditions": [
                "A work report for the same employer is already pending in eWork.",
                "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
                "The report concerns a NEW period of employment."
              ],
              "source": "workreceipt",
              "section": "E1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ],
              "alternative_group": "employment-period"
            },
            {
              "id": "work-report-same-employer-period-update-source-step-2",
              "title": "For the same employment period: Edit",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If the report involves work from the same employment period already shown, select Edit. Do not import D’s initial-report employer-update caution as a prohibition on this E instruction.",
              "conditions": [
                "A work report for the same employer is already pending in eWork.",
                "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
                "The report concerns the SAME period of employment already shown."
              ],
              "source": "workreceipt",
              "section": "E1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ],
              "alternative_group": "employment-period"
            },
            {
              "id": "work-report-same-employer-period-update-source-step-3",
              "title": "Issue a new receipt to the listed reporter",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Issue a new receipt if the reporter is the beneficiary, representative payee or appointed representative. Receipt issuance does not establish an earnings decision.",
              "conditions": [
                "A work report for the same employer is already pending in eWork.",
                "Staff determine whether the current information concerns a new employment period or the same period; a pending work report is not by itself a pending work review.",
                "The reporter is the beneficiary, representative payee OR appointed representative."
              ],
              "source": "workreceipt",
              "section": "E2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          },
          "alternative_groups": [
            {
              "id": "employment-period",
              "label": "Choose the source instruction for the actual employment period",
              "logic": "source_conditions_determine_branch",
              "note": "Add and Edit are alternatives based on the actual period; both are not sequential actions. Unknown or unclear period information establishes neither choice."
            }
          ]
        },
        "original_record": {
          "id": "work-report-same-employer-period-update",
          "title": "A report for the same employer is already pending",
          "when": "A work report for the same employer is already pending in eWork,and you provide information that changes that report or concerns a new period of employment. This concerns a pending work report,not by itself a pending work review.",
          "you": "Tell SSA when you previously reported the employer and which dates the new information covers. Explain whether you are correcting the earlier period or reporting a new period of employment. Keep the new receipt and your earlier submission records.",
          "ssa": "DI13010.020E directs staff to determine whether the information concerns a new employment period or the same period already shown. For a new period select Add;for the same period select Edit. Issue a new receipt when the reporter is the beneficiary,representative payee or appointed representative. D separately cautions against using Edit during its initial-report employer-update procedure;F separately governs a pending work review.",
          "owner": "SSA work-report intake technician",
          "systems": [
            "eWork",
            "Work-report receipt"
          ],
          "route": "Identify pending report and employment period -> applicable staff Add/Edit action -> new receipt for the listed reporter",
          "next": "Check that SSA understands the employment period and keep the acknowledgement. Updating the report or issuing a receipt does not decide how work affects benefits.",
          "source": "workreceipt",
          "section": "E whole steps1-2;D/F context only",
          "timing": "E states no case-completion duration or special receipt deadline. Receipt issuance documents the report;it does not establish an earnings decision or payment-adjustment date.",
          "review_status": "Selected official DI13010.020E checked2026-10-26 with D/F context. Same-employer pending-report trigger,new versus same employment period,and beneficiary/payee/appointed-representative receipt list retained. Initial D and pending-review F procedures remain separate. Customer explanation editorial;no benefits determination or runtime certification.",
          "source_receipt": {
            "report": "service-work-report020E-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "work-report-same-employer-period-update",
            "title": "A report for the same employer is already pending",
            "when": "A work report for the same employer is already pending in eWork,and you provide information that changes that report or concerns a new period of employment. This concerns a pending work report,not by itself a pending work review.",
            "you": "Tell SSA when you previously reported the employer and which dates the new information covers. Explain whether you are correcting the earlier period or reporting a new period of employment. Keep the new receipt and your earlier submission records.",
            "ssa": "DI13010.020E directs staff to determine whether the information concerns a new employment period or the same period already shown. For a new period select Add;for the same period select Edit. Issue a new receipt when the reporter is the beneficiary,representative payee or appointed representative. D separately cautions against using Edit during its initial-report employer-update procedure;F separately governs a pending work review.",
            "owner": "SSA work-report intake technician",
            "systems": [
              "eWork",
              "Work-report receipt"
            ],
            "route": "Identify pending report and employment period -> applicable staff Add/Edit action -> new receipt for the listed reporter",
            "next": "Check that SSA understands the employment period and keep the acknowledgement. Updating the report or issuing a receipt does not decide how work affects benefits.",
            "source": "workreceipt",
            "section": "E whole steps1-2;D/F context only",
            "timing": "E states no case-completion duration or special receipt deadline. Receipt issuance documents the report;it does not establish an earnings decision or payment-adjustment date.",
            "review_status": "Selected official DI13010.020E checked2026-10-26 with D/F context. Same-employer pending-report trigger,new versus same employment period,and beneficiary/payee/appointed-representative receipt list retained. Initial D and pending-review F procedures remain separate. Customer explanation editorial;no benefits determination or runtime certification.",
            "source_receipt": {
              "report": "service-work-report020E-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-employer-not-established": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "titleii-paystubs-employer-not-established",
          "full_route": "report-disability-work/titleii-paystubs-employer-not-established",
          "entry_conditions": [
            "A Title II beneficiary submits pay stubs and no work review is pending.",
            "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
          ],
          "steps": [
            {
              "id": "titleii-paystubs-employer-not-established-source-step-1",
              "title": "Establish the missing employer’s work report",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Return to the eWork main menu and establish a Work Report under G1’s missing-employer condition.",
              "conditions": [
                "A Title II beneficiary submits pay stubs and no work review is pending.",
                "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
              ],
              "source": "workreceipt",
              "section": "G1; G opening",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "titleii-paystubs-employer-not-established-source-step-2",
              "title": "Apply the stated receipt condition",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Issue the receipt under the referenced work-report and C1 receipt instructions; reporter, recipient, channel and exceptions retain their own conditions.",
              "conditions": [
                "A Title II beneficiary submits pay stubs and no work review is pending.",
                "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
              ],
              "source": "workreceipt",
              "section": "G1; B; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "titleii-paystubs-employer-not-established-source-step-3",
              "title": "Input the pay-stub information",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Then input the pay-stub information. This input does not evaluate its benefit effect or create the work report’s controls.",
              "conditions": [
                "A Title II beneficiary submits pay stubs and no work review is pending.",
                "The employer has not been established in the Pay Stub Report listing; this is not the pending-review/other-jurisdiction route."
              ],
              "source": "workreceipt",
              "section": "G1; G opening",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "titleii-paystubs-employer-not-established",
          "title": "SSA needs to establish an employer before recording your pay stubs",
          "when": "You receive Title II disability benefits, no work review is pending, and SSA finds that the employer for the pay stubs you report has not been established in its Pay Stub Report listing.",
          "you": "Provide the employer and work information SSA requests along with your pay stubs. Ask whether your work report and pay-stub information were recorded and whether you should receive a receipt. Keep copies for your records.",
          "ssa": "DI13010.020G.1 directs staff, when no work review is pending and the employer is missing from the Pay Stub Report listing, to establish a Work Report and issue a receipt under the referenced reporting instructions, then input the pay-stub information. G.1 also retains the C.1 reporter conditions for receipts. A pending work review instead follows its responsible-office route; inability to use eWork follows the separate Evidence Portal/DPS route.",
          "owner": "SSA technician receiving the Title II pay-stub report;responsible work-review office only if a review is actually pending",
          "systems": [
            "eWork Work Report and Pay Stub Report (staff use)"
          ],
          "route": "No pending work review -> missing-employer Work Report establishment -> pay-stub entry and applicable receipt",
          "next": "Ask SSA what follow-up is needed for evaluating your work. Recording a report or issuing a receipt does not determine how the work affects benefit entitlement.",
          "source": "workreceipt",
          "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
          "timing": "G.1 gives no customer processing or benefit-decision deadline for this missing-employer route. Its one-day tickle applies to the separate pending-review/other-jurisdiction condition.",
          "review_status": "Selected whole G.1 checked2026-10-26 against revision2024-06-14/TN84(01-25)/batch2025-03-25;C.1/C.2 reporter/privacy conditions retained. Customer explanation editorial;internal execution not independently tested.",
          "source_receipt": {
            "report": "service-work020G1-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "titleii-paystubs-employer-not-established",
            "title": "SSA needs to establish an employer before recording your pay stubs",
            "when": "You receive Title II disability benefits, no work review is pending, and SSA finds that the employer for the pay stubs you report has not been established in its Pay Stub Report listing.",
            "you": "Provide the employer and work information SSA requests along with your pay stubs. Ask whether your work report and pay-stub information were recorded and whether you should receive a receipt. Keep copies for your records.",
            "ssa": "DI13010.020G.1 directs staff, when no work review is pending and the employer is missing from the Pay Stub Report listing, to establish a Work Report and issue a receipt under the referenced reporting instructions, then input the pay-stub information. G.1 also retains the C.1 reporter conditions for receipts. A pending work review instead follows its responsible-office route; inability to use eWork follows the separate Evidence Portal/DPS route.",
            "owner": "SSA technician receiving the Title II pay-stub report;responsible work-review office only if a review is actually pending",
            "systems": [
              "eWork Work Report and Pay Stub Report (staff use)"
            ],
            "route": "No pending work review -> missing-employer Work Report establishment -> pay-stub entry and applicable receipt",
            "next": "Ask SSA what follow-up is needed for evaluating your work. Recording a report or issuing a receipt does not determine how the work affects benefit entitlement.",
            "source": "workreceipt",
            "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
            "timing": "G.1 gives no customer processing or benefit-decision deadline for this missing-employer route. Its one-day tickle applies to the separate pending-review/other-jurisdiction condition.",
            "review_status": "Selected whole G.1 checked2026-10-26 against revision2024-06-14/TN84(01-25)/batch2025-03-25;C.1/C.2 reporter/privacy conditions retained. Customer explanation editorial;internal execution not independently tested.",
            "source_receipt": {
              "report": "service-work020G1-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/third-party-work-report-receipt-privacy": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "third-party-work-report-receipt-privacy",
          "full_route": "report-disability-work/third-party-work-report-receipt-privacy",
          "entry_conditions": [
            "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
            "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
          ],
          "steps": [
            {
              "id": "third-party-work-report-receipt-privacy-source-step-1",
              "title": "Keep mandatory-receipt and requester rules distinct",
              "kind": "action",
              "actor": "SSA staff",
              "action": "C2 does not make a receipt mandatory for this outside-reporter condition. Do not generalize this exception to listed reporters.",
              "conditions": [
                "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
                "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
              ],
              "source": "workreceipt",
              "section": "C2; C1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "third-party-work-report-receipt-privacy-source-step-2",
              "title": "Protect the receipt’s recipient",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Inform the requester that the receipt will be mailed to the beneficiary or representative payee; do not issue it directly to the reporter because it contains beneficiary PII. No completed mailing or disclosure authority is established.",
              "conditions": [
                "The reporting party is outside the beneficiary, representative payee, appointed representative and Title XVI deemor roles listed in C1.",
                "That third party requests a receipt; this is not a basis to disclose beneficiary information directly to the reporting party."
              ],
              "source": "workreceipt",
              "section": "C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "third-party-work-report-receipt-privacy",
          "title": "A workplace reports work and asks for a receipt",
          "when": "A sheltered workshop or another reporter outside the beneficiary,representative payee,appointed representative or deemor roles reports work and requests a receipt. This branch concerns the specified third-party reporting situation,not a request by a listed C.1 reporter.",
          "you": "Keep a record of what was submitted and ask SSA about the applicable acknowledgement. If you made the report for someone else,do not expect SSA to send you a receipt containing that person’s private information.",
          "ssa": "C.2 says a receipt is not mandatory for a report from someone outside the listed beneficiary,payee,appointed representative or deemor roles. If a third party requests a receipt,inform them that SSA will mail it to the beneficiary or representative payee. Do not issue the receipt directly to that reporter because it contains the beneficiary’s personally identifiable information. The C.1 mandatory-receipt table and its listed recipient roles remain separate.",
          "route": "Outside third-party work report andreceipt request to SSA;receipt mailed to beneficiary orrepresentative payee ratherthan directly tooutside reporter",
          "next": "Confirm which reporting or follow-up steps still apply. The receipt route protects information;it does not decide the effect of work on benefits or give the reporter access to the beneficiary’s record.",
          "source": "workreceipt",
          "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
          "timing": "C.2 gives no separate completion duration for this selected third-party receipt request. C.1 timing remains subject to its stated reporter/channel conditions;no benefit-decision deadline is established.",
          "review_status": "Whole C.1-C.2 checked2026-10-26 againstretainedofficialDI13010.020. Outside-reporter trigger distinctfrommandatoryC.1reporters andDdeemor soon-to-start/no-paystub route. Customer follow-up explanation editorial;no internal execution orrecord-access right certified.",
          "owner": "SSA technician handling the work report andreceipt request",
          "systems": [],
          "source_receipt": {
            "report": "service-work020C2-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "third-party-work-report-receipt-privacy",
            "title": "A workplace reports work and asks for a receipt",
            "when": "A sheltered workshop or another reporter outside the beneficiary,representative payee,appointed representative or deemor roles reports work and requests a receipt. This branch concerns the specified third-party reporting situation,not a request by a listed C.1 reporter.",
            "you": "Keep a record of what was submitted and ask SSA about the applicable acknowledgement. If you made the report for someone else,do not expect SSA to send you a receipt containing that person’s private information.",
            "ssa": "C.2 says a receipt is not mandatory for a report from someone outside the listed beneficiary,payee,appointed representative or deemor roles. If a third party requests a receipt,inform them that SSA will mail it to the beneficiary or representative payee. Do not issue the receipt directly to that reporter because it contains the beneficiary’s personally identifiable information. The C.1 mandatory-receipt table and its listed recipient roles remain separate.",
            "route": "Outside third-party work report andreceipt request to SSA;receipt mailed to beneficiary orrepresentative payee ratherthan directly tooutside reporter",
            "next": "Confirm which reporting or follow-up steps still apply. The receipt route protects information;it does not decide the effect of work on benefits or give the reporter access to the beneficiary’s record.",
            "source": "workreceipt",
            "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
            "timing": "C.2 gives no separate completion duration for this selected third-party receipt request. C.1 timing remains subject to its stated reporter/channel conditions;no benefit-decision deadline is established.",
            "review_status": "Whole C.1-C.2 checked2026-10-26 againstretainedofficialDI13010.020. Outside-reporter trigger distinctfrommandatoryC.1reporters andDdeemor soon-to-start/no-paystub route. Customer follow-up explanation editorial;no internal execution orrecord-access right certified.",
            "owner": "SSA technician handling the work report andreceipt request",
            "systems": [],
            "source_receipt": {
              "report": "service-work020C2-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/cdr-mailer-already-developed-receipt-exception": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "cdr-mailer-already-developed-receipt-exception",
          "full_route": "report-disability-work/cdr-mailer-already-developed-receipt-exception",
          "entry_conditions": [
            "The work information comes from a CDR mailer.",
            "That work has already been developed; both source conditions must apply."
          ],
          "steps": [
            {
              "id": "cdr-mailer-already-developed-receipt-exception-source-step-1",
              "title": "Apply only the stated receipt exception",
              "kind": "action",
              "actor": "SSA staff",
              "action": "C2 makes a receipt nonmandatory for work information from a CDR mailer when that work was already developed. B reporting duties remain; this does not complete the medical review or evaluate new work.",
              "conditions": [
                "The work information comes from a CDR mailer.",
                "That work has already been developed; both source conditions must apply."
              ],
              "source": "workreceipt",
              "section": "C2; B; C1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "cdr-mailer-already-developed-receipt-exception",
          "title": "The work in your CDR mailer was already developed",
          "when": "SSA receives work information from a CDR mailer and that work has already been developed. Both the mailer origin and prior work development must apply.",
          "you": "Keep a copy or other submission record. Ask SSA whether the work information was already developed and whether any new or changed work still needs to be reported. Continue reporting work changes as required.",
          "ssa": "DI13010.020C.2 makes a work-report receipt nonmandatory when work information comes from a CDR mailer and the work has already been developed. This selected receipt exception does not determine the medical review outcome or the effect of earnings on benefits. B reporting duties and C.1 reporter, recipient and channel conditions remain separate.",
          "owner": "SSA technician receiving the CDR mailer work information",
          "systems": [],
          "route": "CDR mailer work information -> staff confirms the work was already developed -> receipt requirement considered separately from any benefit or medical review decision",
          "next": "Ask which work information SSA has already developed and whether it needs anything further. A missing receipt alone does not show that the medical review is complete, benefits continue, or additional work information can be omitted.",
          "source": "workreceipt",
          "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
          "timing": "C.2 gives no separate completion deadline for this exception. C.1 immediate/five-day receipt rules retain their own conditions; this branch creates no review-completion or benefit-decision deadline.",
          "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Mailer origin AND already-developed work required. Nonmandatory does not mean receipt issuance is prohibited or reporting is optional. The CDREO-triggered SSA-821-BK/SSA-820-BK exception and other C.2 exceptions remain distinct.",
          "source_receipt": {
            "report": "service-cdr-mailer-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "cdr-mailer-already-developed-receipt-exception",
            "title": "The work in your CDR mailer was already developed",
            "when": "SSA receives work information from a CDR mailer and that work has already been developed. Both the mailer origin and prior work development must apply.",
            "you": "Keep a copy or other submission record. Ask SSA whether the work information was already developed and whether any new or changed work still needs to be reported. Continue reporting work changes as required.",
            "ssa": "DI13010.020C.2 makes a work-report receipt nonmandatory when work information comes from a CDR mailer and the work has already been developed. This selected receipt exception does not determine the medical review outcome or the effect of earnings on benefits. B reporting duties and C.1 reporter, recipient and channel conditions remain separate.",
            "owner": "SSA technician receiving the CDR mailer work information",
            "systems": [],
            "route": "CDR mailer work information -> staff confirms the work was already developed -> receipt requirement considered separately from any benefit or medical review decision",
            "next": "Ask which work information SSA has already developed and whether it needs anything further. A missing receipt alone does not show that the medical review is complete, benefits continue, or additional work information can be omitted.",
            "source": "workreceipt",
            "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
            "timing": "C.2 gives no separate completion deadline for this exception. C.1 immediate/five-day receipt rules retain their own conditions; this branch creates no review-completion or benefit-decision deadline.",
            "review_status": "Whole B/C.1/C.2 checked 2026-10-26 against DI13010.020 revision 2024-06-14/TN84(01-25). Mailer origin AND already-developed work required. Nonmandatory does not mean receipt issuance is prohibited or reporting is optional. The CDREO-triggered SSA-821-BK/SSA-820-BK exception and other C.2 exceptions remain distinct.",
            "source_receipt": {
              "report": "service-cdr-mailer-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/concurrent-work-expense-ssimwv-exclusion": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "concurrent-work-expense-ssimwv-exclusion",
          "full_route": "report-disability-work/concurrent-work-expense-ssimwv-exclusion",
          "entry_conditions": [
            "The case is concurrent Title II/Title XVI and is in the source-named MSSICS context.",
            "The pay stubs involve BWEs OR IRWEs. This proposal does not determine which expenses qualify or supply the linked alternative input procedure."
          ],
          "steps": [
            {
              "id": "concurrent-work-expense-ssimwv-exclusion-source-step-1",
              "title": "Keep the input exclusion in its exact scope",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Do not enter these concurrent MSSICS-case pay stubs involving BWEs or IRWEs into SSIMWV. Detailed monthly-pay-stub processing is referred to SI00820.144 and remains held here.",
              "conditions": [
                "The case is concurrent Title II/Title XVI and is in the source-named MSSICS context.",
                "The pay stubs involve BWEs OR IRWEs. This proposal does not determine which expenses qualify or supply the linked alternative input procedure."
              ],
              "source": "workreceipt",
              "section": "G3",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "MSSICS is the published system name in this source; no automatic CCE or SSIMWV alias is created. SI00820.144 remains a source gap, not a guessed fallback."
              ]
            },
            {
              "id": "concurrent-work-expense-ssimwv-exclusion-source-step-2",
              "title": "Keep the IRWE notice condition separate",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If IRWEs are involved, make sure the person responsible for the Title II decision is aware of them. Do not broaden this IRWE-specific instruction to every BWE-only case or treat it as a completed handoff.",
              "conditions": [
                "All concurrent MSSICS/work-expense parent conditions apply.",
                "IRWEs are involved; BWE-only involvement does not itself satisfy this step condition."
              ],
              "source": "workreceipt",
              "section": "G3",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "MSSICS is the published system name in this source; no automatic CCE or SSIMWV alias is created. SI00820.144 remains a source gap, not a guessed fallback."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "id": "concurrent-work-expense-ssimwv-exclusion",
          "title": "You receive both benefits and report disability-related work expenses",
          "when": "You receive concurrent Title II disability and SSI benefits, the case is in MSSICS, and monthly pay stubs involve blind work expenses (BWEs) or impairment-related work expenses (IRWEs). This selected branch concerns the stated input exclusion; it does not decide whether an expense qualifies.",
          "you": "Tell SSA that you receive both benefits and describe the work expenses with your wage report. Ask what evidence and follow-up SSA needs, and ask whether the person handling your Title II decision has been told about any IRWEs. Keep the acknowledgement of your report.",
          "ssa": "DI 13010.020 G.3 says pay stubs for concurrent MSSICS cases involving BWEs or IRWEs cannot be entered into SSIMWV. It refers detailed monthly pay-stub processing to SI 00820.144 and directs staff to make the person responsible for the Title II decision aware of any IRWEs. G.2 regular-report and first-work/change routes remain distinct. The G opening warns that recording pay stubs does not itself evaluate effects on benefits.",
          "owner": "SSA wage-report technician and person responsible for the Title II decision, for the specified IRWE awareness handoff",
          "systems": [
            "MSSICS, stated case condition",
            "SSIMWV, excluded input path for this condition"
          ],
          "route": "Concurrent MSSICS case with BWE or IRWE -> identify SSIMWV input exclusion -> separately obtain applicable wage-processing instructions; notify Title II decision owner of IRWEs",
          "next": "Ask SSA which evidence remains needed for each benefit. This illustration does not determine an allowable expense, a benefit amount or the correct alternative input screen. Detailed SI 00820.144 processing remains an open source gap here.",
          "source": "workreceipt",
          "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
          "timing": "G.3 supplies no deadline for expense development, the staff handoff or a benefit decision. C.1 receipt timing depends on the stated reporter and channel conditions and is not a completion deadline.",
          "review_status": "Whole selected DI 13010.020 G.3 with G opening, G.2 and C.1 checked 2026-10-26; page revision 2024-06-14, TN84 (01-25), batch 2025-03-25. Concurrent MSSICS and BWE/IRWE conditions retained. Title II awareness instruction applies to IRWEs. Linked SI 00820.144 detail remains unverified after preserved404; no fallback screen, expense allowance, physical interface or runtime inferred. Customer explanation editorial.",
          "source_receipt": {
            "report": "service-concurrent-g3-exclusion-integration-gate.json",
            "snapshot_path": "sources/workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-26"
          }
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "id": "concurrent-work-expense-ssimwv-exclusion",
            "title": "You receive both benefits and report disability-related work expenses",
            "when": "You receive concurrent Title II disability and SSI benefits, the case is in MSSICS, and monthly pay stubs involve blind work expenses (BWEs) or impairment-related work expenses (IRWEs). This selected branch concerns the stated input exclusion; it does not decide whether an expense qualifies.",
            "you": "Tell SSA that you receive both benefits and describe the work expenses with your wage report. Ask what evidence and follow-up SSA needs, and ask whether the person handling your Title II decision has been told about any IRWEs. Keep the acknowledgement of your report.",
            "ssa": "DI 13010.020 G.3 says pay stubs for concurrent MSSICS cases involving BWEs or IRWEs cannot be entered into SSIMWV. It refers detailed monthly pay-stub processing to SI 00820.144 and directs staff to make the person responsible for the Title II decision aware of any IRWEs. G.2 regular-report and first-work/change routes remain distinct. The G opening warns that recording pay stubs does not itself evaluate effects on benefits.",
            "owner": "SSA wage-report technician and person responsible for the Title II decision, for the specified IRWE awareness handoff",
            "systems": [
              "MSSICS, stated case condition",
              "SSIMWV, excluded input path for this condition"
            ],
            "route": "Concurrent MSSICS case with BWE or IRWE -> identify SSIMWV input exclusion -> separately obtain applicable wage-processing instructions; notify Title II decision owner of IRWEs",
            "next": "Ask SSA which evidence remains needed for each benefit. This illustration does not determine an allowable expense, a benefit amount or the correct alternative input screen. Detailed SI 00820.144 processing remains an open source gap here.",
            "source": "workreceipt",
            "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
            "timing": "G.3 supplies no deadline for expense development, the staff handoff or a benefit decision. C.1 receipt timing depends on the stated reporter and channel conditions and is not a completion deadline.",
            "review_status": "Whole selected DI 13010.020 G.3 with G opening, G.2 and C.1 checked 2026-10-26; page revision 2024-06-14, TN84 (01-25), batch 2025-03-25. Concurrent MSSICS and BWE/IRWE conditions retained. Title II awareness instruction applies to IRWEs. Linked SI 00820.144 detail remains unverified after preserved404; no fallback screen, expense allowance, physical interface or runtime inferred. Customer explanation editorial.",
            "source_receipt": {
              "report": "service-concurrent-g3-exclusion-integration-gate.json",
              "snapshot_path": "sources/workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-26"
            }
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "another-review-jurisdiction",
          "full_route": "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction",
          "entry_conditions": [
            "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
            "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
            "The employer is already established in eWork with a work report.",
            "The Title II work review is pending in ANOTHER jurisdiction."
          ],
          "steps": [
            {
              "id": "another-review-jurisdiction-source-step-1",
              "title": "Send the pay stubs to the responsible review office",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Send the pay stubs to the FO responsible for the pending work review.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The employer is already established in eWork with a work report.",
                "The Title II work review is pending in ANOTHER jurisdiction."
              ],
              "source": "workreceipt",
              "section": "G opening; G1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "another-review-jurisdiction-source-step-2",
              "title": "Alert the other jurisdiction",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Alert the other jurisdiction about the pay-stub input; no completed alert or receipt is established.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The employer is already established in eWork with a work report.",
                "The Title II work review is pending in ANOTHER jurisdiction."
              ],
              "source": "workreceipt",
              "section": "G1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            },
            {
              "id": "another-review-jurisdiction-source-step-3",
              "title": "Establish only the stated staff reminder",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Establish the one-day tickle on the eWork developmental worksheet under this other-jurisdiction condition. It is not a one-day decision deadline, and an unavailable-eWork fallback supplies no invented substitute.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The employer is already established in eWork with a work report.",
                "The Title II work review is pending in ANOTHER jurisdiction."
              ],
              "source": "workreceipt",
              "section": "G1",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "source": "workreceipt",
          "section": "G opening; G.1",
          "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
          "source_receipt": {
            "report": "service-batch14-workreport-preparation.json",
            "snapshot_path": "sources\\workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-25"
          },
          "id": "another-review-jurisdiction",
          "title": "Another field office owns the pending review",
          "when": "The TitleII pay-stub report belongs to a pending review in another jurisdiction. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
          "you": "Identify the office already reviewing your work and keep your receipt.",
          "ssa": "Send the pay stubs to the responsible review office. Alert that office to the input and establish the stated one-day eWork development-worksheet tickle when using this procedure.",
          "route": "Pay-stub intake → responsible review office in another jurisdiction",
          "next": "The reviewing office evaluates the earnings effect; the tickle is a staff control, not a decision deadline.",
          "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "titleii-paystubs-pending-work-review",
            "title": "Your pay stubs belong to a pending disability work review",
            "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
            "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
            "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
            "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
            "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          },
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "another-review-jurisdiction",
            "title": "Another field office owns the pending review",
            "when": "The TitleII pay-stub report belongs to a pending review in another jurisdiction. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
            "you": "Identify the office already reviewing your work and keep your receipt.",
            "ssa": "Send the pay stubs to the responsible review office. Alert that office to the input and establish the stated one-day eWork development-worksheet tickle when using this procedure.",
            "route": "Pay-stub intake → responsible review office in another jurisdiction",
            "next": "The reviewing office evaluates the earnings effect; the tickle is a staff control, not a decision deadline.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/ework-not-available": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "ework-not-available",
          "full_route": "report-disability-work/titleii-paystubs-pending-work-review/ework-not-available",
          "entry_conditions": [
            "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
            "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
            "The parent pending Title II pay-stub work-review condition applies.",
            "The employer was already established in eWork with a work report.",
            "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
          ],
          "steps": [
            {
              "id": "ework-not-available-source-step-1",
              "title": "Store the pay stubs under the stated fallback",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The parent pending Title II pay-stub work-review condition applies.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "ework-not-available-source-step-2",
              "title": "Issue the fallback receipt",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The parent pending Title II pay-stub work-review condition applies.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "ework-not-available-source-step-3",
              "title": "Alert the evaluating technician",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The parent pending Title II pay-stub work-review condition applies.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "source": "workreceipt",
          "section": "G opening; G.1",
          "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
          "source_receipt": {
            "report": "service-batch14-workreport-preparation.json",
            "snapshot_path": "sources\\workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-25"
          },
          "id": "ework-not-available",
          "title": "SSA cannot use eWork for your TitleII pay stubs",
          "when": "The parent pending TitleII pay-stub review situation applies and staff are unable to use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
          "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
          "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
          "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
          "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
          "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
          "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "titleii-paystubs-pending-work-review",
            "title": "Your pay stubs belong to a pending disability work review",
            "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
            "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
            "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
            "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
            "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          },
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "ework-not-available",
            "title": "SSA cannot use eWork for your TitleII pay stubs",
            "when": "The parent pending TitleII pay-stub review situation applies and staff are unable to use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
            "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
            "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
            "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
            "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
            "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
            "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      },
      "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction/ework-not-available": {
        "flow": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "ework-not-available",
          "full_route": "report-disability-work/titleii-paystubs-pending-work-review/another-review-jurisdiction/ework-not-available",
          "entry_conditions": [
            "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
            "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
            "The Title II work review is pending in another office’s jurisdiction.",
            "The employer was already established in eWork with a work report.",
            "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
          ],
          "steps": [
            {
              "id": "ework-not-available-source-step-1",
              "title": "Store the pay stubs under the stated fallback",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When unable to use eWork, fax the pay stubs into Evidence Portal. Keep the separate verified-in-eWork/no-additional-fax condition distinct.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The Title II work review is pending in another office’s jurisdiction.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "ework-not-available-source-step-2",
              "title": "Issue the fallback receipt",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Issue SSA-L724 through DPS under the source’s receipt conditions; this does not decide how earnings affect benefits.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The Title II work review is pending in another office’s jurisdiction.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT; C1-C2",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            },
            {
              "id": "ework-not-available-source-step-3",
              "title": "Alert the evaluating technician",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Alert the technician responsible for evaluating work activity according to local procedures. No completed alert, evaluation or substitute tickle is established.",
              "conditions": [
                "The report concerns Title II pay stubs; the G Pay Stub Report feature’s employer/work-report scope remains applicable.",
                "Input alone does not evaluate the earnings effect or provide the work report’s controls. Actual case facts are not established.",
                "The Title II work review is pending in another office’s jurisdiction.",
                "The employer was already established in eWork with a work report.",
                "The technician is unable to use eWork for this Title II pay-stub handling. Prior verification is not established or treated as false by choosing the example."
              ],
              "source": "workreceipt",
              "section": "G1 IMPORTANT",
              "source_context_refs": [
                "DI13010.020-whole"
              ],
              "qualifications": [
                "The cards organize selected published instructions. They do not establish actual report facts, completed staff actions, case decisions or a successful return to the usual path.",
                "Receipts acknowledge information and receipt dates; they do not decide the effect of earnings, eligibility or payment. Prescribed receipt/tickle timing is not measured benefit-processing time.",
                "Reporter, receipt recipient and reporting channel are different facts. Preserve C1/C2 privacy and exception scopes; no new authorization or disclosure is established.",
                "The old record, source dates, source flags and all previous R16 current-source bindings remain unchanged. This proposal appends only an exact approved exception_flow.",
                "G1 separately says pay stubs verified in eWork can be returned without an additional fax to eView or EP. This example does not establish prior verification, invent a precedence rule for overlapping conditions, or add a substitute for an unavailable eWork tickle.",
                "This is the named EP fallback, not an instruction to fax into both eView and EP. Local procedures and receipt/privacy conditions remain separate."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual input, receipt delivery, jurisdiction or evidence handoff, evaluation and subsequent benefit outcome remain unverified."
            ]
          }
        },
        "original_record": {
          "source": "workreceipt",
          "section": "G opening; G.1",
          "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
          "source_receipt": {
            "report": "service-batch14-workreport-preparation.json",
            "snapshot_path": "sources\\workreports020-current-20261025.html",
            "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
            "checked_on": "2026-10-25"
          },
          "id": "ework-not-available",
          "title": "SSA cannot use eWork for your TitleII pay stubs",
          "when": "Another office owns the pending TitleII work review and the intake technician cannot use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
          "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
          "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
          "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
          "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
          "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
          "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
        },
        "journey_signature": {
          "id": "report-disability-work",
          "category": "Disability",
          "title": "Report a work change while receiving disability",
          "short": "Keep a work-report receipt and understand who owns follow-up.",
          "story": "Jane starts work or changes her hours while receiving disability benefits.",
          "scope": "Selected procedural path; not every eligibility rule or exceptional case is modeled.",
          "level": "Procedural walkthrough",
          "review_status": "Selected claims checked; exceptions remain",
          "path": [
            "You",
            "FO / TSC report intake",
            "Existing review owner if any",
            "Receipt / further review"
          ],
          "channels": {
            "office": "POMS accepts in-person reports; confirm appointment arrangements.",
            "phone": "POMS accepts telephone work reports.",
            "online": "Current SSA customer guidance describes online wage reporting and an SSA-795 upload route. This does not mean every work change is handled by the wage-reporting screen."
          },
          "checklist": [
            "Identify what changed and when.",
            "Prepare available wage or work evidence.",
            "Keep the report receipt; it is not a benefit determination."
          ],
          "steps": [
            {
              "id": "report-disability-work-1",
              "title": "Report the change",
              "you": "Explain the change and date.",
              "ssa": "Record the work report and check for a pending review.",
              "owner": "SSA intake technician",
              "route": "eWork / review owner",
              "next": "A receipt documents the report date.",
              "source": "workreceipt",
              "section": "A–D",
              "systems": [
                "eWork"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-2",
              "title": "Receive acknowledgement",
              "you": "Keep the receipt.",
              "ssa": "Give or mail the required receipt using the applicable channel rule.",
              "owner": "SSA intake technician",
              "route": "Reporter / eligible recipient",
              "next": "Receipt does not decide the earnings effect.",
              "source": "workreceipt",
              "section": "C.1",
              "systems": [
                "eWork",
                "DPS"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            },
            {
              "id": "report-disability-work-3",
              "title": "Follow the existing review",
              "you": "Respond to further requests.",
              "ssa": "A pending review’s jurisdiction receives the report automatically.",
              "owner": "Office with review jurisdiction",
              "route": "Pending work review",
              "next": "The responsible technician evaluates the information.",
              "source": "workreceipt",
              "section": "F",
              "systems": [
                "eWork",
                "DCF"
              ],
              "timing": "No completion duration established",
              "verification": "Selected public subsection checked"
            }
          ],
          "decision": null,
          "timing": "For covered in-person/phone reports, give or mail the receipt immediately; mailed, faxed or dropped-off reports: establish and mail within five days. These are receipt instructions, not a claim-decision deadline.",
          "timing_type": "Source-specific timing",
          "outcome": "A recorded work report, the applicable receipt, and routing to the work-review owner. Any effect on benefits needs separate evaluation.",
          "gaps": [
            "Remaining cross-references, individual eligibility and notice deadlines need further review.",
            "Instructions describe required handling, not independently measured office performance."
          ],
          "source_ids": [
            "workreceipt",
            "workpublic",
            "selfemploymentwork025run72",
            "workcdrfo025run72",
            "workdueprocess185run72",
            "worksuspension160run72",
            "workenforcement027run72",
            "vern675run72",
            "workexclusion25"
          ],
          "timing_source": {
            "source": "workreceipt",
            "section": "C.1"
          }
        },
        "ancestor_records": [
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "titleii-paystubs-pending-work-review",
            "title": "Your pay stubs belong to a pending disability work review",
            "when": "You receive TitleII disability benefits and submit pay stubs while a work review is pending.",
            "you": "Tell SSA that a work review is already open. Keep the receipt and respond to the office reviewing your work.",
            "ssa": "Check the eWork Development Worksheet and send the pay stubs to the field office responsible for the pending review. If another jurisdiction owns it, alert that office about the input and establish a one-day tickle on the development worksheet.",
            "route": "Pay-stub intake → responsible work-review field office; alert other jurisdiction when applicable",
            "next": "Pay-stub input alone does not evaluate the effect of earnings on benefits; the responsible technician still evaluates the information.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          },
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "another-review-jurisdiction",
            "title": "Another field office owns the pending review",
            "when": "The TitleII pay-stub report belongs to a pending review in another jurisdiction. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
            "you": "Identify the office already reviewing your work and keep your receipt.",
            "ssa": "Send the pay stubs to the responsible review office. Alert that office to the input and establish the stated one-day eWork development-worksheet tickle when using this procedure.",
            "route": "Pay-stub intake → responsible review office in another jurisdiction",
            "next": "The reviewing office evaluates the earnings effect; the tickle is a staff control, not a decision deadline.",
            "timing": "The one-day tickle is a staff follow-up control, not a promise of a decision or payment adjustment within one day."
          },
          {
            "source": "workreceipt",
            "section": "G opening; G.1",
            "review_status": "Selected current TitleII pay-stub instructions independently checked2026-10-25. Customer next steps are editorial explanations; staff actions summarize published instructions. Concurrent and SSI-only procedures remain separate. Nested scenario prerequisites and separate verified-paystub condition manually reviewed 2026-10-25; source G opening and full G.1. Customer selection does not establish office jurisdiction or system availability.",
            "source_receipt": {
              "report": "service-batch14-workreport-preparation.json",
              "snapshot_path": "sources\\workreports020-current-20261025.html",
              "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
              "checked_on": "2026-10-25"
            },
            "id": "ework-not-available",
            "title": "SSA cannot use eWork for your TitleII pay stubs",
            "when": "Another office owns the pending TitleII work review and the intake technician cannot use eWork. The employer has already been established in eWork with a work report; this is the Title II pay-stub context described in G.",
            "you": "Keep your submission record and the work-report receipt. Follow SSA’s request for any additional information.",
            "ssa": "When unable to use eWork, fax the pay stubs into Evidence Portal, issue SSA-L724 through DPS and alert the technician responsible for evaluating work under local procedures. Separate condition: if pay stubs were already verified in eWork, the source permits returning them without an additional fax into eView or EP.",
            "route": "Intake technician → EP evidence and DPS receipt → responsible work evaluator",
            "next": "The responsible technician still evaluates the effect of earnings. This scenario does not establish that the pay stubs were verified earlier.",
            "timing": "No overall evaluation or payment-adjustment deadline is stated here. The unavailable-eWork fallback does not establish a substitute for the one-day eWork control.",
            "interpretation": "Conditional reuse of the existing independently reviewed fallback. No completion promise, automatic system edge or substitute eWork tickle is inferred."
          }
        ],
        "source_signatures": {
          "wages": {
            "code": "SSA guidance",
            "title": "Report monthly wages and other income",
            "url": "https://www.ssa.gov/ssi/reporting/wages",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssichanges": {
            "code": "SSA guidance",
            "title": "SSI Reporting Responsibilities",
            "url": "https://www.ssa.gov/ssi/text-report-ussi.htm",
            "revision": "Public page; no revision date asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16",
            "verification_scope": "Only the subsections and claims used in this walkthrough were checked. No full-page or operational completeness claim."
          },
          "ssiwageevidence": {
            "code": "SI 00820.130",
            "title": "Evidence of Wages or Termination of Wages",
            "url": "https://secure.ssa.gov/poms.nsf/links/0500820130",
            "revision": "Rev2025-03-25; TN99 (03-25); live official page",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A.1.b A.5 and C evidence priority selected claims only; reported/verified and receipt rules require separate review",
            "additional_review_scopes": [
              {
                "checked_on": "2026-10-27",
                "scope": "SSI130C2h whole paystubcredibility examples/furtherevidence directive;A1b-A3/C2d-g ordinarycopy/missingdate/missingstub boundaries retained. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
                "snapshot_path": "sources/ssi-wage130-current-20261027.html",
                "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
                "revision": "2025-03-25;TN99(03-25)",
                "batch_run": "2026-09-11",
                "source_review": "service-SSI-paystub-C2h-manual-proposal.json"
              }
            ]
          },
          "ssimonthlywageprocessing": {
            "code": "SI 00820.143",
            "title": "Monthly Wage Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820143",
            "revision": "TN91(05-24); Rev2013-09-26; batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D1; F opening selected acceptance and receipt requirements"
          },
          "ssiwageestimates": {
            "code": "SI 00820.150",
            "title": "Estimating Future Wages",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820150",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E; F"
          },
          "ssiwageverificationcompanies": {
            "code": "SI 00820.147",
            "title": "Evidence of Wages from Wage Verification Companies",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820147",
            "revision": "TN91(05-24); Rev2023-11-20; batch2026-04-27",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "C1c; D1-2"
          },
          "ssicafeteriaplans": {
            "code": "SI 00820.102",
            "title": "Cafeteria Benefit Plans",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820102",
            "revision": "TN91(05-24); Rev2023-11-20; batch2025-09-18",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "D2; D3 selected evidence and routing steps"
          },
          "ssireportingresponsibilities": {
            "code": "SI 02301.005",
            "title": "SSI Posteligibility - Recipient Reporting",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502301005",
            "revision": "TN86(03-26); Rev/batch2026-03-11",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B1 B3-5 D1-3"
          },
          "ssinesedetermination": {
            "code": "SI 00820.210",
            "title": "How to Determine Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820210",
            "revision": "TN91(05-24); Rev2007-05-30; batch2026-01-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1 A4-6 B1"
          },
          "ssineseverification": {
            "code": "SI 00820.220",
            "title": "How to Verify Net Earnings from Self-Employment",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820220",
            "revision": "TN91(05-24); Rev2011-05-13; batch2026-10-02",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A B1-4 C2a,c selected evidence priority"
          },
          "ssinesecurrentestimate": {
            "code": "SI 00820.230",
            "title": "How to Estimate NESE for Current Taxable Year",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0500820230",
            "revision": "TN91(05-24); Rev/batch2024-05-29",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-3"
          },
          "ssimefmatch": {
            "code": "SI 02310.056",
            "title": "Master Earnings File Match J3 and J5 Diaries",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310056",
            "revision": "TN68(01-25); Rev2009-03-06; batch2025-09-15",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "E5 E7 selected evidence routes"
          },
          "ssialertdevelopment": {
            "title": "SI 02310.007 Processing Alerts from Computer Matches",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310007",
            "revision": "TN 43 (06-08); Rev 2008-06-23; batch 2026-09-18",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A.1 screening independently checked; B and disclosure cross-references remain separate scope",
            "code": "SI 02310.007"
          },
          "ssitaxinterview": {
            "code": "SI 02310.042",
            "title": "Tax Data Interface Interview Guidelines",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310042",
            "revision": "TN44; Rev2012-05-16; batch2012-05-21",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "B4 privacy only; special timing deferred"
          },
          "ssitaxdisclosure": {
            "code": "SI 02310.041",
            "title": "Disclosure of Tax Data",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310041",
            "revision": "TN12; Rev1994-07-11; batch2024-01-30",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 B1-2 authorization scope; other disclosure rules separate"
          },
          "ssiirslimited": {
            "code": "SI 02310.047",
            "title": "IRS Alert Development - Limited Development",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310047",
            "revision": "Rev2015-03-10; batch2026-09-10",
            "kind": "POMS selected staff procedure",
            "checked_on": "2026-10-17",
            "verification_scope": "A1-2 income transaction gates only; resource A3/4 separate"
          },
          "irsfulldevelopment": {
            "code": "SI 02310.048",
            "title": "IRS Alert Development - Full Development",
            "slug": "0502310048",
            "revision": "2013-08-13",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502310048",
            "checked_on": "2026-10-17",
            "kind": "POMS",
            "currency_note": "Live rev2013-08-13 batch2026-09-30 TN70(02-25); exact financialverification mechanisms require linked instructions, no invented electronic-only rule."
          },
          "ssipayroll": {
            "code": "SI 00820.148",
            "title": "Payroll Information Exchange Wage Evidence",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820148",
            "revision": "2025-03-25",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected cited public subsections checked; no full-case or operational screen certification."
          },
          "payrollauthorization": {
            "code": "GN 00204.150",
            "title": "Authorization to Obtain Wage and Employment Information from Payroll Data Providers",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0200204150",
            "revision": "Rev2025-06-18; TN150(07-25); batch2026-03-11; live official checked2026-10-16",
            "kind": "POMS staff procedure",
            "checked_on": "2026-10-16",
            "verification_scope": "A; B.1-3 B.6; C.2 selected voluntary authorization, authority, receipt and reporting distinction"
          },
          "workreceipt": {
            "code": "DI 13010.020",
            "title": "Work Reports and Receipts",
            "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0413010020",
            "revision": "2024-06-14",
            "kind": "POMS",
            "checked_on": "2026-10-16",
            "verification_scope": "Selected subsections checked; remaining cross-references and operational execution not independently verified.",
            "additional_review_scopes": [
              {
                "section": "G.2; C.1 receipt conditions; G.3 held exception context",
                "checked_on": "2026-10-26",
                "scope": "Selected first-time/change concurrent work-report route;BWE/IRWE cases excluded;linked144404 held. Receipt timing is not decision timing.",
                "snapshot_path": "sources/workreports020-concurrent-current-20261026.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent020-integration-gate.json"
              },
              {
                "section": "E whole steps1-2;D/F context only",
                "checked_on": "2026-10-26",
                "scope": "Selected whole E pending same-employer work report: new employment period Add, same period Edit, and new receipt for listed reporters. D initial-report and F pending-review conditions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work-report020E-integration-gate.json"
              },
              {
                "section": "D whole selected deemor soon-to-start/no-paystub paragraph;C.1-C.2 whole receipt/privacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected upcoming deemor work without paystubs;DPS SSA-L724 to beneficiary/payee. Whole C1/C2 receipt privacy and channel-dependent timing retained;routine monthly wages and SSIMWV exclusions separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor020D-integration-gate.json"
              },
              {
                "section": "G.1 whole selected no-pending-review/missing-employer condition;C.1-C.2 whole receipt/privacy boundaries",
                "checked_on": "2026-10-26",
                "scope": "WholeG1 selected no-pending-review and missing-employer WorkReport then paystub input;Gopening benefit-evaluation limit and C1/C2receipt/privacy retained;pendingreview/unavailable/concurrent routes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020G1-integration-gate.json"
              },
              {
                "section": "C.2 whole selected outside-reporter andthird-party-request receipt/privacy paragraphs;C.1 whole reporter/recipient/channel boundaries",
                "checked_on": "2026-10-26",
                "scope": "Whole C.1/C.2 selected outside-reporter receipt request and privacy route; mandatory reporter/recipient table and channel timing retained; deemor upcoming-work and other exception routes remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-work020C2-integration-gate.json"
              },
              {
                "section": "C.2 whole selected Title XVI consistently-under-$65 receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected TitleXVI consistently-under65 receipt exception;currentmonth AND consistentpattern andwholeBreporting duties/C1roles/channel/privacy retained;otherreporting/benefit scopes separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-ssi-low65-integration-gate.json"
              },
              {
                "section": "C.2 whole selected CDR-mailer/already-developed receipt exception; B whole reporting duties; C.1 whole reporter/recipient/channel context",
                "checked_on": "2026-10-26",
                "scope": "Whole C2 selected CDR-mailer AND already-developed work receipt exception; B reporting duties and C1 roles/channel/privacy retained; CDREO review-form exception and medical-review/benefit decisions remain separate.",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-cdr-mailer-integration-gate.json"
              },
              {
                "section": "G.3 whole concurrent MSSICS work-expense exclusion; G opening and G.2 whole context; C.1 whole receipt conditions",
                "checked_on": "2026-10-26",
                "scope": "Whole G3 concurrent MSSICS BWE/IRWE input exclusion with G opening/G2/C1;IRWE-onlyTitleIIawareness retained;144detailheld/noalternativeinputorallowance",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-concurrent-g3-exclusion-integration-gate.json"
              },
              {
                "section": "D whole deemor paragraph,selected SSIMWV-exclusion condition;C.1-C.2 whole receipt andprivacy context",
                "checked_on": "2026-10-26",
                "scope": "Whole D selected deemor SSIMWV-exclusion receipt route with C1/C2 reporter,recipient,privacy andchannel timing;no exclusioncriteria oralternative wageinput;soon-to-start/no-paystub andconcurrentG3 separate",
                "snapshot_path": "sources/workreports020-current-20261025.html",
                "snapshot_sha256": "751755959d29455ac0add7f27fd9f687997beb06eb46896460a1ac60563080f3",
                "report": "service-deemor-ssimwv-exclusion-integration-gate.json"
              }
            ]
          },
          "ssiwage135run72": {
            "code": "SI00820.135",
            "title": "Wage Verification and Reported Wages Over $65 per Month",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0500820135",
            "kind": "Published SSA worker instructions; selected evidence-development scope",
            "revision": "2023-11-20",
            "transmittal": "TN99(03-25)",
            "batch_run": "2026-10-15",
            "checked_on": "2026-10-27",
            "snapshot_path": "sources/ssi-wage135-current-20261027.html",
            "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
            "scope": "SelectedB1steps10-11withwholechartcontext; notallcrossreferences oractualruntime."
          },
          "workpublic": {
            "code": "SSA guidance",
            "title": "Report changes to work and income",
            "url": "https://www.ssa.gov/disability/reporting/wages",
            "revision": "Public page; revision date not asserted",
            "kind": "SSA customer guidance",
            "checked_on": "2026-10-16"
          },
          "selfemploymentwork025run72": {
            "code": "DI 10510.025",
            "title": "Documenting Self-Employment Cases Using the SSA-820-BK and SSA-823",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0410510025",
            "revision": "2025-01-08",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "verification_scope": "A; C.3; D.1; E selected self-employment work-CDR documentation only. No SGA threshold, initial claim or whole-page certification.",
            "snapshot_path": "../../sources/self-employment-work025-current-20261025.html",
            "snapshot_sha256": "ed39c1130fc3f4136bb3bc84b6654579044c84a2d9cda38e44a5675da1c9fede",
            "currency_note": "Revision2025-01-08; TN23(12-25); batch2026-10-21; captured2026-10-25. These are distinct date kinds."
          },
          "workcdrfo025run72": {
            "code": "DI 13010.025",
            "title": "Field Office (FO) Responsibilities in Work Continuing Disability Reviews (CDRs)",
            "slug": "0413010025",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010025",
            "revision": "2026-05-08",
            "batch_run": "2026-05-08",
            "transmittal": "TN 94 (05-26)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "1820ad8554eb31130ef68b16cc129eff2b65858480f3b6e5dd8fcfb4bee88423",
            "verification_scope": "B.5 only: accurate input, adjudicator responsibility, staff RO/AWIC escalation. B.4/B.6 preserved as context; no operational certification."
          },
          "workdueprocess185run72": {
            "code": "DI 13010.185",
            "title": "Due Process in Work Issue Cases",
            "slug": "0413010185",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010185",
            "revision": "2024-06-13",
            "batch_run": "2026-09-14",
            "transmittal": "TN 85 (01-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
            "verification_scope": "H.3 evidence-time request including rare further-time exception; H.2/H.4-H.6 and D/E context retained. No personal eligibility, appeal-deadline or payment-continuation determination.",
            "additional_review_scopes": [
              {
                "section": "H.4 whole including NOTE; H.2-H.3 and H.5-H.6 response and determination boundaries; D-E context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefacknowledgment/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185H4-acknowledgment-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context",
                "checked_on": "2026-10-26",
                "scope": "WholeH4includingNOTE with wholeH andD-E context;additionalinformationchangesnoaspectofproposeddecision/briefmaterial-conflict/no-significance statement/laterformaldecision;no merits,outcome,newclockorcontinuedpayment inferred",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service-work185G-material-conflict-integration-gate.json"
              },
              {
                "section": "DI13010.185G whole; A-F and H-I context (scope wording correction)",
                "checked_on": "2026-10-26",
                "scope": "Corrects inherited H4 wording in the preceding G scope note. WholeG covers both material-conflict triggers, resolution with beneficiary and written notice even when beneficiary supplied adverse evidence; no personal outcome, new deadline or continued payment inferred. Original scope entry retained as history.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "report": "service876-work185G-scope-correction.json"
              },
              {
                "checked_on": "2026-10-27",
                "section": "DI13010.185I whole; A-H work-issue and notice context",
                "scope": "Whole DI13010.185I auxiliarydueprocess household/nonpayment/suspense distinction; A-H context. Work-issue due process only; not medical CDR or EXR award notice rules. Provide due process even when auxiliaries are in suspense. For auxiliaries already in nonpayment, modify language to exclude receipt-of-benefits and benefits-being-paid references. Prepare and release notices including file copy at the same time as primary-beneficiary due process. Do not infer a separate notice for an auxiliary living in the same household as the primary. Advise non-household auxiliaries of proposed adverse action before cessation or termination. No benefit-continuation entitlement, restart or payment promise is established. No appeal period, new response clock or processing turnaround is inferred from section I. Customer suggestions are Atlas explanations; published staff instructions remain distinct.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13;TN85(01-25)",
                "batch_run": "2026-09-14",
                "source_review": "service-work185I-auxiliary-manual-proposal.json"
              },
              {
                "section": "H.6 whole; H.1-H.5, D-G and I context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H6 whole earlier-date trigger/revised notice; H1-H5,D-G,I contexts preserved. Applies when the beneficiary response causes an earlier cessation date than the original notice. A new due-process notice must include revised information; this is not the final determination notice. H6 does not establish the same result for later dates or unrelated corrections. No separately specified H6 response-period restart, extension or appeal deadline is inferred; H2-H3 remain distinct. No guaranteed payment continuation, merits outcome, waiver, fraud or eligibility finding. Concurrent-program separate-notice requirements in F and E exceptions remain independently applicable. H3 more-time, H4 no-significance acknowledgment, H5 written no-more-evidence and G material-conflict rules stay separate. Auxiliary household/suspense notice limits in I remain unchanged. Published worker notice actions do not prove eWork automatically mails a notice or a physical interface.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H6-earlier-date-integration-gate.json"
              },
              {
                "section": "H.5 whole; H.2-H.4/H.6 and A-G/I full context retained separately",
                "checked_on": "2026-10-27",
                "scope": "H5 whole written-response trigger; H2-H4/H6 and A-G/I contexts and all prior source branches retained. Only the work-issue due-process H5 procedure; no general waiver or appeal procedure. Requires the beneficiary response in writing that no additional evidence will be submitted; silence, a telephone statement or missing documents do not meet this trigger. The ordinary 15-day wait remains unless that written statement is received; H2 response/mail-time and H3 extensions remain separate. Immediate final-determination processing is a published staff instruction, not a promised processing deadline or guaranteed customer outcome. Do not advise a beneficiary to give up evidence, request cessation or sign such a statement; seeking more time and disputing evidence remain separate routes. The final formal decision and its notice are distinct from the proposed due-process notice; no appeal deadline or payment-continuation result inferred. H4 acknowledgment and H6 revised earlier-date notice remain separate, as do G material-conflict and I auxiliary-notice rules. H5 names eWork DW documentation and storage in eView or EP; it does not prove automatic transmission, a new interface, or an actual screen execution. TitleII/TitleXVI concurrent-notice and E exception boundaries remain intact; no independent benefit eligibility finding.",
                "snapshot_path": "sources/work-due-process185-current-20261025.html",
                "snapshot_sha256": "e0c1a3c3ef89e82182ebb5b02a0bcf7d9a67a4892adb65cfbab576c2816fddd6",
                "revision": "2024-06-13",
                "batch_run": "2026-09-14",
                "report": "service-work185H5-written-response-integration-gate.json"
              }
            ]
          },
          "worksuspension160run72": {
            "code": "DI 13010.160",
            "title": "Suspending Benefits for Title II",
            "slug": "0413010160",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010160",
            "revision": "2024-06-25",
            "batch_run": "2026-09-14",
            "transmittal": "TN 81 (09-24)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "preserved_snapshot_sha256": "21fbb15f5c1613603000bd7cadd542a81e67886eca753e02eb3f5f0462964ecd",
            "verification_scope": "B.1.a failed DIB CESS input with distinct B.1.b POS exclusion and limiting A.2/B.1/B.2 context. Published staff instructions; customer follow-up is an explanation, not an instruction to use internal systems. No eligibility/payment result or timing guarantee."
          },
          "workenforcement027run72": {
            "code": "DI 13010.027",
            "title": "Continuing Disability Review (CDR) Earnings Enforcements",
            "slug": "0413010027",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010027",
            "revision": "2025-08-14",
            "batch_run": "2026-10-15",
            "transmittal": "TN 88 (09-25)",
            "checked_on": "2026-10-25",
            "kind": "POMS staff instructions",
            "snapshot_path": "sources/work-enforcement027-current-20261025.html",
            "snapshot_sha256": "ff7e4d56ebeb25c7ee4f4c1d2c1fb80bf54a0c0fcda9d275e288c151681ba069",
            "verification_scope": "Whole DI13010.027E.2 checked2026-10-25 with E.1 and A-D context retained. Pending report/no initiated work review only; staff control clearance is distinct from a substantive benefit decision. No payment or completion guarantee."
          },
          "vern675run72": {
            "code": "DI 13010.675",
            "title": "The Verify/Update Earnings (VERN) Screen",
            "slug": "0413010675",
            "revision": "2012-10-01",
            "checked_on": "2026-10-26",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010675",
            "snapshot_path": "sources/vern675-current-20261026.html",
            "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
            "kind": "POMS",
            "currency_note": "Printed revision2012-10-01; batch2026-07-29; exact source retrieved and selected H with D context reviewed2026-10-26. Detailed cross-references remain held.",
            "additional_review_scopes": [
              {
                "section": "H whole; D display-only context",
                "checked_on": "2026-10-26",
                "snapshot_path": "sources/vern675-current-20261026.html",
                "snapshot_sha256": "ea6425bed9e0ceb458e3a5bce347604f3782e5a6b0963516e5cc109296f5566c",
                "report": "service-vern675-ssi-display-correction-integration-gate.json",
                "scope": "Title XVI display-only data/underlying SSR correction/conditional IRMK explanation/sole paid-versus-earned exception; detailed linked input instructions held."
              }
            ]
          },
          "workexclusion25": {
            "code": "DI 13010.026",
            "slug": "0413010026",
            "title": "Processing eWork Exclusion Cases",
            "revision": "2025-01-03",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0413010026",
            "checked_on": "2026-10-25",
            "kind": "POMS",
            "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
            "snapshot_path": "sources\\ework-exclusion-20261025.html",
            "currency_note": "Published heading revision retained separately from retrieval. Selected A.1–2 and B reviewed; no complete cross-reference or internal KCNET review.",
            "additional_verification_scopes": [
              {
                "section": "A.3 whole; A opening/A1-A2 and B context",
                "checked_on": "2026-10-27",
                "report": "service-ework026-A3-integration-gate.json",
                "snapshot_sha256": "021db790cc4be748752c4cb314d5555c2b2a61252b772c1889b601b806ede3c6",
                "scope": "Manual work CDR procedure; no payment or eligibility outcome, KCNET timing or physical interface inference."
              }
            ]
          }
        }
      }
    },
    "counts": {
      "inherited_routes_mapped": 16,
      "top": 13,
      "nested": 3,
      "minimum_cards": 1,
      "maximum_cards": 3,
      "current_frozen_R22_flow_count_unchanged": 41,
      "prospective_future_mapped": 57,
      "prospective_remaining_legacy": 1007
    },
    "projection_contract": "Append exception_flow to exactly these16 existing records. Strip only exactapprovedflow fields on these16 to reconstruct the entire currentR22data/workflows; every oldrecord/source/status/R16binding/other41flow remains exact. Existing export packets for these journeys may grow approvedflows; entire nonflow selectedroute and allother metadata stay exact. Concrete query pins must be captured independently before integration.",
    "source_holds": [
      "Detailed SI00820.143/144 monthly wage/input/work-incentive procedures are not supplied; no guessed exclusion criteria or fallback.",
      "Do not equate sourceC1 SSA-724 label automatically with sourceD/G SSA-L724 or create a native form alias.",
      "Unable-eWork fallback and separately verified-in-eWork/no-fax condition remain distinct; no invented mutual exclusivity or precedence, prior verification or substitute tickle.",
      "eWork F source-described assignment/DCF consequence is not current runtime proof and does not generalize to G pay-stub inputs."
    ],
    "negative_QA": [
      {
        "input": "Currentmonthlyunder65 but no consistentpattern",
        "required_boundary": "C2 narrowexception notestablished."
      },
      {
        "input": "Deemorreport",
        "required_boundary": "Do not enter deemorworkreportineWork; receipt recipient notautomaticallydeemor."
      },
      {
        "input": "Pendingworkreport vs pendingworkreview",
        "required_boundary": "EAdd/Edit periodlogic separate fromFjurisdictionlogic."
      },
      {
        "input": "Sameperiod report",
        "required_boundary": "Edit underE1, notDinitialreportcaution generalized."
      },
      {
        "input": "CDREOalert but differentform",
        "required_boundary": "RequireSSA821BK ORSSA820BKresponse; notallforms."
      },
      {
        "input": "CDRmailer but worknotdeveloped",
        "required_boundary": "BothC2predicatesrequired."
      },
      {
        "input": "Paystubinput alone",
        "required_boundary": "No benefit-effect evaluation or work-reportcontrols inferred."
      },
      {
        "input": "Otherjurisdiction",
        "required_boundary": "One-day tickle isstaffcontrol notdecisiondeadline."
      },
      {
        "input": "UnableeWork",
        "required_boundary": "No invented replacementtickle; EP OR/alternative destination notbothautomatic."
      },
      {
        "input": "Priorverification unknown",
        "required_boundary": "Not automaticallyverified or false; return/no-fax condition separate."
      },
      {
        "input": "BWEonly concurrentcase",
        "required_boundary": "No automaticIRWE-specificTitleIIcommunicationpremise."
      },
      {
        "input": "GenericMSSICSname",
        "required_boundary": "No CCE/systemidentity/alias inferred."
      },
      {
        "input": "Thirdparty outsideC1roles requestsreceipt",
        "required_boundary": "No directPII receipt; beneficiary/payee mailing instruction remains."
      },
      {
        "input": "SamechildID underdifferentparents",
        "required_boundary": "Fullparentpaths remain distinct; allancestorbindings required."
      },
      {
        "input": "Flow fields changed",
        "required_boundary": "Selectedreviewmust failclosed; source/history unchanged."
      }
    ],
    "new_native_entities_aliases_edges_acceptance": false,
    "frozen_R22_or_live_writes": false,
    "independent_source_review_sha256": "a3e3d485cc511c0795926de662b95fed2bbf82b54865b9fe6f0da1b91d8a10a2",
    "public_capture_links": {
      "maintext_url": "/service/sources/DI13010.020-r23-main.txt",
      "snapshot_url": "/service/sources/DI13010.020-r23-DOM-snapshot.txt",
      "metadata_url": "/service/sources/DI13010.020-r23-metadata.json"
    }
  },
  "r24_selected_twenty": {
    "schema": "securitystat.selected-sequence-ledger/1",
    "scope": "Twenty source-defined flows on existing routes only; retained old source histories are not re-dated. No whole-page acceptance, actual case finding, native adoption or measured processing time.",
    "flows": {
      "medical-records-authorization/undated-authorization": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "undated-authorization",
        "full_route": "medical-records-authorization/undated-authorization",
        "entry_conditions": [
          "The SSA-827 has no date of signing."
        ],
        "steps": [
          {
            "id": "undated-authorization-step-1",
            "title": "Return the undated form",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Return the form for the claimant to date; do not request an undated SSA-827.",
            "conditions": [
              "The required date is missing."
            ],
            "source": "ssa827signature",
            "section": "A",
            "source_context_refs": [
              "DI11005.056-A",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "undated-authorization-step-2",
            "title": "Complete the signing date",
            "kind": "you",
            "actor": "Claimant",
            "action": "Date the form with the date of signing. Staff do not supply an invented date for the claimant.",
            "conditions": [
              "The form has been returned for dating."
            ],
            "source": "ssa827signature",
            "section": "A",
            "source_context_refs": [
              "DI11005.056-A",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/payee-not-signing-authority": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "payee-not-signing-authority",
        "full_route": "medical-records-authorization/payee-not-signing-authority",
        "entry_conditions": [
          "A representative payee or appointed representative proposes to sign as an other personal representative."
        ],
        "steps": [
          {
            "id": "payee-not-signing-authority-step-1",
            "title": "Check the separate authority basis",
            "kind": "action",
            "actor": "SSA staff",
            "action": "A payee or appointed-representative designation alone is not authority to sign the SSA-827 as an other personal representative. Apply the separately applicable state-law authority requirement.",
            "conditions": [
              "The proposed signer relies on payee or appointed-representative status."
            ],
            "source": "ssa827signature",
            "section": "B",
            "source_context_refs": [
              "DI11005.056-B",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "payee-not-signing-authority-step-2",
            "title": "Explain an established authority basis",
            "kind": "you",
            "actor": "Authorized signer",
            "action": "If signing as an other personal representative under an established applicable authority, explain that basis in the space on the form. This walkthrough does not establish that authority.",
            "conditions": [
              "Other-personal-representative authority is established under the applicable rule."
            ],
            "source": "ssa827signature",
            "section": "B",
            "source_context_refs": [
              "DI11005.056-B",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/physically-unable-sign": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "physically-unable-sign",
        "full_route": "medical-records-authorization/physically-unable-sign",
        "entry_conditions": [
          "The claimant agrees to authorize disclosure.",
          "The claimant is physically incapable of signing by all permissible means, including pen and ink, click and sign and attestation."
        ],
        "steps": [
          {
            "id": "physically-unable-sign-step-1",
            "title": "Annotate the authorization",
            "kind": "action",
            "actor": "FO",
            "action": "Write “Individual physically unable to sign” in the INDIVIDUAL authorizing disclosure box.",
            "conditions": [
              "Both agreement and incapacity by permissible means are established."
            ],
            "source": "ssa827signature",
            "section": "C1",
            "source_context_refs": [
              "DI11005.056-C1",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "physically-unable-sign-step-2",
            "title": "Alert DDS through EDCS",
            "kind": "action",
            "actor": "FO",
            "action": "Annotate the Remarks screen on EDCS 3367 to alert DDS to the situation.",
            "conditions": [
              "The C1 physical-incapacity conditions apply."
            ],
            "source": "ssa827signature",
            "section": "C1",
            "source_context_refs": [
              "DI11005.056-C1",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "physically-unable-sign-step-3",
            "title": "Explain the situation to the medical source",
            "kind": "action",
            "actor": "DDS",
            "action": "Explain in a cover letter that the claimant is physically unable to sign the SSA-827.",
            "conditions": [
              "The C1 physical-incapacity conditions apply."
            ],
            "source": "ssa827signature",
            "section": "C1",
            "source_context_refs": [
              "DI11005.056-C1",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "physically-unable-sign-step-4",
            "title": "Provide the annotated form",
            "kind": "action",
            "actor": "DDS",
            "action": "Provide the medical source a copy bearing the specified physical-incapacity annotation.",
            "conditions": [
              "The C1 physical-incapacity conditions apply."
            ],
            "source": "ssa827signature",
            "section": "C1",
            "source_context_refs": [
              "DI11005.056-C1",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/minor-age12-signatures": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "minor-age12-signatures",
        "full_route": "medical-records-authorization/minor-age12-signatures",
        "entry_conditions": [
          "The claimant is at least 12 and is still a minor under applicable state law.",
          "Signer authority and the relevant source/state-law conditions must be established; unknown facts select no exception automatically."
        ],
        "steps": [
          {
            "id": "minor-age12-signatures-step-1",
            "title": "Ordinary two-signature instruction",
            "kind": "you",
            "actor": "Child and authorized adult",
            "action": "The child signs the left INDIVIDUAL box. The authorized adult marks the relationship, signs below the check boxes and explains other-personal-representative authority when applicable. Complete the date of signing.",
            "conditions": [
              "The C3 ordinary rule applies; no applicable exception displaces it."
            ],
            "source": "ssa827signature",
            "section": "C3",
            "source_context_refs": [
              "DI11005.056-C3",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "minor-signature-scope"
          },
          {
            "id": "minor-age12-signatures-step-2",
            "title": "Possible waiver of the child signature",
            "kind": "action",
            "actor": "FO",
            "action": "If the parent or guardian strongly objects AND the source accepts the form without the child signature, the FO may waive it, document the waiver in EDCS 3367 Remarks and follow C4. If the source requires both signatures, explain that requirement and follow the published D2b reference.",
            "conditions": [
              "Strong parental/guardian objection AND source acceptance without the child signature are both established for the waiver."
            ],
            "source": "ssa827signature",
            "section": "C3",
            "source_context_refs": [
              "DI11005.056-C3",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "minor-signature-scope"
          },
          {
            "id": "minor-age12-signatures-step-3",
            "title": "Confidential minor treatment",
            "kind": "you",
            "actor": "Claimant",
            "action": "Only the claimant signs when applicable state law provides confidential minor treatment without parental or guardian consent or knowledge.",
            "conditions": [
              "The applicable confidential-treatment state-law condition is established."
            ],
            "source": "ssa827signature",
            "section": "C3",
            "source_context_refs": [
              "DI11005.056-C3",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "minor-signature-scope"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "minor-signature-scope",
            "label": "Different source-conditioned instructions",
            "logic": "source_conditions_determine_branch",
            "note": "These are conditional alternatives, not a sequence of all three actions. The source supplies no precedence rule for overlapping exceptions; unclear facts require review."
          }
        ]
      },
      "medical-records-authorization/child-under12": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-under12",
        "full_route": "medical-records-authorization/child-under12",
        "entry_conditions": [
          "The claimant is under 12.",
          "The child’s applicant has the applicable authority to sign."
        ],
        "steps": [
          {
            "id": "child-under12-step-1",
            "title": "Sign and identify the relationship",
            "kind": "you",
            "actor": "Child’s applicant",
            "action": "Sign in the INDIVIDUAL authorizing disclosure box and mark the appropriate relationship entry.",
            "conditions": [
              "The claimant is under 12 and the applicant is the appropriate signer."
            ],
            "source": "ssa827signature",
            "section": "C4",
            "source_context_refs": [
              "DI11005.056-C4",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "child-under12-step-2",
            "title": "Explain other representative authority when applicable",
            "kind": "you",
            "actor": "Child’s applicant",
            "action": "If signing as an other personal representative, explain the authority basis in the space provided. Attestation is permitted in this situation only subject to its own D2 conditions.",
            "conditions": [
              "The signer acts as an other personal representative for the explanation; any attestation must independently satisfy D2."
            ],
            "source": "ssa827signature",
            "section": "C4",
            "source_context_refs": [
              "DI11005.056-C4",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/review-before-attestation": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "review-before-attestation",
        "full_route": "medical-records-authorization/review-before-attestation",
        "entry_conditions": [
          "The person has not reviewed the SSA-827, or chooses not to attest."
        ],
        "steps": [
          {
            "id": "review-before-attestation-step-1",
            "title": "Provide an opportunity to review",
            "kind": "action",
            "actor": "SSA or DDS employee",
            "action": "Give the person an opportunity to review the form before attestation. On telephone contact, use the source’s review arrangements; do not attest before review.",
            "conditions": [
              "The form has not been reviewed."
            ],
            "source": "ssa827signature",
            "section": "D2b",
            "source_context_refs": [
              "DI11005.056-D2b",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "review-before-attestation-step-2",
            "title": "Attest only if separately permitted",
            "kind": "action",
            "actor": "SSA or DDS employee",
            "action": "Proceed only after review, when the person chooses attestation and the D2a signer/contact conditions and applicable procedure are met. Review alone does not establish consent.",
            "conditions": [
              "Review is complete AND the person chooses attestation AND all applicable D2a conditions hold."
            ],
            "source": "ssa827signature",
            "section": "D2a",
            "source_context_refs": [
              "DI11005.056-D2a",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "review-signature-choice"
          },
          {
            "id": "review-before-attestation-step-3",
            "title": "Use the pen-and-ink alternative",
            "kind": "you",
            "actor": "Signer",
            "action": "The person can opt out before attestation is complete and use the paper pen-and-ink process. Not submitting the authorization invokes separately referenced instructions; this illustration does not decide denial or cooperation.",
            "conditions": [
              "The person chooses not to attest or opts out before completion."
            ],
            "source": "ssa827signature",
            "section": "D2b",
            "source_context_refs": [
              "DI11005.056-D2b",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "review-signature-choice"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "review-signature-choice",
            "label": "Signature choice after the applicable review",
            "logic": "source_conditions_determine_branch",
            "note": "Choose only the applicable instruction. No automatic consent or completed signing is inferred."
          }
        ]
      },
      "medical-records-authorization/adult-court-incompetence-signer": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "adult-court-incompetence-signer",
        "full_route": "medical-records-authorization/adult-court-incompetence-signer",
        "entry_conditions": [
          "A court has deemed the adult claimant incompetent.",
          "A guardian or another person authorized under state law is available."
        ],
        "steps": [
          {
            "id": "adult-court-incompetence-signer-step-1",
            "title": "Use the source-qualified signer",
            "kind": "you",
            "actor": "Authorized guardian or state-law representative",
            "action": "Sign in the INDIVIDUAL authorizing disclosure box. In the court-incompetence situation the claimant should not sign; in the no-appointed-representative situation use the proper applicant who signed the application.",
            "conditions": [
              "A court has deemed the adult claimant incompetent.",
              "A guardian or another person authorized under state law is available."
            ],
            "source": "ssa827signature",
            "section": "C2",
            "source_context_refs": [
              "DI11005.056-C2",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "adult-court-incompetence-signer-step-2",
            "title": "Record relationship and authority",
            "kind": "you",
            "actor": "Authorized guardian or state-law representative",
            "action": "Mark the appropriate relationship entry. If signing as an other personal representative, explain the authority basis in the space provided.",
            "conditions": [
              "The selected C2 signer conditions are established."
            ],
            "source": "ssa827signature",
            "section": "C2",
            "source_context_refs": [
              "DI11005.056-C2",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/no-appointed-adult-representative": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "no-appointed-adult-representative",
        "full_route": "medical-records-authorization/no-appointed-adult-representative",
        "entry_conditions": [
          "The adult claimant is unable to sign.",
          "The claimant does not have a legally appointed representative.",
          "The proper applicant who signed the benefit application is identified under the applicable proper-applicant rule."
        ],
        "steps": [
          {
            "id": "no-appointed-adult-representative-step-1",
            "title": "Use the source-qualified signer",
            "kind": "you",
            "actor": "Proper applicant who signed the application",
            "action": "Sign in the INDIVIDUAL authorizing disclosure box. In the court-incompetence situation the claimant should not sign; in the no-appointed-representative situation use the proper applicant who signed the application.",
            "conditions": [
              "The adult claimant is unable to sign.",
              "The claimant does not have a legally appointed representative.",
              "The proper applicant who signed the benefit application is identified under the applicable proper-applicant rule."
            ],
            "source": "ssa827signature",
            "section": "C2",
            "source_context_refs": [
              "DI11005.056-C2",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "no-appointed-adult-representative-step-2",
            "title": "Record relationship and authority",
            "kind": "you",
            "actor": "Proper applicant who signed the application",
            "action": "Mark the appropriate relationship entry. If signing as an other personal representative, explain the authority basis in the space provided.",
            "conditions": [
              "The selected C2 signer conditions are established."
            ],
            "source": "ssa827signature",
            "section": "C2",
            "source_context_refs": [
              "DI11005.056-C2",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/electronic-attestation-copy": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "electronic-attestation-copy",
        "full_route": "medical-records-authorization/electronic-attestation-copy",
        "entry_conditions": [
          "A D2a permitted signer chooses attestation during a qualifying interview/contact.",
          "The signer has reviewed the form and agrees to authorize disclosure.",
          "The special D2f procedure is not applicable; two signatures or an excluded claim without an associated electronic folder require separate handling."
        ],
        "steps": [
          {
            "id": "electronic-attestation-copy-step-1",
            "title": "Confirm intent and attest",
            "kind": "action",
            "actor": "SSA or designated State agency employee",
            "action": "Confirm intent and agreement using the applicable script, then click Attest, Submit and Print in EDCS or eView. A refusal does not authorize attestation.",
            "conditions": [
              "A D2a permitted signer chooses attestation during a qualifying interview/contact.",
              "The signer has reviewed the form and agrees to authorize disclosure.",
              "The special D2f procedure is not applicable; two signatures or an excluded claim without an associated electronic folder require separate handling."
            ],
            "source": "ssa827signature",
            "section": "D2c",
            "source_context_refs": [
              "DI11005.056-D2c",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "electronic-attestation-copy-step-2",
            "title": "Electronic form is populated",
            "kind": "action",
            "actor": "SSA systems",
            "action": "The source describes propagation of the signer’s name, date and identity information and the attesting employee’s information onto the electronic form. This describes the source procedure, not observed runtime execution.",
            "conditions": [
              "The permitted standard attestation has been completed."
            ],
            "source": "ssa827signature",
            "section": "D2c",
            "source_context_refs": [
              "DI11005.056-D2c",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "electronic-attestation-copy-step-3",
            "title": "Associate the electronic form",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Under the standard electronic procedure, the signed form is automatically added to the electronic folder; do not separately fax or scan that form under this instruction.",
            "conditions": [
              "The standard electronic procedure applies; do not extend this no-fax instruction to D2f paper handling."
            ],
            "source": "ssa827signature",
            "section": "D2c",
            "source_context_refs": [
              "DI11005.056-D2c",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "electronic-attestation-copy-step-4",
            "title": "Give the person a copy",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Provide a printed copy of the signed authorization for the person’s records.",
            "conditions": [
              "The applicable standard attestation is complete."
            ],
            "source": "ssa827signature",
            "section": "D2d",
            "source_context_refs": [
              "DI11005.056-D2d",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        }
      },
      "medical-records-authorization/dual-or-excluded-attestation": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dual-or-excluded-attestation",
        "full_route": "medical-records-authorization/dual-or-excluded-attestation",
        "entry_conditions": [
          "The attestation process is being used and its applicable signer/contact/review/agreement conditions are met.",
          "Two signatures are required OR (the claim is an EDCS exclusion AND has no associated electronic folder)."
        ],
        "steps": [
          {
            "id": "dual-or-excluded-attestation-step-1",
            "title": "Verify the signer’s identity",
            "kind": "action",
            "actor": "Technician",
            "action": "Use the separately referenced GN03380.005 and GN00203.020 identity procedures. This mapping supplies no identity finding.",
            "conditions": [
              "The attestation process is being used and its applicable signer/contact/review/agreement conditions are met.",
              "Two signatures are required OR (the claim is an EDCS exclusion AND has no associated electronic folder)."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-2",
            "title": "Review before proceeding",
            "kind": "action",
            "actor": "Technician",
            "action": "Provide the opportunity to review the form and proceed with attestation only after review.",
            "conditions": [
              "The person has reviewed the SSA-827 before proceeding."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-3",
            "title": "Print and read the script",
            "kind": "action",
            "actor": "Technician",
            "action": "Print the SSA-827 and read the D2e scripted language as written.",
            "conditions": [
              "Review is complete and the applicable attestation procedure is being used."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-4",
            "title": "Record an actual agreement on paper",
            "kind": "action",
            "actor": "Technician",
            "action": "Only if the person agrees, enter the claimant name, and where another signer is involved the relationship and representative name, the date of attestation, and the specified witness wording, staff first initial/last name and office phone/city/state/ZIP.",
            "conditions": [
              "The person actually agrees to the script."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-5",
            "title": "Record the required electronic notation",
            "kind": "action",
            "actor": "Technician",
            "action": "Document the agreement to sign by attestation, the agreement date and the technician’s first initial and last name, using the applicable following component instruction.",
            "conditions": [
              "Agreement has occurred; use the applicable record/component scope."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-6",
            "title": "EDCS or eView documentation",
            "kind": "action",
            "actor": "Technician",
            "action": "Use the subject section of the SSA-5002 ROC OR the appropriate DCPS case-note section for the required notation. These alternatives do not establish record identity.",
            "conditions": [
              "An EDCS/eView claim is involved."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "component-documentation"
          },
          {
            "id": "dual-or-excluded-attestation-step-7",
            "title": "FO documentation for a non-electronic claim",
            "kind": "action",
            "actor": "FO",
            "action": "For an EDCS exclusion without an associated electronic folder, put the required notation and non-electronic status on RPOC in MCS for Title II or CCE for Title XVI.",
            "conditions": [
              "EDCS exclusion AND no associated electronic folder AND FO handling."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "component-documentation"
          },
          {
            "id": "dual-or-excluded-attestation-step-8",
            "title": "DDS or DCR documentation for a non-electronic claim",
            "kind": "action",
            "actor": "DDS or DCR",
            "action": "For an EDCS exclusion without an associated electronic folder, put the required notation in a DCPS case-note entry.",
            "conditions": [
              "EDCS exclusion AND no associated electronic folder AND DDS/DCR handling."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "component-documentation"
          },
          {
            "id": "dual-or-excluded-attestation-step-9",
            "title": "OHO or OAO documentation for a non-electronic claim",
            "kind": "action",
            "actor": "OHO or OAO",
            "action": "For an EDCS exclusion without an associated electronic folder, document the required notation on a ROC in ENM.",
            "conditions": [
              "EDCS exclusion AND no associated electronic folder AND OHO/OAO handling."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ],
            "alternative_group": "component-documentation"
          },
          {
            "id": "dual-or-excluded-attestation-step-10",
            "title": "Associate the valid completed paper form",
            "kind": "action",
            "actor": "Technician",
            "action": "Scan, fax or upload the valid completed paper SSA-827 into the applicable EDCS/eView electronic folder or Evidence Portal, associate it with the paper folder, or upload into ENM where applicable. These are scoped destinations, not a direction to send to all of them.",
            "conditions": [
              "The paper form is valid and complete; choose the applicable folder/system destination."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          },
          {
            "id": "dual-or-excluded-attestation-step-11",
            "title": "Give a copy of the completed form",
            "kind": "action",
            "actor": "Technician",
            "action": "Provide a copy of the scanned completed paper SSA-827 to the individual.",
            "conditions": [
              "The valid completed paper authorization has been handled under the applicable procedure."
            ],
            "source": "ssa827signature",
            "section": "D2f",
            "source_context_refs": [
              "DI11005.056-D2f",
              "DI11005.056-whole"
            ],
            "qualifications": [
              "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
              "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
          "automatic_transition": false,
          "unknowns": [
            "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "component-documentation",
            "label": "Use the documentation instruction for the actual claim and component",
            "logic": "source_conditions_determine_branch",
            "note": "The following four cards are scoped alternatives, not four universal documentation steps. No generic CPS/DCPS identity or case-system migration is inferred."
          }
        ]
      },
      "childhood-disability-after-dds/child-ssi-dedicated-account-exact-threshold": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-dedicated-account-exact-threshold",
        "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-exact-threshold",
        "entry_conditions": [
          "SSA is reviewing past-due SSI for an individual under age 18 with a representative payee. Other dedicated-account exceptions remain separately applicable.",
          "After interim-assistance reimbursement and direct payment of representative fees, the remaining past-due amount is EXACTLY six times the FBR plus any federally administered OSS."
        ],
        "steps": [
          {
            "id": "child-ssi-dedicated-account-exact-threshold-source-step-1",
            "title": "Keep the exact-six boundary distinct",
            "kind": "action",
            "actor": "SSA staff",
            "action": "At exactly 6 × (FBR + federally administered OSS), the table places the payment in the installment range and does not require a dedicated account. Collectible-overpayment offset and separately applicable installment exceptions remain separate. The greater-than-six dedicated-account instruction is not triggered merely by equality.",
            "conditions": [
              "SSA is reviewing past-due SSI for an individual under age 18 with a representative payee. Other dedicated-account exceptions remain separately applicable.",
              "After interim-assistance reimbursement and direct payment of representative fees, the remaining past-due amount is EXACTLY six times the FBR plus any federally administered OSS."
            ],
            "source": "ssidedicatedaccount",
            "section": "A; B.1 threshold table; B.6",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "Do not replace the strict greater-than-six threshold with equal-to-or-greater-than-six. The earlier recorded SI02101.002 comparison remains a separate unresolved history; no dollar rate is inferred from historical examples."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      },
      "childhood-disability-after-dds/child-ssi-dedicated-account-setup-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-dedicated-account-setup-evidence",
        "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-setup-evidence",
        "entry_conditions": [
          "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
          "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts."
        ],
        "steps": [
          {
            "id": "child-ssi-dedicated-account-setup-evidence-source-step-1",
            "title": "Keep the account requirement before release",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The payee must establish the required dedicated account before SSA releases past-due benefits to that payee. Unknown account information does not establish completion.",
            "conditions": [
              "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
              "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.1",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
            ]
          },
          {
            "id": "child-ssi-dedicated-account-setup-evidence-source-step-2",
            "title": "Once the account is established: obtain and input its information",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When the payee has established the account and provided the required financial-institution/account information, obtain the signed and dated SSA-552, input the institution information through UPOA, and use the stated UPSP/UPOT A-OTP procedure for the dedicated account. The account cannot be the regular recurring-payment account; a matching SSR/DRDP account causes a UP reject and does not establish payment.",
            "conditions": [
              "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
              "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts.",
              "The account is established and the payee provides its required institution name/address, routing/account numbers, title/type and opening-deposit amount."
            ],
            "source": "ssidedicatedaccount",
            "section": "C.3",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
            ],
            "alternative_group": "account-status"
          },
          {
            "id": "child-ssi-dedicated-account-setup-evidence-source-step-3",
            "title": "After 30 days without establishment: follow successor-payee review",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If the payee has not established the account 30 days after the original notice explaining the requirement, follow GN00504.100. EA maturity generates an E1 alert; follow-up alerts recur every 15 days until the EA diary is resolved. This is not automatic payee replacement or a payment guarantee.",
            "conditions": [
              "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
              "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts.",
              "At least 30 days have elapsed after the original required-account notice AND the account has not been established."
            ],
            "source": "ssidedicatedaccount",
            "section": "C.5",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
            ],
            "alternative_group": "account-status"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "account-status",
            "label": "Account-established and overdue-not-established situations",
            "logic": "source_conditions_determine_branch",
            "note": "These source situations are alternatives, not successive steps. Before 30 days, unknown notice dates, incomplete information or an unresolved UP reject do not select the overdue or successful-payment outcome."
          }
        ]
      },
      "childhood-disability-after-dds/child-turns18-before-pastdue-notice": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-turns18-before-pastdue-notice",
        "full_route": "childhood-disability-after-dds/child-turns18-before-pastdue-notice",
        "entry_conditions": [
          "The individual attains age 18 before SSA issues the notice determining eligibility for past-due benefits; application and disability-onset dates are not substituted for this boundary."
        ],
        "steps": [
          {
            "id": "child-turns18-before-pastdue-notice-source-step-1",
            "title": "Use the age-at-notice exception",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Dedicated-account provisions do not apply in this situation. Apply normal underpayment rules; installments may still apply. The D.2 example retains a representative payee, so this exception does not by itself remove the payee.",
            "conditions": [
              "The individual attains age 18 before SSA issues the notice determining eligibility for past-due benefits; application and disability-onset dates are not substituted for this boundary."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.1 age-18 row; D.2",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      },
      "childhood-disability-after-dds/child-ssi-death-account-versus-unpaid-benefits": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-death-account-versus-unpaid-benefits",
        "full_route": "childhood-disability-after-dds/child-ssi-death-account-versus-unpaid-benefits",
        "entry_conditions": [
          "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
          "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable."
        ],
        "steps": [
          {
            "id": "child-ssi-death-account-versus-unpaid-benefits-source-step-1",
            "title": "If death precedes establishment: keep the underpayment review separate",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The B.1 death-before-establishment row directs normal underpayment review to determine whether and to whom past-due benefits may be issued. Its SI02101.002 target conflicts with the previously recorded deceased-underpayment review; this selected flow does not resolve that cross-reference or choose a recipient.",
            "conditions": [
              "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
              "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable.",
              "The individual died before the payee established the dedicated account."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.1 death-before-establishment row",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The old additional SI02101.003 citation, its review history and recorded .002/.003 cross-reference disagreement are preserved. They are not re-reviewed or silently resolved by this .010-only source package."
            ],
            "alternative_group": "death-account-status"
          },
          {
            "id": "child-ssi-death-account-versus-unpaid-benefits-source-step-2",
            "title": "If an account already exists: distinguish the estate account",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When death follows establishment, B.1 states that SSA has no authority over that established dedicated account and that the account is part of the individual’s estate. This statement does not award unpaid SSI to an estate or settle its separate payment rules.",
            "conditions": [
              "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
              "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable.",
              "The payee established the dedicated account before the individual’s death."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.1 death-after-establishment row",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The old additional SI02101.003 citation, its review history and recorded .002/.003 cross-reference disagreement are preserved. They are not re-reviewed or silently resolved by this .010-only source package."
            ],
            "alternative_group": "death-account-status"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "death-account-status",
            "label": "Account timing at death",
            "logic": "source_conditions_determine_branch",
            "note": "The two rows have different establishment predicates. Neither determines survivor entitlement or treats an estate account as unpaid SSI."
          }
        ]
      },
      "childhood-disability-after-dds/child-ssi-dedicated-account-medical-cessation": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-dedicated-account-medical-cessation",
        "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-medical-cessation",
        "entry_conditions": [
          "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation."
        ],
        "steps": [
          {
            "id": "child-ssi-dedicated-account-medical-cessation-source-step-1",
            "title": "Closed period in PSY N07",
            "kind": "action",
            "actor": "SSA staff",
            "action": "For a closed-period disability case placed in PSY N07, a child under 18 with a representative payee does not require a dedicated account, even if the payee appeals. This does not decide that appeal.",
            "conditions": [
              "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
              "This is a CLOSED-PERIOD case placed in PSY N07, rather than an inference from any nonpayment status."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.9 first bullet",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
            ],
            "alternative_group": "cessation-case"
          },
          {
            "id": "child-ssi-dedicated-account-medical-cessation-source-step-2",
            "title": "Medical cessation without approved continuation",
            "kind": "action",
            "actor": "SSA staff",
            "action": "In a medical cessation case, dedicated-account rules stop at termination unless SSA approves benefit continuation. An appeal alone is not approval. The source separately says rules for an existing dedicated account cease unless continuation applies.",
            "conditions": [
              "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
              "This is a medical cessation case; termination has occurred for the stop-at-termination instruction, and approved benefit continuation does not apply."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.9 second and third bullets",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
            ],
            "alternative_group": "cessation-case"
          },
          {
            "id": "child-ssi-dedicated-account-medical-cessation-source-step-3",
            "title": "Medical cessation with benefit continuation",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When benefit continuation applies, the dedicated-account rules continue under B.9. This illustration does not establish that continuation was requested or approved, or supply an election deadline.",
            "conditions": [
              "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
              "This is a medical cessation case AND benefit continuation actually applies."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.9 second and third bullets",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
            ],
            "alternative_group": "cessation-case"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "cessation-case",
            "label": "Keep closed-period status and medical-cessation continuation separate",
            "logic": "source_conditions_determine_branch",
            "note": "These are source-conditioned alternatives. Appealing, PSY N07, termination and approved continuation are different facts. Unknown facts establish no branch."
          }
        ]
      },
      "childhood-disability-after-dds/child-ssi-dedicated-installment-nonpay": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-dedicated-installment-nonpay",
        "full_route": "childhood-disability-after-dds/child-ssi-dedicated-installment-nonpay",
        "entry_conditions": [
          "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
          "The individual’s actual correctional-institution residence is a separate case fact."
        ],
        "steps": [
          {
            "id": "child-ssi-dedicated-installment-nonpay-source-step-1",
            "title": "Outside the correctional-institution exception: issue the scheduled installment",
            "kind": "action",
            "actor": "SSA staff",
            "action": "B.10 directs the FO to issue the scheduled installment to the payee by A-OTP and prepare a manual notice when the individual is not residing in a correctional institution. Nonpay or suspense alone does not cancel this scheduled installment.",
            "conditions": [
              "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
              "The individual’s actual correctional-institution residence is a separate case fact.",
              "The individual is NOT residing in a correctional institution."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.10",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
            ],
            "alternative_group": "residence-exception"
          },
          {
            "id": "child-ssi-dedicated-installment-nonpay-source-step-2",
            "title": "If correctional residence applies: hold the general payment route",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Do not apply the B.10 nonpay payment instruction as authority to pay a person residing in a correctional institution. The source refers to SI00529.001 for the prohibition; its detailed release rules remain outside this selected source review.",
            "conditions": [
              "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
              "The individual’s actual correctional-institution residence is a separate case fact.",
              "The individual IS residing in a correctional institution."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.10",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
            ],
            "alternative_group": "residence-exception"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "residence-exception",
            "label": "Apply the actual residence condition",
            "logic": "source_conditions_determine_branch",
            "note": "The general scheduled-payment instruction and its correctional-institution exclusion are alternatives. Unknown residence does not establish either payment authorization or a final denial."
          }
        ]
      },
      "childhood-disability-after-dds/child-ssi-optional-subsequent-dedicated-deposit": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-optional-subsequent-dedicated-deposit",
        "full_route": "childhood-disability-after-dds/child-ssi-optional-subsequent-dedicated-deposit",
        "entry_conditions": [
          "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
          "The payee’s actual deposit choice and whether installments have already begun are separate facts."
        ],
        "steps": [
          {
            "id": "child-ssi-optional-subsequent-dedicated-deposit-source-step-1",
            "title": "Preserve the optional deposit and its restrictions",
            "kind": "action",
            "actor": "SSA staff",
            "action": "A qualifying subsequent payment of 6 × (FBR + OSS) or less need not be deposited into the dedicated account. If the payee elects deposit, limited permitted expenditures still apply. Amounts equal to or greater than three times but not exceeding six times remain subject to installment provisions.",
            "conditions": [
              "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
              "The payee’s actual deposit choice and whether installments have already begun are separate facts."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.2; C.4",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "General permitted-expenditure detail and the source’s must/may/may-not-deposit distinction require their own applicable conditions. This selected optional-deposit scenario does not classify every later payment."
            ]
          },
          {
            "id": "child-ssi-optional-subsequent-dedicated-deposit-source-step-2",
            "title": "When installments already began: keep the new-payment notice",
            "kind": "action",
            "actor": "SSA staff",
            "action": "If installments have begun, C.4 adds the new underpayment to the next installment and requires notice explaining it and instructing the payee to contact the FO if direct payment is wanted. This condition does not itself prove a payee election or completed payment.",
            "conditions": [
              "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
              "The payee’s actual deposit choice and whether installments have already begun are separate facts.",
              "Installments have ALREADY begun and there is a new underpayment."
            ],
            "source": "ssidedicatedaccount",
            "section": "C.4",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "General permitted-expenditure detail and the source’s must/may/may-not-deposit distinction require their own applicable conditions. This selected optional-deposit scenario does not classify every later payment."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      },
      "childhood-disability-after-dds/child-ssi-installment-exception-dedicated-account": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-installment-exception-dedicated-account",
        "full_route": "childhood-disability-after-dds/child-ssi-installment-exception-dedicated-account",
        "entry_conditions": [
          "The benefits otherwise require deposit into a dedicated account.",
          "SSA establishes EITHER a medical condition expected to result in death within 12 months OR ineligibility at the time of payment AND likely continued ineligibility for the next 12 months."
        ],
        "steps": [
          {
            "id": "child-ssi-installment-exception-dedicated-account-source-step-1",
            "title": "Apply the installment exception without removing the account rule",
            "kind": "action",
            "actor": "SSA staff",
            "action": "When either stated B.6 exception applies, deposit the entire amount into the dedicated account using A-OTP rather than dividing it into installments. The dedicated-account restriction remains. Twelve months is a source condition, not a processing-time promise.",
            "conditions": [
              "The benefits otherwise require deposit into a dedicated account.",
              "SSA establishes EITHER a medical condition expected to result in death within 12 months OR ineligibility at the time of payment AND likely continued ineligibility for the next 12 months."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.6 final exception paragraphs",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The ineligibility exception requires both ineligibility AT PAYMENT and likely ineligibility for the NEXT12months. The old additional SI02101.020 citation and its broader installment-process scope are preserved without being newly re-reviewed."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      },
      "childhood-disability-after-dds/child-ssi-currentmonth-separate-payment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-currentmonth-separate-payment",
        "full_route": "childhood-disability-after-dds/child-ssi-currentmonth-separate-payment",
        "entry_conditions": [
          "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
          "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
        ],
        "steps": [
          {
            "id": "child-ssi-currentmonth-separate-payment-source-step-1",
            "title": "Separate the included calendar-month payments",
            "kind": "action",
            "actor": "SSA staff",
            "action": "After the listed prerequisites, the FO uses A-OTP to issue included current or subsequent calendar-month benefits to the payee. Calendar month and computation month differ: the source’s August/September and August/October examples identify different payments to separate, not a universal completion deadline.",
            "conditions": [
              "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
              "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.7 and note; examples1-2",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The examples’ abbreviated less-than3/6FBR wording is not used to replace B.1/B.6 FBR-plus-federally-administered-OSS thresholds or their equality boundaries. Detailed prepayment and transaction manuals remain separate."
            ]
          },
          {
            "id": "child-ssi-currentmonth-separate-payment-source-step-2",
            "title": "Reassess the remaining amount without assuming a threshold result",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Separating these monthly payments may remove the case from installment or dedicated-account provisions. Whether it does depends on the remaining amount; this illustration does not calculate an actual award or guarantee removal.",
            "conditions": [
              "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
              "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.7; examples1-2",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The examples’ abbreviated less-than3/6FBR wording is not used to replace B.1/B.6 FBR-plus-federally-administered-OSS thresholds or their equality boundaries. Detailed prepayment and transaction manuals remain separate."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      },
      "childhood-disability-after-dds/child-ssi-increased-dedicated-installment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "child-ssi-increased-dedicated-installment",
        "full_route": "childhood-disability-after-dds/child-ssi-increased-dedicated-installment",
        "entry_conditions": [
          "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
          "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
        ],
        "steps": [
          {
            "id": "child-ssi-increased-dedicated-installment-source-step-1",
            "title": "Document the additional-amount request",
            "kind": "action",
            "actor": "SSA staff",
            "action": "The technician documents the request for an additional amount on a Report of Contact when the individual has outstanding debts or expenses under the referenced installment instructions. This does not approve an individual purchase or expense.",
            "conditions": [
              "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
              "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.6 first/second installment paragraph",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The impairment-related qualifier applies to the latter list; it is not silently removed or imposed as a new qualifier on the separately listed medical-treatment/education categories. The old GN00602.140 manual-notice/appeal reference remains preserved but is not newly reviewed or extended here."
            ]
          },
          {
            "id": "child-ssi-increased-dedicated-installment-source-step-2",
            "title": "Apply the dedicated-account expense limits",
            "kind": "action",
            "actor": "SSA staff",
            "action": "Because dedicated-account restrictions apply, increases should be limited to debts related to medical treatment or education/job-skills training, or to impairment-related personal-needs assistance, special equipment, housing modification, therapy or rehabilitation. Broader general-installment examples do not remove these dedicated-account limits.",
            "conditions": [
              "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
              "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
            ],
            "source": "ssidedicatedaccount",
            "section": "B.6 permitted-debt list",
            "source_context_refs": [
              "SI02101.010-whole"
            ],
            "qualifications": [
              "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
              "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
              "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
              "The impairment-related qualifier applies to the latter list; it is not silently removed or imposed as a new qualifier on the separately listed medical-treatment/education categories. The old GN00602.140 manual-notice/appeal reference remains preserved but is not newly reviewed or extended here."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
          ]
        }
      }
    },
    "SSA827_source": {
      "schema": "securitystat.source-bound-exception-flow-package/1",
      "status": "FUTURE_SOURCE_PROPOSAL_INDEPENDENT_REVIEW_REQUIRED_NO_INTEGRATION",
      "baseline_data_sha256": "9ab9e1413868b5a03bcf07550bbca2cefccccfa7b6cff94c4e7d9f154ba9684c",
      "baseline_release": "R23 frozen R2; parent subsequently confirmed actual activation",
      "source_capture": {
        "metadata": {
          "links": [
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005055",
              "text": "Previous"
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005057",
              "text": "Next"
            },
            {
              "href": "",
              "text": "DI 11005.056"
            },
            {
              "href": "http://www.gpo.gov/fdsys/pkg/PLAW-104publ191/pdf/PLAW-104publ191.pdf",
              "text": "P.L. 104-191"
            },
            {
              "href": "http://www.gpo.gov/fdsys/pkg/USCODE-2011-title20/pdf/USCODE-2011-title20-chap31-subchapIII-part4-sec1232g.pdf",
              "text": "20 U.S.C. 1232g"
            },
            {
              "href": "http://www.gpo.gov/fdsys/pkg/USCODE-2011-title38/pdf/USCODE-2011-title38-partV-chap73-subchapIII-sec7332.pdf",
              "text": "38 U.S.C. 7332"
            },
            {
              "href": "http://www.gpo.gov/fdsys/pkg/USCODE-2008-title42/pdf/USCODE-2008-title42-chap6A-subchapIII-A-partD-sec290dd.pdf",
              "text": "42 U.S.C. 290dd-2"
            },
            {
              "href": "https://www.ecfr.gov/current/title-34/subtitle-A/part-99",
              "text": "eCFR :: 34\n               CFR Part 99 -- Family Educational Rights and Privacy"
            },
            {
              "href": "https://www.ecfr.gov/current/title-34/subtitle-B/chapter-III/part-300",
              "text": "eCFR :: 34 CFR Part 300 -- Assistance to States for the Education of Children with\n               Disabilities"
            },
            {
              "href": "https://www.ecfr.gov/current/title-38/chapter-I/part-1/subject-group-ECFRb43f3bbd123e801/section-1.475",
              "text": "eCFR :: 38 CFR 1.475 -- Form of written consent."
            },
            {
              "href": "https://www.ecfr.gov/current/title-42/chapter-I/subchapter-A/part-2",
              "text": "eCFR :: 42 CFR Part 2 -- Confidentiality of Substance Use Disorder Patient\n               Records"
            },
            {
              "href": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-2",
              "text": "eCFR :: 45 CFR Part 2 -- Testimony by Employees and Production of Documents in Proceedings\n               Where\n               the United States Is Not a Party"
            },
            {
              "href": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160",
              "text": "eCFR :: 45 CFR Part 160 -- General Administrative Requirements"
            },
            {
              "href": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164",
              "text": "eCFR :: 45 CFR Part 164 -- Security and Privacy"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411018005",
              "text": "DI 11018.005"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d",
              "text": "DI 11005.056D."
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#c",
              "text": "DI 11005.056C"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0200502139#b",
              "text": "GN 00502.139B."
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/personal-representatives/index.html",
              "text": "Personal Representatives | HHS.gov"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0200204003",
              "text": "GN 00204.003"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#c4",
              "text": "DI 11005.056C.4"
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d2b",
              "text": "DI 11005.056D.2.b"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d2d",
              "text": "DI 11005.056D.2.d"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411018005",
              "text": "DI 11018.005"
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "http://www.ssa.gov/online/ssa-827.pdf",
              "text": "http://www.ssa.gov/online/ssa-827.pdf"
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#b3",
              "text": "DI 11005.056B.3."
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d2e",
              "text": "DI 11005.056D2.e."
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "",
              "text": ""
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d2d",
              "text": "DI 11005.056D.2.d"
            },
            {
              "href": "https://secure.ssa.gov/poms.nsf/lnx/0411005056#d2e",
              "text": "DI 11005.056D.2.e."
            },
            {
              "href": "http://policy.ssa.gov/poms.nsf/lnx/0411005056",
              "text": "http://policy.ssa.gov/poms.nsf/lnx/0411005056"
            },
            {
              "href": "https://ssa.gov/accessibility/",
              "text": "Accessibility"
            },
            {
              "href": "https://ssa.gov/foia/",
              "text": "FOIA"
            },
            {
              "href": "https://ssa.gov/open/",
              "text": "Open Government"
            },
            {
              "href": "https://ssa.gov/agency/glossary/",
              "text": "Glossary"
            },
            {
              "href": "https://ssa.gov/agency/privacy.html",
              "text": "Privacy"
            },
            {
              "href": "http://oig.ssa.gov/report-fraud-waste-or-abuse",
              "text": "Report Fraud, Waste or Abuse"
            },
            {
              "href": "https://ssa.gov/sitemap.htm",
              "text": "Site Map"
            },
            {
              "href": "https://ssa.gov/agency/websitepolicies.html",
              "text": "Website Policies"
            },
            {
              "href": "http://www.govbenefits.gov/",
              "text": "Benefits.gov"
            },
            {
              "href": "https://www.disability.gov/",
              "text": "Disability.gov"
            },
            {
              "href": "https://www.healthcare.gov/",
              "text": "Healthcare.gov"
            },
            {
              "href": "http://mymoney.gov/",
              "text": "MyMoney.gov"
            },
            {
              "href": "https://regulations.gov/",
              "text": "Regulations.gov"
            },
            {
              "href": "https://www.usa.gov/",
              "text": "USA.gov"
            },
            {
              "href": "https://ssa.gov/agency/other-gov-websites.html",
              "text": "Other Government Sites"
            },
            {
              "href": "https://twitter.com/socialsecurity/",
              "text": "Twitter"
            },
            {
              "href": "https://facebook.com/socialsecurity/",
              "text": "Facebook"
            },
            {
              "href": "https://youtube.com/socialsecurityonline/",
              "text": "YouTube"
            },
            {
              "href": "https://blog.ssa.gov/",
              "text": "Blog"
            },
            {
              "href": "https://ssa.gov/socialmedia/",
              "text": "More Social Media"
            }
          ],
          "title": "SSA - POMS: DI 11005.056 - Signature Requirements for Form SSA-827 - 04/17/2026",
          "url": "https://secure.ssa.gov/poms.nsf/lnx/0411005056",
          "main_chars": 19571,
          "utc": "2026-10-31T19:06:24.127Z",
          "source_truth_review": false,
          "main_sha256": "3077c88fbdd4fa0c1a5dac9650f9603b16691567f4c1d3ff2a12d9888f2b7159",
          "capture_note": "Initial main tag lookup returned null; observed role=main is #content; actual capture uses #content."
        },
        "maintext_sha256": "3077c88fbdd4fa0c1a5dac9650f9603b16691567f4c1d3ff2a12d9888f2b7159",
        "snapshot_sha256": "db0e67e62c9390936fe71b27843d5c75f8d61147482397dd79abf3182bbf72e9",
        "metadata_sha256": "ffb17f1a9a8f3bceff2173d7985ee5dc2217fa4fced9fcb1ca02827c7776d734",
        "capture_type": "Whole actual Browser rendered #content and DOM/accessibility snapshot; not raw HTTP"
      },
      "prior_source_object": {
        "code": "DI 11005.056",
        "title": "Signature Requirements for Form SSA-827",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0411005056",
        "revision": "2026-04-17; TN 132 (04-26)",
        "kind": "POMS",
        "checked_on": "2026-10-16",
        "verification_scope": "A/B selected authorization intake, signer authority and missing date; full minor/attestation exceptions remain."
      },
      "source_contexts": {
        "DI11005.056-A": {
          "source_code": "DI11005.056",
          "locator": "A",
          "start": 881,
          "end": 3317,
          "exact_text": "A. \nObtaining one signed Form SSA-827\n\nGenerally, the field office (FO) obtains one signed Form SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)) from the claimant (or proper applicant) at each adjudicative level (initial, reconsideration, and hearing) to process disability claims, continuing disability reviews, or non-disability claims in which capability is an issue.\n\nDo not make annotations, including check marks, to indicate where to complete and sign the form. Use a cover note (sticky note) if guidance is necessary.\n\nFor information on FO responsibilities when the claimant fails to provide a signed Form SSA-827, see DI 11018.005.\n\n1. \nWhat we mean by one Form SSA-827\n\nFederal law permits sources with information about the claimant to release that information if the person authorizing disclosure signs one authorization to release all of the claimants information from all of the claimants possible sources (unless there are other state requirements).\n\nGenerally, the adjudicating component (for example, the disability determination services (DDS) or the hearing office) makes copies of the signed form to send to each source. If needed later, the adjudicating component obtains an additional original signed and dated Form SSA-827. However, any local adjudicating component can make special arrangements with an FO to obtain more than one signed Form SSA-827.\n\nNOTE: A properly completed and legible pen and ink signed Form SSA-827 is acceptable if submitted in person, by mail, or by fax or scan. We also accept forms signed by other means, such as via SSAs Internet click-and-sign process and by our attestation process.\n\n2. \nSigning and dating Form SSA-827\n\nForm SSA-827 must include the appropriate signature and date of signing.\n\nAcceptable signature methods for Form SSA-827 are:\n\n•\n\npen and ink signature on a paper Form SSA-827;\n\n•\n\nSSAs Internet click-and-sign process; or\n\n•\n\nSSAs attestation process.\n\nIMPORTANT: We require pen and ink signatures in any situation where we do not permit the Internet or attestation signature processes. For an explanation of when we permit the Internet or attestation signatures, see DI 11005.056D., in this section.\n\n3. \nIf claimant inadvertently submits an undated Form SSA-827\n\nNever instruct the claimant to provide an undated Form SSA-827. If the claimant submits an undated Form SSA-827, return it to the claimant for dating.\n\n",
          "span_sha256": "7fbd31f42947a52bc7c41faea349c4804cb0457a2006dac35f9fde7b5dcc4b3c"
        },
        "DI11005.056-B": {
          "source_code": "DI11005.056",
          "locator": "B",
          "start": 3317,
          "end": 4715,
          "exact_text": "B. \nAuthority to authorize disclosure of the claimants medical and education records\n\nIn most cases, the claimant authorizes disclosure of their records by signing Form SSA-827. However, an authorized individual other than the claimant may sign Form SSA-827 authorizing disclosure in the situations detailed in DI 11005.056C in this section.\n\nGenerally, mark the appropriate sign box to sign as:\n\n1. \nParent of minor\n\nThe parent must have authority to make health care decisions and educational decisions for the minor child claimant.\n\n2. \nGuardian of minor\n\nThe individual must be the legal guardian of the claimant. For more information on guardianship, see GN 00502.139B.\n\n3. \nOther personal representative\n\nGenerally, the personal representative is someone other than a guardian who has authority to make health care decisions for the claimant under state law. The personal representative must explain the basis of their authority to sign the Form SSA-827 in the space provided on the form.\n\nIMPORTANT: Designation as either a representative payee or appointed representative is not a legal basis to sign the Form SSA-827 authorizing disclosure as an other personal representative. Information on personal representatives is available at the U.S. Department of Health & Human Services website: Personal Representatives | HHS.gov.\n\nC. \nForm SSA-827 signature requirements for special situations\n",
          "span_sha256": "3a6c0553ae886a7398a66431f4b3009f72bda544684f2efa89423cb7ea0ed843"
        },
        "DI11005.056-C1": {
          "source_code": "DI11005.056",
          "locator": "C1",
          "start": 4715,
          "end": 5489,
          "exact_text": "1. \nPhysically unable to sign\n\nWhenever a claimant agrees to authorize disclosure, but is physically incapable of signing by permissible means (for example, pen and ink, click and sign, and attestation), see the following actions:\n\na. \nThe FO actions\n•\n\nannotates Individual physically unable to sign in the INDIVIDUAL authorizing disclosure box; and\n\n•\n\nalerts the DDS of the situation by annotating the Remarks screen on the Electronic Disability Collect System (EDCS) 3367.\n\nb. \nThe DDS actions\n•\n\nexplains in a cover letter to the medical source that the claimant is physically unable to sign Form SSA-827; and\n\n•\n\nprovides the medical source a copy of Form SSA-827 with the annotation Individual physically unable to sign in the INDIVIDUAL authorizing disclosure box.\n\n",
          "span_sha256": "9dfe60ce40ce93ae73041f6fd2b898788f396d6f313d4c060571b81a5fbba9b5"
        },
        "DI11005.056-C2": {
          "source_code": "DI11005.056",
          "locator": "C2",
          "start": 5489,
          "end": 6746,
          "exact_text": "2. \nAdult found legally incompetent; adult with a court-appointed legal guardian; or comatose adult\na. \nCourt-appointed representative available\n\nIf a court has deemed the claimant incompetent, the claimant should not sign the SSA-827. The guardian, or other person authorized under state law to act on the claimants behalf, must:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block, such as parent or guardian; and\n\n•\n\nif they sign as other personal representative, then explain the basis for personal representative authority in the space provided.\n\nb. \nCourt-appointed representative not available\n\nWhen the claimant is unable to sign Form SSA-827. but does not have a legally appointed representative, the proper applicant who signed the application on behalf of the claimant should:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block, such as parent or guardian; and\n\n•\n\nif they sign as other personal representative, then explain the basis for authority to sign in the space provided.\n\nFor an explanation of proper applicant policy, see GN 00204.003.\n\n",
          "span_sha256": "d916d68e834a3d85db452a946c0c469998cc23eabcc26bb501d634e607109338"
        },
        "DI11005.056-C3": {
          "source_code": "DI11005.056",
          "locator": "C3",
          "start": 6746,
          "end": 8371,
          "exact_text": "3. \nMinor child claimant age 12 or older\n\nIf the claimant is age 12 or older, but still considered a minor under state law, both the claimant and their parent, guardian, or other person authorized by state law to act for the claimant must sign Form SSA-827.\n\nObtain both signatures and date of signing as follows:\n\na. \n\nThe claimant (child) signs in the INDIVIDUAL authorizing disclosure signature box on the left; and\n\nb. \n\nThe parent, guardian, or other authorized personal representative:\n\n•\n\nmarks the appropriate entry in the IF not signed by subject of disclosure relationship block;\n\n•\n\nsigns in the box below the check boxes; and\n\n•\n\nif they sign as other personal representative, then they explain the basis for authority to sign in the space provided.\n\nc. \n\nEnsure the Date Signed box is completed with the date of signing.\n\nEXCEPTION 1: If the claimant's parent or guardian has a strong objection to the claimant signing Form SSA-827, and the source will accept Form SSA-827 without the signature of the child, the FO may waive the requirement for the childs signature. In that case, document the waiver in the Remarks screen on the EDCS 3367, and follow the same instructions for minor child under age 12 in DI 11005.056C.4 in this section. If the source requires both signatures, explain this to the parent or guardian and follow the instructions in DI 11005.056D.2.b in this section.\n\nEXCEPTION 2: If state law provides for confidential treatment of minor persons (that is, when state law does not require the consent or knowledge of parents or guardians), we only need the claimant to sign the authorization.\n\n",
          "span_sha256": "726866b65a69ffba419642b1b1611b9f920aa42ddd48daaedc27f0e70853518d"
        },
        "DI11005.056-C4": {
          "source_code": "DI11005.056",
          "locator": "C4",
          "start": 8371,
          "end": 8847,
          "exact_text": "4. \nMinor child under age 12\n\nWhen the claimant is under age 12, the childs applicant should:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block; and\n\n•\n\nif they sign as other personal representative, then they explain the basis for authority to sign in the space provided.\n\nNOTE: We permit attestation in this situation.\n\nD. \nAlternative signature processes for Form SSA-827\n",
          "span_sha256": "a33332f8074b96b808ab4e7896c36991fb5052be762e20661cc180138295e78b"
        },
        "DI11005.056-D1": {
          "source_code": "DI11005.056",
          "locator": "D1",
          "start": 8847,
          "end": 10160,
          "exact_text": "1. \nInternet click-and-sign process\n\nAdult claimants (age 18 or older) who complete an iClaim/i3368 (Internet Benefit Application/Internet Adult Disability Report) or i3441 (Internet Disability Report - Appeal) on their own behalf may choose to use the Internet to sign and submit Form SSA-827, along with the i3368 or i3441. If the claimant agrees to sign Form SSA-827, clicking on the Submit button at the end of the i3368 or i3441 represents the claimants intent to sign and submit the forms to SSA.\n\nWhen the claimant signs Form SSA-827 with the internet click and sign process, we consider it signed when the claimant submits it. SSA systems then propagate the claimants name (that is, Electronically Signed By (first, middle, last name, and suffix)), the date, and the claimants identity information (based on information already entered during completion of the i3368 or i3441) onto an electronic version of Form SSA-827. The claimant can print a copy of the signed Form SSA-827 for their records.\n\nAt any time before submitting the signed Form SSA-827, the claimant can opt out of the Internet process and continue with the pen and ink signature process, even if they complete the i3368 or i3441. The claimant can also choose not to submit a Form SSA-827.\n\n2. \nIn-office and telephone attestation process\n",
          "span_sha256": "46874c5efb8ab080a8625c0dd301e123835e43437cd0c3372a280b33a57a6405"
        },
        "DI11005.056-D2a": {
          "source_code": "DI11005.056",
          "locator": "D2a",
          "start": 10160,
          "end": 11009,
          "exact_text": "a. \nWhen attestation is permitted\n\nThe SSA or DDS employee may use the attestation process in DI 11005.056D.2.d, in this section, to obtain a signed and dated Form SSA-827 when the following conditions exist:\n\n1. \n\nThe claimant is one of the following:\n\n•\n\nan adult (age 18 or older) who is signing on their own behalf, or\n\n•\n\na child (under age 18) who is signing on their own behalf, or\n\n•\n\na child whose claim is being pursued by an individual with the authority to sign on behalf of a child claimant (for example, a parent or guardian).\n\n2. \n\nThe individual signing the Form SSA-827 chooses to sign using the attestation process in one of the following situations:\n\n•\n\nduring a FO disability interview (for example, in office, video conference, or teleclaim interview), or\n\n•\n\nvia face-to-face or telephone contact with an SSA or DDS employee.\n\n",
          "span_sha256": "b2c1f616c7e2fe7105c17103896bea3d1418c96f433d4e1bb80e10af8b850cc9"
        },
        "DI11005.056-D2b": {
          "source_code": "DI11005.056",
          "locator": "D2b",
          "start": 11009,
          "end": 11575,
          "exact_text": "b. \nWhen attestation is not permitted\n\nWe do not permit attestation when:\n\n1. \n\nThe claimant has not reviewed Form SSA-827.\n\nClaimants must have the opportunity to review Form SSA-827 before we permit attestation.\n\n2. \n\nThe individual chooses not to attest.\n\nAt any time before completing the attestation process, the individual can opt out of the attestation process and continue with the paper (pen and ink signature) process.\n\nNOTE: If the claimant chooses not to submit Form SSA-827, see DI 11018.005 for FO responsibilities when a claimant fails to cooperate.\n\n",
          "span_sha256": "987b4f2c0e7f1d5a0baadd1eec2af83aab48e799e017716b61eb83c7749a1d54"
        },
        "DI11005.056-D2c": {
          "source_code": "DI11005.056",
          "locator": "D2c",
          "start": 11575,
          "end": 12774,
          "exact_text": "c. \nHow attestation works\n1. \n\nThe SSA or designated State agency employee (the employee) confirms the individuals (claimant or form signer) intent to sign Form SSA-827 and to authorize disclosure of information to SSA. If the individual agrees, the employee attests to the individuals intent to authorize disclosure by clicking the Attest, Submit, and Print buttons in EDCS or eView. The employee's act of attesting to these facts documents the individuals agreement. The process of the individual agreeing and the employee attesting constitutes a signature.\n\n2. \n\nSSA systems then propagate the individuals name (that is, Electronically Signed By (first, middle, last name, and suffix)), the date, and the individuals identity information (based on information already collected) on an electronic version of Form SSA-827. In addition, SSA systems propagate the employees information (that is, Attested by SSA or Designated State Agency Employee first initial, last name) and office phone number, city, state, and ZIP code in the witness block on the electronic version of the form.\n\n3. \n\nThe employee provides a printed, paper copy of the signed Form SSA-827 to the individual for their records.\n\n",
          "span_sha256": "e66c9747b203a2aeaf2869fc9594712ffc2377d5e10678cb89eba9dadc08095f"
        },
        "DI11005.056-D2d": {
          "source_code": "DI11005.056",
          "locator": "D2d",
          "start": 12774,
          "end": 14715,
          "exact_text": "d. \nIn situations where we permit attestation, follow these procedures:\n1. \n\nProvide the individual the opportunity to review Form SSA-827.\n\nFor telephone interviews or contacts, you may either:\n\n•\n\ndirect the individual to a copy of the form online: http://www.ssa.gov/online/ssa-827.pdf, or\n\n•\n\nprovide a copy in advance with the appointment letter, or Disability Starter Kit.\n\nDo not continue with the attestation process if the individual has not had the opportunity to review Form SSA-827.\n\nProceed with the attestation process once the individual has reviewed the form, or obtain a pen and ink signed and dated paper Form SSA-827.\n\n2. \n\nFor child claims:\n\n•\n\nselect or enter the name of the individual authorized to sign Form SSA-827.\n\n•\n\nif you enter an individuals name, you must enter their address and telephone number.\n\n•\n\nselect the basis for that individuals authority to sign the form (that is, parent of minor, guardian, or other personal representative).\n\n•\n\nif an other personal representative is signing, you must document their explanation for authority to sign in the space provided. For more information about personal representatives, see DI 11005.056B.3., in this section.\n\n3. \n\nRead the scripted language on the SSA-827 eAuthorization screen in EDCS, eView, or as written in DI 11005.056D2.e., in this section.\n\n4. \n\nIndicate the individuals intent to authorize disclosure by selecting Yes or No.\n\n•\n\nIf Yes, attest to the individuals intent to authorize disclosure by clicking the Attest, Submit, and Print buttons.\n\nNOTE: The system automatically adds the signed Form SSA-827 to the electronic folder. You do not need to fax or scan the form into the electronic folder.\n\n•\n\nIf No, select the reason for declining and provide the individual the opportunity to complete a paper Form SSA-827 with a pen and ink signature.\n\n5. \n\nProvide the printed copy of the signed Form SSA-827 to the individual for their records.\n\n",
          "span_sha256": "e93d2aeaf4dc7153fe9caf514524c6b1986c651137426d01c1797d83a8716e26"
        },
        "DI11005.056-D2e": {
          "source_code": "DI11005.056",
          "locator": "D2e",
          "start": 14715,
          "end": 16190,
          "exact_text": "e. \nScripts for attestation\n1. \n\nIn-office interview or contact\n\nHere is a printed copy of the SSA-827 for your review. We will ask you to acknowledge that you have read the SSA-827 (Authorization to Disclose Information to the Social Security Administration), and confirm your intent to sign this form. It will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks.\n\n•\n\nDo you understand that the SSA-827 that you have read will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks?\n\n•\n\nDo you agree to authorize disclosure of (your or claimants name) information to Social Security?\n\n2. \n\nTelephone interview or contact\n\nWe will ask you to acknowledge that you have read the SSA-827 (Authorization to Disclose Information to the Social Security Administration), and confirm your intent to sign this form. It will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks.\n\n•\n\nDo you understand that the SSA-827 that you have read will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks?\n\n•\n\nDo you agree to authorize disclosure of (your or claimants name) information to Social Security?\n\n",
          "span_sha256": "03f3d00e756892ff13d9ded4bdf6d2a0ff79632c96b873397439c91e00017ad3"
        },
        "DI11005.056-D2f": {
          "source_code": "DI11005.056",
          "locator": "D2f",
          "start": 16190,
          "end": 19206,
          "exact_text": "f. \nWhen using the Attestation process for Form SSA-827 where two signatures are required or the claim is an EDCS exclusion without an associated electronic folder, technicians must:\n1. \n\nVerify the identity of the signer using the processes described in GN 03380.005 and GN 00203.020.\n\n2. \n\nProvide the individual(s) with the opportunity to review Form SSA-827, per the instructions in DI 11005.056D.2.d.1.\n\n3. \n\nProceed with attestation only after the individual has reviewed the form.\n\n4. \n\nPrint Form SSA-827.\n\n5. \n\nRead the scripted language as written in DI 11005.056D.2.e.\n\n6. \n\nIf the person agrees to the script, indicate the individuals intent to sign on the paper printed SSA-827 by writing the claimants name in the Individual authorizing disclosure box, or if the individual intending to sign is someone other than the claimant, indicate the individuals intent to sign by:\n\n•\n\nWriting the claimants name in the Individual authorizing disclosure box;\n\n•\n\nMarking the appropriate entry in the IF not signed by subject of disclosure relationship block;\n\n•\n\nWriting the parent/guardian/other personal representatives name in the box below the checkboxes;\n\n•\n\nEnsuring the Date Signed box is completed with the date of attestation; and\n\n•\n\nDocument the attestation by:\n\n–\n\nWriting in the Witness box, Attested by SSA or Designated State Agency Employee followed by your first initial and last name; and\n\n–\n\nWriting the office phone number, city, state, and zip code.\n\n7. \n\nElectronically document the attestation with a notation that includes:\n\na. \n\nthat the individual agreed to sign the SSA-827 via attestation;\n\nb. \n\nthe date of agreement; and\n\nc. \n\nthe first initial and last name of the technician who took attestation.\n\n8. \n\nFor EDCS/eView claims, electronically document attestation with the required notation using the subject section of the Form SSA-5002 Report of Contact Form (ROC) or in the appropriate case note section of the Disability Case Processing System (DCPS).\n\n9. \n\nFor EDCS exclusion claims without an associated electronic folder, electronically document the attestation by following the appropriate procedures below:\n\na. \n\nFO: Document attestation with the required notation and that the cases is non-electronic on the Report of Contact (RPOC) in Modernized Claim Systems (MCS) for T2 claims and Consolidated Claim Experience (CCE) for T16 claims.\n\nb. \n\nDDS, DCR: Document attestation with the required notation on a case note entry in the Disability Case Processing System (DCPS).\n\nc. \n\nOHO: Document the attestation with the required notation on a Report of Contact (ROC) in the Electronic Non-Medical system (ENM).\n\nd. \n\nOAO: Document attestation with the required notation on a ROC in ENM.\n\n10. \n\nScan/Fax/Upload the valid, completed paper Form SSA-827 into the electronic folder (EDCS/eView) or Evidence Portal, associate with the paper folder, or upload into ENM system where applicable.\n\n11. \n\nProvide a copy of the scanned completed paper Form SSA-827 to the individual.\n\n \n\n",
          "span_sha256": "36ccee008abab6528d04ed5f3508c1986e677cc8ab3b13ab12570ae7d88897b0"
        },
        "DI11005.056-whole": {
          "source_code": "DI11005.056",
          "locator": "whole rendered main",
          "start": 0,
          "end": 19571,
          "exact_text": "Effective Dates: 04/17/2026 - Present\nPrevious | Next\n\nTN 132 (04-26)\n\nDI 11005.056 Signature Requirements for Form SSA-827\n\nCITATIONS:\n\nP.L. 104-191 Health Insurance Portability and Accountability Act of 1996 (HIPAA);\n20 U.S.C. 1232g Family Education Rights and Privacy Act (FERPA);\n38 U.S.C. 7332;\n42 U.S.C. 290dd-2;\neCFR :: 34 CFR Part 99 -- Family Educational Rights and Privacy and eCFR :: 34 CFR Part 300 -- Assistance to States for the Education of Children with Disabilities;\neCFR :: 38 CFR 1.475 -- Form of written consent.;\neCFR :: 42 CFR Part 2 -- Confidentiality of Substance Use Disorder Patient Records;\neCFR :: 45 CFR Part 2 -- Testimony by Employees and Production of Documents in Proceedings Where the United States Is Not a Party, eCFR :: 45 CFR Part 160 -- General Administrative Requirements, and eCFR :: 45 CFR Part 164 -- Security and Privacy; and State law.\nA. \nObtaining one signed Form SSA-827\n\nGenerally, the field office (FO) obtains one signed Form SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)) from the claimant (or proper applicant) at each adjudicative level (initial, reconsideration, and hearing) to process disability claims, continuing disability reviews, or non-disability claims in which capability is an issue.\n\nDo not make annotations, including check marks, to indicate where to complete and sign the form. Use a cover note (sticky note) if guidance is necessary.\n\nFor information on FO responsibilities when the claimant fails to provide a signed Form SSA-827, see DI 11018.005.\n\n1. \nWhat we mean by one Form SSA-827\n\nFederal law permits sources with information about the claimant to release that information if the person authorizing disclosure signs one authorization to release all of the claimants information from all of the claimants possible sources (unless there are other state requirements).\n\nGenerally, the adjudicating component (for example, the disability determination services (DDS) or the hearing office) makes copies of the signed form to send to each source. If needed later, the adjudicating component obtains an additional original signed and dated Form SSA-827. However, any local adjudicating component can make special arrangements with an FO to obtain more than one signed Form SSA-827.\n\nNOTE: A properly completed and legible pen and ink signed Form SSA-827 is acceptable if submitted in person, by mail, or by fax or scan. We also accept forms signed by other means, such as via SSAs Internet click-and-sign process and by our attestation process.\n\n2. \nSigning and dating Form SSA-827\n\nForm SSA-827 must include the appropriate signature and date of signing.\n\nAcceptable signature methods for Form SSA-827 are:\n\n•\n\npen and ink signature on a paper Form SSA-827;\n\n•\n\nSSAs Internet click-and-sign process; or\n\n•\n\nSSAs attestation process.\n\nIMPORTANT: We require pen and ink signatures in any situation where we do not permit the Internet or attestation signature processes. For an explanation of when we permit the Internet or attestation signatures, see DI 11005.056D., in this section.\n\n3. \nIf claimant inadvertently submits an undated Form SSA-827\n\nNever instruct the claimant to provide an undated Form SSA-827. If the claimant submits an undated Form SSA-827, return it to the claimant for dating.\n\nB. \nAuthority to authorize disclosure of the claimants medical and education records\n\nIn most cases, the claimant authorizes disclosure of their records by signing Form SSA-827. However, an authorized individual other than the claimant may sign Form SSA-827 authorizing disclosure in the situations detailed in DI 11005.056C in this section.\n\nGenerally, mark the appropriate sign box to sign as:\n\n1. \nParent of minor\n\nThe parent must have authority to make health care decisions and educational decisions for the minor child claimant.\n\n2. \nGuardian of minor\n\nThe individual must be the legal guardian of the claimant. For more information on guardianship, see GN 00502.139B.\n\n3. \nOther personal representative\n\nGenerally, the personal representative is someone other than a guardian who has authority to make health care decisions for the claimant under state law. The personal representative must explain the basis of their authority to sign the Form SSA-827 in the space provided on the form.\n\nIMPORTANT: Designation as either a representative payee or appointed representative is not a legal basis to sign the Form SSA-827 authorizing disclosure as an other personal representative. Information on personal representatives is available at the U.S. Department of Health & Human Services website: Personal Representatives | HHS.gov.\n\nC. \nForm SSA-827 signature requirements for special situations\n1. \nPhysically unable to sign\n\nWhenever a claimant agrees to authorize disclosure, but is physically incapable of signing by permissible means (for example, pen and ink, click and sign, and attestation), see the following actions:\n\na. \nThe FO actions\n•\n\nannotates Individual physically unable to sign in the INDIVIDUAL authorizing disclosure box; and\n\n•\n\nalerts the DDS of the situation by annotating the Remarks screen on the Electronic Disability Collect System (EDCS) 3367.\n\nb. \nThe DDS actions\n•\n\nexplains in a cover letter to the medical source that the claimant is physically unable to sign Form SSA-827; and\n\n•\n\nprovides the medical source a copy of Form SSA-827 with the annotation Individual physically unable to sign in the INDIVIDUAL authorizing disclosure box.\n\n2. \nAdult found legally incompetent; adult with a court-appointed legal guardian; or comatose adult\na. \nCourt-appointed representative available\n\nIf a court has deemed the claimant incompetent, the claimant should not sign the SSA-827. The guardian, or other person authorized under state law to act on the claimants behalf, must:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block, such as parent or guardian; and\n\n•\n\nif they sign as other personal representative, then explain the basis for personal representative authority in the space provided.\n\nb. \nCourt-appointed representative not available\n\nWhen the claimant is unable to sign Form SSA-827. but does not have a legally appointed representative, the proper applicant who signed the application on behalf of the claimant should:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block, such as parent or guardian; and\n\n•\n\nif they sign as other personal representative, then explain the basis for authority to sign in the space provided.\n\nFor an explanation of proper applicant policy, see GN 00204.003.\n\n3. \nMinor child claimant age 12 or older\n\nIf the claimant is age 12 or older, but still considered a minor under state law, both the claimant and their parent, guardian, or other person authorized by state law to act for the claimant must sign Form SSA-827.\n\nObtain both signatures and date of signing as follows:\n\na. \n\nThe claimant (child) signs in the INDIVIDUAL authorizing disclosure signature box on the left; and\n\nb. \n\nThe parent, guardian, or other authorized personal representative:\n\n•\n\nmarks the appropriate entry in the IF not signed by subject of disclosure relationship block;\n\n•\n\nsigns in the box below the check boxes; and\n\n•\n\nif they sign as other personal representative, then they explain the basis for authority to sign in the space provided.\n\nc. \n\nEnsure the Date Signed box is completed with the date of signing.\n\nEXCEPTION 1: If the claimant's parent or guardian has a strong objection to the claimant signing Form SSA-827, and the source will accept Form SSA-827 without the signature of the child, the FO may waive the requirement for the childs signature. In that case, document the waiver in the Remarks screen on the EDCS 3367, and follow the same instructions for minor child under age 12 in DI 11005.056C.4 in this section. If the source requires both signatures, explain this to the parent or guardian and follow the instructions in DI 11005.056D.2.b in this section.\n\nEXCEPTION 2: If state law provides for confidential treatment of minor persons (that is, when state law does not require the consent or knowledge of parents or guardians), we only need the claimant to sign the authorization.\n\n4. \nMinor child under age 12\n\nWhen the claimant is under age 12, the childs applicant should:\n\n•\n\nsign in the INDIVIDUAL authorizing disclosure box;\n\n•\n\nmark the appropriate entry in the IF not signed by subject of disclosure relationship block; and\n\n•\n\nif they sign as other personal representative, then they explain the basis for authority to sign in the space provided.\n\nNOTE: We permit attestation in this situation.\n\nD. \nAlternative signature processes for Form SSA-827\n1. \nInternet click-and-sign process\n\nAdult claimants (age 18 or older) who complete an iClaim/i3368 (Internet Benefit Application/Internet Adult Disability Report) or i3441 (Internet Disability Report - Appeal) on their own behalf may choose to use the Internet to sign and submit Form SSA-827, along with the i3368 or i3441. If the claimant agrees to sign Form SSA-827, clicking on the Submit button at the end of the i3368 or i3441 represents the claimants intent to sign and submit the forms to SSA.\n\nWhen the claimant signs Form SSA-827 with the internet click and sign process, we consider it signed when the claimant submits it. SSA systems then propagate the claimants name (that is, Electronically Signed By (first, middle, last name, and suffix)), the date, and the claimants identity information (based on information already entered during completion of the i3368 or i3441) onto an electronic version of Form SSA-827. The claimant can print a copy of the signed Form SSA-827 for their records.\n\nAt any time before submitting the signed Form SSA-827, the claimant can opt out of the Internet process and continue with the pen and ink signature process, even if they complete the i3368 or i3441. The claimant can also choose not to submit a Form SSA-827.\n\n2. \nIn-office and telephone attestation process\na. \nWhen attestation is permitted\n\nThe SSA or DDS employee may use the attestation process in DI 11005.056D.2.d, in this section, to obtain a signed and dated Form SSA-827 when the following conditions exist:\n\n1. \n\nThe claimant is one of the following:\n\n•\n\nan adult (age 18 or older) who is signing on their own behalf, or\n\n•\n\na child (under age 18) who is signing on their own behalf, or\n\n•\n\na child whose claim is being pursued by an individual with the authority to sign on behalf of a child claimant (for example, a parent or guardian).\n\n2. \n\nThe individual signing the Form SSA-827 chooses to sign using the attestation process in one of the following situations:\n\n•\n\nduring a FO disability interview (for example, in office, video conference, or teleclaim interview), or\n\n•\n\nvia face-to-face or telephone contact with an SSA or DDS employee.\n\nb. \nWhen attestation is not permitted\n\nWe do not permit attestation when:\n\n1. \n\nThe claimant has not reviewed Form SSA-827.\n\nClaimants must have the opportunity to review Form SSA-827 before we permit attestation.\n\n2. \n\nThe individual chooses not to attest.\n\nAt any time before completing the attestation process, the individual can opt out of the attestation process and continue with the paper (pen and ink signature) process.\n\nNOTE: If the claimant chooses not to submit Form SSA-827, see DI 11018.005 for FO responsibilities when a claimant fails to cooperate.\n\nc. \nHow attestation works\n1. \n\nThe SSA or designated State agency employee (the employee) confirms the individuals (claimant or form signer) intent to sign Form SSA-827 and to authorize disclosure of information to SSA. If the individual agrees, the employee attests to the individuals intent to authorize disclosure by clicking the Attest, Submit, and Print buttons in EDCS or eView. The employee's act of attesting to these facts documents the individuals agreement. The process of the individual agreeing and the employee attesting constitutes a signature.\n\n2. \n\nSSA systems then propagate the individuals name (that is, Electronically Signed By (first, middle, last name, and suffix)), the date, and the individuals identity information (based on information already collected) on an electronic version of Form SSA-827. In addition, SSA systems propagate the employees information (that is, Attested by SSA or Designated State Agency Employee first initial, last name) and office phone number, city, state, and ZIP code in the witness block on the electronic version of the form.\n\n3. \n\nThe employee provides a printed, paper copy of the signed Form SSA-827 to the individual for their records.\n\nd. \nIn situations where we permit attestation, follow these procedures:\n1. \n\nProvide the individual the opportunity to review Form SSA-827.\n\nFor telephone interviews or contacts, you may either:\n\n•\n\ndirect the individual to a copy of the form online: http://www.ssa.gov/online/ssa-827.pdf, or\n\n•\n\nprovide a copy in advance with the appointment letter, or Disability Starter Kit.\n\nDo not continue with the attestation process if the individual has not had the opportunity to review Form SSA-827.\n\nProceed with the attestation process once the individual has reviewed the form, or obtain a pen and ink signed and dated paper Form SSA-827.\n\n2. \n\nFor child claims:\n\n•\n\nselect or enter the name of the individual authorized to sign Form SSA-827.\n\n•\n\nif you enter an individuals name, you must enter their address and telephone number.\n\n•\n\nselect the basis for that individuals authority to sign the form (that is, parent of minor, guardian, or other personal representative).\n\n•\n\nif an other personal representative is signing, you must document their explanation for authority to sign in the space provided. For more information about personal representatives, see DI 11005.056B.3., in this section.\n\n3. \n\nRead the scripted language on the SSA-827 eAuthorization screen in EDCS, eView, or as written in DI 11005.056D2.e., in this section.\n\n4. \n\nIndicate the individuals intent to authorize disclosure by selecting Yes or No.\n\n•\n\nIf Yes, attest to the individuals intent to authorize disclosure by clicking the Attest, Submit, and Print buttons.\n\nNOTE: The system automatically adds the signed Form SSA-827 to the electronic folder. You do not need to fax or scan the form into the electronic folder.\n\n•\n\nIf No, select the reason for declining and provide the individual the opportunity to complete a paper Form SSA-827 with a pen and ink signature.\n\n5. \n\nProvide the printed copy of the signed Form SSA-827 to the individual for their records.\n\ne. \nScripts for attestation\n1. \n\nIn-office interview or contact\n\nHere is a printed copy of the SSA-827 for your review. We will ask you to acknowledge that you have read the SSA-827 (Authorization to Disclose Information to the Social Security Administration), and confirm your intent to sign this form. It will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks.\n\n•\n\nDo you understand that the SSA-827 that you have read will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks?\n\n•\n\nDo you agree to authorize disclosure of (your or claimants name) information to Social Security?\n\n2. \n\nTelephone interview or contact\n\nWe will ask you to acknowledge that you have read the SSA-827 (Authorization to Disclose Information to the Social Security Administration), and confirm your intent to sign this form. It will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks.\n\n•\n\nDo you understand that the SSA-827 that you have read will be used to request all of (your or claimants name) medical records and other information related to (your or claimants name) ability to perform tasks?\n\n•\n\nDo you agree to authorize disclosure of (your or claimants name) information to Social Security?\n\nf. \nWhen using the Attestation process for Form SSA-827 where two signatures are required or the claim is an EDCS exclusion without an associated electronic folder, technicians must:\n1. \n\nVerify the identity of the signer using the processes described in GN 03380.005 and GN 00203.020.\n\n2. \n\nProvide the individual(s) with the opportunity to review Form SSA-827, per the instructions in DI 11005.056D.2.d.1.\n\n3. \n\nProceed with attestation only after the individual has reviewed the form.\n\n4. \n\nPrint Form SSA-827.\n\n5. \n\nRead the scripted language as written in DI 11005.056D.2.e.\n\n6. \n\nIf the person agrees to the script, indicate the individuals intent to sign on the paper printed SSA-827 by writing the claimants name in the Individual authorizing disclosure box, or if the individual intending to sign is someone other than the claimant, indicate the individuals intent to sign by:\n\n•\n\nWriting the claimants name in the Individual authorizing disclosure box;\n\n•\n\nMarking the appropriate entry in the IF not signed by subject of disclosure relationship block;\n\n•\n\nWriting the parent/guardian/other personal representatives name in the box below the checkboxes;\n\n•\n\nEnsuring the Date Signed box is completed with the date of attestation; and\n\n•\n\nDocument the attestation by:\n\n–\n\nWriting in the Witness box, Attested by SSA or Designated State Agency Employee followed by your first initial and last name; and\n\n–\n\nWriting the office phone number, city, state, and zip code.\n\n7. \n\nElectronically document the attestation with a notation that includes:\n\na. \n\nthat the individual agreed to sign the SSA-827 via attestation;\n\nb. \n\nthe date of agreement; and\n\nc. \n\nthe first initial and last name of the technician who took attestation.\n\n8. \n\nFor EDCS/eView claims, electronically document attestation with the required notation using the subject section of the Form SSA-5002 Report of Contact Form (ROC) or in the appropriate case note section of the Disability Case Processing System (DCPS).\n\n9. \n\nFor EDCS exclusion claims without an associated electronic folder, electronically document the attestation by following the appropriate procedures below:\n\na. \n\nFO: Document attestation with the required notation and that the cases is non-electronic on the Report of Contact (RPOC) in Modernized Claim Systems (MCS) for T2 claims and Consolidated Claim Experience (CCE) for T16 claims.\n\nb. \n\nDDS, DCR: Document attestation with the required notation on a case note entry in the Disability Case Processing System (DCPS).\n\nc. \n\nOHO: Document the attestation with the required notation on a Report of Contact (ROC) in the Electronic Non-Medical system (ENM).\n\nd. \n\nOAO: Document attestation with the required notation on a ROC in ENM.\n\n10. \n\nScan/Fax/Upload the valid, completed paper Form SSA-827 into the electronic folder (EDCS/eView) or Evidence Portal, associate with the paper folder, or upload into ENM system where applicable.\n\n11. \n\nProvide a copy of the scanned completed paper Form SSA-827 to the individual.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0411005056\n\t\nDI 11005.056 - Signature Requirements for Form SSA-827 - 04/17/2026\nBatch run: 10/16/2026\nRev:04/17/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
          "span_sha256": "3077c88fbdd4fa0c1a5dac9650f9603b16691567f4c1d3ff2a12d9888f2b7159"
        }
      },
      "flows": {
        "undated-authorization": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "undated-authorization",
          "full_route": "medical-records-authorization/undated-authorization",
          "entry_conditions": [
            "The SSA-827 has no date of signing."
          ],
          "steps": [
            {
              "id": "undated-authorization-step-1",
              "title": "Return the undated form",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Return the form for the claimant to date; do not request an undated SSA-827.",
              "conditions": [
                "The required date is missing."
              ],
              "source": "ssa827signature",
              "section": "A",
              "source_context_refs": [
                "DI11005.056-A",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "undated-authorization-step-2",
              "title": "Complete the signing date",
              "kind": "you",
              "actor": "Claimant",
              "action": "Date the form with the date of signing. Staff do not supply an invented date for the claimant.",
              "conditions": [
                "The form has been returned for dating."
              ],
              "source": "ssa827signature",
              "section": "A",
              "source_context_refs": [
                "DI11005.056-A",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "payee-not-signing-authority": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "payee-not-signing-authority",
          "full_route": "medical-records-authorization/payee-not-signing-authority",
          "entry_conditions": [
            "A representative payee or appointed representative proposes to sign as an other personal representative."
          ],
          "steps": [
            {
              "id": "payee-not-signing-authority-step-1",
              "title": "Check the separate authority basis",
              "kind": "action",
              "actor": "SSA staff",
              "action": "A payee or appointed-representative designation alone is not authority to sign the SSA-827 as an other personal representative. Apply the separately applicable state-law authority requirement.",
              "conditions": [
                "The proposed signer relies on payee or appointed-representative status."
              ],
              "source": "ssa827signature",
              "section": "B",
              "source_context_refs": [
                "DI11005.056-B",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "payee-not-signing-authority-step-2",
              "title": "Explain an established authority basis",
              "kind": "you",
              "actor": "Authorized signer",
              "action": "If signing as an other personal representative under an established applicable authority, explain that basis in the space on the form. This walkthrough does not establish that authority.",
              "conditions": [
                "Other-personal-representative authority is established under the applicable rule."
              ],
              "source": "ssa827signature",
              "section": "B",
              "source_context_refs": [
                "DI11005.056-B",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "physically-unable-sign": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "physically-unable-sign",
          "full_route": "medical-records-authorization/physically-unable-sign",
          "entry_conditions": [
            "The claimant agrees to authorize disclosure.",
            "The claimant is physically incapable of signing by all permissible means, including pen and ink, click and sign and attestation."
          ],
          "steps": [
            {
              "id": "physically-unable-sign-step-1",
              "title": "Annotate the authorization",
              "kind": "action",
              "actor": "FO",
              "action": "Write “Individual physically unable to sign” in the INDIVIDUAL authorizing disclosure box.",
              "conditions": [
                "Both agreement and incapacity by permissible means are established."
              ],
              "source": "ssa827signature",
              "section": "C1",
              "source_context_refs": [
                "DI11005.056-C1",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "physically-unable-sign-step-2",
              "title": "Alert DDS through EDCS",
              "kind": "action",
              "actor": "FO",
              "action": "Annotate the Remarks screen on EDCS 3367 to alert DDS to the situation.",
              "conditions": [
                "The C1 physical-incapacity conditions apply."
              ],
              "source": "ssa827signature",
              "section": "C1",
              "source_context_refs": [
                "DI11005.056-C1",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "physically-unable-sign-step-3",
              "title": "Explain the situation to the medical source",
              "kind": "action",
              "actor": "DDS",
              "action": "Explain in a cover letter that the claimant is physically unable to sign the SSA-827.",
              "conditions": [
                "The C1 physical-incapacity conditions apply."
              ],
              "source": "ssa827signature",
              "section": "C1",
              "source_context_refs": [
                "DI11005.056-C1",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "physically-unable-sign-step-4",
              "title": "Provide the annotated form",
              "kind": "action",
              "actor": "DDS",
              "action": "Provide the medical source a copy bearing the specified physical-incapacity annotation.",
              "conditions": [
                "The C1 physical-incapacity conditions apply."
              ],
              "source": "ssa827signature",
              "section": "C1",
              "source_context_refs": [
                "DI11005.056-C1",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "minor-age12-signatures": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "minor-age12-signatures",
          "full_route": "medical-records-authorization/minor-age12-signatures",
          "entry_conditions": [
            "The claimant is at least 12 and is still a minor under applicable state law.",
            "Signer authority and the relevant source/state-law conditions must be established; unknown facts select no exception automatically."
          ],
          "steps": [
            {
              "id": "minor-age12-signatures-step-1",
              "title": "Ordinary two-signature instruction",
              "kind": "you",
              "actor": "Child and authorized adult",
              "action": "The child signs the left INDIVIDUAL box. The authorized adult marks the relationship, signs below the check boxes and explains other-personal-representative authority when applicable. Complete the date of signing.",
              "conditions": [
                "The C3 ordinary rule applies; no applicable exception displaces it."
              ],
              "source": "ssa827signature",
              "section": "C3",
              "source_context_refs": [
                "DI11005.056-C3",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "minor-signature-scope"
            },
            {
              "id": "minor-age12-signatures-step-2",
              "title": "Possible waiver of the child signature",
              "kind": "action",
              "actor": "FO",
              "action": "If the parent or guardian strongly objects AND the source accepts the form without the child signature, the FO may waive it, document the waiver in EDCS 3367 Remarks and follow C4. If the source requires both signatures, explain that requirement and follow the published D2b reference.",
              "conditions": [
                "Strong parental/guardian objection AND source acceptance without the child signature are both established for the waiver."
              ],
              "source": "ssa827signature",
              "section": "C3",
              "source_context_refs": [
                "DI11005.056-C3",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "minor-signature-scope"
            },
            {
              "id": "minor-age12-signatures-step-3",
              "title": "Confidential minor treatment",
              "kind": "you",
              "actor": "Claimant",
              "action": "Only the claimant signs when applicable state law provides confidential minor treatment without parental or guardian consent or knowledge.",
              "conditions": [
                "The applicable confidential-treatment state-law condition is established."
              ],
              "source": "ssa827signature",
              "section": "C3",
              "source_context_refs": [
                "DI11005.056-C3",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "minor-signature-scope"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          },
          "alternative_groups": [
            {
              "id": "minor-signature-scope",
              "label": "Different source-conditioned instructions",
              "logic": "source_conditions_determine_branch",
              "note": "These are conditional alternatives, not a sequence of all three actions. The source supplies no precedence rule for overlapping exceptions; unclear facts require review."
            }
          ]
        },
        "child-under12": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-under12",
          "full_route": "medical-records-authorization/child-under12",
          "entry_conditions": [
            "The claimant is under 12.",
            "The child’s applicant has the applicable authority to sign."
          ],
          "steps": [
            {
              "id": "child-under12-step-1",
              "title": "Sign and identify the relationship",
              "kind": "you",
              "actor": "Child’s applicant",
              "action": "Sign in the INDIVIDUAL authorizing disclosure box and mark the appropriate relationship entry.",
              "conditions": [
                "The claimant is under 12 and the applicant is the appropriate signer."
              ],
              "source": "ssa827signature",
              "section": "C4",
              "source_context_refs": [
                "DI11005.056-C4",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "child-under12-step-2",
              "title": "Explain other representative authority when applicable",
              "kind": "you",
              "actor": "Child’s applicant",
              "action": "If signing as an other personal representative, explain the authority basis in the space provided. Attestation is permitted in this situation only subject to its own D2 conditions.",
              "conditions": [
                "The signer acts as an other personal representative for the explanation; any attestation must independently satisfy D2."
              ],
              "source": "ssa827signature",
              "section": "C4",
              "source_context_refs": [
                "DI11005.056-C4",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "review-before-attestation": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "review-before-attestation",
          "full_route": "medical-records-authorization/review-before-attestation",
          "entry_conditions": [
            "The person has not reviewed the SSA-827, or chooses not to attest."
          ],
          "steps": [
            {
              "id": "review-before-attestation-step-1",
              "title": "Provide an opportunity to review",
              "kind": "action",
              "actor": "SSA or DDS employee",
              "action": "Give the person an opportunity to review the form before attestation. On telephone contact, use the source’s review arrangements; do not attest before review.",
              "conditions": [
                "The form has not been reviewed."
              ],
              "source": "ssa827signature",
              "section": "D2b",
              "source_context_refs": [
                "DI11005.056-D2b",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "review-before-attestation-step-2",
              "title": "Attest only if separately permitted",
              "kind": "action",
              "actor": "SSA or DDS employee",
              "action": "Proceed only after review, when the person chooses attestation and the D2a signer/contact conditions and applicable procedure are met. Review alone does not establish consent.",
              "conditions": [
                "Review is complete AND the person chooses attestation AND all applicable D2a conditions hold."
              ],
              "source": "ssa827signature",
              "section": "D2a",
              "source_context_refs": [
                "DI11005.056-D2a",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "review-signature-choice"
            },
            {
              "id": "review-before-attestation-step-3",
              "title": "Use the pen-and-ink alternative",
              "kind": "you",
              "actor": "Signer",
              "action": "The person can opt out before attestation is complete and use the paper pen-and-ink process. Not submitting the authorization invokes separately referenced instructions; this illustration does not decide denial or cooperation.",
              "conditions": [
                "The person chooses not to attest or opts out before completion."
              ],
              "source": "ssa827signature",
              "section": "D2b",
              "source_context_refs": [
                "DI11005.056-D2b",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "review-signature-choice"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          },
          "alternative_groups": [
            {
              "id": "review-signature-choice",
              "label": "Signature choice after the applicable review",
              "logic": "source_conditions_determine_branch",
              "note": "Choose only the applicable instruction. No automatic consent or completed signing is inferred."
            }
          ]
        },
        "adult-court-incompetence-signer": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "adult-court-incompetence-signer",
          "full_route": "medical-records-authorization/adult-court-incompetence-signer",
          "entry_conditions": [
            "A court has deemed the adult claimant incompetent.",
            "A guardian or another person authorized under state law is available."
          ],
          "steps": [
            {
              "id": "adult-court-incompetence-signer-step-1",
              "title": "Use the source-qualified signer",
              "kind": "you",
              "actor": "Authorized guardian or state-law representative",
              "action": "Sign in the INDIVIDUAL authorizing disclosure box. In the court-incompetence situation the claimant should not sign; in the no-appointed-representative situation use the proper applicant who signed the application.",
              "conditions": [
                "A court has deemed the adult claimant incompetent.",
                "A guardian or another person authorized under state law is available."
              ],
              "source": "ssa827signature",
              "section": "C2",
              "source_context_refs": [
                "DI11005.056-C2",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "adult-court-incompetence-signer-step-2",
              "title": "Record relationship and authority",
              "kind": "you",
              "actor": "Authorized guardian or state-law representative",
              "action": "Mark the appropriate relationship entry. If signing as an other personal representative, explain the authority basis in the space provided.",
              "conditions": [
                "The selected C2 signer conditions are established."
              ],
              "source": "ssa827signature",
              "section": "C2",
              "source_context_refs": [
                "DI11005.056-C2",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "no-appointed-adult-representative": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "no-appointed-adult-representative",
          "full_route": "medical-records-authorization/no-appointed-adult-representative",
          "entry_conditions": [
            "The adult claimant is unable to sign.",
            "The claimant does not have a legally appointed representative.",
            "The proper applicant who signed the benefit application is identified under the applicable proper-applicant rule."
          ],
          "steps": [
            {
              "id": "no-appointed-adult-representative-step-1",
              "title": "Use the source-qualified signer",
              "kind": "you",
              "actor": "Proper applicant who signed the application",
              "action": "Sign in the INDIVIDUAL authorizing disclosure box. In the court-incompetence situation the claimant should not sign; in the no-appointed-representative situation use the proper applicant who signed the application.",
              "conditions": [
                "The adult claimant is unable to sign.",
                "The claimant does not have a legally appointed representative.",
                "The proper applicant who signed the benefit application is identified under the applicable proper-applicant rule."
              ],
              "source": "ssa827signature",
              "section": "C2",
              "source_context_refs": [
                "DI11005.056-C2",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "no-appointed-adult-representative-step-2",
              "title": "Record relationship and authority",
              "kind": "you",
              "actor": "Proper applicant who signed the application",
              "action": "Mark the appropriate relationship entry. If signing as an other personal representative, explain the authority basis in the space provided.",
              "conditions": [
                "The selected C2 signer conditions are established."
              ],
              "source": "ssa827signature",
              "section": "C2",
              "source_context_refs": [
                "DI11005.056-C2",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "electronic-attestation-copy": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "electronic-attestation-copy",
          "full_route": "medical-records-authorization/electronic-attestation-copy",
          "entry_conditions": [
            "A D2a permitted signer chooses attestation during a qualifying interview/contact.",
            "The signer has reviewed the form and agrees to authorize disclosure.",
            "The special D2f procedure is not applicable; two signatures or an excluded claim without an associated electronic folder require separate handling."
          ],
          "steps": [
            {
              "id": "electronic-attestation-copy-step-1",
              "title": "Confirm intent and attest",
              "kind": "action",
              "actor": "SSA or designated State agency employee",
              "action": "Confirm intent and agreement using the applicable script, then click Attest, Submit and Print in EDCS or eView. A refusal does not authorize attestation.",
              "conditions": [
                "A D2a permitted signer chooses attestation during a qualifying interview/contact.",
                "The signer has reviewed the form and agrees to authorize disclosure.",
                "The special D2f procedure is not applicable; two signatures or an excluded claim without an associated electronic folder require separate handling."
              ],
              "source": "ssa827signature",
              "section": "D2c",
              "source_context_refs": [
                "DI11005.056-D2c",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "electronic-attestation-copy-step-2",
              "title": "Electronic form is populated",
              "kind": "action",
              "actor": "SSA systems",
              "action": "The source describes propagation of the signer’s name, date and identity information and the attesting employee’s information onto the electronic form. This describes the source procedure, not observed runtime execution.",
              "conditions": [
                "The permitted standard attestation has been completed."
              ],
              "source": "ssa827signature",
              "section": "D2c",
              "source_context_refs": [
                "DI11005.056-D2c",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "electronic-attestation-copy-step-3",
              "title": "Associate the electronic form",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Under the standard electronic procedure, the signed form is automatically added to the electronic folder; do not separately fax or scan that form under this instruction.",
              "conditions": [
                "The standard electronic procedure applies; do not extend this no-fax instruction to D2f paper handling."
              ],
              "source": "ssa827signature",
              "section": "D2c",
              "source_context_refs": [
                "DI11005.056-D2c",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "electronic-attestation-copy-step-4",
              "title": "Give the person a copy",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Provide a printed copy of the signed authorization for the person’s records.",
              "conditions": [
                "The applicable standard attestation is complete."
              ],
              "source": "ssa827signature",
              "section": "D2d",
              "source_context_refs": [
                "DI11005.056-D2d",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          }
        },
        "dual-or-excluded-attestation": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "dual-or-excluded-attestation",
          "full_route": "medical-records-authorization/dual-or-excluded-attestation",
          "entry_conditions": [
            "The attestation process is being used and its applicable signer/contact/review/agreement conditions are met.",
            "Two signatures are required OR (the claim is an EDCS exclusion AND has no associated electronic folder)."
          ],
          "steps": [
            {
              "id": "dual-or-excluded-attestation-step-1",
              "title": "Verify the signer’s identity",
              "kind": "action",
              "actor": "Technician",
              "action": "Use the separately referenced GN03380.005 and GN00203.020 identity procedures. This mapping supplies no identity finding.",
              "conditions": [
                "The attestation process is being used and its applicable signer/contact/review/agreement conditions are met.",
                "Two signatures are required OR (the claim is an EDCS exclusion AND has no associated electronic folder)."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-2",
              "title": "Review before proceeding",
              "kind": "action",
              "actor": "Technician",
              "action": "Provide the opportunity to review the form and proceed with attestation only after review.",
              "conditions": [
                "The person has reviewed the SSA-827 before proceeding."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-3",
              "title": "Print and read the script",
              "kind": "action",
              "actor": "Technician",
              "action": "Print the SSA-827 and read the D2e scripted language as written.",
              "conditions": [
                "Review is complete and the applicable attestation procedure is being used."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-4",
              "title": "Record an actual agreement on paper",
              "kind": "action",
              "actor": "Technician",
              "action": "Only if the person agrees, enter the claimant name, and where another signer is involved the relationship and representative name, the date of attestation, and the specified witness wording, staff first initial/last name and office phone/city/state/ZIP.",
              "conditions": [
                "The person actually agrees to the script."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-5",
              "title": "Record the required electronic notation",
              "kind": "action",
              "actor": "Technician",
              "action": "Document the agreement to sign by attestation, the agreement date and the technician’s first initial and last name, using the applicable following component instruction.",
              "conditions": [
                "Agreement has occurred; use the applicable record/component scope."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-6",
              "title": "EDCS or eView documentation",
              "kind": "action",
              "actor": "Technician",
              "action": "Use the subject section of the SSA-5002 ROC OR the appropriate DCPS case-note section for the required notation. These alternatives do not establish record identity.",
              "conditions": [
                "An EDCS/eView claim is involved."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "component-documentation"
            },
            {
              "id": "dual-or-excluded-attestation-step-7",
              "title": "FO documentation for a non-electronic claim",
              "kind": "action",
              "actor": "FO",
              "action": "For an EDCS exclusion without an associated electronic folder, put the required notation and non-electronic status on RPOC in MCS for Title II or CCE for Title XVI.",
              "conditions": [
                "EDCS exclusion AND no associated electronic folder AND FO handling."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "component-documentation"
            },
            {
              "id": "dual-or-excluded-attestation-step-8",
              "title": "DDS or DCR documentation for a non-electronic claim",
              "kind": "action",
              "actor": "DDS or DCR",
              "action": "For an EDCS exclusion without an associated electronic folder, put the required notation in a DCPS case-note entry.",
              "conditions": [
                "EDCS exclusion AND no associated electronic folder AND DDS/DCR handling."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "component-documentation"
            },
            {
              "id": "dual-or-excluded-attestation-step-9",
              "title": "OHO or OAO documentation for a non-electronic claim",
              "kind": "action",
              "actor": "OHO or OAO",
              "action": "For an EDCS exclusion without an associated electronic folder, document the required notation on a ROC in ENM.",
              "conditions": [
                "EDCS exclusion AND no associated electronic folder AND OHO/OAO handling."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ],
              "alternative_group": "component-documentation"
            },
            {
              "id": "dual-or-excluded-attestation-step-10",
              "title": "Associate the valid completed paper form",
              "kind": "action",
              "actor": "Technician",
              "action": "Scan, fax or upload the valid completed paper SSA-827 into the applicable EDCS/eView electronic folder or Evidence Portal, associate it with the paper folder, or upload into ENM where applicable. These are scoped destinations, not a direction to send to all of them.",
              "conditions": [
                "The paper form is valid and complete; choose the applicable folder/system destination."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            },
            {
              "id": "dual-or-excluded-attestation-step-11",
              "title": "Give a copy of the completed form",
              "kind": "action",
              "actor": "Technician",
              "action": "Provide a copy of the scanned completed paper SSA-827 to the individual.",
              "conditions": [
                "The valid completed paper authorization has been handled under the applicable procedure."
              ],
              "source": "ssa827signature",
              "section": "D2f",
              "source_context_refs": [
                "DI11005.056-D2f",
                "DI11005.056-whole"
              ],
              "qualifications": [
                "Source instructions describe prescribed handling, not a finding that consent, signer authority, identity, submission or evidence release has been established.",
                "State-law authority, proper-applicant and identity procedures remain separately applicable; this mapping does not decide a real case."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "note": "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration.",
            "automatic_transition": false,
            "unknowns": [
              "The source gives conditional staff instructions; completed handling and return to the usual path are not established by this illustration."
            ]
          },
          "alternative_groups": [
            {
              "id": "component-documentation",
              "label": "Use the documentation instruction for the actual claim and component",
              "logic": "source_conditions_determine_branch",
              "note": "The following four cards are scoped alternatives, not four universal documentation steps. No generic CPS/DCPS identity or case-system migration is inferred."
            }
          ]
        }
      },
      "route_notes": {
        "adult-court-incompetence-signer": "C2b body requires no legally appointed representative; an existing representative being unreachable is not that condition. Court findings and proper-applicant authority are not decided here.",
        "no-appointed-adult-representative": "C2b body requires no legally appointed representative; an existing representative being unreachable is not that condition. Court findings and proper-applicant authority are not decided here."
      },
      "holds": [
        "No prior whole-page capture is claimed byte-compared here; the retained source object has an October16 selected-scope check, preserved verbatim.",
        "State-law authority, confidential-minor treatment, guardianship, proper-applicant and identity findings require their applicable separately reviewed authority; no case finding is made.",
        "C3 exception1 references D2b when the source requires both signatures; D2f separately governs permitted attestation where two signatures are required. Preserve both scopes without inventing a conflict resolution or precedence rule.",
        "C3 exception overlap has no specified precedence here.",
        "D2a enumerates adult self-signers and child signing situations; do not infer general adult proxy attestation permission from C2 alone.",
        "Internet D1 is reviewed context but is not one of these ten mapped route proposals.",
        "No medical evidence original-disposition source hold is resolved by this authorization policy."
      ],
      "projection_contract": {
        "approved_field_append_only": "exception_flow on the exact ten original full routes only",
        "old_records_sources_statuses_history": "exact after stripping only the ten approved exception_flow fields",
        "no_new_routes_entities_edges_aliases": true,
        "all_rejoins_unknown": true,
        "prospective_only_counts": {
          "mapped_if_integrated": 67,
          "legacy_if_integrated": 997,
          "currently_reviewed_R23_mapped": 57,
          "currently_R23_legacy": 1007
        }
      },
      "negative_cases": [
        {
          "id": "N01",
          "case": "Only unable to write with a pen; other permissible signing methods not evaluated",
          "required_boundary": "Do not assert C1 all-methods physical incapacity."
        },
        {
          "id": "N02",
          "case": "Payee or appointed representative designation alone",
          "required_boundary": "Do not establish other-personal-representative authority."
        },
        {
          "id": "N03",
          "case": "Age12 but no applicable minor-under-state-law finding",
          "required_boundary": "Do not assume C3 minor scope."
        },
        {
          "id": "N04",
          "case": "Parent strongly objects but source requires child signature",
          "required_boundary": "Do not grant the C3 exception1 waiver."
        },
        {
          "id": "N05",
          "case": "Confidential treatment state-law condition unknown",
          "required_boundary": "Do not select child-only signing."
        },
        {
          "id": "N06",
          "case": "Legally appointed representative exists but is unreachable",
          "required_boundary": "Do not substitute C2b no-legally-appointed-representative premise."
        },
        {
          "id": "N07",
          "case": "Adult proxy proposes attestation based only on proper-applicant status",
          "required_boundary": "C2 is not a general D2a proxy-attestation permission."
        },
        {
          "id": "N08",
          "case": "No review or person declines attestation",
          "required_boundary": "Do not attest or infer authorization."
        },
        {
          "id": "N09",
          "case": "EDCS exclusion but an associated electronic folder exists and no two-signature requirement",
          "required_boundary": "Do not infer the exclusion-without-EF trigger; preserve independent two-signature trigger."
        },
        {
          "id": "N10",
          "case": "Two signatures required, claim otherwise electronic",
          "required_boundary": "Do not require exclusion as well; D2f trigger is OR."
        },
        {
          "id": "N11",
          "case": "Special paper attestation uses valid completed form",
          "required_boundary": "Do not apply standard electronic no-fax/scan instruction to D2f."
        },
        {
          "id": "N12",
          "case": "DDS no-EF case",
          "required_boundary": "Do not send FO RPOC/MCS/CCE or OHO/OAO ENM instructions as universal."
        },
        {
          "id": "N13",
          "case": "CaseNote, SSA5002, ROC and generic CPS retrieved together",
          "required_boundary": "Do not infer aliases or graph edges."
        },
        {
          "id": "N14",
          "case": "Step completion or signed form receipt not observed",
          "required_boundary": "Do not claim successful release, runtime propagation, rejoin, or benefit outcome."
        }
      ],
      "revision": {
        "prior_package_sha256": "9fbe6a827c1d525a1000123bdc1cb28242f2196f5779d939dd211506273ecc9c",
        "reason": "Independent actor-side/schema/Boolean-clarity review; no source capture changes.",
        "approved_diff_scope": [
          "Public signer actions kind action→you; confidential-minor signing actor Claimant/you.",
          "Ten rejoin records add automatic_transition:false and note copied into unknowns.",
          "D2f source trigger gains explicit parentheses in wrapper and repeated step conditions."
        ],
        "source_capture_contexts_original_records_unchanged": true
      }
    },
    "dedicated_account_source": {
      "schema": "securitystat.source-bound-exception-flow-package/1",
      "status": "DRAFT_SELECTED_DEDICATED_ACCOUNT10_PENDING_INDEPENDENT_SOURCE_REVIEW",
      "created_utc": "2026-10-31T19:35:37.182579+00:00",
      "baseline_frozen_R23_R2_data_sha256": "9ab9e1413868b5a03bcf07550bbca2cefccccfa7b6cff94c4e7d9f154ba9684c",
      "source_capture": {
        "main_sha256": "1f06fc6b166cbfb0f7eb09f9ad62f32f394658bbfac3cc997268e2d7df9da8c1",
        "snapshot_sha256": "ec1081078180d18abc7cc8e7c373af4726ced2c1c8a1d9e6fe60d6043d4784f1",
        "metadata_sha256": "047fdf070346c7b636e22762de706ca3a09f6face1a93cb25ec6188a86edf4a3",
        "whole_chars": 22876,
        "observed_revision": "2026-04-13 TN40(04-26)",
        "primary_URL": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502101010"
      },
      "source_contexts": [
        {
          "id": "SI02101.010-whole",
          "source_code": "SI02101.010",
          "locator": "Whole A-D including tables, notes and examples",
          "start": 0,
          "end": 22876,
          "exact_text": "Effective Dates: 04/13/2026 - Present\nPrevious | Next\n\nTN 40 (04-26)\n\nSI 02101.010 Past-Due Benefits Payable - Individual Alive Under Age 18 with Representative Payee - Dedicated Account Required\n\nCITATIONS:\n\nSocial Security Act §1631(a)(2)(F) and (10);\n20 C.F.R. §416.546, §416.640(e)(2), and §416.545\nA. \nIntroduction - dedicated accounts\n\nEffective August 1996, after any Interim Assistance (IA) reimbursement payment and direct payment of representative fees, we must pay any remaining past-due payment that exceeds six times the Federal Benefit Rate (FBR) plus any federally-administered Optional State Supplement (OSS) that we would normally pay to the representative payee (payee) of an eligible individual under age 18, into a dedicated account at a financial institution. For dedicated account requirements, refer to GN 00603.025. For information regarding collective savings and checking accounts, refer to GN 00603.020.\n\nB. \nPolicy - dedicated accounts\n1. \nPast-due benefits paid to a dedicated account\n\nThe payee must establish a dedicated account before we release the past-due benefits. We will deposit the past-due benefits into this account. The funds may be used only for certain limited expenditures as described in GN 00602.140.\n\nEXCEPTION: If we have appointed the Bureau of Indian Affairs as the payee and direct deposit is not possible, an automated one-time payment (A-OTP) directly to the Bureau of Indian Affairs for deposit into the child’s account.\n\nIF…\n\n\t\n\nTHEN…\n\n\n\n\nAfter reimbursement for IA and direct payment for representative fees, the past-due benefit is not equal to or greater than 3 X (FBR + OSS)\n\n\t\n\nNormal underpayment rules apply and we will release the past-due benefits or offset for a collectible overpayment.\n\n\n\n\nAfter reimbursement for IA and direct payment for representative fees, the past-due benefit equals or exceeds 3 X (FBR + OSS) but does not exceed 6 X (FBR + OSS)\n\n\t\n\nInstallment provisions will apply, and we will release the past-due benefits in installment payments or offset for a collectible overpayment. For more installment payment information, refer to SI 02101.020. A dedicated account is not required.\n\n\n\n\nAfter reimbursement for IA and direct payment of representative fees, the past-due benefits are greater than 6 X (FBR + OSS)\n\n\t\n\nWe must issue these payments in installments at 6-month intervals, in addition to depositing them in a dedicated account that the payee established. For installment requirements, refer to SI 02101.020.\n\n\n\n\nAfter reimbursement for IA and direct payment of representative fees, the past-due benefits are greater than 6 X (FBR + OSS) but payee does not establish a dedicated account\n\n\t\n\nWe cannot release the past-due benefits to the payee. The technician must determine the need for a new payee, per GN 00504.100.\n\n\n\n\nThe individual dies prior to the payee establishing a dedicated account\n\n\t\n\nFollow normal underpayment rules in SI 02101.002 to determine if and to whom we may issue the past-due benefits.\n\n\n\n\nThe individual dies after the payee establishes a dedicated account\n\n\t\n\nWe have no authority over this account upon the individual's death. The dedicated account is part of the deceased individual’s estate.\n\n\n\n\nThe individual attains age 18 prior to the issuance of the notice of determination of eligibility for past-due benefits\n\n\t\n\nThe dedicated account provision does not apply. Normal underpayment rules apply, per SI 02101.001. Installments may apply, per SI 02101.020.\n\n\n\n\nAn individual is under age 18 but does not have a payee\n\n\t\n\nDedicated account rules do not apply. Normal underpayment rules apply, per SI 02101.001. Installments may apply, per SI 02101.020.\n\n2. \nOptional deposits to a dedicated account\n\nAfter a payee establishes a dedicated account, subsequent past-due benefits that are 6 X (FBR + OSS) or less are not required to be deposited in the dedicated account. If the payee chooses to deposit the funds into a dedicated account, the payee must use the funds in the dedicated account for limited permissible expenditures. For more information about permitted expenditures from a dedicated account, refer to GN 00602.140.\n\nIf the subsequent past-due benefit is equal to or greater than 3 X (FBR +OSS), but does not exceed 6 X (FBR +OSS), installment provisions apply.\n\n3. \nDefinition - past-due benefits\n•\n\nBenefits due, but unpaid, that accrued prior to the month of payment effectuation;\n\n•\n\nBenefits due, but unpaid, that accrued during a period of suspension for which the individual was subsequently determined to have been eligible; or\n\n•\n\nAny adjustment to benefits that results in an accrual of unpaid benefits.\n\n4. \nPayee responsibilities\n\nThe payee may use benefits deposited into a dedicated account only for specific and limited expenses for the child. For more information about the payee requirements and responsibilities concerning these dedicated accounts, refer to GN 00602.140.\n\n5. \nResource and income exclusions\n\nPast-due benefits deposited into a dedicated account are excluded from resources. Any accrued interest the account earns is excluded from income and resources. The payee may deposit additional smaller past-due benefits into the dedicated account. These benefits are also excluded from resources. For additional information on this resource and income exclusion, refer to SI 01130.601.\n\n6. \nInstallment dedicated accounts\n\nEffective for past-due benefits paid on May 22, 2006 or later, Section 7502 of the Deficit Reduction Act of 2005, P.L. 109-171, enacted February 8, 2006, changes the formula for determining when we pay SSI past-due benefits in installments.\n\nIf the past-due benefits equal or exceed 3 X (FBR+OSS) but do not exceed 6 X (FBR+OSS), after IA reimbursement and direct payment of representative fees, we must issue these payments in installments, but they do not require a dedicated account.\n\nIf the past-due benefits are greater than 6 X (FBR+OSS), after IA reimbursement and or direct payment of representative fees, we must deposit these payments into a dedicated account in up to 3 installments at 6-month intervals. The first and second installment payments cannot exceed 3 X (FBR + OSS) unless the technician documents the request for an additional amount on a Report of Contact when an individual has outstanding debts or expenses as described in SI 02101.020B.4. However, because of dedicated account restrictions, installment payments to dedicated accounts should only be increased for debts related to:\n\n•\n\nMedical treatment.\n\n•\n\nEducation or job skills training; or\n\nIf related to the individual's impairment:\n\n•\n\nPersonal needs assistance,\n\n•\n\nSpecial equipment,\n\n•\n\nHousing modification,\n\n•\n\nTherapy, or\n\n•\n\nRehabilitation.\n\nFor examples of approved dedicated account expenditures, refer to GN 00602.140F.\n\nThe system determines (after any prepayment review, IA reimbursement, direct payment of representative fees, and automated recovery of any outstanding overpayment) whether installments apply. The system sets EA and IN diaries, and sends E1 and I6 alerts notifying the FO that the past-due benefits are scheduled for A-OTP into the dedicated account. The system also generates an automated notice to the individual explaining the current installment payment and that we will issue the next payment in 6 months.\n\nGenerally, the required dedicated account notices are automated. If a case requires a manual notice, the notices are available in DPS.\n\nIf the system does not automatically offset a prior collectible overpayment, recover the overpayment from the individual's continuing SSI payments at the 10 percent recovery rate.\n\nHowever, even though we must deposit the benefits into a dedicated account, installment procedures do not apply if the individual:\n\n•\n\nHas a medical condition that is expected to result in death within 12 months, or\n\n•\n\nIs ineligible at the time of payment and is likely to remain ineligible for the next 12 months.\n\nIf one of these exceptions applies, we deposit the entire amount into the dedicated account using the A-OTP process.\n\n7. \nCurrent calendar month benefits included in installment dedicated accounts\n\nIf benefits for the current calendar month, or a subsequent month, are included in the benefits subject to installments or dedicated accounts, the FO must use the A-OTP process to issue the current month, or a subsequent month's payment to the payee. In some instances, this action removes the case from the installment or dedicated account provision.\n\nNOTE: \n\nWe will only take this action after any prepayment review of large underpayments adjustment for reimbursement for IA, calculation or adjustment for direct payment of attorney or non-attorney fees, or automated recovery of any collectible overpayment. For more information about the prepayment review requirements for large underpayments, refer to SI 02101.025.\n\nEXAMPLE 1: If the technician effectuated the SSI claim on August 15th, the current computation month is September. we will issue the first monthly payment on September 1 and treat all benefits through August as an underpayment subject to the installment or dedicated account provisions. The FO must issue an A-OTP for August (the current calendar month).\n\nEXAMPLE 2: If the technician effectuated the claim after the current computation month cutoff in August, the current computation month would be October. We would issue the first monthly payment on October 1, and treat all benefits due through September as an underpayment subject to installment or dedicated account provisions. In this situation, the FO must issue an A-OTP for the current calendar month’s benefits (August), and September benefits.\n\nIn both examples, the A-OTP may reduce the underpayment to less than 3 X FBR so that the installment provisions do not apply or less than 6 X FBR so that dedicated account provisions do not apply.\n\n8. \nInterim Assistance Reimbursement (IAR) cases\n\nEffective November 2010, when the FO, or an automated interface adds a pending grant reimbursement code (GRC) to an SSR, the system holds the entire underpayment with a UPV:V until the IAR is processed. Reimbursement to the state occurs automatically, without FO involvement unless the case requires FO intervention or the case is an eIAR exception. For information on FO intervention cases, refer to SM 01311.662C. For eIAR exception cases, refer to SI 02003.023.\n\nIf a dedicated account is not required after IAR, direct payment for representative fees, and automated recovery of any collectible overpayment, we release the underpayment.\n\nFor installment procedures, refer to SI 02101.020.\n\n9. \nClosed period of disability at time of past-due benefit determination and medical cessation cases\n•\n\nClosed period of disability cases placed in PSY N07 (i.e., not disabled) do not require a dedicated account for a child under 18 with a representative payee, even if the payee files an appeal.\n\n•\n\nIn medical cessation cases (CDRs), even when the individual appeals the cessation, the dedicated account rules stop at termination, unless we approve a request for benefit continuation. If benefit continuation applies, then dedicated account rules continue.\n\n•\n\nIf an existing dedicated account is involved in a medical cessation case, the rules for the account cease, unless benefit continuation applies.\n\n10. \nNon-pay dedicated account cases with installments\n\nIf a case goes into non-pay or suspense status during the installment process, the FO must issue the scheduled installment to the payee by A-OTP unless the individual is residing in a correctional institution. The case requires a manual notice. For instructions on the prohibition against paying installments to persons residing in a correctional institution, refer to SI 00529.001.\n\nC. \nProcedure\n1. \nIAR involvement – underpayment $15,000 or more\n\nIf the past-due benefits are equal to or greater than $15,000, the FO must complete the underpayment prepayment review as described in SI 02101.025. Use the Underpayment Processing (UOUP) screen through Direct SSR Update. For more information on the UOUP screen, refer to MS 00304.018.\n\nOnce the FO completes the prepayment review, select option 4 = Release Underpayment/Prepayment Review Completed or Title II Offset Involved from the UOUP screen. If the FO does not complete the prepayment review through the UOUP screen, the case will not be automated. If the case is automated, the system generates:\n\n•\n\nAn underpayment verification code (UPV) of ‘V’;\n\n•\n\nA request that the State submit its request for reimbursement for IA within 25 days through the eIAR website.\n\nOnce the State submits the request, the system will compute and issue the reimbursement amount, and process the remaining underpayment according to the priority of payment rules. If the system cannot issue the reimbursement automatically, it will post an I9 diary to the record which requires FO intervention;\n\nNOTE: \n\nThe system will not set the E1 alert or the EA diary until the IAR is resolved.\n\n•\n\nAn E1 alert to the FO for the payee to establish a dedicated account; and\n\n•\n\nAn EA diary indicating need for account establishment.\n\nThe system then determines whether the remaining underpayment requires a dedicated account and whether installments are required and changes the UPV field from a ‘V’ to ‘2’ or ‘B.’ When the payee has established the dedicated account, the past-due benefits should be direct deposited into the account by A-OTP, per SM 01311.660 and MS 00304.018.\n\nNOTE: \n\nFor past-due benefits less than $15,000 with IAR involvement, the system also determines whether a dedicated account is required after the State and or direct payment of representative fees has been paid. If a dedicated account is still required, the system generates an alert and diary for the establishment of the account and benefit payment.\n\nOnce the account is established, follow the procedures in SI 02101.010C.3. in this section.\n\nThe system releases the underpayment in installments, if required if a dedicated account is not required after IA reimbursement and or direct payment for representative fees. For an overview of the SSI underpayment system process, refer to SM 01311.660.\n\nWhen there is a prior collectible overpayment on the record and there is direct payment of authorized representative fees, the systems priority of payment order is:\n\n•\n\nIAR payment\n\n•\n\nDirect Payment of Representative Fee\n\n•\n\nRecovery of Prior Overpayment\n\n2. \nNo IAR involvement and no direct payment of representative fee\n\nIf the past-due benefits require a prepayment review, the FO should follow instructions in SI 02101.025. After the prepayment review, use the UOUP screen to release the underpayment using the appropriate option. Refer to MS 00304.018 and SM 01311.661.\n\nThe system determines if a dedicated account with installments applies. It sets the UPV to ‘B’ and issues an automated notice to the payee informing them to set up a dedicated account. The system also sets an EA diary with a 30-day maturity date. If the diary matures, the system generates an E1 alert to notify the FO that the payee must establish a dedicated account. The system sends follow-up alerts every 15 days thereafter until we issue an A-OTP to the dedicated account, resolving the diary.\n\nNOTE: \n\nIf no prepayment review is necessary but the record requires a dedicated account, the system sets the UPV to ‘B’ and sets appropriate diaries and alerts, as explained. The system also generates the appropriate notices.\n\n3. \nPayee establishes dedicated account\n\nOnce the payee establishes a dedicated account for an individual who is disabled and provides the FO with the required information for the account (the name and address of the financial institution, the routing number, account number, account title, type of account, and the amount of money deposited to open the account), the FO should:\n\n•\n\nHave the payee or individual in direct pay sign and date the SSA-552 “Dedicated Account Use of Funds Statement.” A PDF version of the SSA-552 is available on the inFORM Library website to print. The SSA-552 is also available online. An individual payee with a my Social Security account can complete and submit the form through Upload Documents, located in the my Social Security individual payee portal. A technician also can initiate the request to complete and submit the SSA-552 electronically utilizing the Upload Documents task in the Technician Experience Dashboard (TED); a link to complete, sign, and submit the SSA-552 Electronically in Upload Documents will be sent directly to the payee by email or text.\n\nNOTE: \n\nFor instructions on completing the SSA-552 statement, refer to GN 00602.140F.\n\n•\n\nInput the financial institution information (routing number, account number, etc.) using the One-Time Payment Address (UPOA) screen. For A-OTP rules for records with direct deposit to the dedicated account, refer to SM 01901.160.\n\nThe dedicated account cannot be the same financial account to which we issue the regular, recurring SSI payment. If the bank account input on the A-OTP matches the bank account on the SSR in the DRDP segment of the SSR, the system will issue a UP reject. Refer to SM 01901.160 for A-OTP rules for records with direct deposit. Use the Special Payments Menu (UPSP) from the Direct SSR Update to establish an A-OTP from the One-time Payment (UPOT) screen (Option 2) to direct this payment to the new dedicated account. This does NOT affect the regular, recurring SSI payment information on the SSR.\n\n4. \nPayee establishes dedicated account - subsequent underpayments\n\nAfter the payee has established a dedicated account, the amount of a subsequent underpayment determines whether we must deposit, may deposit, or may not deposit it into the dedicated account.\n\n•\n\nIf the subsequent underpayment may be deposited, the system releases the underpayment and notice with language stating that it may be deposited into the dedicated account.\n\n•\n\nIf the subsequent underpayment is equal to or greater than 3 X FBR+OSS, it is paid in installments.\n\n•\n\nIf we have begun installments, we will add any ‘new’ underpayment to the next installment. The system releases a notice that explains the new underpayment and instructs the payee to contact the field office if they want the money paid directly to them.\n\n5. \nPayee does not establish a dedicated account\n\nIf, after 30 days from the original notice explaining the requirement for a dedicated account, the payee has not established the account, follow instructions in “Determining the Need for a Successor Payee” GN 00504.100. Once the EA diary matures, the system generates an E1 alert to the FO to notify them that the record is still waiting for a dedicated account. The system generates follow-up alerts every 15 days until the EA diary is resolved.\n\nD. \nExamples\n1. \nIndividual under age 18 with payee - past-due benefits payable - dedicated account required\n\nJune is the payee for their child, Jake, a 7-year old who has a disability. The SSI claim was filed on January 3, 2023. On October 22, 2024, the FO receives a favorable disability determination from DDS that the child has a disability as of January 3, 2023.\n\nThe FO knows that the child's past-due benefit will exceed 6 times the adjusted FBR plus any federally administered optional State supplements ($914 + 75 State supplement for 2023 and $943 +$75 State supplement for 2024). The FO conducts the prepayment review ($21,059 in past-due benefits for February 2023 – October 2024), completes the UOUP screen through Direct SSR Update, and enters the appropriate selection.\n\nThe system holds the past-due benefits, sets the appropriate UPV code and diary, and issues an alert, if necessary. No IAR or representative fees are involved. The automated notice is released to the payee explaining the requirements of a dedicated account.\n\nAfter receiving the dedicated account notice, the payee visits the FO with the required financial institution information. The FO has the payee sign and date the SSA-552, Dedicated Account Use of Funds Statement, explaining the limited expenditures authorized from this account.\n\nThe FO transmits the financial institution information on the UPOA screen and issues the first installment payment of $3,054 by A-OTP into the account. This resolves the EA diary. The system establishes an IN diary to indicate the next installment payment is due.\n\nTwo months prior to the second installment payment, June visits the FO to request $1,500 to purchase special equipment that is related to Jake’s impairment. The technician documents June’s request for the additional underpayment installment amount on a Report of Contact and issues an A-OTP to June to purchase the special equipment.\n\n2. \nAn individual with a disability attains age 18 prior to the determination of eligibility for past-due benefits - dedicated account is not required\n\nJean is payee for their child, Ross. Jean filed an SSI claim for Ross on February 3, 2024. On November 27, 2024, the FO receives a favorable DDS disability determination that Ross has a disability as of February 3, 2024. Ross attained age 18 on September 2, 2024.\n\nThe FO determines that Ross needs a payee. Although the past-due benefits exceed 6 times the FBR + OSS, because Ross attained age 18 prior to SSA issuing a determination they are eligible for past-due benefits, the past-due benefits are not subject to the dedicated account requirements, but we must pay them in installments.\n\nTherefore, after prepayment review, if the underpayment is $15,000 or more, the FO adjudicates the case to pay and the system releases the past-due benefits in installment payments to the representative payee, along with an award notice.\n\n3. \nIAR involved - dedicated account not required\n\nThe FO receives a favorable disability determination from the DDS on November 25, 2024 that Matt, who is ten years old, has a disability as of February 11, 2024. Matt's parent is selected as the payee.\n\nAlthough there is an IAR, the FO believes the past-due benefits may still exceed 6 times the FBR + OSS, after we have paid the State. After we receive the SSA-L8125-F6 from the State and issue an A-OTP for the IAR, the past-due benefits no longer exceed 6 times the FBR + OSS. Therefore, a dedicated account is not required. If installments apply, the system releases the first installment to the payee and sets the UPV to ‘2’ to control for the next installment.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0502101010\n\t\nSI 02101.010 - Past-Due Benefits Payable - Individual Alive Under Age 18 with Representative Payee - Dedicated Account Required - 04/13/2026\nBatch run: 04/13/2026\nRev:04/13/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
          "sha256": "1f06fc6b166cbfb0f7eb09f9ad62f32f394658bbfac3cc997268e2d7df9da8c1"
        }
      ],
      "original_source_object": {
        "code": "SI 02101.010",
        "title": "Past-Due Benefits Payable - Individual Alive Under Age 18 with Representative Payee - Dedicated Account Required",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0502101010",
        "revision": "Rev/batch2026-04-13; TN40(04-26)",
        "kind": "POMS staff policy/procedure",
        "checked_on": "2026-10-17",
        "verification_scope": "A; B1/B6 thresholds; C2-C3/C5 discovered; other cross-references pending"
      },
      "flows": {
        "childhood-disability-after-dds/child-ssi-dedicated-account-exact-threshold": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-dedicated-account-exact-threshold",
          "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-exact-threshold",
          "entry_conditions": [
            "SSA is reviewing past-due SSI for an individual under age 18 with a representative payee. Other dedicated-account exceptions remain separately applicable.",
            "After interim-assistance reimbursement and direct payment of representative fees, the remaining past-due amount is EXACTLY six times the FBR plus any federally administered OSS."
          ],
          "steps": [
            {
              "id": "child-ssi-dedicated-account-exact-threshold-source-step-1",
              "title": "Keep the exact-six boundary distinct",
              "kind": "action",
              "actor": "SSA staff",
              "action": "At exactly 6 × (FBR + federally administered OSS), the table places the payment in the installment range and does not require a dedicated account. Collectible-overpayment offset and separately applicable installment exceptions remain separate. The greater-than-six dedicated-account instruction is not triggered merely by equality.",
              "conditions": [
                "SSA is reviewing past-due SSI for an individual under age 18 with a representative payee. Other dedicated-account exceptions remain separately applicable.",
                "After interim-assistance reimbursement and direct payment of representative fees, the remaining past-due amount is EXACTLY six times the FBR plus any federally administered OSS."
              ],
              "source": "ssidedicatedaccount",
              "section": "A; B.1 threshold table; B.6",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "Do not replace the strict greater-than-six threshold with equal-to-or-greater-than-six. The earlier recorded SI02101.002 comparison remains a separate unresolved history; no dollar rate is inferred from historical examples."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        },
        "childhood-disability-after-dds/child-ssi-dedicated-account-setup-evidence": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-dedicated-account-setup-evidence",
          "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-setup-evidence",
          "entry_conditions": [
            "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
            "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts."
          ],
          "steps": [
            {
              "id": "child-ssi-dedicated-account-setup-evidence-source-step-1",
              "title": "Keep the account requirement before release",
              "kind": "action",
              "actor": "SSA staff",
              "action": "The payee must establish the required dedicated account before SSA releases past-due benefits to that payee. Unknown account information does not establish completion.",
              "conditions": [
                "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
                "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.1",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
              ]
            },
            {
              "id": "child-ssi-dedicated-account-setup-evidence-source-step-2",
              "title": "Once the account is established: obtain and input its information",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When the payee has established the account and provided the required financial-institution/account information, obtain the signed and dated SSA-552, input the institution information through UPOA, and use the stated UPSP/UPOT A-OTP procedure for the dedicated account. The account cannot be the regular recurring-payment account; a matching SSR/DRDP account causes a UP reject and does not establish payment.",
              "conditions": [
                "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
                "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts.",
                "The account is established and the payee provides its required institution name/address, routing/account numbers, title/type and opening-deposit amount."
              ],
              "source": "ssidedicatedaccount",
              "section": "C.3",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
              ],
              "alternative_group": "account-status"
            },
            {
              "id": "child-ssi-dedicated-account-setup-evidence-source-step-3",
              "title": "After 30 days without establishment: follow successor-payee review",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If the payee has not established the account 30 days after the original notice explaining the requirement, follow GN00504.100. EA maturity generates an E1 alert; follow-up alerts recur every 15 days until the EA diary is resolved. This is not automatic payee replacement or a payment guarantee.",
              "conditions": [
                "SSA has established that the child’s past-due SSI requires a dedicated account; this illustration does not decide that threshold or exception question.",
                "Whether the required account has actually been established, and when the original account notice was issued, are separate case facts.",
                "At least 30 days have elapsed after the original required-account notice AND the account has not been established."
              ],
              "source": "ssidedicatedaccount",
              "section": "C.5",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "C.2’s no-IAR/no-direct-representative-fee diary context is not generalized to every setup case. C.3 permits an individual payee with a my Social Security account to use the payee portal Upload Documents option; a technician can initiate the SSA-552 electronic request in TED. No form submission or receipt is established here. GN00504.100 and detailed SM01901.160 transaction instructions are not newly reviewed."
              ],
              "alternative_group": "account-status"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          },
          "alternative_groups": [
            {
              "id": "account-status",
              "label": "Account-established and overdue-not-established situations",
              "logic": "source_conditions_determine_branch",
              "note": "These source situations are alternatives, not successive steps. Before 30 days, unknown notice dates, incomplete information or an unresolved UP reject do not select the overdue or successful-payment outcome."
            }
          ]
        },
        "childhood-disability-after-dds/child-turns18-before-pastdue-notice": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-turns18-before-pastdue-notice",
          "full_route": "childhood-disability-after-dds/child-turns18-before-pastdue-notice",
          "entry_conditions": [
            "The individual attains age 18 before SSA issues the notice determining eligibility for past-due benefits; application and disability-onset dates are not substituted for this boundary."
          ],
          "steps": [
            {
              "id": "child-turns18-before-pastdue-notice-source-step-1",
              "title": "Use the age-at-notice exception",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Dedicated-account provisions do not apply in this situation. Apply normal underpayment rules; installments may still apply. The D.2 example retains a representative payee, so this exception does not by itself remove the payee.",
              "conditions": [
                "The individual attains age 18 before SSA issues the notice determining eligibility for past-due benefits; application and disability-onset dates are not substituted for this boundary."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.1 age-18 row; D.2",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        },
        "childhood-disability-after-dds/child-ssi-death-account-versus-unpaid-benefits": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-death-account-versus-unpaid-benefits",
          "full_route": "childhood-disability-after-dds/child-ssi-death-account-versus-unpaid-benefits",
          "entry_conditions": [
            "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
            "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable."
          ],
          "steps": [
            {
              "id": "child-ssi-death-account-versus-unpaid-benefits-source-step-1",
              "title": "If death precedes establishment: keep the underpayment review separate",
              "kind": "action",
              "actor": "SSA staff",
              "action": "The B.1 death-before-establishment row directs normal underpayment review to determine whether and to whom past-due benefits may be issued. Its SI02101.002 target conflicts with the previously recorded deceased-underpayment review; this selected flow does not resolve that cross-reference or choose a recipient.",
              "conditions": [
                "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
                "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable.",
                "The individual died before the payee established the dedicated account."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.1 death-before-establishment row",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The old additional SI02101.003 citation, its review history and recorded .002/.003 cross-reference disagreement are preserved. They are not re-reviewed or silently resolved by this .010-only source package."
              ],
              "alternative_group": "death-account-status"
            },
            {
              "id": "child-ssi-death-account-versus-unpaid-benefits-source-step-2",
              "title": "If an account already exists: distinguish the estate account",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When death follows establishment, B.1 states that SSA has no authority over that established dedicated account and that the account is part of the individual’s estate. This statement does not award unpaid SSI to an estate or settle its separate payment rules.",
              "conditions": [
                "Death has occurred while child SSI past-due benefits or a dedicated account is involved.",
                "Whether the dedicated account was established before death is a distinct fact; funds in an established account and unpaid SSI are not interchangeable.",
                "The payee established the dedicated account before the individual’s death."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.1 death-after-establishment row",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The old additional SI02101.003 citation, its review history and recorded .002/.003 cross-reference disagreement are preserved. They are not re-reviewed or silently resolved by this .010-only source package."
              ],
              "alternative_group": "death-account-status"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          },
          "alternative_groups": [
            {
              "id": "death-account-status",
              "label": "Account timing at death",
              "logic": "source_conditions_determine_branch",
              "note": "The two rows have different establishment predicates. Neither determines survivor entitlement or treats an estate account as unpaid SSI."
            }
          ]
        },
        "childhood-disability-after-dds/child-ssi-dedicated-account-medical-cessation": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-dedicated-account-medical-cessation",
          "full_route": "childhood-disability-after-dds/child-ssi-dedicated-account-medical-cessation",
          "entry_conditions": [
            "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation."
          ],
          "steps": [
            {
              "id": "child-ssi-dedicated-account-medical-cessation-source-step-1",
              "title": "Closed period in PSY N07",
              "kind": "action",
              "actor": "SSA staff",
              "action": "For a closed-period disability case placed in PSY N07, a child under 18 with a representative payee does not require a dedicated account, even if the payee appeals. This does not decide that appeal.",
              "conditions": [
                "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
                "This is a CLOSED-PERIOD case placed in PSY N07, rather than an inference from any nonpayment status."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.9 first bullet",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
              ],
              "alternative_group": "cessation-case"
            },
            {
              "id": "child-ssi-dedicated-account-medical-cessation-source-step-2",
              "title": "Medical cessation without approved continuation",
              "kind": "action",
              "actor": "SSA staff",
              "action": "In a medical cessation case, dedicated-account rules stop at termination unless SSA approves benefit continuation. An appeal alone is not approval. The source separately says rules for an existing dedicated account cease unless continuation applies.",
              "conditions": [
                "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
                "This is a medical cessation case; termination has occurred for the stop-at-termination instruction, and approved benefit continuation does not apply."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.9 second and third bullets",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
              ],
              "alternative_group": "cessation-case"
            },
            {
              "id": "child-ssi-dedicated-account-medical-cessation-source-step-3",
              "title": "Medical cessation with benefit continuation",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When benefit continuation applies, the dedicated-account rules continue under B.9. This illustration does not establish that continuation was requested or approved, or supply an election deadline.",
              "conditions": [
                "The case involves a closed period of disability or medical cessation. Staff must establish the actual payment status and any approved benefit continuation.",
                "This is a medical cessation case AND benefit continuation actually applies."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.9 second and third bullets",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The source’s existing-account statement and its scope are retained separately; this sequence does not infer an earlier termination date, general cessation appeal rule or benefit-continuation eligibility."
              ],
              "alternative_group": "cessation-case"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          },
          "alternative_groups": [
            {
              "id": "cessation-case",
              "label": "Keep closed-period status and medical-cessation continuation separate",
              "logic": "source_conditions_determine_branch",
              "note": "These are source-conditioned alternatives. Appealing, PSY N07, termination and approved continuation are different facts. Unknown facts establish no branch."
            }
          ]
        },
        "childhood-disability-after-dds/child-ssi-dedicated-installment-nonpay": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-dedicated-installment-nonpay",
          "full_route": "childhood-disability-after-dds/child-ssi-dedicated-installment-nonpay",
          "entry_conditions": [
            "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
            "The individual’s actual correctional-institution residence is a separate case fact."
          ],
          "steps": [
            {
              "id": "child-ssi-dedicated-installment-nonpay-source-step-1",
              "title": "Outside the correctional-institution exception: issue the scheduled installment",
              "kind": "action",
              "actor": "SSA staff",
              "action": "B.10 directs the FO to issue the scheduled installment to the payee by A-OTP and prepare a manual notice when the individual is not residing in a correctional institution. Nonpay or suspense alone does not cancel this scheduled installment.",
              "conditions": [
                "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
                "The individual’s actual correctional-institution residence is a separate case fact.",
                "The individual is NOT residing in a correctional institution."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.10",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
              ],
              "alternative_group": "residence-exception"
            },
            {
              "id": "child-ssi-dedicated-installment-nonpay-source-step-2",
              "title": "If correctional residence applies: hold the general payment route",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Do not apply the B.10 nonpay payment instruction as authority to pay a person residing in a correctional institution. The source refers to SI00529.001 for the prohibition; its detailed release rules remain outside this selected source review.",
              "conditions": [
                "The case enters nonpay or suspense status during an existing dedicated-account installment process.",
                "The individual’s actual correctional-institution residence is a separate case fact.",
                "The individual IS residing in a correctional institution."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.10",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits."
              ],
              "alternative_group": "residence-exception"
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          },
          "alternative_groups": [
            {
              "id": "residence-exception",
              "label": "Apply the actual residence condition",
              "logic": "source_conditions_determine_branch",
              "note": "The general scheduled-payment instruction and its correctional-institution exclusion are alternatives. Unknown residence does not establish either payment authorization or a final denial."
            }
          ]
        },
        "childhood-disability-after-dds/child-ssi-optional-subsequent-dedicated-deposit": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-optional-subsequent-dedicated-deposit",
          "full_route": "childhood-disability-after-dds/child-ssi-optional-subsequent-dedicated-deposit",
          "entry_conditions": [
            "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
            "The payee’s actual deposit choice and whether installments have already begun are separate facts."
          ],
          "steps": [
            {
              "id": "child-ssi-optional-subsequent-dedicated-deposit-source-step-1",
              "title": "Preserve the optional deposit and its restrictions",
              "kind": "action",
              "actor": "SSA staff",
              "action": "A qualifying subsequent payment of 6 × (FBR + OSS) or less need not be deposited into the dedicated account. If the payee elects deposit, limited permitted expenditures still apply. Amounts equal to or greater than three times but not exceeding six times remain subject to installment provisions.",
              "conditions": [
                "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
                "The payee’s actual deposit choice and whether installments have already begun are separate facts."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.2; C.4",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "General permitted-expenditure detail and the source’s must/may/may-not-deposit distinction require their own applicable conditions. This selected optional-deposit scenario does not classify every later payment."
              ]
            },
            {
              "id": "child-ssi-optional-subsequent-dedicated-deposit-source-step-2",
              "title": "When installments already began: keep the new-payment notice",
              "kind": "action",
              "actor": "SSA staff",
              "action": "If installments have begun, C.4 adds the new underpayment to the next installment and requires notice explaining it and instructing the payee to contact the FO if direct payment is wanted. This condition does not itself prove a payee election or completed payment.",
              "conditions": [
                "A dedicated account already exists, and the subsequent past-due payment is six times FBR plus federally administered OSS or less.",
                "The payee’s actual deposit choice and whether installments have already begun are separate facts.",
                "Installments have ALREADY begun and there is a new underpayment."
              ],
              "source": "ssidedicatedaccount",
              "section": "C.4",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "General permitted-expenditure detail and the source’s must/may/may-not-deposit distinction require their own applicable conditions. This selected optional-deposit scenario does not classify every later payment."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        },
        "childhood-disability-after-dds/child-ssi-installment-exception-dedicated-account": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-installment-exception-dedicated-account",
          "full_route": "childhood-disability-after-dds/child-ssi-installment-exception-dedicated-account",
          "entry_conditions": [
            "The benefits otherwise require deposit into a dedicated account.",
            "SSA establishes EITHER a medical condition expected to result in death within 12 months OR ineligibility at the time of payment AND likely continued ineligibility for the next 12 months."
          ],
          "steps": [
            {
              "id": "child-ssi-installment-exception-dedicated-account-source-step-1",
              "title": "Apply the installment exception without removing the account rule",
              "kind": "action",
              "actor": "SSA staff",
              "action": "When either stated B.6 exception applies, deposit the entire amount into the dedicated account using A-OTP rather than dividing it into installments. The dedicated-account restriction remains. Twelve months is a source condition, not a processing-time promise.",
              "conditions": [
                "The benefits otherwise require deposit into a dedicated account.",
                "SSA establishes EITHER a medical condition expected to result in death within 12 months OR ineligibility at the time of payment AND likely continued ineligibility for the next 12 months."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.6 final exception paragraphs",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The ineligibility exception requires both ineligibility AT PAYMENT and likely ineligibility for the NEXT12months. The old additional SI02101.020 citation and its broader installment-process scope are preserved without being newly re-reviewed."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        },
        "childhood-disability-after-dds/child-ssi-currentmonth-separate-payment": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-currentmonth-separate-payment",
          "full_route": "childhood-disability-after-dds/child-ssi-currentmonth-separate-payment",
          "entry_conditions": [
            "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
            "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
          ],
          "steps": [
            {
              "id": "child-ssi-currentmonth-separate-payment-source-step-1",
              "title": "Separate the included calendar-month payments",
              "kind": "action",
              "actor": "SSA staff",
              "action": "After the listed prerequisites, the FO uses A-OTP to issue included current or subsequent calendar-month benefits to the payee. Calendar month and computation month differ: the source’s August/September and August/October examples identify different payments to separate, not a universal completion deadline.",
              "conditions": [
                "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
                "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.7 and note; examples1-2",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The examples’ abbreviated less-than3/6FBR wording is not used to replace B.1/B.6 FBR-plus-federally-administered-OSS thresholds or their equality boundaries. Detailed prepayment and transaction manuals remain separate."
              ]
            },
            {
              "id": "child-ssi-currentmonth-separate-payment-source-step-2",
              "title": "Reassess the remaining amount without assuming a threshold result",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Separating these monthly payments may remove the case from installment or dedicated-account provisions. Whether it does depends on the remaining amount; this illustration does not calculate an actual award or guarantee removal.",
              "conditions": [
                "Current or subsequent calendar-month benefits are included in benefits subject to installment or dedicated-account provisions.",
                "Required prepayment review and applicable IA reimbursement, representative-fee and automated collectible-overpayment adjustments are prerequisites under the source note."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.7; examples1-2",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The examples’ abbreviated less-than3/6FBR wording is not used to replace B.1/B.6 FBR-plus-federally-administered-OSS thresholds or their equality boundaries. Detailed prepayment and transaction manuals remain separate."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        },
        "childhood-disability-after-dds/child-ssi-increased-dedicated-installment": {
          "schema": "securitystat.exception-flow/1",
          "record_id": "child-ssi-increased-dedicated-installment",
          "full_route": "childhood-disability-after-dds/child-ssi-increased-dedicated-installment",
          "entry_conditions": [
            "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
            "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
          ],
          "steps": [
            {
              "id": "child-ssi-increased-dedicated-installment-source-step-1",
              "title": "Document the additional-amount request",
              "kind": "action",
              "actor": "SSA staff",
              "action": "The technician documents the request for an additional amount on a Report of Contact when the individual has outstanding debts or expenses under the referenced installment instructions. This does not approve an individual purchase or expense.",
              "conditions": [
                "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
                "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.6 first/second installment paragraph",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The impairment-related qualifier applies to the latter list; it is not silently removed or imposed as a new qualifier on the separately listed medical-treatment/education categories. The old GN00602.140 manual-notice/appeal reference remains preserved but is not newly reviewed or extended here."
              ]
            },
            {
              "id": "child-ssi-increased-dedicated-installment-source-step-2",
              "title": "Apply the dedicated-account expense limits",
              "kind": "action",
              "actor": "SSA staff",
              "action": "Because dedicated-account restrictions apply, increases should be limited to debts related to medical treatment or education/job-skills training, or to impairment-related personal-needs assistance, special equipment, housing modification, therapy or rehabilitation. Broader general-installment examples do not remove these dedicated-account limits.",
              "conditions": [
                "The request concerns an additional amount above the normal FIRST or SECOND installment to a dedicated account.",
                "SSA must determine the actual outstanding debt or expense and whether it meets the dedicated-account purpose restrictions."
              ],
              "source": "ssidedicatedaccount",
              "section": "B.6 permitted-debt list",
              "source_context_refs": [
                "SI02101.010-whole"
              ],
              "qualifications": [
                "Selected published instructions only: actual account establishment, case conditions, receipt, inputs, payment and return to the usual path are not established by choosing this example.",
                "The original record and all source dates, flags, additional references and recorded disagreements remain unchanged. Only an independently approved exception_flow may later be appended.",
                "No financial account or identifier is collected here. No individual eligibility, payee, prognosis, expenditure, recipient or payment decision is made. Linked transaction, spending and successor-payee instructions retain separate review limits.",
                "The impairment-related qualifier applies to the latter list; it is not silently removed or imposed as a new qualifier on the separately listed medical-treatment/education categories. The old GN00602.140 manual-notice/appeal reference remains preserved but is not newly reviewed or extended here."
              ]
            }
          ],
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual source predicates, completed account or input actions, payment and a successful return to the usual path remain unverified."
            ]
          }
        }
      },
      "counts": {
        "existing_routes": 10,
        "new_routes": 0,
        "selected_cards": 19,
        "source_contexts": 1,
        "all_old_records_retained": true
      },
      "projection_contract": {
        "only_allowed_future_change": "Append exact independently approved exception_flow to these10existingrecords; preserve entire old data/workflow after removing ONLYthose10flow additions.",
        "native_entities_edges_aliases": 0,
        "source_status_date_promotion": false
      },
      "source_holds": [
        "GN00603.025 account establishment details; GN00602.140 spending/notice detail; SI02101.020 other installment rules; SI02101.025 prepayment review; GN00504.100 successor-payee determination; SM01901.160 transaction rejection/release; SI00529.001 correctional policy.",
        "Earlier .002/.003 deceased-underpayment discrepancy and additional-source histories are retained, not resolved.",
        "Source records remain selected-scope; no exhaustive payment workflow, rejoin, native-system interface, runtime or case completion is established."
      ],
      "negative_QA": [
        "Exactly6 does not satisfy greater-than6;3 is included in the installment range.",
        "Use FBR plus federally administered OSS, after the source-defined IA/fee adjustments.",
        "Do not resolve the old SI02101.002 threshold or deceased-underpayment cross-reference history by date precedence.",
        "Required account establishment precedes release; a recurring-account match causes UP reject, not successful payment.",
        "30 days runs from the ORIGINAL account notice; successor-payee review is not automatic replacement.",
        "Age18 boundary is notice issuance, not application/onset/first-payment date.",
        "Established estate account is distinct from unpaidSSI; no survivor or estate recipient is selected.",
        "Closed-periodPSYN07 is not every nonpay status; appeal alone is not approved benefit continuation.",
        "Correctional residence excludes the B10 payment instruction; unreviewedSI00529.001 does not imply a new release rule.",
        "Optional smaller deposit retains limited-use restrictions.",
        "Next installment aggregation requires installments to have already begun; no payee election is inferred.",
        "Ineligible at payment AND likely ineligible next12months is not OR.",
        "Removing installment division does not remove the dedicated-account requirement.",
        "Current/computation-month separation may change thresholds, never guarantees it.",
        "First/second installment increase is not a general-third-installment authority; required debt purpose and documentation remain.",
        "No actual account/routingnumber, prognosis, beneficiary finding, payment transaction or eligibility decision is performed."
      ],
      "independent_source_review_complete": false,
      "source_native_acceptance": false,
      "live_or_frozen_site_writes": false
    },
    "independent_reviews": {
      "SSA827": "3261e849c0c93cd909b9ac8a4ef614d83eca12b98edec2c309e2c973f8ff56df",
      "dedicated_account": "4cda7ca956b51296db70284dd7d01f7a999cba08e18e29d324f3d4e2d350241d"
    },
    "capture_links": {
      "SSA827": {
        "main": "/service/sources/DI11005.056-r24-main.txt",
        "snapshot": "/service/sources/DI11005.056-r24-DOM-snapshot.txt",
        "metadata": "/service/sources/DI11005.056-r24-metadata.json"
      },
      "dedicated_account": {
        "main": "/service/sources/SI02101.010-r24-main.txt",
        "snapshot": "/service/sources/SI02101.010-r24-DOM-snapshot.txt",
        "metadata": "/service/sources/SI02101.010-r24-metadata.json"
      }
    }
  },
  "r25_policy_change_eleven": {
    "schema": "securitystat.source-bound-exception-flow-package/1",
    "status": "SELECTED_ELEVEN_EXISTING_POLICY_CHANGE_SEQUENCES_INDEPENDENTLY_SOURCE_REVIEWED",
    "baseline_frozen_R24_data_sha256": "d12468b12b2b902a3b9d0f610e17e3d9049cfeb6b29e4948465d8ee0c080d4fd",
    "original_records": {
      "childhood-disability-intake/cdb-prior-denial-age22-reentitlement-review": {
        "id": "cdb-prior-denial-age22-reentitlement-review",
        "title": "Check the actual CDB denial dates behind the code",
        "when": "DDS evaluates a later childhood-disability claim involving an earlier G1 or G2 vocational denial.",
        "you": "Identify the earlier decision and relevant claim or reentitlement dates; SSA must assess its own prior records.",
        "ssa": "A G1 code alone does not show whether the earlier denial occurred after age 22. DDS checks that date. If the claim was not denied after age 22, DDS processes the later filing as a standard CDB claim. For a G1 reentitlement denial, if the reentitlement period was last met on or after the prior decision date, DDS uses the standard reentitlement route. G2 indicates a denial after that period ended and raises a potential res judicata issue requiring review.",
        "route": "DDS prior-claim date review → standard CDB or reentitlement processing, or applicable res judicata screening.",
        "next": "Ask which dates support the selected route. The code alone does not decide the new claim or eligibility.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "B.1 CDB paragraphs",
        "timing": "Age and period endpoints classify the claim; no determination duration is given.",
        "review_status": "Official CDB distinctions checked; general benefit eligibility, onset and reopening conditions remain separate."
      },
      "duplicate-benefit-application/prior-disability-past-work-policy-change": {
        "id": "prior-disability-past-work-policy-change",
        "title": "The earlier disability denial relied on past work under older rules",
        "when": "An applicable later Title II claim follows a pre-June 22, 2024 denial after non-disability requirements were last met, based on ability to perform past relevant work.",
        "you": "Identify the earlier denial and the dates and duration of the work it relied on.",
        "ssa": "The field office routes applicable cases to DDS with the potential-res-judicata review message. DDS checks prior documentation under the specific benefit and denial-basis criteria. A new substantive determination is required if the relied-on work was before the applicable five-year relevant period or began and ended in fewer than 30 calendar days. Work within that period spanning at least 30 days may still permit res judicata if all usual conditions are met.",
        "route": "Field office → DDS prior-denial and work-policy review.",
        "next": "Ask whether the earlier work finding requires a new determination under the changed rule; this does not establish disability or payment.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "B opening; B.1–B.2",
        "timing": "June 22, 2024 is the policy-change date; the work-period tests are not processing deadlines.",
        "review_status": "Official benefit/denial-basis scope checked. Other-work findings, CDB coding distinctions and listing changes remain separate candidates."
      },
      "duplicate-benefit-application/prior-other-work-experience-category-change": {
        "id": "prior-other-work-experience-category-change",
        "title": "Changed work-experience categories affect the earlier other-work denial",
        "when": "DDS reviews an applicable earlier Title II disability denial based on ability to adjust to other work.",
        "you": "Provide accurate work dates and duties; SSA determines the vocational categories and applicable rule.",
        "ssa": "DDS compares the prior finding, prior vocational rule and current category under the changed past-work definition. Res judicata does not apply where prior skilled or semiskilled transferable work used rule 201.03, 201.07, 201.11, 201.15, 202.03 or 202.07 and the current category is nontransferable skilled/semiskilled, unskilled or none; or where prior unskilled work used 203.03 or 203.11 and the current category is none.",
        "route": "DDS vocational comparison under the published table → substantive determination where the exception applies.",
        "next": "Ask whether the prior rule and current work category satisfy the table. A new determination is not an automatic allowance.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "B.3 opening; B.3.a table",
        "timing": "No vocational-review completion time is specified.",
        "review_status": "Exact table rows checked; age55/no-work profile in B3b remains separate and requires linked ruling review."
      },
      "duplicate-benefit-application/digestive-skin-2023-listing-change-review": {
        "id": "digestive-skin-2023-listing-change-review",
        "title": "Digestive or skin criteria changed after the earlier denial",
        "when": "A later Title II disability claim involves a digestive disorder, or a skin disorder other than Xeroderma Pigmentosum, and the earlier denial predates October 6, 2023.",
        "you": "Identify the earlier decision and the condition being evaluated; provide requested medical evidence.",
        "ssa": "DDS compares the earlier decision date and impairment with the listing-change table. For these specified rows, staff prepare a new substantive determination rather than denying the later claim on res judicata grounds. The skin row expressly excludes Xeroderma Pigmentosum; that exclusion does not by itself decide whether other exceptions apply.",
        "route": "Field-office exception handoff → DDS impairment/date comparison → new substantive determination where this condition applies.",
        "next": "Ask whether the relevant listing-change row applies. New medical adjudication does not automatically establish disability or reopen the earlier decision.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C opening; Digestive Disorders and Skin Disorders rows",
        "timing": "October 6, 2023 is the comparison date for these rows, not a processing deadline.",
        "review_status": "Official rows and skin exclusion checked; other impairment rows require their own dates and conditions."
      },
      "duplicate-benefit-application/sensory-respiratory-listing-change-prior-denial": {
        "id": "sensory-respiratory-listing-change-prior-denial",
        "title": "Hearing, vision or respiratory criteria changed after the denial",
        "when": "A later Title II disability claim involves hearing loss, vision or a respiratory impairment and an earlier denial predates the corresponding listing change.",
        "you": "Identify the prior decision and relevant condition; provide requested evidence.",
        "ssa": "DDS checks the impairment-specific date: hearing loss, August 2, 2010; vision, April 29, 2013; respiratory impairment, October 7, 2016. If the earlier denial predates the applicable date, staff prepare a new substantive determination under the table rather than applying res judicata to deny the later claim.",
        "route": "Field-office exception handoff → DDS listing-date comparison → substantive medical determination.",
        "next": "Ask which row and prior decision date apply. The new determination can still be favorable or unfavorable on the evidence.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Special Senses and Speech; Respiratory Disorders rows",
        "timing": "The dates select the listing-change exception; no completion duration is supplied.",
        "review_status": "Exact three dates checked. Musculoskeletal exclusion wording has a separately recorded unresolved conflict."
      },
      "duplicate-benefit-application/cardiovascular-hematological-listing-change-review": {
        "id": "cardiovascular-hematological-listing-change-review",
        "title": "Heart, vascular or blood-disorder criteria changed after the denial",
        "when": "A later Title II disability claim involves a cardiovascular or hematological disorder with an earlier denial before the applicable listing-change date.",
        "you": "Identify the earlier decision and condition; supply requested medical evidence.",
        "ssa": "DDS compares the exact impairment and prior denial date with the current table: all cardiovascular disorders, October 30, 2026; all hematological disorders, May 18, 2015. If the prior claim was denied before the applicable row date, DDS prepares a new substantive determination instead of denying the subsequent claim on res judicata grounds, subject to the source’s Title II subsequent-claim scope. A new determination does not itself establish disability, entitlement or reopening.",
        "route": "Field-office exception handoff → DDS impairment/date comparison → substantive determination.",
        "next": "Ask which impairment-specific row applies and review the resulting determination. The changed criteria do not themselves establish entitlement.",
        "source": "r24_resjudicata_cv_hematology",
        "section": "Current C Cardiovascular System row (10/30/2026) and Hematological Disorders row (05/18/2015), with A Title II subsequent-claim scope",
        "timing": "These are listing-change comparison dates, not processing deadlines.",
        "review_status": "Selected current A scope and C cardiovascular/hematological rows compared against the whole DI27516.010 captured October31,2026, revisionOctober29,2026/TN27. The current all-cardiovascular row uses October30,2026; hematological row uses May18,2015. Earlier1994/2006 wording and itsOctober17check are preserved in the historical record. Selected public-guidance review does not determine eligibility, reopening, payment or current system operation.",
        "source_revision_history": {
          "schema": "securitystat.versioned-source-repair-history/1",
          "prior_source_id": "disabilitypreclusionpolicychanges",
          "prior_record": {
            "id": "cardiovascular-hematological-listing-change-review",
            "title": "Heart, vascular or blood-disorder criteria changed after the denial",
            "when": "A later Title II disability claim involves a cardiovascular or hematological disorder with an earlier denial before the applicable listing-change date.",
            "you": "Identify the earlier decision and condition; supply requested medical evidence.",
            "ssa": "DDS compares the exact impairment and denial date: all cardiovascular disorders, February 10, 1994; chronic heart failure, ischemic heart disease or peripheral arterial disease, April 13, 2006; all hematological disorders, May 18, 2015. If the earlier denial predates the applicable row date, DDS prepares a new substantive determination instead of denying the later claim on res judicata grounds.",
            "route": "Field-office exception handoff → DDS impairment/date comparison → substantive determination.",
            "next": "Ask which impairment-specific row applies and review the resulting determination. The changed criteria do not themselves establish entitlement.",
            "source": "disabilitypreclusionpolicychanges",
            "section": "C Cardiovascular System and Hematological Disorders rows",
            "timing": "These are listing-change comparison dates, not processing deadlines.",
            "review_status": "Three official date/scope conditions checked; reopening and benefit-payment effects remain separate."
          },
          "reason": "Current published table has an all-cardiovascular October30/2026 row; retain earlier1994/selected2006 wording as historical, not current. HematologicalMay18/2015 remains supported.",
          "current_scope": "Only current A TitleII/subsequent-claim scope plus C cardiovascular and hematological rows; not entire resjudicata workflow or whole-page acceptance."
        }
      },
      "duplicate-benefit-application/neurological-mental-adult-down-listing-change": {
        "id": "neurological-mental-adult-down-listing-change",
        "title": "Neurological, mental or adult Down syndrome criteria changed",
        "when": "The later Title II disability claim involves one of these listing-table conditions and an earlier denial predates its specified change.",
        "you": "Identify the earlier decision and condition; provide requested records.",
        "ssa": "DDS checks the relevant row and date: non-mosaic Down syndrome in an individual age 18 or older, June 19, 2000; ALS, August 28, 2003; other neurological disorders, September 29, 2016; mental disorders, January 17, 2017. If the earlier denial predates the applicable change, DDS prepares a new substantive determination rather than denying the later claim on res judicata grounds.",
        "route": "Field-office exception handoff → DDS impairment, age-scope and date comparison → substantive determination.",
        "next": "Ask which row applies and review the resulting decision. This route does not independently establish onset, eligibility or payment.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Congenital, Neurological and Mental Disorders rows",
        "timing": "The dates select the listing-change exception; no processing duration is specified.",
        "review_status": "Four row conditions checked, including adult non-mosaic scope and separate ALS date. Current medical eligibility remains an individual determination."
      },
      "duplicate-benefit-application/immune-subgroup-listing-change-prior-denial": {
        "id": "immune-subgroup-listing-change-prior-denial",
        "title": "Immune-disorder criteria changed after the earlier denial",
        "when": "A later Title II disability claim involves an immune-system disorder and the prior denial predates the applicable subgroup change.",
        "you": "Identify the prior decision and condition; supply requested medical evidence.",
        "ssa": "DDS distinguishes the table subgroups: June 16, 2008 for immune disorders other than HIV infection, systemic sclerosis, polymyositis, dermatomyositis and inflammatory arthritis; January 17, 2017 for symptomatic HIV infection; April 2, 2021 for systemic sclerosis, polymyositis, dermatomyositis and inflammatory arthritis. If the prior denial predates the applicable change, DDS prepares a new substantive determination rather than applying res judicata to deny the later claim.",
        "route": "Field-office exception handoff → DDS exact impairment/date comparison → substantive determination.",
        "next": "Ask which subgroup applies and review the resulting decision. A changed listing does not by itself establish benefit entitlement.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Immune System Disorders rows and action paragraphs",
        "timing": "These are subgroup comparison dates, not processing deadlines.",
        "review_status": "Official subgroup exclusions and symptomatic-HIV qualifier checked. No clinical diagnosis or individual eligibility conclusion is made."
      },
      "duplicate-benefit-application/cancer2009-subgroup-listing-change": {
        "id": "cancer2009-subgroup-listing-change",
        "title": "A specified cancer subgroup has an older denial before November 2009",
        "when": "A later Title II claim involves malignant neoplastic disease of the skin, thyroid gland, breast, lungs or female genital tract, with an earlier denial before November 5, 2009.",
        "you": "Identify the earlier decision and condition; provide requested evidence.",
        "ssa": "DDS compares the prior decision date and exact cancer subgroup with the November 2009 listing-change row. For the listed conditions with a denial before that date, DDS prepares a new substantive determination instead of denying the later claim on res judicata grounds.",
        "route": "Field-office exception handoff → DDS cancer-subgroup/date comparison → substantive determination.",
        "next": "Ask whether the listed subgroup and date apply; review the resulting decision. This is not an automatic allowance or reopening of the prior claim.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Cancer row dated November 5, 2009",
        "timing": "The date selects this row; no processing duration is specified.",
        "review_status": "Official five cancer subgroups checked. Other cancer dates and conflicting gallbladder/bile-duct wording require separate disposition."
      },
      "duplicate-benefit-application/cancer2004-subgroup-listing-change": {
        "id": "cancer2004-subgroup-listing-change",
        "title": "A specified cancer subgroup has a denial before December 2004",
        "when": "A later Title II disability claim involves a condition in the December 15, 2004 cancer row and the prior denial predates that date.",
        "you": "Identify the earlier decision and condition; provide requested evidence.",
        "ssa": "DDS checks the row covering malignant neoplastic disease of soft tissue of the head and neck, skin, breast, skeletal system, lungs, small intestine, kidneys/adrenals/ureters or female genital tract; malignancy treated by bone marrow or stem cell transplantation; leukemia; multiple myeloma; or unknown primary site after appropriate search. For that scope and earlier date, DDS prepares a new substantive determination instead of applying res judicata to deny the later claim.",
        "route": "Field-office exception handoff → DDS exact cancer-row/date comparison → substantive determination.",
        "next": "Ask whether the exact condition meets this row and review the new decision. The route does not automatically establish entitlement.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Cancer row dated December 15, 2004",
        "timing": "December 15, 2004 is the comparison date, not a decision deadline.",
        "review_status": "Official subgroup list checked; other cancer rows remain separately scoped."
      },
      "duplicate-benefit-application/cancer2015-listing-scope-change": {
        "id": "cancer2015-listing-scope-change",
        "title": "The earlier cancer denial predates the July 2015 listing changes",
        "when": "A later Title II claim involves a cancer listing specified in the July 20, 2015 table row and the earlier denial predates that date.",
        "you": "Identify the prior decision and condition; provide requested medical evidence.",
        "ssa": "DDS checks the row’s listing scope: 13.02, 13.03, 13.05, 13.06, 13.10, 13.12, 13.13, 13.15, 13.16, 13.17, 13.18, 13.20, 13.22, 13.23, 13.24 and 13.29. For the specified conditions and earlier date, DDS prepares a new substantive determination rather than denying the later claim on res judicata grounds.",
        "route": "Field-office exception handoff → DDS exact listing/date comparison → substantive determination.",
        "next": "Ask whether the condition falls within the listed scope; review the new determination. This does not automatically establish disability or reopen the earlier claim.",
        "source": "disabilitypreclusionpolicychanges",
        "section": "C Cancer row dated July 20, 2015",
        "timing": "July 20, 2015 is the comparison date; no processing duration is supplied.",
        "review_status": "Exact sixteen identifiers checked against the official row; current medical criteria and historical numbering require individual staff review."
      }
    },
    "flows": {
      "childhood-disability-intake/cdb-prior-denial-age22-reentitlement-review": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdb-prior-denial-age22-reentitlement-review",
        "full_route": "childhood-disability-intake/cdb-prior-denial-age22-reentitlement-review",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "DDS is evaluating the actual dates and basis of a prior G1 or G2 CDB vocational denial; the code alone does not establish a res judicata issue."
        ],
        "steps": [
          {
            "id": "cdb-prior-denial-age22-reentitlement-review-review-step-1",
            "title": "Check the actual denial and period dates",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Determine whether the prior denial was after the date non-disability requirements were last met; G1 alone does not show whether the denial was after age22.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "DDS is evaluating the actual dates and basis of a prior G1 or G2 CDB vocational denial; the code alone does not establish a res judicata issue."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; B.1",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "cdb-prior-denial-age22-reentitlement-review-review-step-2",
            "title": "If the prior CDB denial was not after age22",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Process the subsequent filing as a standard CDB claim. This is a processing instruction, not a finding of entitlement.",
            "conditions": [
              "The earlier CDB claim was NOT denied after age22."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.1 CDB paragraphs",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "CDB-date-situations"
          },
          {
            "id": "cdb-prior-denial-age22-reentitlement-review-review-step-3",
            "title": "If the G1 reentitlement period was last met on or after the prior decision",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Process the subsequent filing as a standard CDB reentitlement claim.",
            "conditions": [
              "The prior G1 denial concerned reentitlement AND its reentitlement period was last met on or after the prior determination or decision date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.1 CDB paragraphs",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "CDB-date-situations"
          },
          {
            "id": "cdb-prior-denial-age22-reentitlement-review-review-step-4",
            "title": "If G2 indicates a prior denial after the reentitlement period",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Treat the code/date situation as a potential res judicata issue requiring the applicable review; it is not an automatic denial.",
            "conditions": [
              "The G2 denial was after the end of the reentitlement period."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.1 CDB paragraphs",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "CDB-date-situations"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "CDB-date-situations",
            "label": "Use the actual source-defined CDB date situation",
            "logic": "source_conditions_determine_branch",
            "note": "These source situations are conditional alternatives, not a sequence of decisions or a rule for resolving unknown or overlapping facts."
          }
        ]
      },
      "duplicate-benefit-application/prior-disability-past-work-policy-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "prior-disability-past-work-policy-change",
        "full_route": "duplicate-benefit-application/prior-disability-past-work-policy-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "The prior claim was denied after non-disability requirements were last met and before June22,2024, and the B.1 benefit/code and actual prior-past-work basis apply."
        ],
        "steps": [
          {
            "id": "prior-disability-past-work-policy-change-review-step-1",
            "title": "Forward the source-qualified prior-denial case",
            "kind": "ssa",
            "actor": "FO",
            "action": "Forward the applicable case to DDS and add the CEF message: “DDS jurisdiction: potential denial on basis of res judicata. DDS review necessary.” This alerts staff to potential review, not a determination.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "The prior claim was denied after non-disability requirements were last met and before June22,2024, and the B.1 benefit/code and actual prior-past-work basis apply."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B opening; B.1",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "prior-disability-past-work-policy-change-review-step-2",
            "title": "Review the prior file and actual work",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Review the prior claim documentation and identify the relied-on past work and its relevant period/duration. Use the applicable DIB/DWB H2 or CDB G1/G2 past-work scope.",
            "conditions": [
              "The applicable source-qualified claim was forwarded for past-work review."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.1-B.2",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "prior-disability-past-work-policy-change-review-step-3",
            "title": "If either less-restrictive past-work condition applies",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Make a new substantive determination if the prior denial relied on work before the applicable five-year relevant period OR work that began and ended in fewer than30calendar days.",
            "conditions": [
              "The relied-on work was before the applicable five-year period OR began and ended in fewer than30calendar days."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.2",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "past-work-conditions"
          },
          {
            "id": "prior-disability-past-work-policy-change-review-step-4",
            "title": "If the work remains within the period and spans at least30days",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Res judicata may be a basis for denial only if work was within the relevant five-year period, spanned at least30calendar days AND all usual requirements are satisfied. This illustration supplies no such case finding.",
            "conditions": [
              "Within the relevant five-year period AND spanning at least30calendar days AND the usual res judicata conditions are satisfied."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.2",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "past-work-conditions"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "past-work-conditions",
            "label": "Different prior-work findings",
            "logic": "source_conditions_determine_branch",
            "note": "Source-conditioned alternatives; unknown dates or usual requirements establish neither a denial nor a new allowance."
          }
        ]
      },
      "duplicate-benefit-application/prior-other-work-experience-category-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "prior-other-work-experience-category-change",
        "full_route": "duplicate-benefit-application/prior-other-work-experience-category-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "DDS reviews an applicable earlier Title II disability denial based on ability to adjust to other work."
        ],
        "steps": [
          {
            "id": "prior-other-work-experience-category-change-review-step-1",
            "title": "Compare all three table dimensions",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Review the actual prior other-work denial, prior vocational rule and work-experience category under current rules. Preserve the applicable B.1/B.3 benefit, code and denial-basis conditions.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "DDS reviews an applicable earlier Title II disability denial based on ability to adjust to other work."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.1; B.3 opening",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "prior-other-work-experience-category-change-review-step-2",
            "title": "If the transferable-work table row fits",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Res judicata does not apply when prior skilled/semiskilled transferable work AND prior rule201.03/201.07/201.11/201.15/202.03/202.07 AND current nontransferable skilled/semiskilled, unskilled or no-work category all match.",
            "conditions": [
              "All three dimensions of the stated B.3.a transferable-work row match."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.3.a first table row",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "other-work-table-rows"
          },
          {
            "id": "prior-other-work-experience-category-change-review-step-3",
            "title": "If the prior-unskilled table row fits",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Res judicata does not apply when prior unskilled work AND prior rule203.03/203.11 AND current no-work category all match.",
            "conditions": [
              "All three dimensions of the stated B.3.a unskilled-work row match."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "B.3.a second table row",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ],
            "alternative_group": "other-work-table-rows"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "other-work-table-rows",
            "label": "Separate conjunctive table rows",
            "logic": "source_conditions_determine_branch",
            "note": "Do not merge the rows or infer a residual denial where they do not match. B.3.b’s age55/limited-education/no-PRW profile and linked ruling need their own applicable review."
          }
        ]
      },
      "duplicate-benefit-application/digestive-skin-2023-listing-change-review": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "digestive-skin-2023-listing-change-review",
        "full_route": "duplicate-benefit-application/digestive-skin-2023-listing-change-review",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II disability claim involves a digestive disorder, or a skin disorder other than Xeroderma Pigmentosum, and the earlier denial predates October 6, 2023."
        ],
        "steps": [
          {
            "id": "digestive-skin-2023-listing-change-review-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Digestive disorders: October6,2023. Skin disorders other than Xeroderma Pigmentosum: October6,2023. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II disability claim involves a digestive disorder, or a skin disorder other than Xeroderma Pigmentosum, and the earlier denial predates October 6, 2023."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C opening; Digestive Disorders and Skin Disorders rows",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "digestive-skin-2023-listing-change-review-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/sensory-respiratory-listing-change-prior-denial": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "sensory-respiratory-listing-change-prior-denial",
        "full_route": "duplicate-benefit-application/sensory-respiratory-listing-change-prior-denial",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II disability claim involves hearing loss, vision or a respiratory impairment and an earlier denial predates the corresponding listing change."
        ],
        "steps": [
          {
            "id": "sensory-respiratory-listing-change-prior-denial-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Hearing loss: August2,2010; vision: April29,2013; respiratory impairment: October7,2016. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II disability claim involves hearing loss, vision or a respiratory impairment and an earlier denial predates the corresponding listing change."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Special Senses and Speech; Respiratory Disorders rows",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "sensory-respiratory-listing-change-prior-denial-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/cardiovascular-hematological-listing-change-review": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cardiovascular-hematological-listing-change-review",
        "full_route": "duplicate-benefit-application/cardiovascular-hematological-listing-change-review",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II disability claim involves a cardiovascular or hematological disorder with an earlier denial before the applicable listing-change date."
        ],
        "steps": [
          {
            "id": "cardiovascular-hematological-listing-change-review-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "All cardiovascular disorders: October30,2026. All hematological disorders: May18,2015. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II disability claim involves a cardiovascular or hematological disorder with an earlier denial before the applicable listing-change date."
            ],
            "source": "r24_resjudicata_cv_hematology",
            "section": "A; Current C Cardiovascular System row (10/30/2026) and Hematological Disorders row (05/18/2015), with A Title II subsequent-claim scope",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "cardiovascular-hematological-listing-change-review-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "r24_resjudicata_cv_hematology",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/neurological-mental-adult-down-listing-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "neurological-mental-adult-down-listing-change",
        "full_route": "duplicate-benefit-application/neurological-mental-adult-down-listing-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "The later Title II disability claim involves one of these listing-table conditions and an earlier denial predates its specified change."
        ],
        "steps": [
          {
            "id": "neurological-mental-adult-down-listing-change-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Non-mosaic Down syndrome in an individual age18orolder: June19,2000; ALS: August28,2003; neurological disorders other than ALS: September29,2016; mental disorders: January17,2017. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "The later Title II disability claim involves one of these listing-table conditions and an earlier denial predates its specified change."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Congenital, Neurological and Mental Disorders rows",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "neurological-mental-adult-down-listing-change-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/immune-subgroup-listing-change-prior-denial": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "immune-subgroup-listing-change-prior-denial",
        "full_route": "duplicate-benefit-application/immune-subgroup-listing-change-prior-denial",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II disability claim involves an immune-system disorder and the prior denial predates the applicable subgroup change."
        ],
        "steps": [
          {
            "id": "immune-subgroup-listing-change-prior-denial-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Immune disorders other than HIV infection/systemic sclerosis/polymyositis/dermatomyositis/inflammatory arthritis: June16,2008; symptomatic HIV infection: January17,2017; systemic sclerosis/polymyositis/dermatomyositis/inflammatory arthritis: April2,2021. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II disability claim involves an immune-system disorder and the prior denial predates the applicable subgroup change."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Immune System Disorders rows and action paragraphs",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "immune-subgroup-listing-change-prior-denial-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/cancer2009-subgroup-listing-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cancer2009-subgroup-listing-change",
        "full_route": "duplicate-benefit-application/cancer2009-subgroup-listing-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II claim involves malignant neoplastic disease of the skin, thyroid gland, breast, lungs or female genital tract, with an earlier denial before November 5, 2009."
        ],
        "steps": [
          {
            "id": "cancer2009-subgroup-listing-change-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Skin, thyroid gland, breast, lungs or female-genital-tract malignant neoplastic disease: November5,2009. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II claim involves malignant neoplastic disease of the skin, thyroid gland, breast, lungs or female genital tract, with an earlier denial before November 5, 2009."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Cancer row dated November 5, 2009",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "cancer2009-subgroup-listing-change-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/cancer2004-subgroup-listing-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cancer2004-subgroup-listing-change",
        "full_route": "duplicate-benefit-application/cancer2004-subgroup-listing-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II disability claim involves a condition in the December 15, 2004 cancer row and the prior denial predates that date."
        ],
        "steps": [
          {
            "id": "cancer2004-subgroup-listing-change-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "The exact listed December15,2004 subgroup: soft tissue of head/neck, skin, breast, skeletal system, lungs, small intestine, kidneys/adrenals/ureters, female genital tract; bone-marrow/stem-cell-transplantation treated disease; leukemia; multiple myeloma; primary site unknown after appropriate search. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II disability claim involves a condition in the December 15, 2004 cancer row and the prior denial predates that date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Cancer row dated December 15, 2004",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "cancer2004-subgroup-listing-change-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      },
      "duplicate-benefit-application/cancer2015-listing-scope-change": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cancer2015-listing-scope-change",
        "full_route": "duplicate-benefit-application/cancer2015-listing-scope-change",
        "entry_conditions": [
          "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
          "A later Title II claim involves a cancer listing specified in the July 20, 2015 table row and the earlier denial predates that date."
        ],
        "steps": [
          {
            "id": "cancer2015-listing-scope-change-review-step-1",
            "title": "Compare the exact impairment scope and date",
            "kind": "ssa",
            "actor": "DDS",
            "action": "The July20,2015 row’s exact listing identifiers:13.02,13.03,13.05,13.06,13.10,13.12,13.13,13.15,13.16,13.17,13.18,13.20,13.22,13.23,13.24,13.29. Compare the prior determination or decision with the applicable source row; do not substitute an unreviewed clinical diagnosis or a different row.",
            "conditions": [
              "The later Title II claim is being reviewed within the selected source’s res judicata scope; actual prior-decision and non-disability-requirement facts are for staff to establish, not inferred by selecting this example.",
              "A later Title II claim involves a cancer listing specified in the July 20, 2015 table row and the earlier denial predates that date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "A; C Cancer row dated July 20, 2015",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          },
          {
            "id": "cancer2015-listing-scope-change-review-step-2",
            "title": "When the earlier denial predates the applicable row",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare a new substantive determination for the subsequent claim within that row’s exact scope instead of denying it on res judicata grounds. The new determination may be favorable or unfavorable and does not itself reopen the earlier claim.",
            "conditions": [
              "The actual impairment/listing matches the specified row AND the prior denial was BEFORE its applicable change date."
            ],
            "source": "disabilitypreclusionpolicychanges",
            "section": "C applicable row; A",
            "source_context_refs": [
              "DI27516.010-whole"
            ],
            "qualifications": [
              "This is a published staff review instruction, not an actual impairment, age, vocational, disability, entitlement, reopening or payment finding.",
              "The prior decision, relevant dates and all applicable source conditions must be established in the real case. New substantive determination does not mean allowance.",
              "Linked DI27516.001/DI27516.005 and cited rulings retain separately unreviewed details; this mapping supplies no automatic denial, reopening, system execution or completion time."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual staff review, determination and completed return to any prior path are not established."
          ]
        }
      }
    },
    "source_contexts": [
      {
        "id": "DI27516.010-whole",
        "source_code": "DI27516.010",
        "locator": "Whole actual main A-C plus header/footer",
        "start": 0,
        "end": 19186,
        "exact_text": "Effective Dates: 10/29/2026 - Present\nPrevious | Next\n\nTN 27 (10-26)\n\nDI 27516.010 The Principle of Res Judicata and Changes in Policy\nA. \nRes judicata basic policy\n\nFor a definition of res judicata see DI 27516.001A.\n\nIf res judicata applies to a subsequent filing, to deny the claim without making a substantive determination the Disability Determination Services (DDS) will follow the procedures in DI 27516.005E.\n\nIf any of the exceptions to res judicata apply, the DDS will make a new substantive determination; if a denial is appropriate follow the procedures in DI 27516.005.C.1. and if a favorable determination is appropriate follow DI 27516.005.C.2.\n\nBecause there are no potential denials after non-disability requirements for entitlement were last met for a Title XVI claim, res judicata policy will only apply to Title II claims as outlined in these instructions\n\n•\n\nDI 27516.001 Field Office Res Judicata Development and Processing\n\n•\n\nDI 27516.005 Disability Determination Services Res Judicata Development and Processing\n\n•\n\nDI 27516.010 The Principle of Res Judicata and Changes in Policy\n\nBefore applying res judicata to a subsequent Title II disability claim, consider whether:\n\n•\n\nAn exception applies to res judicata listed in DI 27516.001B,\n\nOR\n\n•\n\nThe claimant alleges new and material evidence, and the DDS must develop or review that evidence to determine whether res judicata applies, see DI 27516.005B,\n\nOR\n\n•\n\nThe FO cannot locate the prior folder for the denial after the date the non-disability requirements for entitlement were last met, see DI 27516.005C,\n\nOR\n\n•\n\nSince the denial after the date the non-disability requirements for entitlement were last met, there has been a change in policy that makes the requirements for establishing disability less restrictive (as outlined in this section).\n\nB. \nWork relevancy changes in policy\n\nOn June 22, 2024, we implemented rules that provide a new and less restrictive definition of PRW; see 89 FR 27653 ; 20 CFR 404.1560(b)(1) and Social Security Ruling (SSR) 24-2p.\n\nThe new PRW definition is less restrictive than the prior PRW definition in two ways:\n\n•\n\nThe relevant period considers 5 years rather than 15 years of past work, and\n\n•\n\nWork that started and stopped in fewer than 30 calendar days is not PRW.\n\nThe FO will forward claims denied after the date non-disability requirements were last met and before 6/22/2024, the effective date of the less restrictive policy.\n\nThe FO will alert the DDS to potential res judicata determinations by adding the following message to the certified electronic folder (CEF):\n\nDDS jurisdiction: potential denial on basis of res judicata. DDS review necessary.\n\n1. \nRegulation basis codes for DDS consideration of res judicata\n\nThe FO will send cases that meet the following criteria to DDS for consideration of res judicata:\n\nDisability Insurance Benefits (DIB) and Disabled Widow(er)s Benefits (DWB) claims with regulation basis codes:\n\n•\n\nH2 Capacity for substantial gainful activity (SGA) - Any Relevant Past Work (earnings requirement (ER) or prescribed period (PP) last met prior to date of current decision)\n\nOR\n\nJ2 Capacity for SGA - Other Than Relevant Past Work (ER or PP last met prior to date of current decision)\n\nAnd Childhood Disability Beneficiary (CDB) claims with regulation basis codes:\n\n•\n\nG1 Capacity for SGA Vocational Considerations (CDB claim, or reentitlement CDB claim and reentitlement period (RP) last met on or after date of current decision)\n\nOR\n\nG2 Capacity for SGA - Vocational Considerations(Reentitlement CDB claim and RP last met prior to date of current decision\n\nSince the G1 regulation basis code for CDB claims does not provide information about whether the claim was denied after age 22, the DDS must determine whether the denial was made after the date non-disability requirements were last met for CDB cases.\n\nIf the CDB claim was not denied after age 22, there is no res judicata issue. The DDS will process a subsequent filing as a standard CDB claim.\n\nIf the G1 denial was based on a reentitlement claim and the reintitlement period was last met on or after the date of the prior determination or decision, there is no res judicata issue. The DDS will process the subsequent filing as a standard CDB reintitlement claim.\n\nA G2 regulation basis code reflects a denial after the end of the reentitlement period. G2 denials have a potential res judicata issue because the denial was made after the date the reintitlement non-disability requirements were last met.\n\n2. \nDDS procedures if prior determination or decision found the claimant could do PRW\n\nIf the prior DIB or DWB claim was denied with an RBC of H2, the agency determined the claimant could perform PRW.\n\nIf the prior CDB claim was denied with an RBC of G1 or G2 and the determination was based on the ability to do PRW, follow the instructions in this section.\n\nReview the documentation in the prior claim file. A new substantive determination is required if the prior determination or decision found:\n\n•\n\nThe claimant could perform PRW that was last performed before the 5-year relevant period reflected in the new regulatory definition (see SSR 24-2p, Question 2 describing the relevant period for claims with expired periods of entitlement),\n\nOR\n\n•\n\nThe claimant could perform PRW that began and ended in fewer than 30 calendar days.\n\nIf the claim was denied based on PRW within the relevant 5-year period and the PRW was performed for a period spanning at least 30 calendar days, then res judicata may be a basis for denial of the subsequent claim, provided that the usual requirements for applying res judicata are satisfied.\n\nFor instructions on how to process a denial with an RBC of S1 (res judicata), see DI 27516.005E.\n\n3. \nDDS procedures if prior determination or decision found the claimant could adjust to other work\n\nIf the prior claim was denied with an RBC of G2 or J2 , the agency determined the claimant could adjust to other work in the national economy. If the prior CDB claim was denied after the date disability requirements were last met with an RBC of G1 or G2 and the determination was based on ability to adjust to other work, follow the instructions in this section.\n\na. \n\nThe new definition of PRW produces a change in work experience category that could be material to the determination in the subsequent claim.\n\nRes judicata does not apply\n\nIF the prior determination or decision found the individuals work experience was:\n\n\t\n\nAND the prior claim was denied using (directed or as a framework) rule:\n\n\t\n\nAND the claimants work experience category under current rules is:\n\n\n\n\nSkilled or semiskilled, skills transferable\n\n\t\n\n201.03 201.07 201.11 201.15 202.03 202.07\n\n\t\n\nSkilled or semiskilled, skills not transferable\n\nOR\n\nUnskilled\n\nOR\n\nNone\n\n\n\n\nUnskilled\n\n\t\n\n203.03 203.11\n\n\t\n\nNone\n\nb. \n\nIn the prior claim the claimant had limited education, was age 55 or older and had work experience, but for the new claim, considering the current definition of PRW, they have no PRW.\n\nNOTE: Because the claimant has no PRW under current rules, they would meet the no work profile, see SSR 24-1p.\n\nIf the criteria in DI 27516.010B.3.a. do not apply, the new definition of PRW would not yield an outcome different from the prior determination or decision. In that case, res judicata may be a basis for denial of the subsequent claim, provided that the usual requirements for applying res judicata are satisfied.\n\nFor instructions on how to make a new determination if res judicata does not apply, see DI 27516.005C.\n\nC. \nChanges to the listing of impairments that affect the application of res judicata\n\nSubsequent claims involving the listings shown in the table should not be denied based on res judicata if the determination or decision on the prior claim was made before the date of the listing change.\n\nNOTE: If a listing for a particular impairment is not in the table, a less restrictive change was not made to the listing of impairments and a subsequent claim involving the impairment may be denied based on res judicata, absent new facts or issues.\n\nImpairments/Listings Involved\n\n\t\n\nDate of Change\n\n\t\n\nExplanation and Action\n\n\n\n\nMusculoskeletal Disorders (1.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll musculoskeletal disorders except amputation of both extremities at or above the wrists, hemipelvectomy, or hip disarticulation\n\n\t\n\n04/02/2021\n\n\t\n\nWe so extensively revised the musculoskeletal listings in 2021 that while they are not, in general, less restrictive than the prior listings, the issues are different and include the use of different functional criteria to indicate listing-level severity.\n\nIf the prior claim was denied before 04/02/2021, prepare a new determination for all subsequent claims involving a musculoskeletal impairment other than amputation of both upper extremities at or above the wrists, hemipelvectomy, or hip disarticulation.\n\n\n\n\nSpecial Senses and Speech (2.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll hearing impairments\n\n\t\n\n08/02/10\n\n\t\n\nWe revised the listings for hearing impairments by removing the requirement for testing with hearing aids and replacing listings 2.08 and 102.08 with new listings 2.10 and 102.10, respectively.\n\nIf the prior claim was denied before 08/02/10, prepare a new substantive determination for all subsequent claims involving hearing loss.\n\n\n\n\nVision\n\n\t\n\n04/29/13\n\n\t\n\nIf the prior claim was denied before 04/29/2013, prepare a new substantive determination for all subsequent claims involving vision.\n\n\n\n\nRespiratory Disorders (3.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll respiratory disorders\n\n\t\n\n10/07/16\n\n\t\n\nWe revised the listings for respiratory disorders. While the listings are not, in general, less restrictive, we added new criteria.\n\nIf the prior claim was denied before 10/07/16, prepare a new substantive determination for any subsequent claim involving a respiratory impairment.\n\n\n\n\nCardiovascular Disorders (4.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll cardiovascular disorders\n\n\t\n\n10/30/26\n\n\tWe revised the cardiovascular listings so extensively that, while they are not, in general, less restrictive, the issues are different and we added, removed, or significantly revised criteria throughout the listings.\n\nIf the prior claim was denied before 10/30/26, prepare a new substantive determination for all subsequent claims involving a cardiovascular impairment.\n\n\n\n\nDigestive Disorders (5.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll digestive disorders\n\n\t\n\n10/06/23\n\n\t\n\nWe so extensively revised the digestive disorders listings in 2023 that, while they are not, in general, less restrictive than the prior listings, we added new criteria or revised existing criteria to reflect technological improvements.\n\nIf the prior claim was denied before 10/06/23, prepare a new substantive determination for all subsequent claims involving any digestive disorder.\n\n\n\n\nHematological Disorders (7.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll hematological disorders\n\n\t\n\n05/18/15\n\n\t\n\nWe so extensively revised the hematological disorders listings in 2015 that, while they are not, in general, less restrictive than the prior listings, the issues are different and include the use of functional criteria to indicate listing-level severity.\n\nIf the prior claim was denied before 05/18/15, prepare a new determination for all subsequent claims involving a hematological disorder impairment.\n\n\n\n\nSkin Disorders (8.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll skin disorders except for Xeroderma Pigmentosum\n\n\t\n\n10/06/23\n\n\t\n\nWe so extensively revised the skin disorders listings in 2023 that, while they are not, in general, less restrictive than the prior listings, the issues are different and include the use of different functional criteria to indicate listing-level severity.\n\nIf the prior claim was denied before 10/06/23, prepare a new substantive determination for all subsequent claims involving skin disorders other than Xeroderma Pigmentosum.\n\n\n\n\nCongenital Disorders That Affect Multiple Body Systems (10.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nNon-mosaic Down syndrome in an individual age 18 or older\n\n\t\n\n6/19/00\n\n\t\n\nWe added listing 10.06 for non-mosaic Down syndrome.\n\nIf the prior claim was denied before 06/19/00, prepare a substantive determination for all subsequent claims involving an individual age 18 or older with non-mosaic Down syndrome.\n\n\n\n\nNeurological Disorders (11.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAmyotrophic lateral sclerosis (ALS)\n\n\t\n\n08/28/03\n\n\t\n\nWe revised the listing criteria for evaluating ALS under listing 11.10. We will find disability with medical evidence showing that the claimant has ALS.\n\nIf the prior claim was denied before 08/28/03, prepare a new substantive determination for all subsequent claims involving ALS.\n\n\n\n\nAll neurological disorders except for ALS\n\n\t\n\n09/29/16\n\n\t\n\nWe comprehensively revised the listings for evaluating neurological disorders. We added new listings, removed 3 listings and included new functional criteria for most listings.\n\nIf the prior claim was denied before 09/29/16, prepare a new substantive determination for all subsequent claims involving a neurological disorder other than ALS.\n\n\n\n\nMental Disorders (12.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nMental Disorders\n\n\t\n\n01/17/17\n\n\t\n\nWe extensively revised the mental disorders listings. While these listings are not, in general, less restrictive, we extensively revised the areas of mental functioning considered in the severity criteria.\n\nIf the prior claim was denied before 01/17/17, prepare a new substantive determination for all subsequent claims involving a mental disorder.\n\n\n\n\nCancer (13.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nMalignant neoplastic disease of the esophagus\n\n\t\n\n01/06/86\n\n\t\n\nWe revised the listing for evaluating tumors located in the lower half of the esophagus (13.16) to remove the requirement for metastatic disease.\n\nIf the prior claim was denied before 01/06/86, prepare substantive determination on subsequent claim involving a tumor located in the lower half of esophagus if the prior claim was denied before 01/06/86.\n\n\n\n\nMalignant neoplastic disease of the gallbladder\n\n\t\n\n01/06/86\n\n\t\n\nWe revised the criteria for evaluation of carcinoma of the bile ducts to require less extension of the tumors. This change is less restrictive.\n\nIf the prior claim was denied before 01/06/86, prepare a substantive determination on the subsequent claim involving carcinoma of the bile ducts if the prior claim was denied before 01/06/86.\n\n\n\n\nMalignant neoplastic disease of the penis\n\n\t\n\n01/06/86\n\n\t\n\nWe added new listings to provide standards for tumors of the penis and vulva. (The listing for tumors of the penis was 13.29 from 01/06/86 to 07/08/04. It was renumbered to 13.26 beginning 07/09/04.)\n\nIf the prior claim was denied before 01/06/86, prepare a substantive determination on the subsequent claim involving tumors of the penis.\n\n\n\n•\n\nMalignant neoplastic disease of: soft tissue of the head and neck; skin; breast; skeletal system; lungs; small intestine; kidneys, adrenals, or ureters; female genital tract\n\n•\n\nMalignant neoplastic disease treated by bone marrow or stem cell transplantation\n\n•\n\nLeukemia\n\n•\n\nMultiple myeloma\n\n•\n\nPrimary site unknown after appropriate search\n\n\t\n\n12/15/04\n\n\t\n\nWe revised the listings for these disorders (13.02C, 13.02E, 13.03A, 13.03B2, 13.06, 13.07, 13.10A, 13.11D, 13.14A, 13.17A, 13.21A, 13.23, 13.27, and 13.28). While these listings are not, in general, less restrictive, we added criteria to recognize the length and debilitating effects of treatment for some malignancies. We also:\n\n•\n\nadded criteria for other types of tumors that have a similar prognosis as those already in the listings;\n\n•\n\nrevised the criteria for multiple myeloma to clarify that this listing includes all listing-level manifestations of the disease; and\n\n•\n\nadded criteria for tumors for which the site of origin cannot be determined.\n\nIf the prior claim was denied before 12/15/04, prepare a new substantive determination for all subsequent claims involving these malignant neoplastic diseases.\n\n\n\n\nMalignant neoplastic diseases of: skin; thyroid gland; breast; lungs; female genital tract\n\n\t\n\n11/5/09\n\n\t\n\nWe have revised the listings for these disorders (13.03B, 13.09C, 13.10B, 13.14C, 13.23C). While these listings may not, in general, be less restrictive, we added criteria to recognize the length and debilitating effects of treatment for some malignancies. We also added criteria for evaluating malignant neoplastic diseases of the skin, thyroid gland, and breast.\n\nIf the prior claim was denied before 11/5/09, prepare a new substantive determination for all subsequent claims involving these malignant neoplastic diseases.\n\n\n\n\nCancer\n\n\t\n\n07/20/15\n\n\t\n\nWe revised the listings and added new listings for these disorders (13.02, 13.03, 13.05, 13.06, 13.10, 13.12, 13.13, 13.15, 13.16, 13.17, 13.18, 13.20, 13.22, 13.23, 13.24, 13.29). While these listings may not, in general, be less restrictive, we added criteria to recognize the unfavorable prognoses and length and debilitating effects of treatment for some malignancies.\n\nIf the prior claim was denied before07/20/15, prepare a new substantive determination for all subsequent claims involving these malignant neoplastic diseases.\n\n\n\n\nImmune System Disorders (14.00)\n\n\t\n\n \n\n\t\n\n \n\n\n\n\nAll immune system disorders except human immunodeficiency virus (HIV) infection, systemic sclerosis, polymyositis and dermatomysitis, and inflamatory arthritis\n\n\t\n\n06/16/08\n\n\t\n\nWe revised the listings for these disorders by either making them less restrictive or making major changes that result in the listing criteria being significantly different. For example, in some listings, we added functional criteria to indicate listing-level severity.\n\nIf the prior claim was denied before 06/16/08, prepare a new substantive determination for all subsequent claims involving these immune system disorders listings.\n\n\n\n\nHuman immunodeficiency virus (HIV) Infection\n\n \n\n \n\n \n\n \n\n \n\n \n\nSystemic sclerosis, polymyositis and dermatomyositis, and inflammatory arthritis\n\n\t\n\n01/17/17\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n04/02/2021\n\n\t\n\nWe revised the listing used to evaluate human immunodeficiency virus (HIV) infection. While the new listing is not, in general, less restrictive, we have made a number of significant changes. We have removed many criteria and added new criteria to reflect medical advances and changes in expected outcomes for individuals with HIV infection.\n\nIf the prior claim was denied before 01/17/17, prepare a substantive determination for all subsequent claims involving symptomatic HIV infection.\n\nWe replaced the musculoskeletal functional criteria used to indicate listing-level severity in these listings. While they are not, in general,less restrictive, the issues are different.\n\nIf the prior claim was denied before 04/02/21, prepare a new determination for all subsequent claims involving systemic sclerosis, polymyositis and dermatomyositis, and inflammatory arthritis\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0427516010\n\t\nDI 27516.010 - The Principle of Res Judicata and Changes in Policy - 10/29/2026\nBatch run: 10/29/2026\nRev:10/29/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "bf047d945e39e51d787bd77ecc6fb98ff37681ffdc668085d1c39b762b3eaacd"
      }
    ],
    "source_capture": {
      "metadata": {
        "links": [
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005",
            "text": "Previous"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427520000",
            "text": "Next"
          },
          {
            "href": "",
            "text": "DI 27516.010"
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516001#a",
            "text": "DI 27516.001A."
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005#e",
            "text": "DI 27516.005E."
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005",
            "text": "DI 27516.005"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005",
            "text": "DI 27516.005"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516001",
            "text": "DI 27516.001"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005",
            "text": "DI 27516.005"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516010",
            "text": "DI 27516.010"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516001#b",
            "text": "DI 27516.001B"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005#b",
            "text": "DI 27516.005B"
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005#c",
            "text": "DI 27516.005C"
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "https://www.federalregister.gov/documents/2024/04/18/2024-08150/intermediate-improvement-to-the-disability-adjudication-process-including-how-we-consider-past-work",
            "text": ""
          },
          {
            "href": "http://www.socialsecurity.gov/OP_Home/cfr20/404/404-1560.htm",
            "text": ""
          },
          {
            "href": "http://www.socialsecurity.gov/OP_Home/rulings//di/02/SSR2024-02-di-02.html",
            "text": ""
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005#e",
            "text": "DI 27516.005E."
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "http://www.socialsecurity.gov/OP_Home/rulings//di/02/SSR2024-01-di-02.html",
            "text": ""
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516010#b3a",
            "text": "DI 27516.010B.3.a."
          },
          {
            "href": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516005#c",
            "text": "DI 27516.005C."
          },
          {
            "href": "",
            "text": ""
          },
          {
            "href": "http://policy.ssa.gov/poms.nsf/lnx/0427516010",
            "text": "http://policy.ssa.gov/poms.nsf/lnx/0427516010"
          },
          {
            "href": "https://ssa.gov/accessibility/",
            "text": "Accessibility"
          },
          {
            "href": "https://ssa.gov/foia/",
            "text": "FOIA"
          },
          {
            "href": "https://ssa.gov/open/",
            "text": "Open Government"
          },
          {
            "href": "https://ssa.gov/agency/glossary/",
            "text": "Glossary"
          },
          {
            "href": "https://ssa.gov/agency/privacy.html",
            "text": "Privacy"
          },
          {
            "href": "http://oig.ssa.gov/report-fraud-waste-or-abuse",
            "text": "Report Fraud, Waste or Abuse"
          },
          {
            "href": "https://ssa.gov/sitemap.htm",
            "text": "Site Map"
          },
          {
            "href": "https://ssa.gov/agency/websitepolicies.html",
            "text": "Website Policies"
          },
          {
            "href": "http://www.govbenefits.gov/",
            "text": "Benefits.gov"
          },
          {
            "href": "https://www.disability.gov/",
            "text": "Disability.gov"
          },
          {
            "href": "https://www.healthcare.gov/",
            "text": "Healthcare.gov"
          },
          {
            "href": "http://mymoney.gov/",
            "text": "MyMoney.gov"
          },
          {
            "href": "https://regulations.gov/",
            "text": "Regulations.gov"
          },
          {
            "href": "https://www.usa.gov/",
            "text": "USA.gov"
          },
          {
            "href": "https://ssa.gov/agency/other-gov-websites.html",
            "text": "Other Government Sites"
          },
          {
            "href": "https://twitter.com/socialsecurity/",
            "text": "Twitter"
          },
          {
            "href": "https://facebook.com/socialsecurity/",
            "text": "Facebook"
          },
          {
            "href": "https://youtube.com/socialsecurityonline/",
            "text": "YouTube"
          },
          {
            "href": "https://blog.ssa.gov/",
            "text": "Blog"
          },
          {
            "href": "https://ssa.gov/socialmedia/",
            "text": "More Social Media"
          }
        ],
        "title": "SSA - POMS: DI 27516.010 - The Principle of Res Judicata and Changes in Policy - 10/29/2026",
        "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516010",
        "utc": "2026-10-31T19:09:50.917Z",
        "main_chars": 19186,
        "main_sha256": "bf047d945e39e51d787bd77ecc6fb98ff37681ffdc668085d1c39b762b3eaacd",
        "prior_recorded_source": {
          "title": "DI 27516.010 The Principle of Res Judicata and Changes in Policy",
          "url": "https://secure.ssa.gov/apps10/poms.nsf/lnx/0427516010",
          "revision": "2025-04-14",
          "kind": "POMS",
          "checked_on": "2026-10-17",
          "currency_note": "Official retrieval: revision/batch2025-04-14; TN26 (04-25). Specific Title II subsequent-claim context, not blanket reopening or SSI policy."
        },
        "affected_existing_routes": 11,
        "source_semantic_review": false
      },
      "snapshot_sha256": "81e33d1ca843f4d4c7cc2698618ad8d4ddaf5374ded188e461dffbcac14a16bf",
      "capture_type": "Actual Browser wholemain and DOM/accessibility snapshot, not rawHTTP"
    },
    "retained_holds": [
      "Musculoskeletal summary both-extremities versus action UPPER-extremities wording not resolved; no new musculoskeletal flow.",
      "Gallbladder row label versus bile-duct action wording not resolved; no new combined cancer identity.",
      "Linked DI27516.001/005, SSR24-2p period definitions and SSR24-1p no-work profile not fully supplied/reviewed here.",
      "Current table header/cardiovascular row differs from historical source; R24 versioned repair/history retained, not a publisher full-version redline."
    ],
    "projection_contract": "Append exact exception_flow to these11existingrecords only after independent approval; strip11flowfields reconstructs exact frozenR24data/workflow. No new route, sourceflag/native adoption or fabricated rejoin.",
    "prospective_only_counts": {
      "current_R24_mapped": 77,
      "current_R24_legacy": 987,
      "if_eleven_integrated_mapped": 88,
      "if_eleven_integrated_legacy": 976
    },
    "negative_QA": [
      "TitleXVI claim is not within these TitleII instructions.",
      "G1alone does not establish post-age22 denial.",
      "Reentitlementperiod on the decisiondate is not before it.",
      "Fewerthan30calendar days differs from exactly30.",
      "Work withinfiveyears also needs atleast30 andusualconditions beforepossibleRJdenial.",
      "Other-work table dimensions combinewithAND; currentcategories withinonecell useOR.",
      "No matchingB3table doesnotbyitself authorize denial;B3b/otherexceptions separate.",
      "Prior denial ON rowdate doesnotmeet BEFORE.",
      "Current cardiovascular10/30/2026 not retainedhistorical1994/2006.",
      "XerodermaPigmentosum notinselectedskinrow.",
      "NeurologicalnonALSrow doesnotreplaceALScalendar.",
      "AdultnonmosaicDown row doesnotbroaden toallchildhoodDownclaims.",
      "Immune subgroup exclusions/dates and symptomaticHIVqualification retained.",
      "Newdetermination notautomaticallowance/reopening/payment.",
      "PotentialCEFdenialmessage not actualdenial or systemtelemetry.",
      "Heldmusculoskeletal/gallbladderwording not resolved."
    ],
    "no_live_or_frozen_candidate_changes": true,
    "independent_source_review_sha256": "6785862f159f2131d6e4a63dd7108be019f53fdabc57b978da4c703faa849b73",
    "capture_links": {
      "main": "/service/sources/DI27516.010-r24-main.txt",
      "snapshot": "/service/sources/DI27516.010-r24-DOM-snapshot.txt",
      "metadata": "/service/sources/DI27516.010-r24-metadata.json"
    },
    "source_history_qualification": "Selected current captured instruction revision2026-10-29/TN27 reviewedOctober31; earlier source objects/checks remain unchanged historical metadata. Currentcardiovascularversionedrepair/history fromR24 remainsseparate andexact. No publisherfullversionredline, wholepagepolicyacceptance or outcome."
  },
  "r26_existing_GN15_SI17": {
    "schema": "securitystat.selected-existing-route-sequence-ledger/1",
    "status": "SELECTED_32_SOURCE_PROPOSALS_INDEPENDENTLY_REVIEWED_INTEGRATION_CANDIDATE",
    "checked_on": "2026-10-31",
    "flows": {
      "replace-tax-form/ssa1099-unauthorized-enr-payment-correction": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssa1099-unauthorized-enr-payment-correction",
        "full_route": "replace-tax-form/ssa1099-unauthorized-enr-payment-correction",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR)."
        ],
        "steps": [
          {
            "id": "ssa1099-unauthorized-enr-payment-correction-source-step-1",
            "title": "Handle the alleged incorrect statement",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For the specified allegation of inflated SSA-1099 amounts caused by nonreceipt from alleged fraud, issue a corrected benefit statement. This does not decide tax liability or reimbursement.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR)."
            ],
            "source": "redirectreimbursement020run72",
            "section": "I.1; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "ssa1099-unauthorized-enr-payment-correction-source-step-2",
            "title": "Send a manual-statement request to the processing center",
            "kind": "ssa",
            "actor": "FO",
            "action": "For a manual SSA-1099 request, contact the PC through MDW or RQFA. These source-named routes do not establish a particular MDW application identity.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR)."
            ],
            "source": "redirectreimbursement020run72",
            "section": "I NOTE",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "ssa1099-unauthorized-enr-payment-correction-source-step-3",
            "title": "When no payments were received in that tax year",
            "kind": "ssa",
            "actor": "PC",
            "action": "Prepare a manual SSA-1099 with $0.00 in all boxes when the beneficiary received no payments in the related tax year. Detailed SM00630.070 processing is linked and is not supplied or newly reviewed by this page.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR).",
              "The beneficiary received NO payments during the related tax year."
            ],
            "source": "redirectreimbursement020run72",
            "section": "I.2",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "ssa1099-unauthorized-enr-payment-correction-source-step-4",
            "title": "When actual cash benefits must be reflected",
            "kind": "ssa",
            "actor": "PC",
            "action": "When the real beneficiary filed for cash benefits during that tax year, reflect the amount actually received. Do not zero benefits that were actually received.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR).",
              "The real beneficiary filed for cash benefits during the related tax year."
            ],
            "source": "redirectreimbursement020run72",
            "section": "I.3",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-claim-form-help": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-claim-form-help",
        "full_route": "missing-direct-deposit/redirected-eft-claim-form-help",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
          "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
        ],
        "steps": [
          {
            "id": "redirected-eft-claim-form-help-source-step-1",
            "title": "Query the source-defined form channel",
            "kind": "ssa",
            "actor": "FO",
            "action": "For the nonreceipt claimant visiting the FO, query TCIS Integrated View. Direct Express does not use this TCIS EFT-form route; the source specifies a separate R16 request.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "Nonreceipt was filed AND the person visits the FO; this is not the Direct Express form route.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C opening; Direct Express paragraph",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-claim-form-help-source-step-2",
            "title": "Check any prior reprint before printing",
            "kind": "ssa",
            "actor": "FO",
            "action": "If TCIS shows a Reprint Date, verify the EF or NDRED before reprinting; staff may already have contacted the person and the form may be complete.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "TCIS shows a Reprint Date for the form.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C NOTE",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-claim-form-help-source-step-3",
            "title": "Print the applicable EFT claim form",
            "kind": "ssa",
            "actor": "FO",
            "action": "Print the EFT Claim Form from TCIS under the applicable non-Direct-Express and prior-reprint conditions.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C.1-C.2",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-claim-form-help-source-step-4",
            "title": "Complete the form",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "Complete the EFT Claim Form in its entirety.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C.3",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-claim-form-help-source-step-5",
            "title": "Mail the completed form",
            "kind": "ssa",
            "actor": "FO",
            "action": "Mail it to the address printed at the bottom of page1 of the EFT Claim Form; no specific address is supplied by this illustration.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C.4",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-claim-form-help-source-step-6",
            "title": "Retain the form copy",
            "kind": "ssa",
            "actor": "FO",
            "action": "Place a copy in EF or NDRED. The separate ClaimFormSent/IncompleteResent rows give their own30-day return instructions; do not turn those into a universal C processing deadline.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
              "The person has filed nonreceipt AND is visiting the FO for the C office-help procedure, AND this is not the separate Direct Express/R16 form route."
            ],
            "source": "redirectreimbursement020run72",
            "section": "C.5; D selected form stages",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-form-undeliverable-not-resent": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-form-undeliverable-not-resent",
        "full_route": "missing-direct-deposit/redirected-eft-form-undeliverable-not-resent",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form."
        ],
        "steps": [
          {
            "id": "redirected-eft-form-undeliverable-not-resent-source-step-1",
            "title": "Check the address and prior form",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Check whether the record address was recently updated and whether a prior reprint may already be retained. The exact NOT-resent status is separate from a Treasury resend.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-form-undeliverable-not-resent-source-step-2",
            "title": "If the address was recently updated",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Print from TCIS and send to the new address; when ReprintDate is shown, first verify that the form is not already in EF or NDRED.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form.",
              "The address was recently updated."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "address-state"
          },
          {
            "id": "redirected-eft-form-undeliverable-not-resent-source-step-3",
            "title": "If the address has not been updated",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Develop the current address under GN02605.055; its further unable-to-contact procedure remains a linked dependency. Do not invent an address or a completed update.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form.",
              "The address has NOT recently been updated."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "address-state"
          },
          {
            "id": "redirected-eft-form-undeliverable-not-resent-source-step-4",
            "title": "For a phone request",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Verify the record address. If correct, print and send. If incorrect with DDFP, follow GN02402.023; without DDFP, verify identity and change the address before printing and sending. The phone column says form receipt should be within10businessdays and return within30days; it does not supply a replacement-payment deadline.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form.",
              "The person is making a PHONE request; apply the actual correct/incorrect-address and DDFP facts."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "contact-method"
          },
          {
            "id": "redirected-eft-form-undeliverable-not-resent-source-step-5",
            "title": "For an office request",
            "kind": "ssa",
            "actor": "FO",
            "action": "Verify the record address, verify identity before a needed address change, print for completion and mail the form to its page1 destination. Do not infer phone-only delivery expectations as an office completion clock.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form.",
              "The person makes an IN-OFFICE request."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "contact-method"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "address-state",
            "label": "Address state",
            "logic": "source_conditions_determine_branch",
            "note": "These are different source-conditioned address situations; no actual update or identity verification is established."
          },
          {
            "id": "contact-method",
            "label": "Method-specific instructions",
            "logic": "source_conditions_determine_branch",
            "note": "Phone and in-office handling have different instructions. A UI channel choice does not establish which actual contact occurred."
          }
        ]
      },
      "missing-direct-deposit/redirected-eft-treasury-appeal-pending": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-treasury-appeal-pending",
        "full_route": "missing-direct-deposit/redirected-eft-treasury-appeal-pending",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process."
        ],
        "steps": [
          {
            "id": "redirected-eft-treasury-appeal-pending-source-step-1",
            "title": "Keep the pending Treasury appeal status",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Upload Treasury status to EF or NDRED. This is the claimant’s Treasury appeal after an original denial, not an FI protest.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-treasury-appeal-pending-source-step-2",
            "title": "Title II: apply the specified protest control",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Place the overpayment in protest status E only if a duplicate-payment overpayment exists AND SSA has begun recovery.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process.",
              "TitleII AND duplicate-payment overpayment exists AND recovery has begun."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "program-control"
          },
          {
            "id": "redirected-eft-treasury-appeal-pending-source-step-3",
            "title": "Title XVI: stop collection under the row",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Stop overpayment collection with NT TAC under the TitleXVI pending-appeal instruction.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process.",
              "TitleXVI pending-appeal context applies."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "program-control"
          },
          {
            "id": "redirected-eft-treasury-appeal-pending-source-step-4",
            "title": "Explain the pending stage",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain that no further debt-collection action is taken until Treasury determines the appeal. No appeal-decision deadline is supplied here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "program-control",
            "label": "Program-specific controls",
            "logic": "source_conditions_determine_branch",
            "note": "Use only the applicable program control with its prerequisites; these are not two universal input steps."
          }
        ]
      },
      "missing-direct-deposit/redirected-eft-denied-payee-received": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-denied-payee-received",
        "full_route": "missing-direct-deposit/redirected-eft-denied-payee-received",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "You returned the completed EFT Claim Form and Treasury reports Denied - Payee received payment in the specified unauthorized Automated Enrollment redirection process. This is not a denial for an incomplete form."
        ],
        "steps": [
          {
            "id": "redirected-eft-denied-payee-received-source-step-1",
            "title": "Retain the reported determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury reported that the payee received payment. Upload the exact Treasury status to EF or NDRED. This reports Treasury’s determination, not an independent Atlas finding about the person.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You returned the completed EFT Claim Form and Treasury reports Denied - Payee received payment in the specified unauthorized Automated Enrollment redirection process. This is not a denial for an incomplete form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-payee-received-source-step-2",
            "title": "Apply recovery only to an existing duplicate-payment overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The row directs recovery when a duplicate-payment overpayment is already on the record. Apply separately applicable program/fraud/credit conditions, including the referenced F scope where applicable; no new individual debt is established.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You returned the completed EFT Claim Form and Treasury reports Denied - Payee received payment in the specified unauthorized Automated Enrollment redirection process. This is not a denial for an incomplete form.",
              "A duplicate-payment overpayment is already on the record."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-payee-received-source-step-3",
            "title": "Take denial questions to Treasury",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "For questions about Treasury’s denial, contact Treasury as directed by its actual notice. Use the notice’s contact information; no contact number or appeal period is invented here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "You returned the completed EFT Claim Form and Treasury reports Denied - Payee received payment in the specified unauthorized Automated Enrollment redirection process. This is not a denial for an incomplete form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-payment-returned-followthrough": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-payment-returned-followthrough",
        "full_route": "missing-direct-deposit/redirected-eft-payment-returned-followthrough",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest."
        ],
        "steps": [
          {
            "id": "redirected-eft-payment-returned-followthrough-source-step-1",
            "title": "Apply returned funds only to an existing duplicate-payment debt",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If a duplicate-payment overpayment is on the record, reduce or recover it using the returned funds. The exact status says Treasury returned the redirected payment in full.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
              "The record has an overpayment due to a duplicate payment."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-payment-returned-followthrough-source-step-2",
            "title": "Title II when the beneficiary has not been repaid",
            "kind": "ssa",
            "actor": "PC",
            "action": "Issue the funds using DR or RC Special Entry in MACADE only if SSA has not repaid the beneficiary.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
              "TitleII AND the beneficiary has not been repaid."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "program-action"
          },
          {
            "id": "redirected-eft-payment-returned-followthrough-source-step-3",
            "title": "Title XVI bookkeeping in the published row",
            "kind": "ssa",
            "actor": "OBASA",
            "action": "The row describes partial remittances in SSR OPRR with DOC534 and a full remittance credited to the appropriate PMTH payment. Apply the actual accounting conditions; do not turn this into a partial-return Treasury status.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
              "TitleXVI remittance-accounting context applies."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "program-action"
          },
          {
            "id": "redirected-eft-payment-returned-followthrough-source-step-4",
            "title": "If replacement was already received",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain that the record was updated and no further customer action is needed.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
              "Replacement payment was actually received."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "replacement-receipt"
          },
          {
            "id": "redirected-eft-payment-returned-followthrough-source-step-5",
            "title": "If replacement was not received",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain the published expectation of payment within10businessdays. The row supplies no explicit clock-start event; no personal guarantee or new date is calculated.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
              "Replacement payment was NOT received."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "replacement-receipt"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "program-action",
            "label": "Program-specific follow-through",
            "logic": "source_conditions_determine_branch",
            "note": "Different program/accounting conditions; actual inputs and payment are unverified."
          },
          {
            "id": "replacement-receipt",
            "label": "Different receipt explanations",
            "logic": "source_conditions_determine_branch",
            "note": "Actual receipt is a case fact. Unknown receipt selects neither explanation."
          }
        ]
      },
      "missing-direct-deposit/redirected-eft-no-response-form-followthrough": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-no-response-form-followthrough",
        "full_route": "missing-direct-deposit/redirected-eft-no-response-form-followthrough",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial."
        ],
        "steps": [
          {
            "id": "redirected-eft-no-response-form-followthrough-source-step-1",
            "title": "Retain the Treasury no-response information",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Upload Treasury response to EF or NDRED. This status is not an incomplete-form or merits denial.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-no-response-form-followthrough-source-step-2",
            "title": "Check the recovery condition and original mailing",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If a duplicate-payment overpayment is on the record, the row starts recovery60days after Treasury mailed the ORIGINAL EFT Claim Form; check TCIS ENRClaimDetails. It is not60days from this inquiry.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial.",
              "A duplicate-payment overpayment exists; use the actual original Treasury mailing date."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-no-response-form-followthrough-source-step-3",
            "title": "If the person says they will complete the form",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Print the EFT Claim Form from TCIS and mail or hand it to the person under the applicable C prior-form/Direct-Express boundaries.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial.",
              "The claimant states that they will complete the form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-no-response-form-followthrough-source-step-4",
            "title": "Title II protest control",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply the row’s TitleII protest status E (explanation) instruction in its stated form-follow-through context.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial.",
              "The applicable TitleII no-response/form-follow-through conditions hold."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "noresponse-program-control"
          },
          {
            "id": "redirected-eft-no-response-form-followthrough-source-step-5",
            "title": "Title XVI stop-collection control",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply NT TAC under the TitleXVI instruction. Correct a prior MO TAC to NT TAC only when the source section criteria are met; do not convert every priorMO.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial.",
              "The applicable TitleXVI no-response/form-follow-through conditions hold; any MO correction separately meets section criteria."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "noresponse-program-control"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "noresponse-program-control",
            "label": "Program-specific collection controls",
            "logic": "source_conditions_determine_branch",
            "note": "Do not infer that every person has debt, that everyMO is corrected, or that this is the separate F FI-return/AOTP balance situation."
          }
        ]
      },
      "missing-direct-deposit/redirected-eft-approved-debit-notice-pending": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-approved-debit-notice-pending",
        "full_route": "missing-direct-deposit/redirected-eft-approved-debit-notice-pending",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "The specified unauthorized redirected-payment claim has the ENR status Approved - Debit Notice Sent: the EFT Claim Form was returned complete and Treasury has authority to debit the financial institution. This is not the Payment Returned status or confirmation that a replacement payment reached you."
        ],
        "steps": [
          {
            "id": "redirected-eft-approved-debit-notice-pending-source-step-1",
            "title": "Keep the debit-notice stage separate",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "No SSA action is required at this stage. A complete form and Treasury debit authority do not prove FI credit, returned funds or replacement receipt.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "The specified unauthorized redirected-payment claim has the ENR status Approved - Debit Notice Sent: the EFT Claim Form was returned complete and Treasury has authority to debit the financial institution. This is not the Payment Returned status or confirmation that a replacement payment reached you."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-approved-debit-notice-pending-source-step-2",
            "title": "Explain the two stated response periods",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The FI has30days to respond; the customer explanation states Treasury will determine the claim within30days. No separate start event is specified here, and neither is a replacement-payment or customer-form-return deadline.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "The specified unauthorized redirected-payment claim has the ENR status Approved - Debit Notice Sent: the EFT Claim Form was returned complete and Treasury has authority to debit the financial institution. This is not the Payment Returned status or confirmation that a replacement payment reached you."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-financial-institution-protest-pending": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-financial-institution-protest-pending",
        "full_route": "missing-direct-deposit/redirected-eft-financial-institution-protest-pending",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "The ENR status is FI Protest because the financial institution responded with a protest; this is not your appeal of a Treasury denial."
        ],
        "steps": [
          {
            "id": "redirected-eft-financial-institution-protest-pending-source-step-1",
            "title": "Await the Treasury response",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The source says SSA is awaiting Treasury’s response to the FI protest and no action is required at this stage. This is not the claimant’s appeal and supplies no new response or payment deadline.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "The ENR status is FI Protest because the financial institution responded with a protest; this is not your appeal of a Treasury denial."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-fi-protest-approved-denial": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-fi-protest-approved-denial",
        "full_route": "missing-direct-deposit/redirected-eft-fi-protest-approved-denial",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms FI Protest – Approved for the unauthorized ENR redirection claim. Approval concerns the institution’s protest; Treasury determined you benefited from payment."
        ],
        "steps": [
          {
            "id": "redirected-eft-fi-protest-approved-denial-source-step-1",
            "title": "Retain the reported determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury approved the financial institution’s protest and denied the claim. Upload the exact Treasury status to EF or NDRED. This reports Treasury’s determination, not an independent Atlas finding about the person.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest – Approved for the unauthorized ENR redirection claim. Approval concerns the institution’s protest; Treasury determined you benefited from payment."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-fi-protest-approved-denial-source-step-2",
            "title": "Apply recovery only to an existing duplicate-payment overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The row directs recovery when a duplicate-payment overpayment is already on the record. Apply separately applicable program/fraud/credit conditions, including the referenced F scope where applicable; no new individual debt is established.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest – Approved for the unauthorized ENR redirection claim. Approval concerns the institution’s protest; Treasury determined you benefited from payment.",
              "A duplicate-payment overpayment is already on the record."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-fi-protest-approved-denial-source-step-3",
            "title": "Take denial questions to Treasury",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "For questions about Treasury’s denial, contact Treasury as directed by its actual notice. Use the notice’s contact information; no contact number or appeal period is invented here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest – Approved for the unauthorized ENR redirection claim. Approval concerns the institution’s protest; Treasury determined you benefited from payment."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-fi-protest-denied-followthrough": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-fi-protest-denied-followthrough",
        "full_route": "missing-direct-deposit/redirected-eft-fi-protest-denied-followthrough",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms FI Protest-Denied for the specified unauthorized ENR redirected-payment claim. Denied describes the institution protest, not a claimant claim or appeal denial."
        ],
        "steps": [
          {
            "id": "redirected-eft-fi-protest-denied-followthrough-source-step-1",
            "title": "Retain the exact institution-protest scope",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "This row says SSA receives FI credit after the institution’s protest is denied. TitleXVI actions refer separately to SI02201.007C; Exhibit2 body and detailed target instructions remain unavailable in this source batch.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest-Denied for the specified unauthorized ENR redirected-payment claim. Denied describes the institution protest, not a claimant claim or appeal denial."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-fi-protest-denied-followthrough-source-step-2",
            "title": "If replacement was received",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain that the record was updated and no further customer action is needed.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest-Denied for the specified unauthorized ENR redirected-payment claim. Denied describes the institution protest, not a claimant claim or appeal denial.",
              "Replacement payment was actually received."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "FI-denied-receipt"
          },
          {
            "id": "redirected-eft-fi-protest-denied-followthrough-source-step-3",
            "title": "If replacement was not received",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain the stated10businessday expectation without inventing its start anchor or guaranteeing an individual payment.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms FI Protest-Denied for the specified unauthorized ENR redirected-payment claim. Denied describes the institution protest, not a claimant claim or appeal denial.",
              "Replacement payment was NOT received."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ],
            "alternative_group": "FI-denied-receipt"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "FI-denied-receipt",
            "label": "Replacement-receipt explanations",
            "logic": "source_conditions_determine_branch",
            "note": "These depend on actual receipt; FI protest denial is not a denial of the claimant’s claim."
          }
        ]
      },
      "missing-direct-deposit/redirected-eft-treasury-appeal-denied": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-treasury-appeal-denied",
        "full_route": "missing-direct-deposit/redirected-eft-treasury-appeal-denied",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms Appeal - Denied after Treasury reviewed and denied your appeal in the specified unauthorized Automated Enrollment redirection process. This is your claim appeal outcome, not a financial institution protest outcome."
        ],
        "steps": [
          {
            "id": "redirected-eft-treasury-appeal-denied-source-step-1",
            "title": "Retain the reported determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury denied the claimant’s appeal. Upload the exact Treasury status to EF or NDRED. This reports Treasury’s determination, not an independent Atlas finding about the person.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms Appeal - Denied after Treasury reviewed and denied your appeal in the specified unauthorized Automated Enrollment redirection process. This is your claim appeal outcome, not a financial institution protest outcome."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-treasury-appeal-denied-source-step-2",
            "title": "Apply recovery only to an existing duplicate-payment overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The row directs recovery when a duplicate-payment overpayment is already on the record. Apply separately applicable program/fraud/credit conditions, including the referenced F scope where applicable; no new individual debt is established.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms Appeal - Denied after Treasury reviewed and denied your appeal in the specified unauthorized Automated Enrollment redirection process. This is your claim appeal outcome, not a financial institution protest outcome.",
              "A duplicate-payment overpayment is already on the record."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-treasury-appeal-denied-source-step-3",
            "title": "If the person wants to protest the SSA overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Mail or hand the appropriate appeal forms. SSA overpayment protest is separate from Treasury’s denied appeal; detailed linked rights/rates/waiver instructions are not supplied here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms Appeal - Denied after Treasury reviewed and denied your appeal in the specified unauthorized Automated Enrollment redirection process. This is your claim appeal outcome, not a financial institution protest outcome.",
              "The person wishes to protest the overpayment."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-denied-benefited-from-payment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-denied-benefited-from-payment",
        "full_route": "missing-direct-deposit/redirected-eft-denied-benefited-from-payment",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "Treasury returned the status Denied - Benefited from Payment after receiving your completed EFT claim form."
        ],
        "steps": [
          {
            "id": "redirected-eft-denied-benefited-from-payment-source-step-1",
            "title": "Retain the reported determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury reported that the person benefited from payment. Upload the exact Treasury status to NDRED. This reports Treasury’s determination, not an independent Atlas finding about the person.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury returned the status Denied - Benefited from Payment after receiving your completed EFT claim form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-benefited-from-payment-source-step-2",
            "title": "Apply recovery only to an existing duplicate-payment overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The row directs recovery when a duplicate-payment overpayment is already on the record. Apply separately applicable program/fraud/credit conditions, including the referenced F scope where applicable; no new individual debt is established.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury returned the status Denied - Benefited from Payment after receiving your completed EFT claim form.",
              "A duplicate-payment overpayment is already on the record."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-benefited-from-payment-source-step-3",
            "title": "Take denial questions to Treasury",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "For questions about Treasury’s denial, contact Treasury as directed by its actual notice. Use the notice’s contact information; no contact number or appeal period is invented here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "Treasury returned the status Denied - Benefited from Payment after receiving your completed EFT claim form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-denied-someone-else-benefited": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-denied-someone-else-benefited",
        "full_route": "missing-direct-deposit/redirected-eft-denied-someone-else-benefited",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "After a completed EFT Claim Form is returned, the Treasury status is Denied - Someone Else Benefited."
        ],
        "steps": [
          {
            "id": "redirected-eft-denied-someone-else-benefited-source-step-1",
            "title": "Retain the reported determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury reported that an authorized person benefited from payment. Upload the exact Treasury status to NDRED. This reports Treasury’s determination, not an independent Atlas finding about the person.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "After a completed EFT Claim Form is returned, the Treasury status is Denied - Someone Else Benefited."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-someone-else-benefited-source-step-2",
            "title": "Apply recovery only to an existing duplicate-payment overpayment",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The row directs recovery when a duplicate-payment overpayment is already on the record. Apply separately applicable program/fraud/credit conditions, including the referenced F scope where applicable; no new individual debt is established.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "After a completed EFT Claim Form is returned, the Treasury status is Denied - Someone Else Benefited.",
              "A duplicate-payment overpayment is already on the record."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-denied-someone-else-benefited-source-step-3",
            "title": "Take denial questions to Treasury",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "For questions about Treasury’s denial, contact Treasury as directed by its actual notice. Use the notice’s contact information; no contact number or appeal period is invented here.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "After a completed EFT Claim Form is returned, the Treasury status is Denied - Someone Else Benefited."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "missing-direct-deposit/redirected-eft-undeliverable-already-resent": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "redirected-eft-undeliverable-already-resent",
        "full_route": "missing-direct-deposit/redirected-eft-undeliverable-already-resent",
        "entry_conditions": [
          "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
          "SSA confirms Undeliverable resent referral after a new address was on the MBR or SSR."
        ],
        "steps": [
          {
            "id": "redirected-eft-undeliverable-already-resent-source-step-1",
            "title": "Use the already-resent status",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Treasury has already resent the form after a new address was on MBR or SSR; TCISResentDate records resend. No SSA action is required at this time. A resend date does not establish delivery.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms Undeliverable resent referral after a new address was on the MBR or SSR."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          },
          {
            "id": "redirected-eft-undeliverable-already-resent-source-step-2",
            "title": "Return the form when it is received",
            "kind": "you",
            "actor": "Beneficiary recipient or representative payee",
            "action": "When you have the form, complete and return it within the row’s30day instruction to the address printed at the bottom of page1. No delivery or replacement-payment guarantee is stated.",
            "conditions": [
              "This is the specified unauthorized ENR redirection context; choosing this illustration does not establish actual fraud, identity, payment, liability or debt.",
              "SSA confirms Undeliverable resent referral after a new address was on the MBR or SSR.",
              "The person states that they have the EFT Claim Form."
            ],
            "source": "redirectreimbursement020run72",
            "section": "D exact selected status; A-C",
            "source_context_refs": [
              "GN02402.020-whole"
            ],
            "qualifications": [
              "This is the source’s conditional handling instruction, not a finding that this person committed fraud, received funds, incurred a debt or completed a Treasury or SSA action.",
              "Unauthorized automated-enrollment scope and the exact reported Treasury status matter. Direct Express/R16, other statuses and detailed linked procedures remain separately applicable.",
              "Published status-specific time instructions are not measured processing times, an invented clock-start event or an unconditional payment guarantee."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual receipt, completed forwarding, payment/debt follow-through and return to the usual path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-spouse-quarters-death-divorce": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-spouse-quarters-death-divorce",
        "full_route": "apply-ssi/ssi-lapr-spouse-quarters-death-divorce",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA considers a permanent resident under the 40 qualifying-quarter provision."
        ],
        "steps": [
          {
            "id": "ssi-lapr-spouse-quarters-death-divorce-source-step-1",
            "title": "Develop the relevant marriage periods",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Develop marriage duration and verify earnings under the applicable source and disclosure instructions. This illustration does not establish a legal or holding-out marriage.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers a permanent resident under the 40 qualifying-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "A.5; B.2.d.1; D.2.3-4",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-spouse-quarters-death-divorce-source-step-2",
            "title": "Current or deceased spouse quarters",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Consider quarters earned during marriage by the current spouse or one or more deceased spouses under the source conditions. Remarriage does not erase credited deceased-spouse quarters.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers a permanent resident under the 40 qualifying-quarter provision.",
              "The source-defined current/deceased-spouse relationship and work periods are established."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.d.1",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-spouse-quarters-death-divorce-source-step-3",
            "title": "A former marriage ended before determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not credit the former spouse’s quarters if the marriage ended before the alien-eligibility determination, unless it ended by death.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers a permanent resident under the 40 qualifying-quarter provision.",
              "The applicable marriage ended before the determination; distinguish death from divorce/annulment."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.d.4",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-spouse-quarters-death-divorce-source-step-4",
            "title": "A marriage ends after an earlier determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Previously credited quarters are not lost solely because the marriage later ends. If benefits terminate and a new claim is required, make the new alien-eligibility review; a former spouse’s quarters cannot be credited when divorce/annulment has ended the marriage at that new determination.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers a permanent resident under the 40 qualifying-quarter provision.",
              "A prior determination already credited quarters; distinguish a later ending from a terminated-benefits new claim."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.d.4 NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-family-earnings-record-safeguard": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-family-earnings-record-safeguard",
        "full_route": "apply-ssi/ssi-lapr-family-earnings-record-safeguard",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA verifies qualifying quarters using a living parent or spouse earnings record."
        ],
        "steps": [
          {
            "id": "ssi-lapr-family-earnings-record-safeguard-source-step-1",
            "title": "Verify the source-qualified family earnings",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Use the applicable earnings verification and disclosure instructions for each defined parent or spouse. A related person’s earnings record is not general permission to disclose it.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA verifies qualifying quarters using a living parent or spouse earnings record."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 steps3-4",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-family-earnings-record-safeguard-source-step-2",
            "title": "Keep living-relative earnings records out of the claimant file",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Whether OCE or a certified earnings record is used, do not put a living parent’s or spouse’s earnings document in the claimant file. Record only the quarter count and relevant earning period on an RC or the specified MSSICS remarks field.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA verifies qualifying quarters using a living parent or spouse earnings record.",
              "The parent or spouse is alive."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step4 IMPORTANT",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-noncovered-work-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-noncovered-work-evidence",
        "full_route": "apply-ssi/ssi-lapr-noncovered-work-evidence",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged."
        ],
        "steps": [
          {
            "id": "ssi-lapr-noncovered-work-evidence-source-step-1",
            "title": "Review the noncovered details",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "At the applicable D2 stage, request ALL NON COVERED DETAILS from DEQY for the alleged years. Combine eligible covered/noncovered amounts under the source, exclude report-type C/G pension income, and apply benefit-quarter restrictions. D3/D4 chart/example contents are not supplied in the captured page.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged.",
              "Earlier required review leaves fewer than40quarters and further relevant earnings remain alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step7",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-noncovered-work-evidence-source-step-2",
            "title": "If DEQY still leaves a shortfall and further employment is alleged",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For further alleged employment, obtain employer, dates, amounts and pay information and request available evidence. The noncovered QQ rule does not require the usual evidence-order/probative-value development sequence; supporting evidence still must be in file. Older noncovered earnings beyond the limitations period may count for this scoped determination.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged.",
              "Further NONCOVERED employment remains alleged after the applicable earlier development.",
              "D2 step7 DEQY development has been completed, the combined count remains below40, AND further noncovered employment earnings not on the DEQY remain alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step8",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-noncovered-work-evidence-source-step-3",
            "title": "In that step8 situation, if evidence cannot be supplied",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Contact the employer by phone or FormSSA-L4201 to verify employment and earnings. Do not turn this noncovered rule into a waiver of covered-earnings development.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged.",
              "The person or worker cannot provide evidence of the alleged earnings.",
              "D2 step7 DEQY development has been completed, the combined count remains below40, AND further noncovered employment earnings not on the DEQY remain alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step8",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-noncovered-work-evidence-source-step-4",
            "title": "Document that scoped step8 quarter finding",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Using available evidence and applicable exclusions, staff determine and document the quarter finding and supporting evidence. A shortfall after the required development does not decide every alternative SSI category.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged.",
              "D2 step7 DEQY development has been completed, the combined count remains below40, AND further noncovered employment earnings not on the DEQY remain alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step8; B.3; C NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-noncovered-selfemployment-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-noncovered-selfemployment-evidence",
        "full_route": "apply-ssi/ssi-lapr-noncovered-selfemployment-evidence",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA develops alleged noncovered self-employment for the SSI 40 qualifying-quarter provision.",
          "The applicable earlier D2 development still leaves the combined count below40 AND further noncovered self-employment income is alleged. Step7 can direct SEI to step9; completing the separate employment step8 is not a universal prerequisite."
        ],
        "steps": [
          {
            "id": "ssi-lapr-noncovered-selfemployment-evidence-source-step-1",
            "title": "Establish both required self-employment facts",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For alleged noncovered SEI, establish BOTH a trade or business AND net self-employment earnings under the referenced policies. One fact alone is insufficient; detailed linked examples are not newly reviewed here.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA develops alleged noncovered self-employment for the SSI 40 qualifying-quarter provision.",
              "The applicable earlier D2 development still leaves the combined count below40 AND further noncovered self-employment income is alleged. Step7 can direct SEI to step9; completing the separate employment step8 is not a universal prerequisite."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step9",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-noncovered-selfemployment-evidence-source-step-2",
            "title": "Keep supporting evidence for the scoped older-earnings rule",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For this noncovered QQ determination, SEI beyond the limitations period may be credited only with both required facts and supporting evidence in file. Covered SEI follows separate rules.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA develops alleged noncovered self-employment for the SSI 40 qualifying-quarter provision.",
              "The applicable earlier D2 development still leaves the combined count below40 AND further noncovered self-employment income is alleged. Step7 can direct SEI to step9; completing the separate employment step8 is not a universal prerequisite."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step9 NOTE/IMPORTANT",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-noncovered-selfemployment-evidence-source-step-3",
            "title": "Document the combined quarter determination",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply the combined evidence and benefit-quarter restrictions and document the source-directed finding. Do not compute a person’s SSI eligibility from this illustration.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA develops alleged noncovered self-employment for the SSI 40 qualifying-quarter provision.",
              "The applicable earlier D2 development still leaves the combined count below40 AND further noncovered self-employment income is alleged. Step7 can direct SEI to step9; completing the separate employment step8 is not a universal prerequisite."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step9; B.3",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-benefit-quarter-verification": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-benefit-quarter-verification",
        "full_route": "apply-ssi/ssi-lapr-benefit-quarter-verification",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision."
        ],
        "steps": [
          {
            "id": "ssi-lapr-benefit-quarter-verification-source-step-1",
            "title": "Ask about the correct benefit quarter",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For posted or alleged earnings beginning January1,1997, ask whether the LAPR person or worker received a defined federal means-tested benefit in the same earnings quarter. A6/A7 use program eligibility/certification definitions, not just a payment check date.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "A.6-A.7; B.3.a; E",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-benefit-quarter-verification-source-step-2",
            "title": "Verify dates only when required",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Accept the allegation absent contrary evidence. When verification is required, contact the administering State agency for the dates the person was eligible; do not demand verification in every case.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "E",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-benefit-quarter-verification-source-step-3",
            "title": "Apply the ordinary post-1996 exclusion",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "A quarter beginning after December31,1996 cannot ordinarily be credited when the LAPR person or worker received the defined benefit in that quarter. The separately stated filing-quarter exception must also be considered.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision.",
              "The ordinary B3a conditions apply; do not omit the B3b qualification."
            ],
            "source": "ssilaprquarters",
            "section": "B.3.a",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-benefit-quarter-verification-source-step-4",
            "title": "Consider the needed fortieth quarter in the SSI filing quarter",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Credit the needed40thquarter when it would be creditable in the SSI-filing quarter and no OTHER defined benefit was received before filing. Later receipt does not remove that quarter; the note preserves qualifying quarters from concurrently/later determined retroactive Medicaid eligibility.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision.",
              "The40thquarter is needed to qualify AND is creditable in the filing quarter AND no other defined benefit was received before filing."
            ],
            "source": "ssilaprquarters",
            "section": "B.3.b andNOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-natural-adoptive-parent-quarters": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-natural-adoptive-parent-quarters",
        "full_route": "apply-ssi/ssi-lapr-natural-adoptive-parent-quarters",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA considers natural or adoptive parent earnings for the permanent-resident qualifying-quarter provision."
        ],
        "steps": [
          {
            "id": "ssi-lapr-natural-adoptive-parent-quarters-source-step-1",
            "title": "Establish the parent relationship and applicable periods",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply the source’s relationship verification reference and creditable period through the quarter of age18. The person can now be older, and the parent can be deceased.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers natural or adoptive parent earnings for the permanent-resident qualifying-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "A.5; B.2.c opening; D.2 step3",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-natural-adoptive-parent-quarters-source-step-2",
            "title": "Natural and adoptive parent work",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Natural-parent work can include time before birth. Adoptive-parent work can also include time before birth only when the adoption occurred before age18; retain the source period limits.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers natural or adoptive parent earnings for the permanent-resident qualifying-quarter provision.",
              "The actual natural/adoptive relationship and applicable dates are established."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c.2-C.3",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-natural-adoptive-parent-quarters-source-step-3",
            "title": "Apply the adoption/biological-parent rights distinction",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not newly credit quarters of a biological parent whose parental rights were lost by adoption. Already credited quarters are not lost when that loss occurs after the eligibility determination; this does not itself establish an adoption or its legal effect.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers natural or adoptive parent earnings for the permanent-resident qualifying-quarter provision.",
              "An adoption-related loss of biological parental rights is established; distinguish before-versus-after the eligibility determination."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c.7",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-stepparent-marriage-quarters": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-stepparent-marriage-quarters",
        "full_route": "apply-ssi/ssi-lapr-stepparent-marriage-quarters",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA considers stepparent earnings in the permanent-resident qualifying-quarter review."
        ],
        "steps": [
          {
            "id": "ssi-lapr-stepparent-marriage-quarters-source-step-1",
            "title": "Check the marriage and determination boundaries",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The marriage to the natural/adoptive parent must have occurred before the person turned18 and must not have ended by divorce/annulment before the eligibility determination. Separation without divorce can satisfy this condition.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers stepparent earnings in the permanent-resident qualifying-quarter review."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c.4 andNOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-stepparent-marriage-quarters-source-step-2",
            "title": "Use the source-defined work period and retained-credit rule",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Consider stepparent work from the marriage quarter through the age18quarter. Already credited quarters are not lost solely because the parents later divorce; natural/adoptive-parent quarters have their own conditions.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers stepparent earnings in the permanent-resident qualifying-quarter review."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c.4-C.5",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-parent-holdingout-quarters": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-parent-holdingout-quarters",
        "full_route": "apply-ssi/ssi-lapr-parent-holdingout-quarters",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA considers quarters from a natural or adoptive parent partner under the holding-out spouse rule."
        ],
        "steps": [
          {
            "id": "ssi-lapr-parent-holdingout-quarters-source-step-1",
            "title": "Verify the specific holding-out relationship",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply the linked definition/development policy; this illustration does not establish a relationship from an allegation. At determination it must still exist, the partner must live with the natural/adoptive parent, AND the LAPR person must be under18.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers quarters from a natural or adoptive parent partner under the holding-out spouse rule."
            ],
            "source": "ssilaprquarters",
            "section": "A.5; B.2.c.6",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-parent-holdingout-quarters-source-step-2",
            "title": "Limit the credited work period",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Only consider qualifying work during that established holding-out relationship. Detailed statement/SSA4178/evidence-item requirements remain separately recorded linked-source scope, not newly reviewed from .135 alone.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA considers quarters from a natural or adoptive parent partner under the holding-out spouse rule."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c.6",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-currentyear-fortieth-quarter": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-currentyear-fortieth-quarter",
        "full_route": "apply-ssi/ssi-lapr-currentyear-fortieth-quarter",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "A permanent resident may reach the 40 qualifying-quarter requirement using current-year earnings."
        ],
        "steps": [
          {
            "id": "ssi-lapr-currentyear-fortieth-quarter-source-step-1",
            "title": "Assign only available current or past quarters",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Current-year earnings can support the count, but only past/current calendar quarters may be assigned, one per worker per quarter. A quarter is acquired on its assigned quarter’s first day; do not assign a future quarter now.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident may reach the 40 qualifying-quarter requirement using current-year earnings."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.f",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-currentyear-fortieth-quarter-source-step-2",
            "title": "Check the fortieth quarter during the application life",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For an otherwise eligible person, the40thquarter must become creditable during the application life before the source’s eligibility boundary applies. Application-life/appeal details require their separate linked rule. No individual eligibility date is calculated.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident may reach the 40 qualifying-quarter requirement using current-year earnings."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.f; GN00201.005D reference",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-currentyear-fortieth-quarter-source-step-3",
            "title": "Keep the payment rule distinct",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For claims filed August22,1996or later, the source refers to payment beginning the first day of the month following the later of filing or eligibility. This is a source condition, not a promise of processing or actual payment.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident may reach the 40 qualifying-quarter requirement using current-year earnings."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.f; SI00601.009 reference",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-fiveyear-quarter-gate": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-fiveyear-quarter-gate",
        "full_route": "apply-ssi/ssi-lapr-fiveyear-quarter-gate",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "A permanent resident seeks SSI under the 40 qualifying-quarter provision after entering on or after August22,1996."
        ],
        "steps": [
          {
            "id": "ssi-lapr-fiveyear-quarter-gate-source-step-1",
            "title": "Establish the applicable qualified-status entry event",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For an on/afterAugust22,1996 entry, review whether entry was in qualified status or later adjusted to that status; the five-year period uses the applicable event. Verify disputed entry under the referenced procedure rather than treating a document date as conclusive.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident seeks SSI under the 40 qualifying-quarter provision after entering on or after August22,1996."
            ],
            "source": "ssilaprquarters",
            "section": "B.1 opening/NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-fiveyear-quarter-gate-source-step-2",
            "title": "Review the expressly listed exceptions",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Check actual source-defined pre1996entry/qualifiedstatus/continuous-presence, humanitarian, military/family and specified Indian-status exceptions before applying the five-year limitation. Each requires its own facts and linked authority; this illustration establishes none.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident seeks SSI under the 40 qualifying-quarter provision after entering on or after August22,1996."
            ],
            "source": "ssilaprquarters",
            "section": "B.1 EXCEPTIONS",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-fiveyear-quarter-gate-source-step-3",
            "title": "Keep the quarter and other-category review separate",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Forty quarters alone does not decide the five-year restriction or all SSI eligibility; other listed noncitizen categories may apply. No advice to postpone filing or personal waiting-period calculation is given.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A permanent resident seeks SSI under the 40 qualifying-quarter provision after entering on or after August22,1996."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.a REMINDER; C NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-lapr-no-work-quarter-statement": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-lapr-no-work-quarter-statement",
        "full_route": "apply-ssi/ssi-lapr-no-work-quarter-statement",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "The permanent resident alleges that neither they nor the parents or spouses defined by this provision ever worked while residing in the United States."
        ],
        "steps": [
          {
            "id": "ssi-lapr-no-work-quarter-statement-source-step-1",
            "title": "Confirm the narrow no-work allegation scope",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The person AND all parents/spouses defined by the provision allege that they never worked while residing in the UnitedStates. Otherwise this no-verification instruction does not apply.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "The permanent resident alleges that neither they nor the parents or spouses defined by this provision ever worked while residing in the United States."
            ],
            "source": "ssilaprquarters",
            "section": "D.1",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-lapr-no-work-quarter-statement-source-step-2",
            "title": "Obtain and document the statement",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Explain the ramifications, secure a signed statement specific to that no-work history and record that the40QQ requirement is not met. Distinguish this category from the other possible SSI categories in the C note.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "The permanent resident alleges that neither they nor the parents or spouses defined by this provision ever worked while residing in the United States."
            ],
            "source": "ssilaprquarters",
            "section": "D.1; C NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-family-quarter-totals-not-titleii-credits": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-family-quarter-totals-not-titleii-credits",
        "full_route": "apply-ssi/ssi-family-quarter-totals-not-titleii-credits",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "SSA combines eligible family work periods for the permanent-resident forty-quarter provision."
        ],
        "steps": [
          {
            "id": "ssi-family-quarter-totals-not-titleii-credits-source-step-1",
            "title": "Combine only applicable family quarters",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "After1977, up to4quarters per year per worker may be credited under the source. Eligible own, parent and spouse quarters can make the person’s combined annual total greater than4, subject to relationship periods and benefit exclusions.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA combines eligible family work periods for the permanent-resident forty-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "A.5; B.2.b; D.2 steps3-4",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-family-quarter-totals-not-titleii-credits-source-step-2",
            "title": "Keep SSI family credit separate from the person’s Title II record",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Parent/spouse covered-work quarters credited for this SSI category do not count for the person’s TitleII entitlement and are not posted to that person’s earnings record.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "SSA combines eligible family work periods for the permanent-resident forty-quarter provision."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.b",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-quarter-shortfall-certified-evidence-review": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-quarter-shortfall-certified-evidence-review",
        "full_route": "apply-ssi/ssi-quarter-shortfall-certified-evidence-review",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "Initial record review does not establish forty qualifying quarters and relevant own or family earnings are alleged."
        ],
        "steps": [
          {
            "id": "ssi-quarter-shortfall-certified-evidence-review-source-step-1",
            "title": "Begin the applicable earnings-record checks",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For alleged work, use the source-directed uncertified E/R review; the page identifies ICF OCE as the online uncertified query showing the MEF QC pattern. Follow separate authorization/query instructions, not a new permission inferred here.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Initial record review does not establish forty qualifying quarters and relevant own or family earnings are alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 steps1-2",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-quarter-shortfall-certified-evidence-review-source-step-2",
            "title": "Include eligible family work and required certified records",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When defined family earnings are alleged, follow the relevant record and disclosure instructions. If earlier counts remain below40, obtain the required certified records and review with the respective workers; preserve the living-relative file safeguard.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Initial record review does not establish forty qualifying quarters and relevant own or family earnings are alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 steps3-6",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-quarter-shortfall-certified-evidence-review-source-step-3",
            "title": "Continue only the remaining source-defined development",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If the count remains short AND further earnings remain alleged outside the records, continue to the applicable D2step7 development. If no further earnings are alleged after the required review, retain the claimant’s certified record and document the scoped finding; other eligibility categories remain separate.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Initial record review does not establish forty qualifying quarters and relevant own or family earnings are alleged."
            ],
            "source": "ssilaprquarters",
            "section": "D.2 step6; C NOTE",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "source_defined_conditional",
          "automatic_transition": false,
          "targets": [
            {
              "full_route": "apply-ssi/ssi-lapr-noncovered-work-evidence",
              "source": "ssilaprquarters",
              "section": "D.2 step6 no-and-further-allegations→step7; step7-8 noncovered-employment scope",
              "conditions": [
                "The applicable D2steps1-6 review is complete and the combined count remains below40.",
                "Further relevant noncovered-employment earnings remain alleged that are not on the certified records.",
                "All actual LAPR category, relationship, disclosure and benefit-quarter predicates of the target remain separately applicable; choosing the link establishes none."
              ],
              "source_context_refs": [
                "SI00502.135-whole"
              ]
            }
          ],
          "unknowns": [
            "This is a proposed source-defined navigation continuation, not a completed case transition or successful rejoin."
          ]
        }
      },
      "apply-ssi/ssi-parent-quarter-relationship-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-parent-quarter-relationship-evidence",
        "full_route": "apply-ssi/ssi-parent-quarter-relationship-evidence",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "A parent’s earnings are offered for the LAPR qualifying-quarter category."
        ],
        "steps": [
          {
            "id": "ssi-parent-quarter-relationship-evidence-source-step-1",
            "title": "Use the relationship verification cross-reference",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "A5 requires a parent as defined by the linked policy and verified under SI00502.140D2a. The main rule removes a general same-household condition except for holding-out relationships; it does not waive relationship verification.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A parent’s earnings are offered for the LAPR qualifying-quarter category."
            ],
            "source": "ssilaprquarters",
            "section": "A.5",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-parent-quarter-relationship-evidence-source-step-2",
            "title": "Apply age and relationship-period limits",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Before using a parent’s work, apply the appropriate natural/adoptive/stepparent/holding-out conditions and age18quarter rules. Detailed linked evidence requirements retain their separate recorded review scope.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A parent’s earnings are offered for the LAPR qualifying-quarter category."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.c",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      },
      "apply-ssi/ssi-historical-quarter-paid-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-historical-quarter-paid-evidence",
        "full_route": "apply-ssi/ssi-historical-quarter-paid-evidence",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "The quarter review depends on earnings before1978."
        ],
        "steps": [
          {
            "id": "ssi-historical-quarter-paid-evidence-source-step-1",
            "title": "Distinguish pre1978 paid-quarter evidence",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Before1978, earnings must actually have been PAID in the quarter, not just earned. Follow the separately referenced wage/agricultural/SEI rules for the applicable period; this page does not newly supply alltheir details.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "The quarter review depends on earnings before1978."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.b; B.2.e",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-historical-quarter-paid-evidence-source-step-2",
            "title": "Pre1937 annual evidence alone",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When only annual evidence is available and annual earnings were at least$200, at most1quarter may be credited for that year because payment-quarter detail is unavailable. Assign it advantageously within applicable family-period limits.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "The quarter review depends on earnings before1978.",
              "The work was before1937 AND only annual evidence is available AND earnings were at least$200."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.e pre1937paragraph",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ],
            "alternative_group": "pre1937-evidence"
          },
          {
            "id": "ssi-historical-quarter-paid-evidence-source-step-3",
            "title": "Pre1937 evidence of a full year with one employer",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When annual evidence is supplemented by evidence of work for the same employer all year, divide the yearly total by$50, capped at4quarters. These are the specific historical source thresholds, not current-year rates.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "The quarter review depends on earnings before1978.",
              "The work was before1937 AND annual evidence plus full-year same-employer evidence is available."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.e pre1937paragraph andexamples",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ],
            "alternative_group": "pre1937-evidence"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "pre1937-evidence",
            "label": "Different pre1937 evidence situations",
            "logic": "source_conditions_determine_branch",
            "note": "Do not infer full-year employment from annual earnings alone or use these historical thresholds as current QC rates."
          }
        ]
      },
      "apply-ssi/ssi-simultaneous-spouse-quarter-crediting": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-simultaneous-spouse-quarter-crediting",
        "full_route": "apply-ssi/ssi-simultaneous-spouse-quarter-crediting",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "A claimant is separated but not divorced from a legal spouse and has a current holding-out spouse, or both eligible couple members have earnings."
        ],
        "steps": [
          {
            "id": "ssi-simultaneous-spouse-quarter-crediting-source-step-1",
            "title": "Legal-spouse and current holding-out-spouse situation",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The source permits simultaneous consideration from a legal spouse when separated but not divorced and a current holding-out spouse, subject to actual relationship development. Do not establish either relationship from the dropdown.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A claimant is separated but not divorced from a legal spouse and has a current holding-out spouse, or both eligible couple members have earnings.",
              "The person is separated but NOT divorced from the legal spouse AND has a current holding-out spouse under the applicable relationship definition/development."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.d.2; D.2 steps3-4",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ],
            "alternative_group": "specific-spouse-case"
          },
          {
            "id": "ssi-simultaneous-spouse-quarter-crediting-source-step-2",
            "title": "Apply the eligible-couple rule separately",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Quarters belonging to eligible-couple members may be credited to both under B2d3. That is a distinct source situation; linked living-spouse statements/SSA4178 evidence instructions are not newly reviewed from .135 alone.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "A claimant is separated but not divorced from a legal spouse and has a current holding-out spouse, or both eligible couple members have earnings.",
              "The source-defined eligible-couple situation actually applies."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.d.3",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ],
            "alternative_group": "specific-spouse-case"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "specific-spouse-case",
            "label": "Apply the actual relationship situation",
            "logic": "source_conditions_determine_branch",
            "note": "The wrapper’s OR does not establish either situation. These source clauses may overlap only where their own actual conditions are established; unknown relationship facts select neither instruction."
          }
        ]
      },
      "apply-ssi/ssi-marriageyear-quarter-assignment": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-marriageyear-quarter-assignment",
        "full_route": "apply-ssi/ssi-marriageyear-quarter-assignment",
        "entry_conditions": [
          "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
          "Post1977 spouse earnings and a marriage spanning only part of the earnings year affect the qualifying-quarter count."
        ],
        "steps": [
          {
            "id": "ssi-marriageyear-quarter-assignment-source-step-1",
            "title": "Verify annual earnings and marriage quarters",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For post1977 annual credit, assign eligible available quarters advantageously within the earned year and actual relationship period. The marriage quarter can count although the spouse worked in another part of that year.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Post1977 spouse earnings and a marriage spanning only part of the earnings year affect the qualifying-quarter count."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.e andmarriageexample",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          },
          {
            "id": "ssi-marriageyear-quarter-assignment-source-step-2",
            "title": "Preserve current-year assignment limits",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Current-year assignments remain limited to past/current quarters, one per worker per quarter; a quarter is acquired on its first day. No future-quarter credit or individual payment date is inferred.",
            "conditions": [
              "Staff are considering the LAPR forty-qualifying-quarter category. Actual status, entry/exception, relationship, earnings and benefit-quarter facts must be established; selecting this illustration supplies none of them.",
              "Post1977 spouse earnings and a marriage spanning only part of the earnings year affect the qualifying-quarter count."
            ],
            "source": "ssilaprquarters",
            "section": "B.2.f",
            "source_context_refs": [
              "SI00502.135-whole"
            ],
            "qualifications": [
              "This illustrates published staff review, not a determination of immigration status, family relationship, qualifying quarters, disclosure permission, SSI eligibility or payment for a person.",
              "Relationship, covered-earnings, identity/disclosure, application-life and other merely linked instructions retain their separately recorded source histories; this page alone does not newly review their detailed procedures.",
              "A qualifying-quarter category finding is not complete SSI eligibility or a measured processing time. No current dollar rates, earnings-record update or automatic return is inferred."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual verification, completed quarter determination and return to the usual application path are not established."
          ]
        }
      }
    },
    "original_records": {
      "replace-tax-form/ssa1099-unauthorized-enr-payment-correction": {
        "id": "ssa1099-unauthorized-enr-payment-correction",
        "title": "Your SSA-1099 includes payments you say were redirected without authorization",
        "when": "You report that your SSA-1099 is inflated because you did not receive payments during the tax year due to alleged fraud involving an unauthorized automated enrollment (ENR).",
        "you": "Tell SSA which tax year and payments you dispute and that you are requesting a corrected benefit statement, rather than another copy of the same statement. Keep the statement and related notices.",
        "ssa": "Under GN02402.020I, issue a corrected benefit statement for the described allegation. If the beneficiary received no payments in the related tax year, the processing center prepares a manual SSA-1099 showing $0.00 in all boxes. If the real beneficiary filed for cash benefits during that year, reflect the amount actually received. The field office contacts the processing center through MDW or RQFA for manual SSA-1099 requests.",
        "owner": "SSA field office and processing center handling the manual SSA-1099 request",
        "route": "Customer reports disputed year/payments -> field office contacts processing center -> applicable corrected/manual SSA-1099 handling",
        "next": "Ask SSA which statement and amounts need correction. A corrected statement is separate from repayment of redirected benefits or an overpayment decision.",
        "source": "redirectreimbursement020run72",
        "section": "GN02402.020I whole including NOTE; A-C unauthorizedENR and D-H payment/recovery boundaries retained; SM00630.070 details held",
        "timing": "Section I provides no correction turnaround or tax-filing deadline.",
        "review_status": "WholeI independentlychecked2026-10-27 withofficialA-Kcontext/retainedcapture. SSA1099 correction for allegednonreceipt/fraud fromunauthorizedENRredirectedpayments only; notallmissingpayments orordinaryreplacementcopyrequests. SectionI doesnotestablishSSA1042Scorrection instructions; form-specific linkedpolicy remainsseparate. Customer allegesinflatedstatement/nonreceipt; noindependentfraudfinding, taxliabilityorrefunddetermination byAtlas. PCmanualSSA1099allboxes0 applieswhen beneficiaryreceivednopaymentsduringrelatedtaxyear; notallredirectedpaymentcases. Ifrealbeneficiaryfiledforcashbenefitsduringtaxyear, statementreflectsamountactuallyreceived; do notzerootherreceivedbenefits. FOcontactsPCviaMDWorRQFAfor manualstatementrequests; customerisnotassignedinternalworkflow. DetailedSM00630.070manualformprocessing held; nointernaltransaction orsysteminterface inferred. Correctiondoesnotdecidereimbursement, Treasuryappeal, overpayment, paymentcontinuation orrecovery outcome. Existingreplacementavailability/deceaseddisclosure/privacy rules retained; noaccessauthorization expanded. Nocorrectioncompletiondeadline or taxfilingadvice supplied; retainrevision2025-08-25/TN308(09-25)/batch2026-06-25/capture2026-10-25/review2026-10-27distinct.",
        "source_receipt": {
          "report": "service-redirect020I-SSA1099-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-27"
        }
      },
      "missing-direct-deposit/redirected-eft-claim-form-help": {
        "id": "redirected-eft-claim-form-help",
        "title": "An unauthorized redirected payment needs an EFT claim form",
        "when": "SSA is handling the specified unauthorized-redirection claim and the EFT Claim Form is missing or incomplete.",
        "you": "Tell SSA whether the form arrived. Complete it fully and return it to the address on page1; follow the applicable notice.",
        "ssa": "For an FO visit, staff can print the form from TCIS Integrated View, help obtain its completion, mail it and retain a copy in EF or NDRED. Check prior reprint information and retained copies before reprinting. Direct Express uses a separate R16 request; this EFT form is not sent or stored in TCIS for those cases.",
        "route": "FO assistance → completed EFT claim form → Treasury process",
        "next": "Ask SSA to check the exact Treasury status and any separate overpayment notice.",
        "section": "C; D Claim Form Sent and Incomplete Resent rows",
        "timing": "Those status rows instruct return within30days. The60day no-response recovery rule has separate conditions; neither is a general SSA processing deadline.",
        "source": "redirectreimbursement020run72",
        "review_status": "Selected current GN02402.020 C and specified D status rows checked2026-10-25. Applies to the stated unauthorized-redirection claim, not every missing deposit. Direct Express, duplicate-payment recovery, appeals and other status rules remain distinct.",
        "source_receipt": {
          "report": "redirect-reimbursement020-preparation.json",
          "snapshot_path": "sources\\redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-25"
        }
      },
      "missing-direct-deposit/redirected-eft-form-undeliverable-not-resent": {
        "id": "redirected-eft-form-undeliverable-not-resent",
        "title": "Your redirected-payment claim form was returned as undeliverable",
        "when": "SSA confirms the Treasury status is Undeliverable NOT resent for an EFT Claim Form in the specified unauthorized Automated Enrollment redirection process. This is not the separate status where Treasury already resent the form.",
        "you": "Tell SSA that the form did not arrive and confirm your current mailing address. Ask whether the record needs an address correction and whether the form was already reprinted. Complete the form fully and use the return address at the bottom of page 1.",
        "ssa": "The whole D status row says Treasury does not resend this undeliverable form. Check for a recent address update; if updated, print from TCIS and send to the new address, checking EF or NDRED before reprinting when a Reprint Date is shown. Otherwise develop the current address under GN02605.055, including its separate unreachable-person instructions. For phone requests, verify the record address. If it is wrong and a Direct Deposit Fraud Block is present, follow GN02402.023; without that block, verify identity and change the address before printing and mailing. For an office visit, verify the address, correct it after identity verification if needed, print the form for completion and mail it to the address on page 1. C excludes Direct Express from this TCIS form route and instead requires an R16 request.",
        "owner": "SSA technician assisting the beneficiary, recipient or representative payee; Treasury status supplies the reported condition",
        "systems": [
          "Treasury Check Information System (TCIS), staff use",
          "Electronic Folder (EF) or NDRED for prior-form check"
        ],
        "route": "Confirmed undeliverable/not-resent status -> address and prior-form checks -> applicable phone or office assistance -> form returned to its printed address",
        "next": "Ask SSA which address and form follow-up remain. A resent form does not establish approval of reimbursement, resolution of an overpayment, or a benefit decision.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Undeliverable NOT resent row; A-C unauthorized ENR scope, Direct Express and prior-reprint boundaries; neighboring D statuses retained separately",
        "timing": "The phone-request instructions say the form should arrive within 10 business days and should be completed within 30 days. These are conditional form-delivery and return instructions, not a missing-payment replacement or Treasury decision deadline. Office assistance has its own completion-and-mailing route.",
        "review_status": "Selected whole D undeliverable/not-resent row checked 2026-10-26 against GN02402.020 revision 2025-08-25/TN308(09-25), with A-C and neighboring status contexts. Customer follow-up is editorial; address-development and fraud-block cross-references remain separately held, and internal execution was not tested.",
        "source_receipt": {
          "report": "service-redirect020-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-treasury-appeal-pending": {
        "id": "redirected-eft-treasury-appeal-pending",
        "title": "Your redirected-payment claim appeal is pending with Treasury",
        "when": "Treasury denied the original EFT claim and now reports Appeal - Pending after receiving your appeal through Treasury in the specified unauthorized Automated Enrollment redirection process.",
        "you": "Keep the Treasury appeal and denial notices. Ask SSA whether it has the pending-appeal status and whether collection of any related duplicate-payment debt has been paused under the applicable program rule. Follow Treasury instructions for the appeal.",
        "ssa": "The whole D Appeal - Pending row directs staff to upload Treasury status to EF or NDRED. For Title II, if an overpayment due to a duplicate payment exists and SSA has begun recovery, place it in protest status E (explanation). For Title XVI, stop overpayment collection with an NT TAC. The customer explanation says no further debt-collection action is taken until Treasury decides the appeal. The Treasury claim appeal is distinct from a separate SSA overpayment protest.",
        "owner": "SSA technician documenting Treasury status and applying the applicable program collection control; Treasury decides the claim appeal",
        "systems": [
          "Electronic Folder (EF) or NDRED, staff status documentation"
        ],
        "route": "Treasury pending claim appeal -> SSA status documentation -> applicable Title II or Title XVI collection control while awaiting Treasury decision",
        "next": "Ask which debt and collection action the pause covers and what Treasury needs for the pending appeal. A pending appeal does not establish reimbursement approval, debt cancellation or a payment date.",
        "source": "redirectreimbursement020run72",
        "section": "D whole selected Appeal - Pending row; A-C unauthorized ENR/Direct Express context; neighboring denial and appeal-denied rows remain separate",
        "timing": "This pending-appeal row states no Treasury appeal-decision deadline. Collection follow-through is tied to Treasury making its appeal determination, not to a fixed customer completion time.",
        "review_status": "Whole D Appeal - Pending and A-C checked 2026-10-26 against GN02402.020 revision2025-08-25/TN308(09-25),batch2026-06-25. Title II duplicate-payment overpayment AND recovery-begun conditions retained. Title XVI control stated separately; customer explanations editorial. No Treasury or SSA appeal deadline or operational execution inferred.",
        "source_receipt": {
          "report": "service-redirect020-appeal-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-denied-payee-received": {
        "id": "redirected-eft-denied-payee-received",
        "title": "Treasury says your redirected payment was received",
        "when": "You returned the completed EFT Claim Form and Treasury reports Denied - Payee received payment in the specified unauthorized Automated Enrollment redirection process. This is not a denial for an incomplete form.",
        "you": "Read Treasury’s denial notice and use the contact number printed on that notice for questions about Treasury’s finding. Ask SSA what Treasury status is on file and whether any separate duplicate-payment overpayment notice or collection action applies.",
        "ssa": "The whole D Denied - Payee received payment row says Treasury received the completed form and determined that the beneficiary, recipient or representative payee received payment. Staff upload Treasury status to EF or NDRED. If an overpayment due to a duplicate payment is on the record, the row directs the overpayment recovery process to begin. Explain Treasury’s finding that funds went to the correct account and payment was received; direct questions about the denial to Treasury using the number in its notice.",
        "owner": "Treasury for its claim finding and denial notice; SSA technician for status documentation and any applicable duplicate-payment debt action",
        "systems": [
          "Electronic Folder (EF) or NDRED, staff status documentation"
        ],
        "route": "Completed EFT claim -> Treasury received-payment denial notice -> Treasury questions via notice number; separate conditional SSA duplicate-payment debt follow-through",
        "next": "Keep the Treasury notice and any separate SSA debt notice. Confirm which decision and instructions each notice concerns. This illustration does not decide whether you actually received funds, owe a debt or qualify for reimbursement.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Denied - Payee received payment row; A-C unauthorized ENR/Direct Express context; Incomplete Resent, other denial reasons and appeal statuses remain separate",
        "timing": "This denial row states no deadline for a Treasury response to questions or for completion of an SSA debt review. Follow the actual notice instructions; no appeal filing period or payment date is supplied here.",
        "review_status": "Whole selected D received-payment denial row and A-C checked2026-10-26 against GN02402.020revision2025-08-25/TN308(09-25),batch2026-06-25. Finding attributed to Treasury; completed-form and duplicate-payment-debt conditions retained. Other denial/appeal statuses, detailed debt due process and Direct Express handling remain separately scoped. Customer explanation editorial; no internal execution or individualized determination.",
        "source_receipt": {
          "report": "service-redirect020-denied-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-payment-returned-followthrough": {
        "id": "redirected-eft-payment-returned-followthrough",
        "title": "Treasury returned the redirected payment but you still need payment follow-through",
        "when": "SSA confirms the exact Payment Returned status with ENR Match and TeleTrace (TT) Status Payment Returned in the specified unauthorized ENR redirection process. Treasury has returned the redirected payment in full; this is distinct from a trace request or an FI protest.",
        "you": "Tell SSA whether you already received a replacement payment. Ask SSA to check the exact Treasury status, payment record and any separate duplicate-payment overpayment before explaining the next action.",
        "ssa": "The selected D Payment Returned row says Treasury returned the redirected payment in full. If there is an overpayment on the record due to a duplicate payment, reduce or recover it with the returned funds. For TitleII, if SSA has not repaid the beneficiary, a PC technician issues funds using the DR or RC Special Entry in MACADE. For TitleXVI, OBASA posts partial remittances to SSR OPRR with DOC534 and credits a full remittance to the appropriate PMTH payment. If replacement was received, explain the record was updated and no further customer action is needed; if not, explain the published expectation of payment within10businessdays.",
        "owner": "Treasury for returning redirected funds; TitleII PC technician for unpaid replacement issuance; TitleXVI OBASA for remittance posting and credit",
        "systems": [
          "MACADE DR or RC Special Entry, TitleII staff action",
          "SSR OPRR DOC534 and PMTH, TitleXVI remittance actions"
        ],
        "route": "Confirmed full Payment Returned status -> separate TitleII or TitleXVI record action -> explanation based on whether replacement was received",
        "next": "Keep any SSA notice and ask for case-specific follow-up if the replacement has not arrived. This illustration does not determine payment entitlement, actual receipt or debt liability.",
        "source": "redirectreimbursement020run72",
        "section": "D whole selected Payment Returned ENR Match/TeleTrace row; A-C unauthorized ENR and Direct Express context; other FI debit/protest statuses separate",
        "timing": "For this exact status and no replacement received, the row says payment should be received within10businessdays. It supplies no explicit start-date anchor for that interval; this is not an unconditional payment guarantee, a filing deadline or a general trace-processing time.",
        "review_status": "Whole D selected Payment Returned row and A-C checked2026-10-26 against GN02402.020revision2025-08-25/TN308(09-25),batch2026-06-25. Full-return/status/duplicate-debt and TitleII-versus-TitleXVI conditions retained. Other financial-institution debit/protest rows and Direct Express remain separate. Customer questions editorial;internal execution and individual outcomes not certified.",
        "source_receipt": {
          "report": "service-redirect020-payment-returned-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-no-response-form-followthrough": {
        "id": "redirected-eft-no-response-form-followthrough",
        "title": "Treasury reports no response to the redirected-payment claim form",
        "when": "SSA confirms the No Response status for the specified unauthorized ENR redirection claim because the beneficiary, recipient or representative payee has not returned the EFT Claim Form within60days. This is distinct from an incomplete form or a Treasury merits denial.",
        "you": "Tell SSA whether you can complete the EFT Claim Form and ask for a copy if needed. Keep the Treasury and SSA notices and ask which form, return address and separate overpayment instructions apply.",
        "ssa": "The whole D No Response row directs uploading Treasury response into EF or NDRED. If an overpayment due to a duplicate payment is on the record, recovery begins60days after Treasury mailed the original EFT Claim Form;check the TCIS ENR Claim Details. Explain the form can be provided. If the claimant states they will complete it, print from TCIS and mail or hand it to them. The row then separately directs TitleII protest status E(explanation) and TitleXVI NT TAC to stop collection;correct a prior MO TAC to NT TAC only if section criteria are met.",
        "owner": "SSA technician for exact status,form assistance and applicable program-specific collection control;Treasury for original EFT Claim Form mailing",
        "systems": [
          "EF or NDRED, Treasury response documentation",
          "TCIS ENR Claim Details and EFT Claim Form print",
          "TitleII protest E;TitleXVI NT TAC conditional controls"
        ],
        "route": "Confirmed No Response -> form-completion intention and copy assistance -> separate conditional TitleII or TitleXVI collection control",
        "next": "Complete and return the applicable form using its instructions and ask SSA to confirm what remains outstanding. This illustration does not decide debt liability, waive a debt or promise reimbursement.",
        "source": "redirectreimbursement020run72",
        "section": "D whole No Response row, including claimant intention and prior MO correction; A-C and E whole context; form delivery, incomplete forms, merits denials and appeals separate",
        "timing": "The selected row anchors the60day recovery point to Treasury mailing the original EFT Claim Form,with duplicate-payment overpayment conditions. It is not60days from your call,a general processing guarantee or a new appeal filing period. Follow actual form and notice instructions.",
        "review_status": "Whole D NoResponse row withA-C/Econtext checked2026-10-26 against GN02402.020revision2025-08-25/TN308(09-25),batch2026-06-25. Claimant-will-complete condition/program distinctions/priorMOcriteria retained. E manualnotice/appealrights context is distinct;linkedGN02402.017 andSMdetails not independently rechecked here. DirectExpress R16,other statuses andindividual outcomes held;customerquestions editorial.",
        "source_receipt": {
          "report": "service-redirect020-no-response-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-approved-debit-notice-pending": {
        "id": "redirected-eft-approved-debit-notice-pending",
        "title": "Treasury has sent a debit notice to the financial institution",
        "when": "The specified unauthorized redirected-payment claim has the ENR status Approved - Debit Notice Sent: the EFT Claim Form was returned complete and Treasury has authority to debit the financial institution. This is not the Payment Returned status or confirmation that a replacement payment reached you.",
        "you": "Keep the completed-form and notice details. If you ask SSA about the missing payment, identify the current Treasury status rather than assuming that the word approved means payment has arrived.",
        "ssa": "In the whole GN 02402.020 D Approved - Debit Notice Sent row, Treasury has received the EFT Claim Form and submitted it to the financial institution. The financial institution has 30 days to respond. The SSA action column says no action is required at this time. The customer explanation says Treasury received the form and will make a determination within 30 days. Keep this procedural status separate from actual returned funds, FI credit, denial, appeal and replacement-payment statuses.",
        "owner": "SSA technician explaining Treasury claim status; Treasury and the financial institution perform the stated response steps",
        "systems": [
          "Treasury Check Information System (TCIS) ENR status"
        ],
        "route": "Complete EFT Claim Form received by Treasury -> debit notice submitted to financial institution -> institution response and Treasury determination",
        "next": "Ask SSA to confirm the current status if you need follow-through. This stage does not itself establish that funds were returned, an individual debt was resolved or replacement payment was issued. The separate customer form-return instructions and later Payment Returned explanation do not become rules for this status.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Approved - Debit Notice Sent row; A-C whole unauthorized ENR and Direct Express boundaries; other D disposition and FI debit statuses separate",
        "timing": "The selected row gives the financial institution 30 days to respond and directs staff to explain a Treasury determination within 30 days. It does not specify a separate clock-start event here; no start date is invented. These are the published status-specific instructions, not a replacement-payment deadline, customer form-return period or general SSA processing guarantee.",
        "review_status": "Selected whole source checked against whole official GN 02402.020 A-D on 2026-10-26. Printed revision 2025-08-25, TN 308 (09-25), and review date are distinct. A-C unauthorized ENR and Direct Express limits retained. Customer explanation and staff-role label are editorial; no completed FI debit, funds return, debt outcome or internal execution certified.",
        "source_receipt": {
          "report": "service-redirect020-debit-notice-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-financial-institution-protest-pending": {
        "id": "redirected-eft-financial-institution-protest-pending",
        "title": "The financial institution disputes the redirected-payment claim",
        "when": "The ENR status is FI Protest because the financial institution responded with a protest; this is not your appeal of a Treasury denial.",
        "you": "Keep your claim information and ask which Treasury response remains pending.",
        "ssa": "The published FI Protest row says SSA is awaiting Treasury’s response and no action is required at this stage.",
        "route": "Financial-institution protest awaiting Treasury response; no additional assignment inferred.",
        "next": "A pending FI protest does not establish returned funds, a replacement payment or a final denial.",
        "source": "redirectreimbursement020run72",
        "section": "D whole FI Protest row; A-C whole unauthorized ENR and Direct Express boundaries; other D debit/protest and claimant appeal statuses separate",
        "timing": "The FI Protest row states no response or payment deadline. Do not apply the earlier debit-notice 30-day response period or the separate claimant-appeal collection instructions to this status.",
        "review_status": "Selected official FI Protest row and whole A-C/D context independently checked 2026-10-26; customer explanation is an Atlas summary. Claimant appeals, collection actions, debit outcomes and linked Direct Express procedures remain separate.",
        "source_receipt": {
          "report": "service-redirect020-fi-protest-pending-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-fi-protest-approved-denial": {
        "id": "redirected-eft-fi-protest-approved-denial",
        "title": "The financial institution’s protest was approved and Treasury denied your claim",
        "when": "SSA confirms FI Protest – Approved for the unauthorized ENR redirection claim. Approval concerns the institution’s protest; Treasury determined you benefited from payment.",
        "you": "Read Treasury’s denial notice and contact Treasury about that notice. Ask SSA to explain any duplicate-payment overpayment recorded separately.",
        "ssa": "Retain Treasury status in EF or NDRED. Start recovery only if a duplicate-payment overpayment is on the record. Explain Treasury’s finding and refer denial questions to Treasury.",
        "owner": "SSA claim-handling component; Treasury for denial questions",
        "route": "Treasury denial notice; SSA records Treasury status and handles any applicable duplicate-payment debt",
        "next": "Clarify the exact status and separate Treasury’s denial from any SSA debt notice.",
        "source": "redirectreimbursement020run72",
        "section": "D whole FI Protest – Approved row; A-C whole context; other D dispositions separate",
        "timing": "No new appeal deadline, collection pause, replacement-payment promise or notice-delivery period is established here.",
        "review_status": "Whole selected row checked 2026-10-26; no personal finding or independently verified debt decision.",
        "source_receipt": {
          "report": "service-redirect020-fi-protest-approved-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-fi-protest-denied-followthrough": {
        "id": "redirected-eft-fi-protest-denied-followthrough",
        "title": "The financial institution protest was denied",
        "when": "SSA confirms FI Protest-Denied for the specified unauthorized ENR redirected-payment claim. Denied describes the institution protest, not a claimant claim or appeal denial.",
        "you": "Tell SSA whether you have already received a replacement payment. Keep your payment information so SSA can explain the confirmed status.",
        "ssa": "The published row describes SSA receiving FI credit. If replacement was received, explain the record was updated and no further customer action is needed. If replacement was not received, explain the chart expectation of payment within ten business days. Title XVI actions separately refer to SI02201.007C; detailed instructions remain held.",
        "owner": "SSA technician explaining the confirmed Treasury ENR status",
        "route": "SSA confirms the exact FI Protest-Denied status and distinguishes replacement received from not received",
        "next": "Ask SSA to clarify the exact status and whether its explanation concerns the replacement payment you have not received. This walkthrough does not confirm posting or guarantee receipt.",
        "source": "redirectreimbursement020run72",
        "section": "D whole FI Protest-Denied row with A-C context; referenced Exhibit2 details held",
        "timing": "Ten-business-day expectation only when replacement has not been received. No independently established start anchor or personal payment guarantee.",
        "review_status": "Whole selected FI Protest-Denied row and A-C scope checked2026-10-26. FI protest outcome is distinct from claimant claim/appeal denial. No individual posting or receipt established; SI02201.007C and Exhibit2 details held.",
        "source_receipt": {
          "report": "service-redirect020-fi-protest-denied-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-26"
        }
      },
      "missing-direct-deposit/redirected-eft-treasury-appeal-denied": {
        "id": "redirected-eft-treasury-appeal-denied",
        "title": "Treasury denied your redirected-payment claim appeal",
        "when": "SSA confirms Appeal - Denied after Treasury reviewed and denied your appeal in the specified unauthorized Automated Enrollment redirection process. This is your claim appeal outcome, not a financial institution protest outcome.",
        "you": "Read the Treasury decision and any separate SSA overpayment notice. If you want to protest an SSA overpayment, tell SSA and ask for the appropriate appeal forms and the instructions that apply to that notice. Keep the notices so the two decisions can be distinguished. This is an Atlas explanation of follow-through, not an individual appeal or debt decision.",
        "ssa": "The whole D Appeal - Denied row directs staff to upload Treasury status to EF or NDRED. If an overpayment on the record is due to a duplicate payment, the row directs the overpayment recovery process to begin and refers to section F. Explain Treasury denied the appeal. If the person wishes to protest the overpayment, mail or hand them the appropriate appeal forms. Program-specific recovery, fraud and credit conditions remain separately applicable.",
        "owner": "Treasury for its appeal determination; SSA technician for status documentation and applicable overpayment protest assistance",
        "systems": [
          "Electronic Folder (EF) or NDRED, staff status documentation"
        ],
        "route": "Confirmed Treasury claim-appeal denial -> SSA status documentation -> conditional duplicate-payment debt follow-through and SSA overpayment protest forms when requested",
        "next": "Ask which determination and notice you are disputing and what SSA still needs. This stage does not itself establish that you personally owe a debt or are eligible for reimbursement, waiver or a payment. The earlier pending-appeal collection control is a separate status.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Appeal - Denied row; A-C and neighboring D statuses/F-H boundaries retained; detailed linked appeal/waiver procedures held",
        "timing": "The selected Appeal - Denied row supplies no appeal filing period, recovery rate, further collection pause or payment deadline. Follow the applicable actual notice instructions; paper-check forgery and other status clocks are not imported.",
        "review_status": "Whole selected official Appeal - Denied row checked2026-10-27 against GN02402.020 revision2025-08-25/TN308(09-25)/batch2026-06-25. Customer explanation distinct from staff instructions. Treasuryappealdenied distinct from pendingappeal/initialclaimdenial/FIprotestapproved; customerTreasurydeterminationnotpersonalAtlasfinding. If duplicatepaymentoverpaymentexists recoverybegins; notautomaticdebtforanyone orneweligibilitydetermination. UploadTreasurystatustoEF/NDRED andprovideappropriateappealformsifcustomerwishestoprotestSSAoverpayment; separateSSArightsnotautomaticsecondTreasuryappeal. No newdeadline/rate/waivereligibility/recoverypause orlegaloutcome imported fromunreviewedreferences. A-CunauthorizedENRscope/DirectExpressR16exception/formreprintcheck remain; exact008source404gap notexhausted. Sourceedition/sharedcapture unchanged; notindependentcorroboration/newruntimeorphysicalinterface. SectionFTitleXVIcredit/fraud/remainingAOTPNTTACconditions remainseparate; the Drow doesnot establish a universal recoveryoverride orautomaticpersonal debt. Allcurrent451sources/894branches/parentjourneysteps andallredirect020additionalreviewscopes preserved; newreview scopeonly, no prior wording replacement.",
        "source_receipt": {
          "report": "service-redirect020-appeal-denied-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-27"
        }
      },
      "missing-direct-deposit/redirected-eft-denied-benefited-from-payment": {
        "id": "redirected-eft-denied-benefited-from-payment",
        "title": "Treasury says you benefited from the redirected payment",
        "when": "Treasury returned the status Denied - Benefited from Payment after receiving your completed EFT claim form.",
        "you": "Keep the denial notice and contact Treasury using its instructions if you dispute the finding.",
        "ssa": "Upload Treasury status to NDRED. If a duplicate-payment overpayment exists, begin the applicable recovery process.",
        "owner": "Treasury determines the claim; SSA handles its status and any conditional duplicate-payment debt.",
        "next": "Ask Treasury about its denial. A denial does not by itself establish an SSA duplicate-payment debt.",
        "timing": "This row gives no response or appeal deadline.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Denied - Benefited from Payment row; A-C and neighboring D determinations retained separately",
        "review_status": "Whole selected Treasury status independently checked2026-10-27; customer explanation separate from published staff instructions. Unauthorized ENR scope only; Direct Express remains separate. Completed form and this exact Treasury status required. Treasury finding is reported, not independently determined by Atlas. Recovery instruction applies only if duplicate-payment debt exists. Payee-received, someone-else-benefited and FI-protest-approved statuses remain distinct. No new appeal deadline, waiver standard or linked section-F procedure inferred. No runtime, physical interface or new Tech edge inferred. Original source dates and all prior qualifications remain unchanged.",
        "route": "Treasury denial notice -> contact Treasury for questions; SSA records status and addresses any duplicate-payment debt conditionally",
        "source_receipt": {
          "report": "service-redirect020-benefited-integration-gate-r2.json",
          "snapshot_path": "sources\\redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-27"
        }
      },
      "missing-direct-deposit/redirected-eft-denied-someone-else-benefited": {
        "id": "redirected-eft-denied-someone-else-benefited",
        "title": "Treasury says an authorized person benefited from the redirected payment",
        "when": "After a completed EFT Claim Form is returned, the Treasury status is Denied - Someone Else Benefited.",
        "you": "Read the Treasury Denial Notice and contact Treasury with questions about its determination. Keep the notice and tell SSA which status you are asking about.",
        "ssa": "Explain Treasury determination that an authorized person benefited from the payment, retain the Treasury status in NDRED, and begin recovery only if a duplicate-payment overpayment is already on the record.",
        "owner": "Treasury for the denial determination and notice questions; SSA staff for status retention and applicable duplicate-payment overpayment action",
        "route": "Completed-form Treasury denial status -> SSA status explanation/NDRED retention -> Treasury for Denial Notice questions",
        "next": "The explanation reports Treasury finding; it does not establish authorization, fraud or debt in your individual case.",
        "timing": "This status row supplies no separate processing deadline or replacement-payment date.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Denied - Someone Else Benefited row; A-C and neighboring D denial/appeal/FI statuses retained separately",
        "review_status": "Whole selected D status checked2026-10-27; customer explanation separate from worker instructions. Only the GN02402.020D completed-EFT-claim-form Denied-SomeoneElseBenefited status in the unauthorized ENR recovery process. This is Treasury reported determination and denial notice, not an atlas finding that the person authorized anyone or committed fraud. Completion and return of the EFT Claim Form is part of this status context; it differs from no-response or incomplete-form dispositions. Treasury status is uploaded to NDRED for this exact row; do not substitute the neighboring EF-or-NDRED rule. Overpayment recovery is conditional on an overpayment already on the record due to a duplicate payment; no automatic new debt, liability or amount inferred. Questions about the Denial Notice go to Treasury; no unsupported contact number, appeal deadline or guaranteed outcome supplied. Payee-received, beneficiary-benefited, FI-protest-approved and claimant-appeal statuses remain separate with their own conditions. Direct Express R16 handling and TCIS form availability/reprint verification limits in C remain distinct; do not send this customer to a universal TCIS print path. No notice-processing duration, replacement date, payment continuation, waiver, physical interface or actual internal execution inferred.",
        "source_receipt": {
          "report": "service-EFT-someoneelse020D-integration-gate.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-27"
        }
      },
      "missing-direct-deposit/redirected-eft-undeliverable-already-resent": {
        "id": "redirected-eft-undeliverable-already-resent",
        "title": "Treasury has already resent your redirected-payment claim form",
        "when": "SSA confirms Undeliverable resent referral after a new address was on the MBR or SSR.",
        "you": "Complete the resent form and return it to the address at the bottom of page1. Ask SSA to confirm the resend date if the form has not arrived.",
        "ssa": "The status describes Treasury resending the form; TCIS Resent Date records the resend date. The row requires no staff action at that time.",
        "next": "Confirm the exact status; the separate NOT resent workflow has different address and reprint instructions.",
        "timing": "The selected row gives30days to return the form; it supplies no delivery or replacement-payment guarantee.",
        "source": "redirectreimbursement020run72",
        "section": "D whole Undeliverable resent referral row; A-C retained",
        "owner": "Treasury for the recorded resend; beneficiary, recipient or representative payee for completing and returning the form; SSA staff for the published status explanation.",
        "route": "Treasury resends the EFT Claim Form after an undeliverable return with a new address on MBR or SSR; the individual completes and returns it to the address at the bottom of page1.",
        "systems": [
          "TCIS Resent Date (published status date)",
          "MBR or SSR (new-address condition only)"
        ],
        "review_status": "Whole D already-resent row checked2026-10-27; editorial customer explanation distinct from staff instructions. Exact already-resent status with new address on MBR or SSR only. Treasury resend and TCIS recorded date do not prove receipt or automated address synchronization. Published no-action instruction belongs to this row, not every missing-form inquiry. Thirty-day form return is not a delivery or replacement-payment deadline. NOT resent, incomplete, no-response and DirectExpress/R16 workflows remain separate. Check retained forms/reprint information under C before any separate reprint; no universal TCIS availability. Customer next-step wording editorial and distinct from worker instructions; no individualized fraud/debt determination.",
        "source_receipt": {
          "report": "service-EFT-alreadyresent020D-integration-gate-r2.json",
          "snapshot_path": "sources/redirect-reimbursement020-current-20261025.html",
          "snapshot_sha256": "02d2b9d769982fab190760eb9d2b89779de5125f957a0f74a6da2adbf01fa877",
          "checked_on": "2026-10-27"
        }
      },
      "apply-ssi/ssi-lapr-spouse-quarters-death-divorce": {
        "id": "ssi-lapr-spouse-quarters-death-divorce",
        "title": "Review spouse work quarters after death, remarriage or divorce",
        "when": "SSA considers a permanent resident under the 40 qualifying-quarter provision.",
        "you": "Tell SSA marriage, death and divorce dates and identify relevant spouse employment.",
        "ssa": "The field office develops marriage duration and verifies relevant earnings, observing disclosure rules. Quarters earned during marriage by a current or deceased spouse may count; remarriage does not erase deceased-spouse quarters. Divorce or annulment before the eligibility determination generally prevents using that former spouse. Quarters already credited are retained after a later marriage ending, but termination requiring a new claim requires a new alien-eligibility determination.",
        "route": "Field office SSI eligibility and qualifying-quarter development.",
        "next": "Ask which relationship periods and earnings evidence need verification. This review does not establish overall SSI eligibility.",
        "source": "ssilaprquarters",
        "section": "B.2.d.1 and B.2.d.4; D.2 steps3-4",
        "timing": "Relationship status at determination and a later new claim matter. Five-year restrictions, quarter exclusions and other conditions require separate review; no turnaround is promised.",
        "review_status": "Selected live subsections verified; no family earnings record disclosure inferred."
      },
      "apply-ssi/ssi-lapr-family-earnings-record-safeguard": {
        "id": "ssi-lapr-family-earnings-record-safeguard",
        "title": "Document family work quarters with earnings-record safeguards",
        "when": "SSA verifies qualifying quarters using a living parent or spouse earnings record.",
        "you": "Identify relevant work and relationship periods; ask staff what evidence is needed.",
        "ssa": "The field office verifies relevant family quarters and follows disclosure instructions. Under the step4 safeguard, staff do not put the living parent or spouse earnings query or certified earnings record in the claimant file. They record the quarter count and relevant earning period on a Report of Contact or in the specified remarks field.",
        "route": "Field office qualifying-quarter development and evidence documentation.",
        "next": "SSA documents the quarter determination while protecting the underlying family earnings record. Follow up on any separate evidence request; this safeguard does not mean all development is finished.",
        "source": "ssilaprquarters",
        "section": "D.2 steps3-4, especially step4 IMPORTANT",
        "timing": "The safeguard applies during verification and documentation; no completion time is specified.",
        "review_status": "Live subsection verified; no blanket claim that customer action or access rights end."
      },
      "apply-ssi/ssi-lapr-noncovered-work-evidence": {
        "id": "ssi-lapr-noncovered-work-evidence",
        "title": "Develop noncovered work evidence for SSI qualifying quarters",
        "when": "Prior earnings-record development leaves fewer than 40 qualifying quarters and additional noncovered employment is alleged.",
        "you": "Provide employer details, dates, pay amounts and available work records.",
        "ssa": "The field office obtains noncovered earnings details and excludes pension entries from this calculation. If further employment remains alleged, staff request available evidence such as W-2/W-2c, pay, union, tax or unemployment records and statements. For this noncovered qualifying-quarter determination, staff need not follow the usual evidence order and may consider older earnings beyond the normal limitations period with supporting evidence. If evidence cannot be supplied, staff contact the employer by phone or Form SSA-L4201.",
        "route": "Field office SSI qualifying-quarter evidence development; covered earnings correction follows separate rules.",
        "next": "SSA documents whether combined development establishes the quarter requirement. This does not itself correct a Title II earnings record or establish all SSI eligibility conditions.",
        "source": "ssilaprquarters",
        "section": "D.2 steps7-8 and step8 IMPORTANT",
        "timing": "Older noncovered earnings can be considered for this determination; no employer-response or claim-completion deadline is specified.",
        "review_status": "Live scope verified; model request for customer to supply DEQY rejected."
      },
      "apply-ssi/ssi-lapr-noncovered-selfemployment-evidence": {
        "id": "ssi-lapr-noncovered-selfemployment-evidence",
        "title": "Support both business activity and net self-employment earnings",
        "when": "SSA develops alleged noncovered self-employment for the SSI 40 qualifying-quarter provision.",
        "you": "Provide available evidence of business activity and earnings, and explain missing records.",
        "ssa": "The field office must establish both a trade or business and net self-employment earnings, supported by evidence; one condition alone is insufficient. In the linked evidence procedure, business licenses, invoices, sales records or third-party statements can support business activity. Staff obtain earnings evidence appropriate to farming or other business activity.",
        "route": "Field office SSI qualifying-quarter development using the linked self-employment evidence procedure.",
        "next": "SSA documents the combined quarter determination and supporting evidence. Establishing this factor does not establish all SSI eligibility requirements.",
        "source": "ssilaprquarters",
        "section": "D.2 step9",
        "additional_sources": [
          {
            "source": "selfemploymentdoubt",
            "section": "B.1-B.2"
          }
        ],
        "timing": "For this noncovered quarter determination, older self-employment earnings beyond the limitations period may be considered with both conditions and supporting evidence. Covered earnings follow separate rules; no completion time is promised.",
        "review_status": "Live linked evidence checked; older earnings-correction screen names not applied to SSI workflow."
      },
      "apply-ssi/ssi-lapr-benefit-quarter-verification": {
        "id": "ssi-lapr-benefit-quarter-verification",
        "title": "Check benefit dates before excluding a work quarter",
        "when": "SSA reviews earnings from 1997 onward under the permanent-resident qualifying-quarter provision.",
        "you": "Tell SSA about benefits received by you and the relative whose work is considered, including dates.",
        "ssa": "The field office asks about federal means-tested benefits in the earnings quarter, accepts the allegation absent contrary evidence, and contacts the administering State agency for eligibility dates when verification is required. Such receipt generally prevents crediting a post-1996 quarter. For the needed 40th quarter in the SSI filing quarter, staff check the exception when no other such benefit was received before filing. Later receipt does not remove that quarter.",
        "route": "Field office SSI quarter review; State benefit agency if verification is necessary.",
        "next": "Ask SSA to consider the filing-quarter exception before excluding the needed quarter. Retroactive Medicaid determined concurrently with or after SSI does not remove the 40th or preceding credited quarter under the subsection note.",
        "source": "ssilaprquarters",
        "section": "E; B.3.a-B.3.b including NOTE",
        "timing": "Exact filing and benefit dates matter; no verification turnaround is specified.",
        "review_status": "Live exception verified; no individual quarter count or eligibility conclusion."
      },
      "apply-ssi/ssi-lapr-natural-adoptive-parent-quarters": {
        "id": "ssi-lapr-natural-adoptive-parent-quarters",
        "title": "Review parent work before age 18, including adoption changes",
        "when": "SSA considers natural or adoptive parent earnings for the permanent-resident qualifying-quarter provision.",
        "you": "Tell SSA parent identities, your birth date, adoption dates and available relevant work information.",
        "ssa": "The field office checks the parent work period through the quarter the claimant reached 18, even if the claimant is now older or the parent has died. Natural-parent quarters can include work before the claimant birth. Adoptive-parent quarters can also include earlier work if adoption occurred before age 18. Biological-parent quarters are not creditable after parental rights were lost through adoption, but quarters already credited are not lost if that loss occurred after the eligibility determination. Staff verify relevant earnings under the quarter-development procedure.",
        "route": "Field office SSI parent-relationship and qualifying-quarter review.",
        "next": "Ask which dates and evidence remain needed. Parent quarters considered here do not automatically establish SSI eligibility or Title II entitlement.",
        "source": "ssilaprquarters",
        "section": "B.2.c introductory paragraph, B.2.c.2-B.2.c.3, B.2.c.7; D.2 step3",
        "timing": "The age-18 quarter, adoption date and timing of any prior determination matter; no processing deadline is specified.",
        "review_status": "Live selected rules verified; detailed relationship-document requirements remain a separate review."
      },
      "apply-ssi/ssi-lapr-stepparent-marriage-quarters": {
        "id": "ssi-lapr-stepparent-marriage-quarters",
        "title": "Check stepparent work when parents separate or divorce",
        "when": "SSA considers stepparent earnings in the permanent-resident qualifying-quarter review.",
        "you": "Explain marriage, separation, divorce or annulment dates and identify relevant stepparent work.",
        "ssa": "The field office checks whether the marriage to the natural or adoptive parent occurred before the claimant turned 18 and remained undissolved by divorce or annulment at the eligibility determination. Creditable periods run from the marriage quarter through the age-18 quarter. Separation without divorce can satisfy this relationship condition. Quarters already credited are not lost if the parents later divorce. Natural or adoptive parent quarters may also be considered under their applicable rules.",
        "route": "Field office SSI relationship-period and qualifying-quarter development.",
        "next": "Ask which marriage dates and earnings periods SSA still needs. Relationship review alone does not establish the quarter total or all SSI eligibility conditions.",
        "source": "ssilaprquarters",
        "section": "B.2.c.4 including NOTE; B.2.c.5; D.2 step3",
        "timing": "Marriage before age18 and legal relationship at determination matter; no claim-completion time is specified.",
        "review_status": "Selected live subsection verified; model age18-only trigger rejected."
      },
      "apply-ssi/ssi-lapr-parent-holdingout-quarters": {
        "id": "ssi-lapr-parent-holdingout-quarters",
        "title": "Check a parent holding-out spouse relationship for child work quarters",
        "when": "SSA considers quarters from a natural or adoptive parent partner under the holding-out spouse rule.",
        "you": "Explain the relationship, household and child-age facts, and provide requested evidence.",
        "ssa": "The field office checks whether the holding-out relationship still exists at determination, the partner lives with the parent, and the claimant is under18. Only quarters during that relationship are considered under this branch. Holding out means both people present themselves to their community as married. For the linked noncitizen relationship development, staff obtain the other person signed statement; when both allege holding out, obtain the beginning date, SSA-4178 and at least three qualifying evidence items, then evaluate the evidence.",
        "route": "Field office SSI relationship evidence review and qualifying-quarter development.",
        "next": "Ask which evidence items are needed. Living together alone does not resolve the relationship or overall SSI eligibility.",
        "source": "ssilaprquarters",
        "section": "B.2.c.6",
        "additional_sources": [
          {
            "source": "ssialienmaritalevidence",
            "section": "B.3.a"
          },
          {
            "source": "ssiholdingout",
            "section": "A; C.3-C.4"
          }
        ],
        "timing": "Current relationship and age at determination are required here; no completion deadline is specified.",
        "review_status": "Special noncitizen evidence instructions verified; legal-stepparent adult-claimant rule not imported."
      },
      "apply-ssi/ssi-lapr-currentyear-fortieth-quarter": {
        "id": "ssi-lapr-currentyear-fortieth-quarter",
        "title": "Review current-year earnings near the fortieth qualifying quarter",
        "when": "A permanent resident may reach the 40 qualifying-quarter requirement using current-year earnings.",
        "you": "Report current earnings and any pending appeal; provide requested earnings evidence.",
        "ssa": "The field office checks verified earnings and allowed quarter assignments. Current-year quarters can be assigned only to past or current quarters, one per quarter per worker. If the fortieth quarter becomes creditable during the application life, eligibility under this provision can begin no earlier than the first month of its assigned quarter. Staff review application life and appeal status rather than assuming a new claim is always required.",
        "route": "Field office SSI qualifying-quarter and application/appeal review.",
        "next": "Ask which quarter and application period SSA is considering. Payment-start rules and other eligibility factors still require separate review.",
        "source": "ssilaprquarters",
        "section": "B.2.f",
        "additional_sources": [
          {
            "source": "applicationlifepolicy",
            "section": "D.1-D.2"
          }
        ],
        "timing": "Application life runs through a final determination and can continue through a timely or good-cause appeal up to the ALJ decision, including specified ALJ remands. No future-quarter credit or individual payment date is inferred.",
        "review_status": "Live quarter and application-life subsections verified; current-year self-employment evidence remains a separate detailed path."
      },
      "apply-ssi/ssi-lapr-fiveyear-quarter-gate": {
        "id": "ssi-lapr-fiveyear-quarter-gate",
        "title": "Check entry dates and exceptions before relying on forty quarters",
        "when": "A permanent resident seeks SSI under the 40 qualifying-quarter provision after entering on or after August22,1996.",
        "you": "Provide entry and status-adjustment history, including earlier immigration statuses.",
        "ssa": "The field office checks the five-year restriction as well as the quarter total. The period generally starts with entry as a qualified noncitizen; if entry was not in qualified status, it starts with later adjustment to qualified status. Staff review the listed exceptions before applying the restriction, including qualifying refugee, asylum, withholding and Cuban/Haitian entrant histories and applicable military-family or other exceptions. Each exception requires its own evidence and conditions.",
        "route": "Field office SSI noncitizen eligibility and verified status-history review.",
        "next": "Ask which entry/status date and exception SSA is reviewing. Do not assume forty quarters alone establish eligibility or that everyone must wait five years.",
        "source": "ssilaprquarters",
        "section": "B.1 including EXCEPTIONS",
        "additional_sources": [
          {
            "source": "ssialienbasic",
            "section": "A.3.b"
          }
        ],
        "timing": "The five-year period is measured from the applicable qualified-status event; no individual waiting period, application advice to delay or eligibility result is calculated here.",
        "review_status": "Current basic rule and detailed exceptions checked; older G845 entry-verification pointer not implemented without currency reconciliation."
      },
      "apply-ssi/ssi-lapr-no-work-quarter-statement": {
        "id": "ssi-lapr-no-work-quarter-statement",
        "title": "Explain a no-work history without unnecessary quarter searches",
        "when": "The permanent resident alleges that neither they nor the parents or spouses defined by this provision ever worked while residing in the United States.",
        "you": "Explain the relevant work history accurately and sign the specific statement SSA requests.",
        "ssa": "The field office explains the consequences, obtains a signed statement of that no-work history and records that the forty-quarter requirement is not met. Quarter verification is unnecessary under this narrow condition. Staff distinguish that finding from other possible noncitizen eligibility categories identified in the source.",
        "route": "Field office SSI qualifying-quarter determination and review of other potentially applicable categories.",
        "next": "Tell SSA about any work or relationship information omitted from the allegation and ask whether another category needs development. A failure of this quarter requirement alone does not decide every SSI eligibility route.",
        "source": "ssilaprquarters",
        "section": "D.1; C NOTE",
        "timing": "No signed-statement or claim-completion deadline is specified.",
        "review_status": "Live narrow no-verification condition checked; no automatic overall denial inferred."
      },
      "apply-ssi/ssi-family-quarter-totals-not-titleii-credits": {
        "id": "ssi-family-quarter-totals-not-titleii-credits",
        "title": "Distinguish family SSI quarters from your own earnings record",
        "when": "SSA combines eligible family work periods for the permanent-resident forty-quarter provision.",
        "you": "Identify relevant family work and relationship periods; ask which credits SSA counted.",
        "ssa": "The field office calculates qualifying quarters from covered and noncovered earnings under the applicable rules. After1977, each worker can supply up to four quarters per year. The claimant may receive more than four credited quarters for a year by combining eligible own, parent and spouse quarters, subject to relationship periods and exclusions. Parent or spouse quarters credited for this SSI provision do not establish the claimant Title II entitlement and are not posted to the claimant earnings record.",
        "route": "Field office SSI qualifying-quarter calculation and evidence documentation.",
        "next": "Ask for an explanation of the SSI quarter determination. A family-quarter total here does not mean the relative earnings were transferred to your Social Security record.",
        "source": "ssilaprquarters",
        "section": "B.2.b; D.2 steps3-4",
        "timing": "Annual per-worker limits apply; no earnings-posting or decision deadline is specified.",
        "review_status": "Live distinction verified; model overreach that own quarters never count for TitleII rejected."
      },
      "apply-ssi/ssi-quarter-shortfall-certified-evidence-review": {
        "id": "ssi-quarter-shortfall-certified-evidence-review",
        "title": "Review earnings evidence before concluding a qualifying-quarter shortfall",
        "when": "Initial record review does not establish forty qualifying quarters and relevant own or family earnings are alleged.",
        "you": "Identify missing work periods, employers and which person earned the wages.",
        "ssa": "The field office follows the earnings-record verification sequence, including eligible family earnings when alleged and certified records when earlier counts remain insufficient. Staff review certified records with the respective workers while observing disclosure rules. If further earnings remain alleged, staff continue the referenced earnings development. If the reviewed count remains short and no further earnings are alleged, staff retain the claimant certified record and document the quarter determination and supporting evidence.",
        "route": "Field office SSI quarter review and applicable earnings-evidence development; living-relative record safeguards remain in force.",
        "next": "Ask which earnings periods were reviewed and what evidence can resolve a missing-work allegation. The quarter finding is separate from overall SSI eligibility.",
        "source": "ssilaprquarters",
        "section": "D.2 steps1-6",
        "timing": "The evidence sequence precedes the scoped quarter determination; no record-retrieval or claim-completion deadline is specified.",
        "review_status": "Live sequence and disclosure scope verified; no customer instruction to obtain internal queries."
      },
      "apply-ssi/ssi-parent-quarter-relationship-evidence": {
        "id": "ssi-parent-quarter-relationship-evidence",
        "title": "Document the parent relationship before using family qualifying quarters",
        "when": "A parent’s earnings are offered for the LAPR qualifying-quarter category.",
        "you": "Provide available relationship records and identify conflicting information.",
        "ssa": "The field office documents relationship evidence under the verification cross-reference in SI 00502.135A5. SI 00502.140D2a requires evidence in the file and does not permit an unverified relationship allegation. The quarter rule removes a general same-household requirement except for holding-out relationships. Staff apply the separate age and relationship-period conditions before crediting quarters.",
        "route": "Field office SSI relationship-evidence development, followed by qualifying-quarter review.",
        "next": "Ask what relationship evidence remains needed; supplying evidence does not establish overall SSI eligibility.",
        "source": "ssilaprquarters",
        "section": "A.5; B.2.c",
        "additional_sources": [
          {
            "source": "ssialienmilitaryfamily",
            "section": "D.2.a"
          }
        ],
        "timing": "Relationship verification precedes crediting family quarters; no processing deadline is specified.",
        "review_status": "Selected live cross-references checked; stale parent-definition pointer and general deeming allegation rules recorded separately."
      },
      "apply-ssi/ssi-historical-quarter-paid-evidence": {
        "id": "ssi-historical-quarter-paid-evidence",
        "title": "Check when historical wages were paid before assigning qualifying quarters",
        "when": "The quarter review depends on earnings before1978.",
        "you": "Identify payment dates and available tax, payroll or employer-service records.",
        "ssa": "The field office uses quarters actually paid for pre1978 earnings. For nonagricultural wages after1936 through1977, the linked wage rule requires at least$50 paid in the quarter, combining employers. For pre1937 work with annual tax evidence alone and at least$200 annual earnings,135B2e permits at most one quarter, assigned advantageously. Additional evidence of a full year with the same employer permits dividing annual earnings by$50, capped at four. Staff also apply the family relationship-period limits.",
        "route": "Field office historical earnings and SSI qualifying-quarter review; agricultural wages and self-employment require their separate rules.",
        "next": "Ask which payment period or employer-service evidence is missing. The result establishes the scoped quarter count, not overall eligibility.",
        "source": "ssilaprquarters",
        "section": "B.2.b; B.2.e",
        "additional_sources": [
          {
            "source": "historicalwagequarters",
            "section": "A; B.1-B.2"
          }
        ],
        "timing": "These are historical credit-assignment periods, not a response or processing deadline.",
        "review_status": "Live historical text verified; no current-year dollar threshold inferred."
      },
      "apply-ssi/ssi-simultaneous-spouse-quarter-crediting": {
        "id": "ssi-simultaneous-spouse-quarter-crediting",
        "title": "Review qualifying quarters from concurrent spouse relationships",
        "when": "A claimant is separated but not divorced from a legal spouse and has a current holding-out spouse, or both eligible couple members have earnings.",
        "you": "Identify each relationship, its dates and the relevant work periods.",
        "ssa": "The field office may consider quarters from both the legal spouse and the current holding-out spouse simultaneously under135B2d2. Under135B2d3, quarters belonging to eligible couple members may be credited to both members. Staff verify relationship periods before counting. For a living holding-out spouse,145B3a requires that person’s signed statement; when both allege holding-out, staff obtain the starting date, SSA-4178 and at least three specified evidence items, then evaluate the relationship.",
        "route": "Field office SSI marital-evidence development and qualifying-quarter review; living-relative earnings disclosure safeguards continue.",
        "next": "Ask which relationship periods and evidence items remain unresolved. A combined count does not decide all SSI requirements.",
        "source": "ssilaprquarters",
        "section": "B.2.d.1-B.2.d.3; D.2 step4",
        "additional_sources": [
          {
            "source": "ssialienmaritalevidence",
            "section": "B.1; B.3.a"
          }
        ],
        "timing": "Verify relationships and applicable periods before crediting; no completion deadline specified.",
        "review_status": "Live special marital-evidence and simultaneous-crediting rules checked; no holding-out evidence demand applied to the legal spouse merely because of separation."
      },
      "apply-ssi/ssi-marriageyear-quarter-assignment": {
        "id": "ssi-marriageyear-quarter-assignment",
        "title": "Assign annual earnings to qualifying marriage quarters",
        "when": "Post1977 spouse earnings and a marriage spanning only part of the earnings year affect the qualifying-quarter count.",
        "you": "Provide the marriage date and identify the earnings year.",
        "ssa": "The field office assigns available qualifying quarters within the earnings year advantageously, subject to the applicable restrictions. A quarter of marriage can count even when the spouse worked at another time in that same year. The135B2e example assigns two available quarters to the two quarters touched by an August marriage. Staff verify the relationship period and annual earnings rather than requiring work during each assigned marriage quarter. Current-year assignments remain limited to past and current quarters, one per worker per quarter.",
        "route": "Field office SSI qualifying-quarter assignment and relationship-period review.",
        "next": "Ask whether the annual earnings were assigned to eligible marriage quarters; the quarter finding remains separate from the SSI payment-start decision.",
        "source": "ssilaprquarters",
        "section": "B.2.e example; B.2.f",
        "additional_sources": [
          {
            "source": "quarterassignment",
            "section": "A; B"
          },
          {
            "source": "quarterrestrictions",
            "section": "4"
          }
        ],
        "timing": "A qualifying quarter is acquired on its first day; future quarters cannot be assigned currently. This is not a processing-time promise.",
        "review_status": "Live specialSSI assignment example checked with linked flexible-assignment/future-quarter rules; no blanket import of TitleII freeze exclusions into noncoveredQQs."
      }
    },
    "source_contexts": [
      {
        "id": "GN02402.020-whole",
        "source_code": "GN02402.020",
        "locator": "Whole A-K main text including Dtables, notes and Jplainlabels only",
        "start": 0,
        "end": 23886,
        "exact_text": "Effective Dates: 08/25/2025 - Present\nPrevious | Next\n\nTN 308 (09-25)\n\nGN 02402.020 Reimbursement Process Due to Alleged Fraud and Other Unauthorized Redirection of Reoccurring Payments\nA. \nPurpose of the Electronic File Transfer (EFT) Claim Form\n\nIf a Title II (TII) or Title XVI (TXVI) unauthorized redirected payment results from an Automated Enrollment (ENR), Treasury will pursue the liable Financial Institution (FI) in an attempt to recover lost payments. Treasury will issue EFT Claim Forms (See Section J., Exhibit 1) to FIs sponsoring the automated enrollments (ENR) of redirected payments, associated with SSA beneficiaries, recipients, or representative payees.\n\nB. \nOverview of Treasury's Recovery Process Using EFT Claim Forms\n\nWhen the technician selects the fraud alleged option, within the non receipt screen, it initiates the process for Treasury to recover unauthorized redirected payments. If this recovery effort is unsuccessful, Treasury mails the EFT Claims Form, Treasury notifies the receiving financial institution (RFI) and attains the requested funds.\n\nNOTE: If the beneficiary, recipient, or representative payee does not complete a return the EFT Claim Form, the individual may be at fault for the overpayment (See section C for more information).\n\nC. \nInstructions if a Beneficiary, Recipient, or Representative Payee has not Received or Completed the EFT Claim Form After Claiming Nonreceipt\n\nIf the beneficiary, recipient, or representative payee filed nonreceipt and then visits the FO, they can fill out the EFT Claim Form. The Treasury Check Information System (TCIS), Integrated View, has a print option for the EFT Claim Form. Please follow the below instructions for filling out an EFT Claim Form:\n\n1. \n\nQuery the TCIS Integrated View.\n\n2. \n\nPrint the EFT Claim Form.\n\n3. \n\nRequest the beneficiary, recipient, or representative payee complete the EFT Claim form in its entirety.\n\n4. \n\nMail the EFT Claim form to the address located at the bottom of page 1 in the EFT Claim Form.\n\n5. \n\nPlace a copy of the EFT Claim Form in the Electronic Folder (EF) or Non-Disability Repository for Evidentiary Documents (NDRED).\n\nFor individuals with Direct Express, the EFT Claim Form is not sent, nor stored in TCIS for printing. The technician must complete the R16 request for Direct Express redirected payments.\n\nNOTE: \n\nIf TCIS ENR Status shows \"Reprint Date: MM/DD/YYYY\" for the claim form, an SSA technician may have been in contact with the beneficiary and the form may be complete. Verify the beneficiary's EF or NDRED before reprinting.\n\nD. \nInstructions for Handling Treasury Responses After EFT Claim is Sent\n\nThe following chart explains the ENR Status Codes, as well as, the actions and the explanations to provide to the beneficiary, recipient, or representative payee.\n\nENR Disposition Chart\n\nENR Status\n\n\t\n\nDescription\n\n\t\n\nAction\n\n\t\n\nHow to handle inquiries: Explain the following\n\n\n\n\nPayment Returned (ENR Match and TeleTrace (TT) Status Payment Returned)\n\n\t\n\nTreasury has returned the redirected payment in full.\n\n\t\n\nIf there is an overpayment on the record due to a duplicate payment, reduce or recover the overpayment with the returned funds.\n\nTitle II- If we have not repaid the beneficiary, the PC technician will issue the funds to the beneficiary using the DR or RC Special Entry in Manual Adjustment Credit Award Data Entry (MACADE).\n\nTitle XVI - Office of Benefit Accounting and System Analysis (OBASA) posts remittances for partial payments to the Overpayment Refund Data (OPRR) segment of the Supplemental Security Record (SSR) with a DOC of 534 and updates the credit for a full remittance to the appropriate payment in the payment history (PMTH) segment.\n\n\t\n\nIf the beneficiary, recipient, or representative payee received a replacement payment(s):\n\nExplain we have updated the record and there is no further action for them to take.\n\nIf they did not receive replacement payment, explain that they should receive the payment within 10 business days.\n\n\n\n\nComerica as seen in TCIS Claim Details tab (ENR Match and RTN is Comerica, enrollment was erroneously established).\n\n\t\n\nTreasury has contacted Comerica for return of the redirected payment.\n\n\t\n\n \n\nRefer to GN 02406.008 for guidance related to nonreceipt of a Direct Express card payment.\n\n\t\n\n \n\nRefer to GN 02406.008 for guidance related to nonreceipt of Direct Express card payment.\n\n\n\n\nClaim Form Sent\n\n(Full payment not returned from FI)\n\n\t\n\nThe ENR Status Date shown in TCIS or the paperless alert shows the date Treasury sent the EFT Claim Form to the beneficiary.\n\n\t\n\nNo action is required at this time.\n\n\t\n\nThe beneficiary, recipient, or representative payee states that they have an EFT Claim Form. Instruct them to complete the form within 30 days and to return to the address shown on the bottom of page 1 of the EFT Claim Form.\n\n\n\n\nUndeliverable resent referral (Form returned undeliverable and new address is on the Master Benefit Record (MBR) or SSR)\n\n\t\n\nTreasury resent the EFT Claim Form to the beneficiary, recipient, or representative payee. The TCIS Resent Date shows the date Treasury resent the form. The individual has 30 days to return the form.\n\n\t\n\nNo action is required at this time.\n\n\t\n\nThe beneficiary, recipient, or representative payee states that they have an EFT Claim Form. Instruct them to complete the form within 30 days and to return to the address shown on the bottom of page 1 of the EFT Claim Form.\n\n\n\n\nUndeliverable NOT resent (Form returned undeliverable and NO new address is on the MBR or SSR)\n\n\t\n\nTreasury sent the EFT Claim Form to the beneficiary, recipient, or representative payee. The Post Office has returned the form to Treasury because of an invalid address. Treasury does not resend the form.\n\n\t\n\nCheck to see if address has been recently updated. If the address is updated:\n\n•\n\nPrint the EFT Claim Form from TCIS and send to the beneficiary, recipient, or representative payee’s new address.\n\n•\n\nIf TCIS ENR Status shows “Reprint Date: MM/DD/YYYY” for the claim form, an SSA technician may have already resent the form. Verify the form is not currently present in the EF or NDRED before reprinting.\n\n•\n\nIf the address has not been recently updated:\n\n•\n\nDevelop for current address GN 02605.055.\n\n•\n\nIf unable to contact beneficiary, recipient, or representative payee to update address, continue to follow GN 02605.055 Section B.\n\n\t\n\nPhone Call Requests\n\n•\n\nVerify the Title II and Title XVI address on the record.\n\nIf the address is correct:\n\n•\n\nPrint the EFT Claim Form from TCIS and send to the beneficiary, recipient, or representative payee’s address.\n\n•\n\nExplain that they should receive the form within 10 business days.\n\n•\n\nInstruct them to complete the form within 30 days and return to the address shown on the bottom of page 1 of the EFT Claim Form.\n\nIf the address is incorrect: IMPORTANT: If there is a (Direct Deposit Fraud Block (DDFP) on the record, follow GN 02402.023.\n\nIf there is no DDFP block on the record:\n\n•\n\nVerify their identity and change the address.\n\n•\n\nPrint the EFT Claim Form from TCIS and send to their new address.\n\n•\n\nExplain that they should receive the form within 10 business days.\n\n•\n\nInstruct them to complete the form within 30 days and return to the address shown on the bottom of page 1 of the EFT Claim Form.\n\n•\n\nIn-Office Requests Verify the Title II or Title XVI address on the record.\n\nIf the address is correct:\n\n•\n\nPrint the EFT Claim Form from TCIS and have them complete the form.\n\n•\n\nMail the form to the address shown on the bottom of page 1 of the EFT Claim Form. If the address is incorrect:\n\n•\n\nVerify their identity and change the address.\n\n•\n\nPrint the EFT Claim Form from TCIS and have them complete the form.\n\n•\n\nMail the form to the address shown on the bottom of page 1 of the EFT Claim Form.\n\n\n\n\nIncomplete Resent (Form returned incomplete)\n\n\t\n\nThe beneficiary, recipient, or representative payee submitted an incomplete EFT Claim Form. The TCIS Resent Date shows the date Treasury resent the EFT Claim Form. Treasury sends a Denial Notice and a blank EFT Claim Form to the beneficiary, recipient, or representative payee. The beneficiary, recipient, or representative payee must return the form within 30 days.\n\n\t\n\nNo action is required at this time.\n\n\t\n\nCustomer states that they have a Denial Notice. Treasury sends the Denial Notice because they submitted an incomplete EFT Claim Form. Instruct the beneficiary, recipient, or representative payee to complete the form within 30 days and to return to the address shown on the bottom of page 1 of the EFT Claim Form.\n\n\n\n\nNo Response (No response)\n\n\t\n\nBeneficiary, recipient, or representative payee has not returned the EFT Claim Form within 60 days.\n\n\t\n\nUpload Treasury response into the EF or NDRED.\n\nIf there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins (see Section F).\n\nNOTE: The overpayment recovery process begins 60 days after Treasury mailed the original EFT Claim Form. See ENR Claim Details Tab in TCIS.\n\n\t\n•\n\nCustomer did not return the EFT Claim Form and therefore may be overpaid.\n\n•\n\nExplain that we can provide the EFT Claim Form.\n\n•\n\nIf the claimant states that they will complete the form, print the EFT Claim Form from TCIS and mail or hand them the form.\n\nTII - Place the overpayment in protest status of “E” (explanation). TXVI - Stop overpayment collection with an NT TAC. (See GN 02402.017 for further instructions.) Previous instructions involved the use of the MO TAC (SM 01311.220) which created a BZ diary. Correct any MO TAC input with NT TAC if it meets the criteria in this section.\n\n\n\n\nApproved - Debit Notice Sent (Claim form is returned complete and Treasury has the authority to debit the FI.)\n\n\t\n\nTreasury received the EFT Claim Form and submitted it to the FI. NOTE: The FI has 30 days to respond.\n\n\t\n\nNo action is required at this time.\n\n\t\n\nTreasury has received the beneficiary, recipient, or representative payee’s EFT Claim Form and Treasury will make a determination within 30 days.\n\n\n\n\nDenied - Payee received payment (The beneficiary, recipient, or representative payee returned the completed EFT Claim Form)\n\n\t\n\nTreasury received the EFT Claim Form and determined the beneficiary, recipient, or representative payee received the payment. Treasury sends a denial notice.\n\n\t\n\nUpload Treasury status to the EF or NDRED. If there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins.\n\n\t\n\nExplain that Treasury determined that they deposited their funds into the correct account and that they received the payment. Explain that they should contact Treasury regarding the Denial Notice. The Denial Notice will have the contact number included for questions.\n\n\n\n\nDenied - Benefited from Payment (The beneficiary, recipient, or representative payee returned the completed EFT Claim Form)\n\n\t\n\nTreasury received the EFT Claim Form and determined the beneficiary, recipient, or representative payee benefited from the payment. Treasury sends a denial notice.\n\n\t\n\nUpload Treasury status to NDRED. If there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins (see section F).\n\n\t\n\nExplain that Treasury determined that the beneficiary, recipient, or representative payee deposited their funds into the correct account and that they benefited from the payment. Explain that they should contact Treasury regarding the Denial Notice.\n\n\n\n\nDenied - Someone Else Benefited (The beneficiary, recipient, or representative payee returned the completed EFT Claim Form)\n\n\t\n\nTreasury received the EFT Claim Form and determined the beneficiary, recipient, or representative payee authorized someone to use their personal information to receive the payment. Treasury sends a denial notice.\n\n\t\n\nUpload Treasury status to NDRED. If there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins (see section F).\n\n\t\n\nExplain that Treasury determined that the beneficiary, recipient, or representative payee deposited their funds into the correct account and an authorized person benefited from the payment. Explain that they should contact Treasury regarding the Denial Notice.\n\n\n\n\nAppeal – Pending (The beneficiary, recipient, or representative payee submitted an appeal)\n\n\t\n\nTreasury received the EFT Claim Form and denied the original claim. The beneficiary, recipient, or representative payee has submitted an appeal through Treasury.\n\n\t\n\nUpload Treasury status to the EF or NDRED. TII- If there is an overpayment on the record due to a duplicate payment and SSA has begun recovery, then place the overpayment in protest status of “E” (explanation).\n\nTXVI - Stop overpayment collection with an NT TAC.\n\n\t\n\nTreasury has received the beneficiary, recipient, or representative payee’s appeal. We will take no further action on collection of the debt until Treasury makes a determination on the appeal.\n\n\n\n\nAppeal – Denied (Appeal submitted, reviewed and denied.)\n\n\t\n\nTreasury received the appeal and made a determination to deny the claim.\n\n\t\n\nUpload Treasury status to the EF or NDRED. If there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins (see section F).\n\n\t\n\nTreasury has received the beneficiary, recipient, or representative payee’s appeal and denied the claim. If they wish to protest the overpayment, mail or hand them the appropriate appeal forms. see GN 02201.021, GN 02201.025, GN 02210.030, GN 02406.310, SI 02220.001, SI 02260.001, SI 02220.017\n\nFinancial Institution Debit Process\n\nENR Status\n\n\t\n\nDescription\n\n\t\n\nAction\n\n\t\n\nHow to handle inquiries: Explain the following\n\n\n\n\nFI Debit (FI Responds authorizing debit)\n\n\t\n\nSSA receives credit from FI\n\n\t\n\nFor actions necessary Title XVI, see SI 02201.007 Section C\n\n\tIf the beneficiary, recipient, or representative payee received a replacement payment:\n•\n\nExplain that we have updated the record and there is no further action for them to take.\n\nIf they did not receive replacement payment:\n\n•\n\nExplain that they should receive the payment within 10 business days.\n\n\n\n\nAuto debit (FI does not respond within 30 days)\n\n\t\n\nSSA receives credit from FI\n\n\t\n\nFor actions necessary Title XVI, see SI 02201.007 Section C\n\n\t\n\nIf the beneficiary, recipient, or representative payee received a replacement payment:\n\n•\n\nExplain that we have updated the record and there is no further action necessary for them to take.\n\nIf they did not receive replacement payment:\n\n•\n\nExplain that they should receive the payment within 10 business days.\n\n\n\n\nFI Protest-Denied (Protest is denied) See section J., Exhibit 2.\n\n\t\n\nSSA receives credit from FI\n\n\t\n\nFor actions necessary Title XVI, see SI 02201.007 Section C\n\n\tIf the beneficiary, recipient, or representative payee received a replacement payment:\n•\n\nExplain that we have updated the record and there is no further action for them to take.\n\nIf they did not receive replacement payment:\n\n•\n\nExplain that they should receive the payment within 10 business days.\n\n\n\n\nFI Protest (FI Responds with protest)\n\n\t\n\nSSA is awaiting Treasury response on FI protest.\n\n\t\n\nNo action is required at this time.\n\n\t\n\nWe are awaiting a Treasury response.\n\n\n\n\nFI Protest – Approved (Protest approved)\n\n\t\n\nTreasury received FI protest and determined that the beneficiary, recipient, or representative payee benefited from the payment. Treasury sends a denial notice.\n\n\t\n\nTreasury determined that the beneficiary, recipient, or representative payee benefited from the payment. Upload Treasury status to the EF or NDRED. If there is an overpayment on the record due to a duplicate payment, the overpayment recovery process begins.\n\n\t\n\nExplain that Treasury determined that the beneficiary, recipient, or representative payee deposited their funds into the correct account and that they benefited from the payment. Explain thatthey should contact Treasury regarding the Denial Notice.\n\nE. \nOverpayment Posting Instructions for Non-Returned or Incomplete EFT Claim Forms and SSA Issued a Replacement Payment\n1. \nFor FO instructions regarding Title XVI recipients, follow the below instructions and then choose the applicable option listed under subsection “c”:\na. \n\nCheck TCIS for the status of the EFT Claim Form.\n\nb. \n\nPrepare and mail a manual overpayment notice and ensure that appeal rights are included in the notice.\n\nc. \n\nChange the NT TAC and review the record to begin overpayment recovery (follow instructions in SM 01311.285). In addition, please follow one of the following applicable scenarios:\n\n•\n\nIf the Title XVI record is in current pay (i.e., the SSR shows payment status C01), follow the C01 instructions in SM 01311.285 to change the decision on the (Overpayment Decision) UOPD screen from 7 = Erroneous to 3 = RECOVERY BY CHECK ADJUSTMENT, and send to the Supplemental Security Record (SSR). If the overpayment has no notice date posted, then input the notice date using the MSSICS UOSD Screen, see MS 00304.006. Update Sequence Data (UOSD). A manual overpayment notice maybe necessary.\n\n•\n\nIf the Title XVI record is in non-pay status or if the Title XVI record is in terminated status, follow the applicable instructions under SM 01311.225.B.\n\n2. \nFor Processing Center procedures regarding Title II beneficiaries, please follow the below instructions:\na. \n\nCheck TCIS or Paperless for the status of the EFT claim form\n\nb. \n\nDelete the non-entitled debtor overpayment.\n\nc. \n\nEstablish the overpayment on the beneficiary’s record via the Debt Management System (DMS) Establish Debt (SMED) screen.\n\nd. \n\nPrepare and mail a manual overpayment notice and include an appeal rights in the notice.\n\nF. \nField Office (FO) Instructions for Handling Title XVI Financial Institution (FI) Return Payments, Due to Unauthorized Direct Deposit Changes\n\nIf the suspected overpayment is the result of fraud, follow SI 02201.007C on handling Title XVI overpayment fraud. After following “SSI: Overpayment Fraud” policy, review the PMTH and OPRR segment of the SSR to determine if SSA applied a credit. Please follow the below applicable scenario:\n\n•\n\nIf the credit (returned payment) covers the full overpayment amount, the system reduces the overpayment balance to zero.\n\n•\n\nIf the credit (returned payment) does not fully recover the overpayment (i.e., the FI returned a partial payment), then reduce the overpayment by the credit amount or the partial payment remittance found in the OPRR. OBASA posts the partial payment remittance to the OPRR segment, of the SSR, with a District Office Code (DOC) code of 534. In addition, balance the overpayment on the SSR, if applicable.\n\nNOTE: \n\nFor any remaining overpayment balance resulting from the A-OTP: Do not send the overpayment notice. Stop overpayment collection with an NT TAC. See GN 02402.017.\n\nG. \nProcessing Center Instructions for Handling Title II Financial Institution (FI) Return Payments, Due to Unauthorized Direct Deposit Changes.\n\nWhen the FI returns redirected payments to Treasury, Treasury will fax an ENR Recovery Debit Detail Report (see section J., Exhibit 3.). This report will have one of the following TOEL combination codes:\n\n1. \n\nTOEL 1: CHECK\n\n2. \n\nTOEL 2: DIRDEP\n\n3. \n\nTOEL 3: FRAUD\n\n4. \n\nTOEL 4: FIDEBIT\n\nOnce SSA receives this information into paperless, use the following steps to process:\n\n1. \n\nReview the ENR Recovery Debit Detail Report to determine the amount of the returned credit.\n\n2. \n\nApply the credit or remittance by reducing or removing the overpayment with the subscript of X (via DMS RRRE screen).\n\n3. \n\nOn the next business day, review the record to make sure the overpayment reduced or removed correctly.\n\n4. \n\nPost a Special Message to the MBR: “FI DEBIT RECEIVED FOR FRAUD REDIRECTED PAYMENT – OVERPAYMENT WAS REMOVED OR REDUCED IN THE AMOUNT OF $$$.$$.” If an overpayment balance remains, then terminate collections and ensure the *119 listing code has been annotated before sending the ACR to FIN.\n\nNOTE: \n\nIf there is no NED overpayment on ROAR, follow the applicable instructions under section SM 01311.225.B.\n\nH. \nInstructions for Handling Protests of Overpayments Resulting from Incorrectly Processed Redirected Payments, After the Overpayment Recovery Process\n\nIf the beneficiary, recipient, or representative payee protests the overpayment and alleges fraud, after SSA begun recovery efforts for the redirected payment, refer the case to Office of the Inspector General (OIG) via the Allegation Referral Intake System (ARIS).\n\n1. \n\nFor Title XVI, follow SM 01311.220.\n\n2. \n\nFor Title II, reestablish the overpayment back on the Non-Entitled Debtors (NED) record and follow the steps in SM 01311.225.B.\n\nIf the account holder failed to respond to the EFT Claim Form and protests the overpayment posted, then take the following applicable action:\n\n1. \n\nFor Title XVI, follow SI 02220.017\n\n2. \n\nFor Title II, follow GN 02201.025\n\nNOTE: \n\nIf a FO receives a case involving Title II, they must refer the case to the PC via MDW or RQFA.\n\nI. \nInstructions for Handling Reports of Incorrect SSA-1099 Forms (Social Security Benefit Statement) Due to Unauthorized Redirected Payments Initiated Through Auto-Enrollments (ENR)\n1. \n\nIf a beneficiary, recipient, or representative payee alleges the inflation of payments on the SSA-1099, because of nonreceipt of one or more payments due to alleged fraud, then issue a corrected benefit statement.\n\n2. \n\nIf the beneficiary did not receive payments during the related tax year in question, then the PC will follow the process to prepare a manual SSA-1099, showing $0.00 in all boxes. (For the processing of the manual SSA-1099, see SM 00630.070.)\n\n3. \n\nIf the real beneficiary filed for cash benefits during the related tax year, the SSA-1099 will reflect the amount of benefits that the real beneficiary received.\n\nNOTE: \n\nThe FO must contact the PC via MDW or RQFA regarding requests for a manual SSA-1099.\n\nDirect all program–related and technical questions to your RO support staff or PSC OA staff. RO support staff or PSC OA staff may refer questions or problems to their CO contacts.\n\nJ. \nExhibits\n\nExhibit 1-Sample EFT Claims Form.pdf\n\nExhibit 2-FI Protest Denial.pdf\n\nExhibit 3-ENR Recovery Debit Detail Report.pdf\n\nK. \nReferences\n•\n\nGN 02605.055 Title II Undeliverable Mail — Change of Address (COA)\n\n•\n\nGN 02402.023 Direct Deposit Fraud Prevention Policy\n\n•\n\nSM 01311.220 Bankruptcy and Referral to Another Agency - MJ, MO, MS and MT TAC\n\n•\n\nGN 02201.021 Field Office (FO) Actions Title II Overpayment Waiver Request\n\n•\n\nGN 02402.025 Direct Deposit Post Entitlement Interview\n\n•\n\nGN 02210.030 Request for Change in Overpayment Recovery Rate, Form SSA-634-BK\n\n•\n\nGN 02406.310 Request for Reconsideration of DCN Overpayment or Forgery Determination\n\n•\n\nSI 02220.001 Recovery Procedures for SSI Overpayments- General\n\n•\n\nSI 02260.001 Basic Requirements Concerning Supplemental Security Income (SSI) Overpayment Waiver\n\n•\n\nSI 02220.017 SSI Overpayment- Request for a Different Rate of Adjustment, a Reconsideration or a Waiver\n\n•\n\nSM 01311.285 Deleting or Correcting the N TAC or the NT TAC\n\n•\n\nMS 00304.006 Update Sequence Data (UOSD)\n\n•\n\nSI 02201.007 Supplemental Security Income (SSI): Overpayment Fraud\n\n•\n\nGN 02201.025 Title II Overpayment Reconsideration Request\n\n•\n\nSM 00630.070 Issuing Replacement, Correction, and Manual Form SSA-1099 or SSA-1042S (Social Security Benefit Statement)\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0202402020\n\t\nGN 02402.020 - Reimbursement Process Due to Alleged Fraud and Other Unauthorized Redirection of Reoccurring Payments - 08/25/2025\nBatch run: 06/25/2026\nRev:08/25/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "0e383d7b99407352ccab72bb4aeef0dde766e2f3817748b19af6e4b5ce396667"
      },
      {
        "id": "SI00502.135-whole",
        "source_code": "SI00502.135",
        "locator": "Whole A-E main includingtables, notes andexamples; missingD3/D4targetcontentsnotinvented",
        "start": 0,
        "end": 39704,
        "exact_text": "Effective Dates: 06/21/2017 - Present\nPrevious | Next\n\nTN 69 (04-26)\n\nSI 00502.135 LAPR with 40 Qualifying Quarters of Earnings\nA. \nDefinitions\n1. \nQuarter\n\nA quarter is a period of 3 calendar months ending March 31, June 30, September 30, or December 31.\n\n2. \nCovered Earnings\n\nCovered earnings are wages or self-employment income (SEI) creditable for title II benefit purposes under Social Security law.\n\n3. \nNoncovered Earnings\n\nNoncovered earnings are earnings from employment or SEI which are not creditable for title II benefit purposes under Social Security law. Examples of noncovered earnings are earnings of Federal civilian employees hired before 1984, earnings of employees of State and local governments who are members of the employer's retirement system and who have not been covered by a voluntary Federal/State Social Security agreement, and certain agricultural and domestic earnings.\n\n4. \nQuarter of Coverage (QC)\n\nA quarter of coverage is credit for a requisite amount of covered earnings assigned to a calendar quarter on the earnings record of the worker.\n\n5. \nQualifying Quarter (QQ)\n\nA qualifying quarter is credit for a requisite amount of covered earnings and/or noncovered earnings assigned to a calendar quarter for the purpose of determining SSI eligibility of a LAPR alien.\n\nFor purposes of establishing the SSI eligibility of a LAPR, a QQ is a QQ earned by:\n\n•\n\nThe LAPR alien them self; and/or\n\n•\n\na parent(s) (as defined in SI 00501.010A.2. and verified per SI 00502.140D.2.a., but with no requirement of living in the same household except in holding-out relationships, as defined in SI 00501.152 and developed per SI 00502.145B.3.) in periods in which the alien was under age 18; and /or\n\n•\n\na spouse(s) (as defined in SI 00501.150B. and developed per SI 00502.145 during their marriage if the marriage continues or the spouse is deceased.\n\n6. \nFederal Means-Tested Public Benefit\n\nThe following programs are the only programs which meet the definition of a Federal means-tested public benefit:\n\n•\n\nSSI,\n\n•\n\nMedicaid,\n\n•\n\nFood Stamps, and\n\n•\n\nTemporary Assistance for Needy Families (TANF) formerly Aid to Families with Dependent Children (AFDC).\n\n7. \nReceipt of Federal Means-Tested Public Benefit\n\nBeginning after 12/31/96, an individual “receives” a Federal means-tested public benefit in a calendar quarter if in that quarter the individual is eligible for SSI, TANF, and/or Medicaid, and/or certified to receive food stamps.\n\nNOTE: See SI 00502.135B.3.b below for crediting the 40th QQ when the LAPR alien worked and earned the 40th QQ in the quarter of filing for SSI.\n\n8. \nDetermination of Eligibility\n\nA determination of eligibility is an adjudication of eligibility and/or payment amount by a decision maker. The determination of eligibility becomes final and binding on the date of the notice. (See SI 04070.001.)\n\nB. \nPolicy\n1. \nLimited Eligibility During First 5 Years in U.S.\n\nAn LAPR alien who enters the U.S. on 8/22/1996 or later cannot be eligible based on having 40 QQs for a 5-year period beginning on the LAPR alien's date of entry into the U.S. as a qualified alien (see SI 00502.100A.2.a.). The 5-year period for an alien who enters the U.S. on 8/22/1996 or later and who is not in a qualified alien status (as defined in SI 00502.100A.2.) at entry, but subsequently adjusts to such a status, begins with the date of adjustment to qualified alien status.\n\nNOTE: Determine the LAPR's date of entry from the ADM/ADJ Date on Form I-551. If the ADM/ADJ date on the I-551 is on or after 8/22/1996 and the alien alleges entry prior to 8/22/1996, verify the date of entry using the G-845 procedure.\n\nIf the individual alleges entering the country prior to 8/22/1996 but DHS cannot provide the date because the records are unavailable or the individual was undocumented at entry, verify the entry date using whatever creditable evidence may be available (e.g., NUMIDENT dated prior to 8/22/1996, MBR/ SSR records, employment records, etc.)\n\nEXCEPTIONS: The 5-year limitation on eligibility to LAPR aliens does not apply if the LAPR alien:\n\n•\n\nentered the U.S. before 8/22/1996 and obtained qualified alien status before 8/22/1996;\n\n•\n\nentered the U.S. before 8/22/1996 and obtained qualified alien status after 8/22/1996 and has been continuously present in the U.S. (i.e., has not been outside the U.S. for a full calendar month or for 30 or more consecutive days) from the latest date of entry prior to 8/22/1996;\n\nNOTE: Develop continuous presence only if there is reason to believe the individual has been outside the U.S. for 30 consecutive days or a full month since date of entry. When continuous presence is questionable, follow the development procedures in\nSI 00501.410D.\n\n•\n\nentered the U.S. as a refugee under section 207 of the INA;\n\n•\n\nwas granted asylum under section 208 of the INA;\n\n•\n\nwas granted withholding of deportation under section 243(h) of the INA as in effect prior to 4/1/1997, or withholding of removal under section 241(b)(3) of the INA;\n\n•\n\nwas granted Cuban and Haitian entrant status under section 501(e) of the Refugee Assistance Act of 1980; or\n\n•\n\nwas admitted to the U.S. as an Amerasian immigrant pursuant to section 584 of the Foreign Operations, Export Financing, and Related Programs Appropriations Act, 1988; or\n\n•\n\nis on active duty in the Armed Forces of the U.S., or is a veteran, as described in SI 00502.140; or\n\n•\n\nis the spouse or widow(er) or unmarried dependent child of a person in the Armed Forces of the U.S., or a veteran, as described in SI 00502.140.\n\n•\n\nis an American Indian born in Canada under section 289 of the INA or a member of a federally recognized Indian tribe as defined in section 4(e) of the Indian Self-Determination and Education Assistance Act.\n\n2. \nQualifying Quarters\na. \nNumber Required\n\nAn LAPR alien must have or be credited with 40 QQs to meet the eligibility requirements for this category.\n\nREMINDER: An LAPR who does not have the 40 QQs needed for eligibility under this provision may be eligible:\n\nif admitted as a refugee, granted asylum, had deportation/removal withheld, granted Cuban/Haitian entrant status, or admitted as an Amerasian immigrant less than 7 year ago, or\n\nif lawfully residing in the U.S. and receiving SSI benefits (see SI 00502.100) on 8/22/1996, or\n\nif blind or disabled and lawfully residing in the U.S. on 8/22/1996 (see SI 00502.100D.), or\n\nbased on active duty military service or veteran status of the LAPR alien or the LAPR's spouse, widow(er), or parent (see SI 00502.140); or\n\nif an American Indian born in Canada under section 289 of the INA, or a member of a federally recognized Indian tribe as defined in section 4(e) of the Indian Self-Determination and Education Assistance Act (see SI 00502.105).\n\nb. \nNumber Creditable\n\nAfter 1977, covered and noncovered earnings are divided by the dollar amount needed to earn a QC, (see RS 00301.250, Increment Amounts — Exhibit) to determine the number of QQs earned for a year, up to a maximum of 4 QQs per year per worker.\n\nTo determine the number of QQs creditable for years before 1978, see:\n\n•\n\nRS 00301.310 for wages;\n\n•\n\nRS 00301.320 for agricultural wages; and\n\n•\n\nRS 00301.340 for SEI.\n\nMore than 4 QQs may be credited to an individual under this provision for a calendar year because in addition to QQs from their own earnings, up to 4 QQs per year may also be credited from each parent and/or a spouse(s). QCs for covered employment and self-employment that are credited from a parent(s) and/or a spouse(s) do not count for title II entitlement purposes and will not be posted to the LAPR's earnings record (E/R).\n\nc. \nQQs From a Parent\n\nAn LAPR alien of any age can be credited with QQs earned by a parent through the quarter the LAPR alien attains age 18, whether or not the parent(s) is currently living.\n\n1. \n\nWhen a Parent's QQs Can be Credited\n\nQQs belonging to a parent(s) may be credited to the parent, the parent's spouse, and to one or more children.\n\nEXAMPLE: An LAPR alien couple and their two LAPR alien children (one age 12 and the other age 23) all apply for SSI. Each member of the couple has earned 20 QQs for work done more than 5 years earlier, before the older child turned age 18. All four LAPR aliens meet the 40 QQs eligibility category based on the couple's combined 40 QQs.\n\n2. \n\nQQs Earned by a Natural Parent\n\nAll QQs earned by a natural parent(s) (including the QQs earned prior to the LAPR alien's birth) can be credited through the quarter the LAPR attains age 18.\n\nEXAMPLE: If a natural parent earned 20 QQs prior to the LAPR alien's birth and 20 QQs from the LAPR alien's birth through the quarter the LAPR alien attains age 18, 40 QQs can be credited to the LAPR alien.\n\n3. \n\nQQs Earned by an Adoptive Parent\n\nAll QQs earned by an adoptive parent(s) (including the QQs earned prior to the LAPR alien's birth) can be credited through the quarter the LAPR attains age 18 if the adoption occurred before the LAPR alien attained age 18. EXAMPLE: If the adoptive parent of a LAPR alien born 1/15/1991 and adopted 3/31/1997 earned 20 QQs prior to the LAPR alien's birth and 20 QQs from the LAPR alien's birth through the quarter the LAPR alien attained age 18, 40 QQs can be credited to the LAPR alien.\n\n4. \n\nQQs Earned by a Stepparent\n\nQQs earned by a stepparent can be credited from the quarter of the marriage of the stepparent and the natural/adoptive parent through the quarter of attainment of age 18 if the marriage between the stepparent and the natural/ adoptive parent occurred before the LAPR alien attained age 18 and has not ended by divorce or annulment before the determination of eligibility is made for the LAPR alien.\n\nEXAMPLE: An LAPR alien's natural birth parent married the LAPR alien's stepparent 6/10/1978. The LAPR alien was born 10/12/1972. They are still married when the determination of eligibility is made for the LAPR alien. The QQs from the stepparent can be credited from 6/1978 through the quarter of attainment of age 18.\n\nNOTE: QQs cannot be credited if at the time the determination of eligibility for the LAPR alien is made, the natural/adoptive parent and the stepparent relationship ended as a result of a divorce or annulment. However, QQs can be credited if the natural/adoptive parent and the stepparent are separated but not divorced. QQs credited from a stepparent are not lost if the natural/adoptive parent and the stepparent later divorce.\n\n5. \n\nQQs Earned by Both Natural/Adoptive Parents and a Stepparent\n\nQQs can be credited from both natural/adoptive parents and a stepparent during the time the stepparent is married to the natural/adoptive parent if the marriage between the stepparent and the natural/adoptive parent occurred before the LAPR alien attained age 18 and has not ended by divorce or annulment before the determination of eligibility is made for the LAPR alien.\n\nEXAMPLE: Using the above example, QQs from the stepparent can be credited from 6/1978 through the quarter the LAPR alien attains age 18 and from both natural/adoptive parents through the quarter of attainment of age 18.\n\n6. \n\nQQs Earned by a Parent's Holding-Out Spouse\n\nQQs earned by the LAPR alien's natural/adoptive parent's holding-out spouse (defined in SI 00501.152 and developed per SI 00502.145B.3.) during the time the holding-out relationship existed can be credited to the LAPR alien if at the time the determination of eligibility is made, the holding-out relationship continues to exist (i.e., the holding-out spouse lives with the natural/adoptive parent) and the LAPR alien is under age 18.\n\nEXAMPLE: An LAPR alien born 10/10/1985 currently lives with their natural birth parent and an individual determined to be their natural birth parent's holding-out spouse. The holding-out spouse began living with the LAPR alien and their natural birth parent in 1/1986. The QQs earned by the natural birth parent's holding-out spouse can be credited from 1/1986 through the present since the holding-out relationship still exists and the LAPR alien is under age 18.\n\n7. \n\nQQs Earned by a Biological Parent Whose Child Has Been Adopted\n\nQQs earned by a biological parent(s) whose parental rights are lost as a result of the adoption of the child by another person(s) are not creditable.\n\nQQs credited from a biological parent(s) are not lost if the biological parent(s) loses their parental rights as a result of adoption after a determination of eligibility is made for the LAPR alien.\n\nd. \nQQs From a Spouse\n1. \n\nQQs Earned by a Current Spouse and/or One or More Deceased Spouses\n\nQQs earned by a current spouse and/or one or more deceased spouses during marriage to the LAPR alien can be credited. Develop the duration of marriage as necessary to accurately determine the number of QQs creditable. (See SI 00502.145.)\n\nEXAMPLE:An LAPR alien's current spouse has earned 20 QQs since married to the LAPR alien, and the LAPR alien's former spouse who died while married to the LAPR alien earned over 20 QQs during the marriage. The LAPR alien can be credited with the QQs from both spouses and therefore qualify based on this provision.\n\nNOTE: Eligibility based on the credit of QQs from a deceased spouse is not lost if the LAPR alien remarries.\n\n2. \n\nQQs Earned by More Than One Current Spouse\n\nQQs may be credited to an LAPR alien from more than one current spouse. (That is, an LAPR alien who is separated, but not divorced, from the legal spouse and living with and holding-out with another, may have QQs credited from both the legal spouse and the holding-out spouse simultaneously.)\n\n3. \n\nQQs Belonging to an Eligible Couple\n\nQQs belonging to members of an eligible couple may be credited to both members of the eligible couple.\n\nEXAMPLE: An LAPR alien and their LAPR alien eligible spouse each earned 20 QQs during their marriage. Since the combined QQs total 40, each can qualify based on this provision.\n\n4. \n\nQQs of a Former Spouse\n\nA former spouse's QQs cannot be credited if the marriage ended, unless by death, before a determination of alien eligibility is made for the LAPR alien.\n\nEXAMPLE: An LAPR alien was married to a U.S. citizen for 12 years. The LAPR alien has no QQs of their own. The spouse earned over 40 QQs during their marriage. The marriage terminated by divorce 4 months before the determination of eligibility was made for the LAPR alien. No QQs can be credited from the former spouse in determining SSI eligibility.\n\nNOTE: A legal marriage ends by a divorce or annulment. The holding-out relationship ends the month after the month the holding-out couple is no longer living together. (See SI 00501.150.)\n\nQQs credited from a spouse are not lost if the marriage ends (including a holding-out relationship) for any reason after a determination of eligibility is made for the LAPR alien. However, if benefits terminate and a new claim is required, a new determination of alien eligibility must be made for the LAPR alien. If the marriage has ended as a result of a divorce or annulment when the current determination is being made, the QQs of the former spouse cannot be credited.\n\nWhen a holding-out relationship ended due to the spouse's death, see SI 00502.145B.3.b.\n\ne. \nWhen Creditable\n\nQQs are credited as follows:\n\n•\n\nQQs are acquired when earned income for covered and/or noncovered work for the calendar year equals or exceeds one or more quarterly title II QC increment(s) for the year. (See Chart of Increment Amounts in SI 00502.135D.2. step 3).\n\n•\n\nQQs are creditable for a quarter if they would have been creditable for any part of the quarter. (That is, a QQ(s) is creditable from a parent(s) in the quarter the LAPR alien attains age 18 or from a spouse for the quarter of marriage or the death of the spouse.)\n\n•\n\nAfter 1977, QQs are assigned to specific calendar quarters within the calendar year in which they are earned in the manner most advantageous to the individual, per\nRS 00301.230 - RS 00301.240. For example, if a worker's earnings of $1600 in 1984 were all earned in December, a QQ could be assigned to the first calendar quarter of 1984 and each remaining calendar quarter of the year. A QQ is acquired on the first day of the calendar quarter to which it is assigned.\n\nEXAMPLE: An LAPR alien married in August 1984. The spouse earned 2 QQs in 1984. Since QCs for covered employment and self-employment in 1984 were credited by SSA on an annual basis and not assigned to specific calendar quarters, the 2 QQs earned may be assigned to quarters in the manner most advantageous to the LAPR alien. In this case, since the marriage spanned part or all of 2 calendar quarters, the 2 QQs earned by the spouse for the year may be assigned to those 2 quarters (9/1984 and 12/1984). The time of the year when the spouse worked is irrelevant.\n\n•\n\nTo credit QQs for all years before 1978 (including years prior to 1937), see\nRS 00301.301 - RS 00301.350.\n\nNOTE: Before 1978 (including years prior to 1937), earnings must have actually been paid (i.e., not necessarily earned) in the quarter for a QQ to be credited.\n\nIf evidence of earnings paid in a quarter is not available for years prior to 1937, determine the number of QQs as follows:\n\nIf evidence of annual earnings information (such as income tax records) is the only evidence available and the worker's earnings were $200 or more in the year, a maximum of one QQ can be credited for the year since there is no information available showing when the earnings were actually paid. The quarter can be credited to any quarter in the year that is most advantageous to the LAPR alien; or\n\nIf in addition to the annual tax information, the individual presents evidence indicating the worker worked for the same employer for the entire year (such as retirement papers, years of service documentation, letters of commendation, etc.) the yearly total can be divided by $50 to determine the number of QQs for the year, up to a yearly maximum of 4 QQs.\n\nEXAMPLE 1: An LAPR alien, born in France on 3/30/1917, lived in the U.S. from 12/18/1925 until 10/10/1980 when they returned to France. They returned to the U.S. on 1/10/1996 and was granted LAPR status at that time. On 03/20/1997, they filed for SSI as an aged individual. They are not disabled and they meet no other exception. They must, therefore, meet the 40-QQ determination. Since they entered the U.S. prior to 08/22/1996 as an LAPR alien, it is not a requirement that they reside in the U.S. for 5 years.\n\nHe earned 39 QQs of their own until they left the country in 1980. They have not worked since their return; however, they have a tax return from the year 1935 showing that their parent earned $600 in that year. There is no other evidence of the 1935 earnings available.\n\nCredit can be given for 1 QQ for the 3/1935 quarter (the quarter of attainment of age 18). They meet the 40 QQ determination since they have 39 QQs of their own and can be credited with 1 QQ for 1935.\n\nEXAMPLE 2: Same circumstances as in EXAMPLE 1 above except that the LAPR alien was born 12/30/1917 and has only 36 QQs of their own. In addition to the tax return indicating their parent had earnings of $600 in 1935, they present a letter of commendation from their parent's employer showing that their parent worked for the same employer from 01/1926 - 05/1936.\n\nSince the letter of commendation indicates the LAPR alien's parent worked for the same employer for all of 1935, 4 QQs can be credited for 1935 ($600 ÷ $50 = 12 QQs or a maximum of 4 QQs). All 4 QQs can be credited to the LAPR alien for 1935 since they turned 18 in 12/1935. They, therefore, meet the 40 QQ requirement since they have 36 QQs of their own and can be credited with 4 QQs for 1935.\n\nf. \nCurrent-Year QQs\n\nCurrent year earnings can be used to help establish 40 QQs to determine eligibility under this provision. However, current year QQs can be assigned only to past and current calendar quarters, one per calendar quarter per worker. A QQ is acquired on the first day of the quarter in which it is assigned per RS 00301.230. Current year SEI can be used to help establish 40 QQs following the instructions in RS 01804.110.\n\nIf an otherwise eligible individual's earnings permit the 40th QQ to be credited during the life of the application (see GN 00201.005D.), eligibility can be found based on current year earnings no earlier than the first month of the calendar quarter to which the 40th QQ is assigned. For claims filed 8/22/1996 or later, benefits are payable beginning the first day of the month following the later of the date the individual files the application or becomes eligible (SI 00601.009).\n\nEXAMPLE: An aged LAPR alien files an SSI application on 03/2/1997. They do not meet the 40 QQ determination in 03/1997 as they can only be credited with 39 QQs, 20 QQs of their own and 19 earned by their current spouse during their marriage. They meet all other eligibility factors in March and subsequent months. The FO made the input to the system on 03/15/1997 to deny their claim. The life of their application would have ended on March 15; however, they filed a timely request for reconsideration on 04/30/1997.\n\nIn 04/1997, their spouse earned $700, enough for 1 QQ. The QQ can be credited as of 04/1/1997, giving the spouse a total of 20 QQs. On 05/15/1997, the FO made the reconsideration decision and determined that the LAPR alien did not meet the 40 QQ determination for March but that they did meet it beginning 04/01/1997 since as of April 1, they can be credited with 20 QQs of their own and 20 from their spouse. The FO made the input to the system on 05/15/1997 to pay the LAPR alien SSI benefits beginning 05/1/1997 (the first day of the month following the date they became eligible), based on the 03/2/1997 application.\n\n3. \nReceipt of Federal Means-Tested Public Benefits After 1996\na. \nQQs Not Creditable\n\nQQs cannot be credited for any quarter beginning after 12/31/96, if in the quarter the LAPR alien or the worker (the LAPR alien, their parent(s) and/or spouse(s)) received a Federal means-tested public benefit as defined in SI 00502.135A.\n\nEXAMPLE: In the month of 6/1997, an LAPR alien, age 4, received Medicaid. Their parent was working in the 6/1997 quarter and earned a QQ. However, since the child received Medicaid in the 6/1997 quarter, the QQ cannot be counted.\n\nb. \nCrediting the 40th QQ in the Quarter of Filing for SSI\n\nWhen an LAPR alien's 40th QQ would be creditable in the quarter they file for SSI, and the QQ is needed to qualify, credit the 40th QQ if, prior to the filing date (see GN 00204.007), no other Federal means-tested public benefit was received in the quarter. The QQ is not lost if, after the filing date, a Federal means-tested benefit is received.\n\nNOTE: Medicaid eligibility determined concurrently or after the determination of SSI eligibility will not cause an individual to lose the 40th QQ or the preceding QQ if retroactive Medicaid eligibility is provided for previous months. For example, if an individual has unpaid medical expenses in the 3 months prior to filing for SSI that Medicaid will cover, the retroactive Medicaid eligibility will not affect the QQs credited before the individual files for SSI.\n\nc. \nExamples\n1. \n\n40th QQ Earned in the Quarter an Individual Files for SSI\n\nAn aged LAPR alien, born 02/15/1932, files for SSI on 10/25/1997. They are not disabled and do not meet any other exception. They must therefore meet the 40 QQ provision. They entered the U.S. prior to 08/22/1996 as an LAPR alien and are not required to reside in the U.S. for 5 years before eligibility can exist.\n\nThey have a total of 25 QQs through the 09/1997 quarter and their spouse has 14 QQs for a total of 39 through the 09/1997 quarter. All of their spouse's earnings were prior to 01/1997. In 10/1997, prior to filing for SSI, they worked and earned $1000 (enough for a QQ). They have not received any other Federal means-tested public benefit since 01/1997.\n\nThe 40th QQ earned in 10/1997 can be credited and the LAPR alien is eligible in 10/1997 and can be paid beginning 11/1997 based on the QQ provision since the 40th QQ was earned prior to filing for SSI and they did not receive any Federal means-tested public benefit since 01/1997.\n\n2. \n\nQQ Earned While Certified to Receive Food Stamps\n\nAn LAPR alien files for SSI on 07/10/1997. They last worked in 06/1997 and earned their 38th QQ in 06/1997. They have been married since 01/1997 and their spouse, who is a U.S. citizen, also worked and earned 2 QQs in 1997. Since 01/1997, their spouse has also been certified to receive food stamps; therefore, the 2 QQs earned by the spouse in the 03/1997 and 06/1997 quarters cannot be credited since the spouse was also certified to receive food stamps in both quarters.\n\nTherefore, the LAPR alien cannot meet the 40-QQ eligibility requirement since they can only be credited with the 38 quarters they earned.\n\n3. \n\nQQ Earned in a Year During Which Certified to Receive Food Stamps for Part of Year\n\nAn LAPR alien files for SSI on 10/10/1997. They have never worked and have no QQs of their own. They have been married for 30 years and their spouse, who is a U.S. citizen and who has been working since the couple were married, earned their 40th QQ in 03/1997. The spouse was also certified to receive food stamps in 01/1997 and 02/1997; however, they have not been certified to receive food stamps or eligible for any other Federal means-tested public benefit since 02/1997.\n\nTherefore, since QQs for the current year can be assigned to past and current calendar quarters, the 40th QQ can be assigned to the 06/1997 quarter when the LAPR alien's spouse was not certified for food stamps or eligible for any other Federal means-tested public benefit. Since all 40 QQs were earned during their marriage, the LAPR alien meets the 40-QQ determination in the 06/1997 quarter.\n\nC. \nProcedure - LAPR Alien Status\n\nDevelop and verify LAPR alien status in accordance with GN 00303.440 and SI 00502.115A.\n\nNOTE: An LAPR who does not have the 40 QQs needed for eligibility under this provision may be eligible:\n\n \n\nif admitted as a refugee, granted asylum, had deportation/removal withheld, granted Cuban/Haitian entrant status, or admitted as an Amerasian immigrant less than 7 years ago; or\n\nif lawfully residing in the U.S. and receiving SSI benefits on 8/22/1996 (see SI 00502.100); or\n\nif blind or disabled and lawfully residing in the U.S. on 8/22/1996 (see SI 00502.100.); or\n\nbased on active duty military service or veteran status of the LAPR alien or the LAPR's spouse, widow(er), or parent (see SI 00502.140); or\n\nif an American Indian born in Canada under section 289 of the INA, or a member of a federally recognized Indian tribe as defined in section 4(e) of the Indian Self-Determination and Education Assistance Act (see SI 00502.105).\n\nD. \nProcedure - Qualifying Quarters\n1. \nWhen Verification of QQs Is Not Required\n\nNo QQ verification is necessary if the LAPR alien alleges that they never worked while residing in the U.S. and that their parent(s) or spouse(s) (as defined in SI 00502.135A.)never worked while residing in the U.S.\n\n•\n\nExplain any ramifications,\n\n•\n\nSecure a signed statement specific to this effect, and\n\n•\n\nFind that the 40-QQ requirement is not met.\n\n2. \nWhen Verification of QQs Is Required\n\nQQ verification is required anytime the LAPR alien alleges that they and/ or their parent(s) and/or spouse(s) (as defined in SI 00502.135A.) have worked while residing in the U.S. for an employer or been self-employed. Follow the procedure below to establish QQs based on the LAPR alien's employment record and/or their parent(s) and/or spouse(s).\n\nSTEP\tACTION\n\n\n1\n\n\t\n\nIf the LAPR alien alleges that they have worked while residing in the U.S. for an employer or been self-employed:\n\n•\n\nSecure an uncertified E/R query for the LAPR alien per GN 01010.009 to determine the number of QCs and go to step 2.\n\nNOTE: The Interactive Computation Facility (ICF) Online Computational Earnings (OCE) is the only online uncertified E/R query that displays the QC pattern from the Master Earnings File (MEF). See MSOM MS 02424.001.\n\n\n\n\n2\n\n\t\n\nDo the total QCs on the E/R total 40 or more? (Remember when totalling the number of QCs from the E/R that if the LAPR alien received a Federal means-tested public benefit in any quarter after 12/31/1996, the QC cannot be credited. See SI 00502.135B.3.)\n\n•\n\nIf yes, STOP, — Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination\n(GN 00301.286). For non-MSSICS claims, record the information on a Report of Contact (RC).\n\n•\n\nIf no, go to step 3.\n\n\n\n\n3\n\n\t\n\nAre earnings alleged for a parent(s) and/or spouse(s) as defined in\nSI 00502.135A.?\n\n•\n\nIf yes, follow the procedure in step 1 for each individual involved in the count and determine the total number of QCs. If the LAPR alien had earnings, consider their QCs in conjunction with the QCs of the parent(s) and/or spouse(s). Go to step 4.\n\nREMINDER: Observe the appropriate disclosure instructions. (See GN 03340.005.)\n\n•\n\nIf no, secure a certified E/R for the LAPR alien per GN 01010.009 and go to step 5.\n\n\n\n\n4\n\n\t\n\nIs the total 40 or more? (Remember when totalling the number of QCs from the E/Rs that if the LAPR alien or the worker (the LAPR alien, their parent(s) and/or spouse(s)) received a Federal means-tested public benefit in any quarter after 12/31/1996, the QC cannot be credited. (See SI 00502.135B.3.)\n\n•\n\nIf yes, STOP,— Meets the 40-QQ requirement. Document the\n40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\nIMPORTANT: Regardless of whether the OCE query or a certified E/R is used to verify the number of QCs for a parent(s) and/or spouse(s), do not place the document in the file if the parent(s) or spouse(s) is alive. Record the number of QCs and the relevant period when they were earned on a RC or the MSSICS remarks field. This will prevent the possibility of disclosure of earnings information for the parent or spouse to the LAPR alien.\n\n•\n\nIf no, secure a certified E/R for the LAPR alien and each individual used in the count and go to step 5.\n\n\n\n\n5\n\n\t\n\nExamine the certified E/R(s) and determine the total number of QCs from all E/Rs used. Is the total 40 or more? (Remember when totalling the number of QCs from the E/Rs that if the LAPR alien received a Federal means-tested public benefit in any quarter after 12/31/1996, the QC cannot be credited. See SI 00502.135B.3.)\n\n•\n\nIf yes, STOP,— Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n•\n\nIf no, go to step 6.\n\n\n\n\n6\n\n\t\n\nReview the certified E/R(s) with the respective NH(s) per RS 01404.003. Did the E/R review result in 40 or more QCs? (Remember when totalling the number of QCs from the E/Rs that if the LAPR alien or the worker (the LAPR alien, their parent(s) and/or spouse(s)) received a Federal means-tested public benefit in any quarter after 12/31/1996, the QC cannot be credited. See SI 00502.135B.3.)\n\nREMINDER: If a review of the E/R of a parent(s) and/or spouse(s) is necessary, observe the appropriate disclosure instructions (see GN 03340.005.).\n\nSee RS 00301.101 through RS 00301.350 for developing QCs,\nRS 01404.005 through RS 01404.018 for developing lag earnings,\nRS 01404.105 through RS 01404.180 for developing prelag earnings, and\nRS 01804.001 for developing SEI.\n\n•\n\nIf yes, STOP, — Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n•\n\nIf no, and the LAPR alien and/or individuals used in the count continue to allege earnings that are not on the certified E/Rs, go to step 7.\n\n•\n\nIf no, and no further earnings are alleged by the LAPR alien and/or the individuals used in the count, STOP, — Does not meet the 40-QQ requirement. Retain the LAPR's certified E/R in file and document the QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n\n\n\n7\n\n\t\n\nRequest ALL NON COVERED DETAILS from the Detail Earnings Query (DEQY) for the employment years alleged for the LAPR alien and/or each individual used in the count. (See SM 00344.001 for instructions on the DEQY and SI 00502.135D.4. for an example of a noncovered detail DEQY response.) Divide the figure for the XX YEARLY TOTAL in the TOTAL AMOUNT field on the DEQY by the dollar amount needed to earn a QC as indicated in SI 00502.135D.3. to determine the number of QQs for the year(s). Is the combined total of all QQs 40 or more? (Remember when totalling the number of QQs that if the LAPR alien or the worker (the LAPR alien, their parent(s) and /or spouse(s)) received a Federal means-tested public benefit in any quarter after 12/31/1996, the QQ cannot be credited. See SI 00502.135B.3.)\n\nNOTE: Covered and noncovered earnings can be combined to make a QQ.\n\nIncome shown as “C,” current W-2P (Pension), or “G,” Current Corrected W-2P (Pension), in the R (Report Type) field on the DEQY should not be used when making the QQ determination as pension income should not be included as noncovered earnings. See SM 00344.014 for a list of the R (Report Type) codes and SM 00344.015 for a list of the E (Employment Type) codes on the DEQY.\n\n•\n\nIf yes, STOP, — Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n•\n\nIf no, and the LAPR alien and/or individuals used in the count continue to allege earnings that are not on the DEQY, go to step 8. If SEI is alleged, go to step 9.\n\n•\n\nIf no, and no further earnings are alleged by the LAPR alien and/or the individuals used in the count,STOP, — Does not meet the 40-QQ requirement. Retain the LAPR alien's certified E/R in file and document the QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n\n\n\n8\n\n\t\n\nObtain information regarding the employment (i.e., name/address of employer, dates of employment, amount of earnings, rate of pay, etc.) from the LAPR alien and/or individuals used in the count. Request all available evidence for the alleged employment such as:\n\n•\n\nW-2, W-2c;\n\n•\n\nPay envelopes, vouchers, and similar unsigned employer statements to the employee, a State or Federal agency;\n\n•\n\nUnion records;\n\n•\n\nIndividual's copy of Federal or State income tax returns;\n\n•\n\nRecords of State unemployment insurance agencies;\n\n•\n\nStatements of persons having knowledge of the individual's employment and/or wages; or\n\n•\n\nIndividual's personal records and statements.\n\nNOTE: When asking for evidence of noncovered earnings, it is not necessary to develop evidence in the order required by RS 01403.010, RS 01403.050, and RS 01403.052. The noncovered QQ determination should be made based on evidence readily available and not its probative value.\n\nAlso, for purposes of counting noncovered earnings for the QQ determination, earnings beyond the statute of limitations (RS 02201.001) can be credited. However, evidence must be in file to support the earnings and the QQ determination.\n\nSee SI 00502.135B.2.e. for determining the number of QQs for pre-1937 earnings.\n\n\n \t\n\nIMPORTANT: This development only applies when making a QQ determination for noncovered earnings. Follow existing rules when developing covered earnings.\n\nIf the LAPR alien and/or the individuals used in the count are unable to provide evidence of alleged earnings, contact the employer(s) by phone or send the employer(s) Form SSA-L4201 to request verification of the employment and the amount of earnings.\n\nUsing the evidence available, determine the amount of earnings for the year(s) and divide the figure by the dollar amount needed to earn a QC as indicated in SI 00502.135D. to determine the number of QQs for the year(s). Does all development combined establish 40 QQs? (Remember when totalling the number of QQs that if the LAPR alien or the worker (the LAPR alien, their parent(s) and/or spouse(s)) received a Federal means-tested public benefit in any quarter after 12/31/1996, the QQ cannot be credited. See SI 00502.135B.3.)\n\n•\n\nIf yes, STOP, — Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n•\n\nIf no, STOP, — Does not meet the 40-QQ requirement. Retain the LAPR alien's certified E/R in file and document the QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286) For non-MSSICS claims, record the information on a RC.\n\n\n\n\n9\n\n\t\n\nIf SEI is alleged, follow the policy requirements in RS 01801.010 and RS 01804.070 to determine if the individual(s) was:\n\n•\n\nengaged in a trade or business, and\n\n•\n\nhad net earnings from self-employment.\n\nNOTE: For purposes of counting SEI for the 40-QQ requirement, SEI beyond the statute of limitations (RS 02201.001) can be credited. However, both of the above requirements must be met and evidence in file to support the decision. Meeting just one requirement will not establish SEI.\n\nIMPORTANT: This development only applies when making a QQ determination for noncovered earnings. Follow existing rules when developing SEI for covered earnings.\n\nDoes the evidence presented (combined with all other evidence) establish 40 QQs? (Remember when totalling the number of QQs that if the LAPR alien or the worker (the LAPR alien, their parent(s) and/or spouse(s)) received a Federal means-tested public benefit in any quarter after 12/31/1996, the QQ cannot be credited. See SI 00502.135B.3.)\n\n•\n\nIf yes, STOP, — Meets the 40-QQ requirement. Document the 40-QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\n•\n\nIf no, STOP, — Does not meet the 40-QQ requirement. Retain the LAPR alien's certified E/R in file and document the QQ determination on the Report of Contact page including the evidence used to make the determination (GN 00301.286). For non-MSSICS claims, record the information on a RC.\n\nE. \nProcedure - Federal Means-Tested Public Benefits\n\nIf earnings are posted to the worker's (the LAPR alien and/or their parent(s) and/or spouse(s)) E/R beginning 1/1/1997, or alleged by the worker beginning 1/1/1997, ask if any Federal means-tested public benefits were received by the LAPR alien or the worker in the same quarter the earnings were paid. (See SI 00502.135B.3.)\n\nAccept the allegation regarding the Federal means-tested benefit absent evidence to the contrary. If verification is required, contact the appropriate State agency administering the benefit and obtain the date(s) the individual was eligible.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500502135\n\t\nSI 00502.135 - LAPR with 40 Qualifying Quarters of Earnings - 06/21/2017\nBatch run: 10/29/2026\nRev:06/21/2017\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "46e8e60ef0426c8af21c64b6b241ed5a8da1f5efef6c6a8ea95a3eb564edf52b"
      }
    ],
    "holds": {
      "GN02402.020": [
        "Jexhibits1/2/3 are plainlabels without observedhref/media in both priorHTML andfreshDOM; do not infer formimage/report/noticecontents or guessURL.",
        "GN02406.008 (Direct Express), GN02402.023 (DDFP), GN02605.055, SI02201.007C, SM00630.070 and detailed referenced debt/appeal/waiver/input procedures are not newly reviewed by this GN page alone. Preserve prior source histories.",
        "GenericMDW/RQFA names do not establish an APP_MDW_AI alias, new graph edge or actualinterface.",
        "No date-only precedence or normalization of old source flags/history.",
        "FTitleXVIreturnedpayment/credit/remainingAOTPbalance note is not an allprogram universal recovery override."
      ],
      "SI00502.135": [
        "Samepage#d3/#d4referencebodies/chart/DEQYexample notsupplied in capturedmain; no currentrates orschema guessed.",
        "Detailed relationship140/145/GN00502definitions, disclosureGN03340.005, G845/status/continuouspresence, earnings/SEI/limits/lagprocedures and applicationlife/payment targets are not newlyreviewed by this page. Preserve priorreviewhistories.",
        "No individual lawfulstatus, marriage/adoption, earnings credit, disclosurepermission, category determination or completeSSIeligibility performed.",
        "PriorrawSIcapture notlocated/claimed; freshprimary-versus-authoredscope comparison, notpublisherfullversionredline.",
        "The proposed D2step6→step7 existingroute continuation is conditional navigation only and needs independent exacttarget/globalpredicate review before integration."
      ]
    },
    "unmapped_internal_variants": {
      "missing-direct-deposit/redirected-eft-claim-form-help": [
        "The selected six-card sequence maps C office-visit help only. D ClaimFormSent and IncompleteResent stage-specific no-action/customer30dayinstructions remain in retained raw/source history, not newly modelled as independent ordered sequences here. Further source-qualified refinements would require a separate additive-route or nested-flow proposal."
      ]
    },
    "independent_source_review_sha256": [
      "be07fd44c60247a204e9cda19d4f74f3b3cddb9014232380030b70666b3d69de",
      "e5eb33b97aa70151c383a6ac4485ce5e9339ae34737828f37dbd5ba55b208d1a"
    ],
    "captures": [
      {
        "source_code": "GN02402.020",
        "url": "/service/sources/GN02402.020-main.txt",
        "sha256": "0e383d7b99407352ccab72bb4aeef0dde766e2f3817748b19af6e4b5ce396667",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      },
      {
        "source_code": "GN02402.020",
        "url": "/service/sources/GN02402.020-DOM-snapshot.txt",
        "sha256": "f86ab7b959718a35bdf77156368cff5442db72140348aeb7f83184a17499807f",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      },
      {
        "source_code": "GN02402.020",
        "url": "/service/sources/GN02402.020-metadata.json",
        "sha256": "134c6e88ef74b6dc48350604113d0cd7860f7d618f4425799e31a08fc70682d9",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      },
      {
        "source_code": "SI00502.135",
        "url": "/service/sources/SI00502.135-main.txt",
        "sha256": "46e8e60ef0426c8af21c64b6b241ed5a8da1f5efef6c6a8ea95a3eb564edf52b",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      },
      {
        "source_code": "SI00502.135",
        "url": "/service/sources/SI00502.135-DOM-snapshot.txt",
        "sha256": "3d3fa445a6a989e3ef1b6d453a96599bf4761aec95da15def05086baf140b58a",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      },
      {
        "source_code": "SI00502.135",
        "url": "/service/sources/SI00502.135-metadata.json",
        "sha256": "cf947d29512a60f640d08cfaed572432983d44a1448d143dbe78cc9b090ebef1",
        "capture_semantics": "Whole browser main text, AX/DOM snapshot or capture metadata; not raw HTTP response bytes."
      }
    ],
    "scope": "32 existing route sequences only; earlier source objects, statuses and records remain history. No complete policy review, actual immigration/earnings/representation/payment finding, native acceptance, measured processing time or automatic case transition.",
    "conditional_navigation_limit": "One source-defined step6 to step7 reference is manual exploration only. Its target source, record, flow, journey and ancestor conditions are separately bound. Choosing it establishes no facts or completion."
  },
  "r27_existing32": {
    "schema": "securitystat.selected-source-sequence-ledger/1",
    "status": "SELECTED_32_INDEPENDENTLY_SOURCE_REVIEWED_SEQUENCE_INTEGRATION_CANDIDATE",
    "checked_on": "2026-10-31",
    "flows": {
      "appeal-medical-cessation/incomplete-ssa789-resolution": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "incomplete-ssa789-resolution",
        "full_route": "appeal-medical-cessation/incomplete-ssa789-resolution",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form."
        ],
        "steps": [
          {
            "id": "incomplete-ssa789-resolution-source-step-1",
            "title": "Check the request information",
            "kind": "ssa",
            "actor": "FO",
            "action": "Check hearing-appearance choice and interpreter or language needs when applicable, and date the SSA-789 at the top upon receipt. A signature from the individual or representative payee is not required.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form."
            ],
            "source": "focdrappealdeath",
            "section": "A.1.a",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-ssa789-resolution-source-step-2",
            "title": "Call for missing information",
            "kind": "ssa",
            "actor": "FO",
            "action": "Call the individual for the information needed to complete the SSA-789. Document the contact attempts on SSA-5002 and place a copy in the folder; this documentation is not limited to unsuccessful calls.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form."
            ],
            "source": "focdrappealdeath",
            "section": "A.1.b.1 and A.1.b.3",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-ssa789-resolution-source-step-3",
            "title": "If a call cannot obtain the information",
            "kind": "ssa",
            "actor": "FO",
            "action": "If the individual has no phone or the attempt is unsuccessful, send a call-in or come-in letter and set a 15-day diary.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form.",
              "The individual has no phone OR the telephone attempt was unsuccessful."
            ],
            "source": "focdrappealdeath",
            "section": "A.1.b.2",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-ssa789-resolution-source-step-4",
            "title": "If the hearing or interpreter question remains unanswered",
            "kind": "ssa",
            "actor": "FO",
            "action": "If the individual does not respond within the 15 days about whether they want a hearing or need an interpreter, forward the case to DDS for resolution. This is not a denial or an assumed hearing choice.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form.",
              "The source-prescribed 15-day nonresponse stage has been reached AND the unanswered matter is hearing appearance or interpreter need."
            ],
            "source": "focdrappealdeath",
            "section": "A.1.b.4",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-ssa789-resolution-source-step-5",
            "title": "Provide the applicable procedure information",
            "kind": "ssa",
            "actor": "FO",
            "action": "Provide a copy of SSA-789 if applicable and the English or Spanish SSA-888. Give local and toll-free FO and DDS numbers; explain the preference for substantive hearing questions or changes to go to DDS, while the person may call either office locally or toll-free.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-789 information is incomplete in this medical CDR reconsideration request. A missing signature alone does not establish incompleteness: the individual or payee need not sign this form."
            ],
            "source": "focdrappealdeath",
            "section": "A.1.b.5-7 and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        }
      },
      "appeal-medical-cessation/incomplete-adult-child-appeal-report": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "incomplete-adult-child-appeal-report",
        "full_route": "appeal-medical-cessation/incomplete-adult-child-appeal-report",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "SSA-3441 is incomplete or appears incorrect, or an SSA-3881 is incomplete in a Title XVI childhood disability case. The childhood form is not a universal adult requirement."
        ],
        "steps": [
          {
            "id": "incomplete-adult-child-appeal-report-source-step-1",
            "title": "Contact the person about missing or incorrect information",
            "kind": "ssa",
            "actor": "FO",
            "action": "Contact the individual when the SSA-3441 is incomplete or information appears incorrect. Apply the same actions to an incomplete SSA-3881 only in Title XVI childhood disability cases.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-3441 is incomplete or appears incorrect, or an SSA-3881 is incomplete in a Title XVI childhood disability case. The childhood form is not a universal adult requirement."
            ],
            "source": "focdrappealdeath",
            "section": "A.4.a; A.5",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A4-5"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-adult-child-appeal-report-source-step-2",
            "title": "Record observations from a telephone conversation",
            "kind": "ssa",
            "actor": "FO",
            "action": "Note any auditory observations made during the telephone conversation. An observation is not itself a disability determination.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-3441 is incomplete or appears incorrect, or an SSA-3881 is incomplete in a Title XVI childhood disability case. The childhood form is not a universal adult requirement.",
              "A relevant telephone conversation occurs."
            ],
            "source": "focdrappealdeath",
            "section": "A.4.b",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A4-5"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "incomplete-adult-child-appeal-report-source-step-3",
            "title": "Document the additional information in the applicable record",
            "kind": "ssa",
            "actor": "FO",
            "action": "Document the additional information in EDCS, SSA-3367, or electronic or paper SSA-5002 as applicable. The source separately points Title II to MCS RPOC, Title XVI to Report of Contact page, and non-MSSICS to a paper SSA-5002 added to the electronic or paper folder. These names are not interchangeable identities.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "SSA-3441 is incomplete or appears incorrect, or an SSA-3881 is incomplete in a Title XVI childhood disability case. The childhood form is not a universal adult requirement."
            ],
            "source": "focdrappealdeath",
            "section": "A.4.c.1-2; A.5",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:A4-5"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        }
      },
      "appeal-medical-cessation/concurrent-appeal-record-controls": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "concurrent-appeal-record-controls",
        "full_route": "appeal-medical-cessation/concurrent-appeal-record-controls",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation."
        ],
        "steps": [
          {
            "id": "concurrent-appeal-record-controls-source-step-1",
            "title": "Complete the SSI appeal input first",
            "kind": "ssa",
            "actor": "FO",
            "action": "Use MSSICS to document the medical appeal data on the SSR before entering EDCS. For this concurrent appeal, complete MSSICS before opening the appeal in EDCS.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.a and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-2",
            "title": "Verify that both appeal segments are established",
            "kind": "ssa",
            "actor": "FO",
            "action": "Review EDCS to verify concurrent establishment and address additional appeal questions capturing the Title II data.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.b",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-3",
            "title": "Transfer both segments together",
            "kind": "ssa",
            "actor": "FO",
            "action": "Complete the appeal in EDCS and transfer it to DDS or DHU, ensuring both titled segments are included. This instruction does not establish an actual successful transfer.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.c",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-4",
            "title": "Review both records when the determination is received",
            "kind": "ssa",
            "actor": "FO",
            "action": "Upon receipt from DDS or DHU, review SSR and MBR for the medical determination posting and whether SBC has ended for both programs as applicable. No Title II POS action is required for this stated branch.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation.",
              "The medical determination from DDS or DHU has actually been received."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.d and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-5",
            "title": "Set the record-update control",
            "kind": "ssa",
            "actor": "FO",
            "action": "The source says MBR and SSR should update within five days and directs a five-day CDRW tickle in DCF to control the check. This is a staff record-update expectation and control, not a measured appeal-completion promise.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation.",
              "The source determination-receipt and record-update control stage applies."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.e and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-6",
            "title": "If the SSR has not updated after five days",
            "kind": "ssa",
            "actor": "FO",
            "action": "Proceed with manual SSR update actions under the separately stated C.2 instructions. The selected sequence does not perform those inputs.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation.",
              "The SSR has not automatically updated in five days."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.f; C.2 linked in-page",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "record-followup"
          },
          {
            "id": "concurrent-appeal-record-controls-source-step-7",
            "title": "If the MBR has not updated after five days",
            "kind": "ssa",
            "actor": "FO",
            "action": "Verify the DIBCESS issue on PCACS and follow up with PSC as needed under GN 01070.440. If no DIBCESS issue is present OR there is no THIS-query exception, submit a DCF Problem Report through usual channels. Manual SBC termination, if necessary, is governed by the separately linked DI 12027.090.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The medical determination appeal is concurrent Title II and Title XVI. Appeal data and any applicable SBC election must be established in the real case; the sequence does not grant continuation.",
              "The MBR has not automatically updated in five days."
            ],
            "source": "focdrappealdeath",
            "section": "B.3.f and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:B3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "record-followup"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        },
        "alternative_groups": [
          {
            "id": "record-followup",
            "label": "Apply the follow-up for each record that did not update",
            "logic": "source_conditions_determine_branch",
            "note": "These conditions are independent: both record follow-ups may apply. They are not a choice that establishes a failed update."
          }
        ]
      },
      "appeal-medical-cessation/cdr-appeal-special-destinations": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "cdr-appeal-special-destinations",
        "full_route": "appeal-medical-cessation/cdr-appeal-special-destinations",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The FO is determining the actual case type before routing a medical CDR appeal folder. Selecting a destination does not establish career railroad or foreign status."
        ],
        "steps": [
          {
            "id": "cdr-appeal-special-destinations-source-step-1",
            "title": "Identify the actual case type",
            "kind": "ssa",
            "actor": "FO",
            "action": "Determine whether the case is ordinary, career railroad or foreign before selecting the source destination.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The FO is determining the actual case type before routing a medical CDR appeal folder. Selecting a destination does not establish career railroad or foreign status."
            ],
            "source": "focdrappealdeath",
            "section": "D opening",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:D"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "cdr-appeal-special-destinations-source-step-2",
            "title": "Other than career railroad or foreign",
            "kind": "ssa",
            "actor": "FO",
            "action": "Route the folder to the DDS serving the FO.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The FO is determining the actual case type before routing a medical CDR appeal folder. Selecting a destination does not establish career railroad or foreign status.",
              "The case is neither career railroad nor foreign."
            ],
            "source": "focdrappealdeath",
            "section": "D.1",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:D"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "destination"
          },
          {
            "id": "cdr-appeal-special-destinations-source-step-3",
            "title": "Career railroad case",
            "kind": "ssa",
            "actor": "FO",
            "action": "Follow the separately linked railroad procedure, include the DHU copy of SSA-789, and route the folder to GLPSC Disability Processing, P.O. Box 87755, Chicago, IL 60680-0955.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The FO is determining the actual case type before routing a medical CDR appeal folder. Selecting a destination does not establish career railroad or foreign status.",
              "The case is a career railroad case."
            ],
            "source": "focdrappealdeath",
            "section": "D.2",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:D"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "destination"
          },
          {
            "id": "cdr-appeal-special-destinations-source-step-4",
            "title": "Foreign case",
            "kind": "ssa",
            "actor": "FO",
            "action": "Include all documents in the disability folder and route to OEIO, Social Security Administration, P.O. Box 17775, Baltimore, Maryland 21235-7775. Do not send the material or an SSA-789 copy to the DDS associated with the servicing FO.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The FO is determining the actual case type before routing a medical CDR appeal folder. Selecting a destination does not establish career railroad or foreign status.",
              "The case is a foreign case."
            ],
            "source": "focdrappealdeath",
            "section": "D.3",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:D"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "destination"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        },
        "alternative_groups": [
          {
            "id": "destination",
            "label": "Use the destination for the actual case type",
            "logic": "source_conditions_determine_branch",
            "note": "These are source-conditioned alternatives, not three successive transfers."
          }
        ]
      },
      "appeal-medical-cessation/appeal-posttransfer-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "appeal-posttransfer-evidence",
        "full_route": "appeal-medical-cessation/appeal-posttransfer-evidence",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "New material or information reaches the FO after the medical CDR appeal case has left. Staff must check actual case-control location before choosing a destination."
        ],
        "steps": [
          {
            "id": "appeal-posttransfer-evidence-source-step-1",
            "title": "Record the information and check the folder location",
            "kind": "ssa",
            "actor": "FO",
            "action": "Document verbal information on SSA-5002 or another appropriate SSA form. Upload new material to the electronic folder if possible, and check the case-control system for the actual DDS or DHU location. An upload instruction does not confirm association or receipt.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "New material or information reaches the FO after the medical CDR appeal case has left. Staff must check actual case-control location before choosing a destination."
            ],
            "source": "focdrappealdeath",
            "section": "E.3 opening",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "appeal-posttransfer-evidence-source-step-2",
            "title": "Paper folder at the DDS or DHU",
            "kind": "ssa",
            "actor": "FO",
            "action": "Use SSA-408 to forward subsequent material to DDS or DHU for the applicable pending folder.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "New material or information reaches the FO after the medical CDR appeal case has left. Staff must check actual case-control location before choosing a destination.",
              "The official folder is paper and the applicable case remains at DDS or DHU; the ALJ or Appeals Council location exception does not apply."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.a first bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "evidence-location"
          },
          {
            "id": "appeal-posttransfer-evidence-source-step-3",
            "title": "Reconsideration issued and case has left the DHU",
            "kind": "ssa",
            "actor": "FO",
            "action": "Forward material to DDS, or alert DDS to material in the electronic folder, so DDS can determine relevance and the action to take. This does not make the relevance decision.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "New material or information reaches the FO after the medical CDR appeal case has left. Staff must check actual case-control location before choosing a destination.",
              "A reconsideration determination has been issued AND the case has left DHU AND it is not at an ALJ or Appeals Council location."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.a second bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "evidence-location"
          },
          {
            "id": "appeal-posttransfer-evidence-source-step-4",
            "title": "Case at an ALJ or Appeals Council location",
            "kind": "ssa",
            "actor": "FO",
            "action": "Forward the material for folder association and review to the OHO or Appeals Council office where the folder is located. Do not apply the ordinary DDS route instead.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "New material or information reaches the FO after the medical CDR appeal case has left. Staff must check actual case-control location before choosing a destination.",
              "The actual case is at an ALJ or Appeals Council location."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.a NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "evidence-location"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        },
        "alternative_groups": [
          {
            "id": "evidence-location",
            "label": "Route according to the actual stage and folder location",
            "logic": "source_conditions_determine_branch",
            "note": "The ALJ or Appeals Council location exception controls when applicable; selecting a card does not locate the real folder."
          }
        ]
      },
      "appeal-medical-cessation/appeal-posttransfer-contact": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "appeal-posttransfer-contact",
        "full_route": "appeal-medical-cessation/appeal-posttransfer-contact",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The individual reports an address or telephone change after release of the medical CDR appeal folder. Actual record type, folder format and hearing-site implications remain to be established."
        ],
        "steps": [
          {
            "id": "appeal-posttransfer-contact-source-step-1",
            "title": "Update the applicable records and send an update",
            "kind": "ssa",
            "actor": "FO",
            "action": "Update applicable Title II and Title XVI records, such as MBR, MSSICS and EDCS, and send a UAT to DDS or DHU with the new address or telephone number. The instruction is not confirmation that all systems updated.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual reports an address or telephone change after release of the medical CDR appeal folder. Actual record type, folder format and hearing-site implications remain to be established."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.b first two bullets",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "appeal-posttransfer-contact-source-step-2",
            "title": "For a paper folder, forward the address change",
            "kind": "ssa",
            "actor": "FO",
            "action": "Use SSA-408 to forward the change of address to DDS or DHU, including the office code for the FO serving the current address.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual reports an address or telephone change after release of the medical CDR appeal folder. Actual record type, folder format and hearing-site implications remain to be established.",
              "The official folder is paper and the address-change forwarding instruction applies."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.b third bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "appeal-posttransfer-contact-source-step-3",
            "title": "If a scheduled hearing must move between sites",
            "kind": "ssa",
            "actor": "FO",
            "action": "When a hearing is scheduled AND the address change involves a different DDS or DHU site, telephone DHU and send an email confirmation. DHU forwards or associates that confirmation with the folder.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual reports an address or telephone change after release of the medical CDR appeal folder. Actual record type, folder format and hearing-site implications remain to be established.",
              "A disability hearing is scheduled AND the address change involves a change in DDS or DHU site."
            ],
            "source": "focdrappealdeath",
            "section": "E.3.b fourth bullet and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E3"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        }
      },
      "appeal-medical-cessation/appeal-unprovided-information-dds": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "appeal-unprovided-information-dds",
        "full_route": "appeal-medical-cessation/appeal-unprovided-information-dds",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The individual fails or refuses to complete necessary forms or provide additional evidence needed to support the reconsideration request. This is not an inferred refusal merely because an illustration is selected."
        ],
        "steps": [
          {
            "id": "appeal-unprovided-information-dds-source-step-1",
            "title": "Forward the folder to DDS",
            "kind": "ssa",
            "actor": "FO",
            "action": "Transmit or forward the folder to DDS despite the failure or refusal to provide the necessary information.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual fails or refuses to complete necessary forms or provide additional evidence needed to support the reconsideration request. This is not an inferred refusal merely because an illustration is selected."
            ],
            "source": "focdrappealdeath",
            "section": "E.4 first sentence",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E4"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "appeal-unprovided-information-dds-source-step-2",
            "title": "Identify what is missing",
            "kind": "ssa",
            "actor": "FO",
            "action": "Use SSA-5002 to indicate the missing information and associate it with the appeal folder. This documentation does not decide the medical appeal.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual fails or refuses to complete necessary forms or provide additional evidence needed to support the reconsideration request. This is not an inferred refusal merely because an illustration is selected."
            ],
            "source": "focdrappealdeath",
            "section": "E.4 second sentence",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E4"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "appeal-unprovided-information-dds-source-step-3",
            "title": "Keep insufficient-evidence procedures separate",
            "kind": "ssa",
            "actor": "FO",
            "action": "If DDS lacks sufficient information for a medical determination, the page refers to DI 23005.001 or DI 23007.005. Their detailed rules are not supplied by this selected sequence; no automatic denial or dismissal is inferred.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual fails or refuses to complete necessary forms or provide additional evidence needed to support the reconsideration request. This is not an inferred refusal merely because an illustration is selected.",
              "DDS does not have enough information to make a medical determination."
            ],
            "source": "focdrappealdeath",
            "section": "E.4 final sentence",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E4"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        }
      },
      "appeal-medical-cessation/hearing-change-less-ten-days": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "hearing-change-less-ten-days",
        "full_route": "appeal-medical-cessation/hearing-change-less-ten-days",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The individual requests a change of disability-hearing time or place by contacting the FO rather than DHU or DHO. The less-than-ten-day alert requires the actual scheduled date; it is not a generic filing deadline."
        ],
        "steps": [
          {
            "id": "hearing-change-less-ten-days-source-step-1",
            "title": "If the person visits the FO",
            "kind": "ssa",
            "actor": "FO",
            "action": "Ensure the individual completes SSA-769-U4. The detailed form-completion reference DI 12026.026 remains separately reviewed.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual requests a change of disability-hearing time or place by contacting the FO rather than DHU or DHO. The less-than-ten-day alert requires the actual scheduled date; it is not a generic filing deadline.",
              "The individual visits the FO."
            ],
            "source": "focdrappealdeath",
            "section": "E.1.a",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "contact-method"
          },
          {
            "id": "hearing-change-less-ten-days-source-step-2",
            "title": "If the person calls the FO",
            "kind": "ssa",
            "actor": "FO",
            "action": "Obtain the information needed for SSA-769-U4. Document the telephone conversation electronically in RPOC or Report of Contact page, or on paper SSA-5002, and fax the documentation into NDRED. The source separately specifies Title II SSA-5002 and Title XVI Report of Contact page or non-MSSICS paper SSA-5002 placed in the appeal folder.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual requests a change of disability-hearing time or place by contacting the FO rather than DHU or DHO. The less-than-ten-day alert requires the actual scheduled date; it is not a generic filing deadline.",
              "The individual telephones the FO."
            ],
            "source": "focdrappealdeath",
            "section": "E.1.b.1-2",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "contact-method"
          },
          {
            "id": "hearing-change-less-ten-days-source-step-3",
            "title": "Alert DDS and associate the request",
            "kind": "ssa",
            "actor": "FO",
            "action": "Alert DDS to every request to change hearing time or place and scan or place the forms and information in the official folder. If the paper folder is already at DDS, forward the material using SSA-408.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual requests a change of disability-hearing time or place by contacting the FO rather than DHU or DHO. The less-than-ten-day alert requires the actual scheduled date; it is not a generic filing deadline."
            ],
            "source": "focdrappealdeath",
            "section": "E.1.c",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "hearing-change-less-ten-days-source-step-4",
            "title": "Fewer than ten days before the hearing",
            "kind": "ssa",
            "actor": "FO",
            "action": "If the request is less than ten days before the scheduled hearing, notify DDS by telephone OR email. Forward the request as DDS directs, such as fax, hand delivery or scanning to the folder. The source does not approve the requested change automatically.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual requests a change of disability-hearing time or place by contacting the FO rather than DHU or DHO. The less-than-ten-day alert requires the actual scheduled date; it is not a generic filing deadline.",
              "The request is less than ten days before the actual scheduled hearing date."
            ],
            "source": "focdrappealdeath",
            "section": "E.1.c NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E1"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        },
        "alternative_groups": [
          {
            "id": "contact-method",
            "label": "Document the request using the actual contact method",
            "logic": "source_conditions_determine_branch",
            "note": "The visit and telephone instructions are alternatives. Neither implies that a change was approved."
          }
        ]
      },
      "death-before-disability-hearing/fo-death-proof": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "fo-death-proof",
        "full_route": "death-before-disability-hearing/fo-death-proof",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The individual died before the medical CDR reconsideration determination was made. A reported death does not establish a substitute party or anyone’s entitlement."
        ],
        "steps": [
          {
            "id": "fo-death-proof-source-step-1",
            "title": "Update the records and associate death evidence",
            "kind": "ssa",
            "actor": "FO",
            "action": "Put the death information on the individual’s records and forward or upload proof of death to the folder. A death certificate’s cause information may help the DHO assess the medical issue; this illustration makes no causation finding.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before the medical CDR reconsideration determination was made. A reported death does not establish a substitute party or anyone’s entitlement."
            ],
            "source": "focdrappealdeath",
            "section": "E.6 opening and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6opening"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "fo-death-proof-source-step-2",
            "title": "Review leads to affected people",
            "kind": "ssa",
            "actor": "FO",
            "action": "Review the folder for people who may be entitled or adversely affected. Title II examples include a surviving spouse, auxiliary beneficiaries or an estate representative; Title XVI deceased-underpayment rules are separately linked in SI 02101.003. A lead is not an entitlement finding.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before the medical CDR reconsideration determination was made. A reported death does not establish a substitute party or anyone’s entitlement."
            ],
            "source": "focdrappealdeath",
            "section": "E.6 opening bullets",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6opening"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        }
      },
      "death-before-disability-hearing/fo-substitute-scheduled-hearing": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "fo-substitute-scheduled-hearing",
        "full_route": "death-before-disability-hearing/fo-substitute-scheduled-hearing",
        "entry_conditions": [
          "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
          "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone."
        ],
        "steps": [
          {
            "id": "fo-substitute-scheduled-hearing-source-step-1",
            "title": "Secure the substitution form",
            "kind": "ssa",
            "actor": "FO",
            "action": "Secure SSA-770-U4 for the substitute party pursuing the deceased individual’s appeal. Form instructions in DI 12026.027 remain separate.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a first bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-2",
            "title": "Explain when a hearing may be unnecessary",
            "kind": "ssa",
            "actor": "FO",
            "action": "Inform the substitute party that a hearing may not be necessary if a favorable determination can be issued on available evidence. This is a conditional explanation, not a favorable decision.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a second bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-3",
            "title": "Notify DHU of the death and party information",
            "kind": "ssa",
            "actor": "FO",
            "action": "Telephone DHU to report the death. When the substitute party wishes to appear at the scheduled hearing, tell DHU and provide the party’s name, address and telephone number.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a third bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ]
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-4",
            "title": "If the substitute party wishes to appear",
            "kind": "ssa",
            "actor": "FO",
            "action": "Inform DHU not to postpone the hearing when the substitute party has told the FO they wish to appear at the hearing scheduled for the deceased individual.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone.",
              "The substitute party informed the FO they wish to appear at the scheduled hearing."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a third bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "appearance"
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-5",
            "title": "Otherwise, pending the substitution form",
            "kind": "ssa",
            "actor": "DHU",
            "action": "Otherwise, DHU postpones a scheduled hearing pending receipt of SSA-770-U4. This instruction does not establish an actual postponement.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone.",
              "The source’s appearance-preservation condition is not met; the scheduled hearing awaits SSA-770-U4."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a third bullet",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "appearance"
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-6",
            "title": "Electronic folder",
            "kind": "ssa",
            "actor": "FO",
            "action": "Upload completed SSA-770-U4 and additional medical information to the electronic folder. If DHU differs from the former location, create the message: Substitute party requested disability hearing in your area.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone.",
              "The folder is electronic."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a fourth bullet and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "folder-format"
          },
          {
            "id": "fo-substitute-scheduled-hearing-source-step-7",
            "title": "Paper folder",
            "kind": "ssa",
            "actor": "FO",
            "action": "Use SSA-408 to route completed SSA-770-U4 copies to the component with the folder and the appropriate DHU, including additional medical information. If DHU differs, annotate: Substitute party requested disability hearing in your area - Attached forwarded for folder association.",
            "conditions": [
              "The instruction concerns an FO medical CDR reconsideration appeal. Staff must establish the actual case stage and facts; choosing this illustration does not establish an appeal, hearing right, benefit continuation election, disability or payment outcome.",
              "The individual died before reconsideration determination AND a substitute party is involved. Staff must establish actual party, appearance, folder-format and location facts; a dropdown does not appoint anyone.",
              "The folder is paper."
            ],
            "source": "focdrappealdeath",
            "section": "E.6.a fifth bullet and NOTE",
            "source_context_refs": [
              "DI12026.025-whole",
              "DI12026.025:E6a"
            ],
            "qualifications": [
              "These are published staff instructions, not an actual case finding, completed upload, transfer, system input, hearing change or benefit decision.",
              "An indicated diary or record-update expectation is a source-prescribed staff control, not measured processing time or a customer deadline calculator.",
              "Merely linked forms, system-input, evidence, appeal, reconstruction, withdrawal and eligibility instructions retain separate review limits. Current publication names do not certify current runtime, physical implementation or native record identity.",
              "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks."
            ],
            "alternative_group": "folder-format"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful case handoff, completion or return to the usual path is established by selecting this sequence. Any later route requires its own actual source conditions."
          ]
        },
        "alternative_groups": [
          {
            "id": "appearance",
            "label": "Apply the substitute party’s actual appearance position",
            "logic": "source_conditions_determine_branch",
            "note": "These conditions determine the hearing-control instruction; no choice or approval is inferred from this example."
          },
          {
            "id": "folder-format",
            "label": "Forward the substitution material for the actual folder format",
            "logic": "source_conditions_determine_branch",
            "note": "Electronic and paper processing are alternatives; neither establishes successful receipt."
          }
        ]
      },
      "report-ssi-wages/ssi-paystub-evidence-check": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-paystub-evidence-check",
        "full_route": "report-ssi-wages/ssi-paystub-evidence-check",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Pay stubs are being evaluated as SSI wage evidence under the source priority order."
        ],
        "steps": [
          {
            "id": "ssi-paystub-evidence-check-source-step-1",
            "title": "Review the required pay-stub information",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "At minimum, look for the worker’s name OR full SSN, gross wages, AND the period covered. Original electronic pay stubs and unaltered copies or faxes can be primary evidence when the required information is supplied; a pay date is handled separately.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Pay stubs are being evaluated as SSI wage evidence under the source priority order."
            ],
            "source": "ssiwageevidence",
            "section": "A.1.b; C.2.d-e",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:A",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-paystub-evidence-check-source-step-2",
            "title": "Resolve missing required information using appropriate evidence",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If required information is missing, resolve discrepancies with other primary or secondary evidence in source priority order. Missing pay dates, missing stubs and questionable credibility have their own conditions; do not demand originals in every case. The C.2.g pointer to A.2 is retained, while the explicit minimum fields are stated in A.1.b.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Pay stubs are being evaluated as SSI wage evidence under the source priority order.",
              "The pay stubs do not contain all required information or present a discrepancy that requires development."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.d-h; A.1.b; C priority",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:A",
              "SI00820.130:C2",
              "SI00820.130:Cpriority"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-wage-evidence-unobtainable": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-wage-evidence-unobtainable",
        "full_route": "report-ssi-wages/ssi-wage-evidence-unobtainable",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Acceptable primary AND secondary wage evidence cannot be obtained after the required development. A merely inconvenient or missing pay stub does not establish this fallback."
        ],
        "steps": [
          {
            "id": "ssi-wage-evidence-unobtainable-source-step-1",
            "title": "Document the unsuccessful evidence development",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Record the steps taken to obtain acceptable primary and secondary evidence and why those efforts failed on a Report of Contact. Preserve the priority order rather than treating the individual’s statement as an immediate substitute.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Acceptable primary AND secondary wage evidence cannot be obtained after the required development. A merely inconvenient or missing pay stub does not establish this fallback."
            ],
            "source": "ssiwageevidence",
            "section": "A.5; C.8; C priority",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:A",
              "SI00820.130:C7-10",
              "SI00820.130:Cpriority"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-wage-evidence-unobtainable-source-step-2",
            "title": "Obtain the individual’s statement",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Obtain a signed statement, such as SSA-795, or record the statement on a Report of Contact. Include the gross wage amount, frequency and duration, and the relevant dates received under A.5.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Acceptable primary AND secondary wage evidence cannot be obtained after the required development. A merely inconvenient or missing pay stub does not establish this fallback."
            ],
            "source": "ssiwageevidence",
            "section": "A.5; C.8",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:A",
              "SI00820.130:C7-10"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-wage-evidence-unobtainable-source-step-3",
            "title": "Apply only this documented verification fallback",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When the statement is the sole evidence after acceptable evidence could not be obtained, C.8 directs posting the alleged wages in the verified column or via 1719b with verification code 9. This specific verification fallback is distinct from routine alleged monthly reports under SI 00820.143 F.3, which use code 1; selecting this example establishes neither classification.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Acceptable primary AND secondary wage evidence cannot be obtained after the required development. A merely inconvenient or missing pay stub does not establish this fallback.",
              "The individual’s statement is the sole evidence of wages after the required primary and secondary evidence attempts were unsuccessful and documented."
            ],
            "source": "ssiwageevidence",
            "section": "C.8; A.5",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:A",
              "SI00820.130:C7-10"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-monthly-paystub-receipts": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-monthly-paystub-receipts",
        "full_route": "report-ssi-wages/ssi-monthly-paystub-receipts",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Multiple months of pay stubs are submitted for SSI wage processing. The actual processing system and whether SSIMWV can be used must be established."
        ],
        "steps": [
          {
            "id": "ssi-monthly-paystub-receipts-source-step-1",
            "title": "Use the applicable SSIMWV receipt process",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Whenever possible, process monthly pay-stub reports through SSIMWV, issue its receipt and archive the receipt in ORS. The receipt documents the wage evidence received; no additional wage-documentation action is required for that process.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Multiple months of pay stubs are submitted for SSI wage processing. The actual processing system and whether SSIMWV can be used must be established.",
              "SSIMWV is being used to process the pay-stub reports."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-monthly-paystub-receipts-source-step-2",
            "title": "Keep the months separately receipted",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If processing multiple months of pay stubs through SSIMWV, generate a separate receipt for each month. This does not combine the source’s monthly documentation into a single undifferentiated report.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Multiple months of pay stubs are submitted for SSI wage processing. The actual processing system and whether SSIMWV can be used must be established.",
              "Multiple months are processed using SSIMWV."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-monthly-paystub-receipts-source-step-3",
            "title": "SSI Claims system case without SSIMWV",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Store the wage evidence in the Evidence Portal. Alternatively, record each stub on a separate EVID or all stubs on one Report of Contact page and lock it, identifying monthly gross wages and the required source, period, gross wages, pay date if shown, employer and deductions.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Multiple months of pay stubs are submitted for SSI wage processing. The actual processing system and whether SSIMWV can be used must be established.",
              "The case is in the SSI Claims system AND SSIMWV is not used."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.c SSI Claims system cases",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "non-SSIMWV"
          },
          {
            "id": "ssi-monthly-paystub-receipts-source-step-4",
            "title": "Case outside the SSI Claims system without SSIMWV",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Store the evidence in the Evidence Portal, or record one EVID per stub or use SSA-5125 or SSA-5124 worksheets. Store completed worksheets in the Evidence Portal. Detailed worksheet and retention instructions are separately linked.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Multiple months of pay stubs are submitted for SSI wage processing. The actual processing system and whether SSIMWV can be used must be established.",
              "The case is outside the SSI Claims system AND SSIMWV is not used."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.c non-SSI Claims system cases",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "non-SSIMWV"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "non-SSIMWV",
            "label": "If SSIMWV is not used, apply the actual case-system documentation",
            "logic": "source_conditions_determine_branch",
            "note": "These are different case-system instructions, not documentation steps that all cases must perform."
          }
        ]
      },
      "report-ssi-wages/ssi-paystub-missing-date-copy": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-paystub-missing-date-copy",
        "full_route": "report-ssi-wages/ssi-paystub-missing-date-copy",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Pay stubs have no pay date, are copies, or include missing stubs. Staff must establish which of these independent conditions actually applies."
        ],
        "steps": [
          {
            "id": "ssi-paystub-missing-date-copy-source-step-1",
            "title": "Pay date is not shown",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Record the worker’s statement of the pay date, either signed or on a Report of Contact. A missing pay date is not a blanket reason to reject otherwise sufficient wage evidence.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Pay stubs have no pay date, are copies, or include missing stubs. Staff must establish which of these independent conditions actually applies.",
              "The pay stub does not show the pay date."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.d",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "paystub-condition"
          },
          {
            "id": "ssi-paystub-missing-date-copy-source-step-2",
            "title": "Pay-stub copies were submitted",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Accept copies as primary evidence. Do not recontact the individual for originals unless the copies are questionable OR earnings cannot be determined from them; document them as original stubs would be documented.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Pay stubs have no pay date, are copies, or include missing stubs. Staff must establish which of these independent conditions actually applies.",
              "Photocopied pay stubs were submitted."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.e",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "paystub-condition"
          },
          {
            "id": "ssi-paystub-missing-date-copy-source-step-3",
            "title": "Some stubs are missing but their wages can be established",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not obtain missing stubs when the wages attributable to them can be determined using other evidence, such as wage-verification information or year-to-date totals. This is a sufficiency condition, not permission to guess missing wages.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Pay stubs have no pay date, are copies, or include missing stubs. Staff must establish which of these independent conditions actually applies.",
              "Not all stubs are available AND other evidence establishes the wages attributable to the missing stubs."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.f",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "paystub-condition"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "paystub-condition",
            "label": "Apply each relevant pay-stub condition",
            "logic": "source_conditions_determine_branch",
            "note": "These conditions can overlap. They do not create a universal demand for original documents or missing stubs."
          }
        ]
      },
      "report-ssi-wages/ssi-work-ended-wage-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-work-ended-wage-evidence",
        "full_route": "report-ssi-wages/ssi-work-ended-wage-evidence",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "A worker alleges they stopped working or changed jobs. The final paycheck date may differ from the date last worked."
        ],
        "steps": [
          {
            "id": "ssi-work-ended-wage-evidence-source-step-1",
            "title": "Record both the work-ending and final-pay dates",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Accept the worker’s wage-termination report on a signed statement or Report of Contact unless there is reason to question its accuracy. Include the date last worked AND the date of the employer’s final paycheck.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A worker alleges they stopped working or changed jobs. The final paycheck date may differ from the date last worked."
            ],
            "source": "ssiwageevidence",
            "section": "E opening",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:E"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-work-ended-wage-evidence-source-step-2",
            "title": "If the statement is inaccurate or conflicts with the record",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If an accurate statement cannot be provided OR record evidence conflicts with it, obtain termination evidence in priority order: an approved wage-verification company’s employment-ended information, then an oral employer statement, then written or faxed employer evidence.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A worker alleges they stopped working or changed jobs. The final paycheck date may differ from the date last worked.",
              "The individual cannot provide an accurate statement OR record evidence conflicts with the statement."
            ],
            "source": "ssiwageevidence",
            "section": "E evidence-priority paragraphs",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:E"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-work-ended-wage-evidence-source-step-3",
            "title": "Document the evidence and issue the applicable receipt",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Store wage-termination evidence in the Evidence Portal OR document it on a Report of Contact. When a recipient, payee or authorized representative reports the termination event, issue the work-report receipt under C.10 and its separately referenced DI 13010.020 scope.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A worker alleges they stopped working or changed jobs. The final paycheck date may differ from the date last worked."
            ],
            "source": "ssiwageevidence",
            "section": "E documentation paragraph; C.10",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:E",
              "SI00820.130:C7-10"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-work-ended-wage-evidence-source-step-4",
            "title": "Develop the unemployment-benefit question",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When wage termination is alleged, develop whether unemployment benefits are being received. For an SSI recipient not receiving them, the source directs referral under SI 00510.005; its detailed conditions are not supplied here.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A worker alleges they stopped working or changed jobs. The final paycheck date may differ from the date last worked."
            ],
            "source": "ssiwageevidence",
            "section": "E CAUTION",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:E"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-nonapproved-wage-company": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-nonapproved-wage-company",
        "full_route": "report-ssi-wages/ssi-nonapproved-wage-company",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "An employer uses or refers the worker to a wage-verification company that SSA has not approved. Source evidence priority and the company-specific acceptance conditions still apply."
        ],
        "steps": [
          {
            "id": "ssi-nonapproved-wage-company-source-step-1",
            "title": "Ask the worker to obtain the evidence when required",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If the employer will not provide wage verification and refers staff to a nonapproved company, ask the worker to obtain the company’s evidence directly. The worker’s evidence is not an authorization for SSA staff to access that company’s website.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "An employer uses or refers the worker to a wage-verification company that SSA has not approved. Source evidence priority and the company-specific acceptance conditions still apply.",
              "The employer will not provide verification AND refers the request to a nonapproved company."
            ],
            "source": "ssiwageevidence",
            "section": "C.7 first paragraph; A.2.d",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C7-10",
              "SI00820.130:A"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-nonapproved-wage-company-source-step-2",
            "title": "Do not disclose information to the nonapproved company",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "SSA employees must not create online accounts, enter personal or worker information on a nonapproved website, or otherwise contact or disclose information to the nonapproved company.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "An employer uses or refers the worker to a wage-verification company that SSA has not approved. Source evidence priority and the company-specific acceptance conditions still apply."
            ],
            "source": "ssiwageevidence",
            "section": "C.7 IMPORTANT; A.2.d IMPORTANT",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C7-10",
              "SI00820.130:A"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-nonapproved-wage-company-source-step-3",
            "title": "Retain the conditional secondary-evidence boundary",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Evidence supplied by the individual may be accepted only as secondary evidence under the separately linked SI 00820.147 C.1.c conditions. This page does not newly establish those detailed conditions or replace the source priority order.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "An employer uses or refers the worker to a wage-verification company that SSA has not approved. Source evidence priority and the company-specific acceptance conditions still apply."
            ],
            "source": "ssiwageevidence",
            "section": "C.7; A.2.d; C priority",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C7-10",
              "SI00820.130:A",
              "SI00820.130:Cpriority"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-wrong-titleii-wage-form": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-wrong-titleii-wage-form",
        "full_route": "report-ssi-wages/ssi-wrong-titleii-wage-form",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "An SSI wage-verification request is being considered using SSA-L725. This form’s Title II earned-month request is distinct from SSI wage verification."
        ],
        "steps": [
          {
            "id": "ssi-wrong-titleii-wage-form-source-step-1",
            "title": "Use SSI wage-evidence instructions instead of SSA-L725",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not use SSA-L725 for Title XVI wage verification. It is a Title II form requesting amounts earned for services in a calendar month, regardless of amounts paid. Develop SSI wage evidence under the stated primary and secondary priority order instead; this illustration supplies no actual wage calculation.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "An SSI wage-verification request is being considered using SSA-L725. This form’s Title II earned-month request is distinct from SSI wage verification."
            ],
            "source": "ssiwageevidence",
            "section": "C priority-order NOTE; A; C opening",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:Cpriority",
              "SI00820.130:A"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-reported-wages-verification-exception": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-reported-wages-verification-exception",
        "full_route": "report-ssi-wages/ssi-reported-wages-verification-exception",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "A period of SSI reported-wage development is being reviewed. Staff must establish whether one of the source exceptions applies; a reported amount is not routinely redeveloped just because the case is selected."
        ],
        "steps": [
          {
            "id": "ssi-reported-wages-verification-exception-source-step-1",
            "title": "Check the exception for the actual review period",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not treat reported wages as verified if the period has an S2, K6, K7, S7, J3 or J5 diary, more than two consecutive alleged-wage months, OR more alleged months than reported and verified months combined. When an exception applies, develop all reported and alleged wages for the entire review period.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A period of SSI reported-wage development is being reviewed. Staff must establish whether one of the source exceptions applies; a reported amount is not routinely redeveloped just because the case is selected."
            ],
            "source": "ssiwageevidence",
            "section": "B.2-B.3; D.1",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:B",
              "SI00820.130:D"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-reported-wages-verification-exception-source-step-2",
            "title": "Exception applies without a wage-interface alert",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If an exception applies and no wage-interface alert for that period is present in SSR DIAR, verify wages using the evidence priority and documentation procedures in C.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A period of SSI reported-wage development is being reviewed. Staff must establish whether one of the source exceptions applies; a reported amount is not routinely redeveloped just because the case is selected.",
              "A B.3 exception applies AND no applicable wage-interface alert is present."
            ],
            "source": "ssiwageevidence",
            "section": "D.2; C opening",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:D",
              "SI00820.130:Cpriority"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "alert-route"
          },
          {
            "id": "ssi-reported-wages-verification-exception-source-step-3",
            "title": "Applicable wage-interface alert is present",
            "kind": "handoff",
            "actor": "SSA staff",
            "action": "Follow the source’s separate diary-specific development reference: K6/K7 to SI 02310.055, J3/J5 to SI 02310.056, S2 to SI 02310.062, and S7 to SI 02310.063. The linked development details are not supplied by this sequence.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "A period of SSI reported-wage development is being reviewed. Staff must establish whether one of the source exceptions applies; a reported amount is not routinely redeveloped just because the case is selected.",
              "An applicable wage-interface alert for the review period is present in SSR DIAR."
            ],
            "source": "ssiwageevidence",
            "section": "D.3",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:D"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "alert-route"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "alert-route",
            "label": "Use the development route for the actual alert condition",
            "logic": "source_conditions_determine_branch",
            "note": "An alert is a source-directed development condition, not a finding that wages, fraud or benefit amounts are incorrect."
          }
        ]
      },
      "report-ssi-wages/ssi-wrong-person-wages": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-wrong-person-wages",
        "full_route": "report-ssi-wages/ssi-wrong-person-wages",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Annual or quarterly wage evidence appears to concern someone other than the individual worker or deemor. An apparent mismatch is not an identity or fraud finding."
        ],
        "steps": [
          {
            "id": "ssi-wrong-person-wages-source-step-1",
            "title": "Do not post the apparently different person’s wages",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If the wages appear to belong to someone else, do not post them to the record. The source points potentially erroneous or duplicate earnings postings to RS 01404.140; the detailed correction procedure is not newly reviewed here.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Annual or quarterly wage evidence appears to concern someone other than the individual worker or deemor. An apparent mismatch is not an identity or fraud finding."
            ],
            "source": "ssiwageevidence",
            "section": "C.6.a identity paragraph and linked reference",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C6"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-third-party-wage-disagreement": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-third-party-wage-disagreement",
        "full_route": "report-ssi-wages/ssi-third-party-wage-disagreement",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Secondary third-party wage evidence is being considered and the worker does not agree with the information. Higher-priority evidence development and source-specific documentation requirements remain applicable."
        ],
        "steps": [
          {
            "id": "ssi-third-party-wage-disagreement-source-step-1",
            "title": "Document why higher-priority evidence was unsuccessful",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Before using secondary wage evidence, record the attempts to obtain pay stubs and approved wage-verification data and why those attempts failed on a Report of Contact.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Secondary third-party wage evidence is being considered and the worker does not agree with the information. Higher-priority evidence development and source-specific documentation requirements remain applicable."
            ],
            "source": "ssiwageevidence",
            "section": "C.4.b opening",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C4"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-third-party-wage-disagreement-source-step-2",
            "title": "Seek other evidence when the worker disagrees",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Third-party wage information may be used only when the worker agrees. If they do not agree, seek other evidence rather than posting the disputed query amount as established wages.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Secondary third-party wage evidence is being considered and the worker does not agree with the information. Higher-priority evidence development and source-specific documentation requirements remain applicable."
            ],
            "source": "ssiwageevidence",
            "section": "C.4.a-b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C4"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-third-party-wage-disagreement-source-step-3",
            "title": "Keep the agreement and documentation limits explicit",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Document agreement before using third-party evidence. For sources requiring averaging, document alleged work months; for combined primary and secondary evidence, document the combination used. Do not save IBIQ, NDNH or SASRO printouts or queries in the Evidence Portal.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Secondary third-party wage evidence is being considered and the worker does not agree with the information. Higher-priority evidence development and source-specific documentation requirements remain applicable.",
              "Staff are evaluating any subsequently usable secondary or combined evidence; a current disagreement does not establish later agreement."
            ],
            "source": "ssiwageevidence",
            "section": "C.4.a NOTE; C.4.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C4"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-annual-quarterly-wage-totals": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-annual-quarterly-wage-totals",
        "full_route": "report-ssi-wages/ssi-annual-quarterly-wage-totals",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Only annual or quarterly totals are available for missing monthly wage development. Staff must establish the worker, work months, higher-priority development and any required third-party agreement."
        ],
        "steps": [
          {
            "id": "ssi-annual-quarterly-wage-totals-source-step-1",
            "title": "Document the months actually alleged",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Ask the worker which work months the total covers and document that allegation on a signed statement or Report of Contact. Posting the work months only to the Wages page is insufficient. If the wages appear to belong to another person, do not post them.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Only annual or quarterly totals are available for missing monthly wage development. Staff must establish the worker, work months, higher-priority development and any required third-party agreement."
            ],
            "source": "ssiwageevidence",
            "section": "C.6.a; C.4.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C6",
              "SI00820.130:C4"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-annual-quarterly-wage-totals-source-step-2",
            "title": "No previously verified portion must be preserved",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Divide the annual or quarterly total by the alleged work months to derive monthly amounts. Give preference to quarterly earnings when deciding between annual and quarterly averaging.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Only annual or quarterly totals are available for missing monthly wage development. Staff must establish the worker, work months, higher-priority development and any required third-party agreement.",
              "The ordinary annual or quarterly averaging procedure applies without a previously verified portion requiring the separate C.6.b treatment."
            ],
            "source": "ssiwageevidence",
            "section": "C.6.a",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C6"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "previous-verification"
          },
          {
            "id": "ssi-annual-quarterly-wage-totals-source-step-3",
            "title": "Some months were previously verified",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Do not change verified amounts unless new evidence shows the prior determination was erroneous. Subtract verified amounts from the employer’s total, divide the remainder by the unverified alleged work months, and document the subtraction and division on a Report of Contact.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Only annual or quarterly totals are available for missing monthly wage development. Staff must establish the worker, work months, higher-priority development and any required third-party agreement.",
              "The system already shows verified wages for part of the same employer’s year or quarter being developed."
            ],
            "source": "ssiwageevidence",
            "section": "C.6.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C6"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ],
            "alternative_group": "previous-verification"
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "previous-verification",
            "label": "Apply the calculation for the actual prior-verification state",
            "logic": "source_conditions_determine_branch",
            "note": "These are conditional calculation instructions, not a wage amount or a calculator for the selected example."
          }
        ]
      },
      "report-ssi-wages/ssi-questionable-paystub-further-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-questionable-paystub-further-evidence",
        "full_route": "report-ssi-wages/ssi-questionable-paystub-further-evidence",
        "entry_conditions": [
          "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
          "Staff have an actual reason to question pay-stub credibility, such as altered or missing fields, internal or cross-stub inconsistencies, inaccurate information, or illegibility. Examples do not establish fraud."
        ],
        "steps": [
          {
            "id": "ssi-questionable-paystub-further-evidence-source-step-1",
            "title": "Identify the credibility question without deciding fraud",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Review the actual concern, distinguishing credibility problems from ordinary copies, missing dates or sufficiently documented missing stubs. Copies and electronic pay stubs are not inherently unacceptable.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Staff have an actual reason to question pay-stub credibility, such as altered or missing fields, internal or cross-stub inconsistencies, inaccurate information, or illegibility. Examples do not establish fraud."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.d-h; A.1.b",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2",
              "SI00820.130:A"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          },
          {
            "id": "ssi-questionable-paystub-further-evidence-source-step-2",
            "title": "Obtain further acceptable wage evidence",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When pay stubs are questionable, obtain further evidence under A.1.b through A.3 while preserving source priority, authorization and documentation conditions. This is not a blanket demand for originals or an automatic suspected-fraud procedure.",
            "conditions": [
              "The source concerns SSI wage evidence, not a Title II earned-month calculation or an annual earnings-record correction. Staff must establish the actual evidence, period and reporter circumstances; selecting this illustration establishes no wage amount, benefit, overpayment, fraud or reporting classification.",
              "Staff have an actual reason to question pay-stub credibility, such as altered or missing fields, internal or cross-stub inconsistencies, inaccurate information, or illegibility. Examples do not establish fraud."
            ],
            "source": "ssiwageevidence",
            "section": "C.2.h; A.1.b-A.3",
            "source_context_refs": [
              "SI00820.130-whole",
              "SI00820.130:C2",
              "SI00820.130:A"
            ],
            "qualifications": [
              "Follow the source evidence priority and any applicable authorization, worker agreement, documentation and receipt requirements. This illustration does not perform an input, query, disclosure or case determination.",
              "Merely linked wage-verification, payroll authorization, diary, evidence-retention, unemployment and program procedures retain separately recorded review limits. Named systems are not runtime or identity certification.",
              "The source C.4.a note points to C.3.b, while the complete captured page contains the relevant additional-documentation instructions under C.4.b. That pointer is preserved as a source-reference limitation; no silent publisher correction is made."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No completed evidence verification, posting, receipt or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-wage-method-choice-receipt": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-wage-method-choice-receipt",
        "full_route": "report-ssi-wages/ssi-wage-method-choice-receipt",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "A person chooses a wage-reporting method other than an automated tool. The method alone does not determine whether the report is verified, reported or alleged."
        ],
        "steps": [
          {
            "id": "ssi-wage-method-choice-receipt-source-step-1",
            "title": "Offer recruitment while respecting the chosen method",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Discuss automated reporting as required, but do not require its use or refuse a report made another way, such as mailed pay stubs. The reporter may choose their method.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A person chooses a wage-reporting method other than an automated tool. The method alone does not determine whether the report is verified, reported or alleged."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "D.1; F opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:D",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-wage-method-choice-receipt-source-step-2",
            "title": "Process according to the evidence and reporting criteria",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Apply the actual verified, reported or alleged criteria and the corresponding section F input procedure. A mailed pay-stub report is not rejected merely because it is not automated.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A person chooses a wage-reporting method other than an automated tool. The method alone does not determine whether the report is verified, reported or alleged."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F opening; E opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-wage-method-choice-receipt-source-step-3",
            "title": "Issue the receipt under the applicable method",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The source requires a receipt for wage reports submitted by recipients or their representatives, including payees, regardless of verified, reported or alleged classification. Use the applicable automated or manual receipt instructions; choosing this example does not confirm issuance.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A person chooses a wage-reporting method other than an automated tool. The method alone does not determine whether the report is verified, reported or alleged."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F opening; F.1.c; F.2.c; F.3.b",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-verified-paystub-processing": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-verified-paystub-processing",
        "full_route": "report-ssi-wages/ssi-verified-paystub-processing",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages."
        ],
        "steps": [
          {
            "id": "ssi-verified-paystub-processing-source-step-1",
            "title": "Use the pay-stub processing route that applies",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Use SSIMWV for monthly amounts submitted with pay stubs; do not use it for reports without pay stubs. For a concurrent beneficiary, enter eWork for possible Title II development first; eWork then transfers to SSIMWV for SSI input. SSIMWV prompts for the future estimate under the separately linked estimate rules.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.1.a-b",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-verified-paystub-processing-source-step-2",
            "title": "SSI Claims system case without SSIMWV",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Input the supported verified wage amount in the Verified Amount column on the Wages page. Enter an estimate starting with the month after the reported month under SI 00820.150; no estimate calculation is supplied here.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages.",
              "SSIMWV cannot process the case AND the case is in the SSI Claims system."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.1.b",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ],
            "alternative_group": "SSIMWV-fallback"
          },
          {
            "id": "ssi-verified-paystub-processing-source-step-3",
            "title": "Case outside the SSI Claims system",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Transmit the EN field through SSA-1719(B) with verification code 9. Follow the separate future-estimate instructions beginning with the month after the reported month.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages.",
              "SSIMWV cannot process the case AND the case is outside the SSI Claims system."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.1.b",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ],
            "alternative_group": "SSIMWV-fallback"
          },
          {
            "id": "ssi-verified-paystub-processing-source-step-4",
            "title": "Provide the applicable verified-wage receipt",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "With SSIMWV, issue the receipt to the recipient or payee; for an in-person report, generate and provide it immediately. If SSIMWV cannot process the report, use eWork OR DPS with SSA-L724 for the receipt.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.1.c",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-verified-paystub-processing-source-step-5",
            "title": "Keep the receipt as the evidence documentation",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Archive the SSIMWV receipt in ORS; it documents the pay-stub evidence and requires no separate documentation action. If the receipt is not issued OR is not stored in ORS, follow the separately linked SI 00820.135 and GN 00301.286 documentation procedures.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Monthly wages are submitted with pay stubs that support verified processing. Staff must assess the evidence; the presence of a partial report does not automatically establish verified monthly wages."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.1.d",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "SSIMWV-fallback",
            "label": "If SSIMWV cannot process the case, use its actual case-system fallback",
            "logic": "source_conditions_determine_branch",
            "note": "The SSI Claims system and outside-system inputs are alternatives. Neither is permission to treat an unverified report as verified."
          }
        ]
      },
      "report-ssi-wages/ssi-fo-reported-wage-classification": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-fo-reported-wage-classification",
        "full_route": "report-ssi-wages/ssi-fo-reported-wage-classification",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "The monthly wage amount is submitted directly to the FO without the underlying evidence being used as a verified report. Staff must assess all reported-wage conditions, not infer them from the selected route."
        ],
        "steps": [
          {
            "id": "ssi-fo-reported-wage-classification-source-step-1",
            "title": "Check every reported-wage condition",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Confirm the current or prior month, total gross wages based on pay-stub information in the reporter’s possession, and that all wages for the month have been received. For the current month, no further wages may be expected. Assess actual GK or temporary-period processing and the online-notice exception before classifying the report.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The monthly wage amount is submitted directly to the FO without the underlying evidence being used as a verified report. Staff must assess all reported-wage conditions, not infer them from the selected route."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.1-E.3.a,c; F.2.b.1",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-fo-reported-wage-classification-source-step-2",
            "title": "If all reported-wage conditions are met",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Input the amount in the Reported Amount column, post the future estimate in the Alleged Amount column from the following month under the separately linked instructions, and transmit to SSR. Do not use SSIMWV for reported amounts or SSA-1719(B) to transmit reported amounts; reported transmission is unavailable for cases outside the SSI Claims system.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The monthly wage amount is submitted directly to the FO without the underlying evidence being used as a verified report. Staff must assess all reported-wage conditions, not infer them from the selected route.",
              "The report concerns total gross wages for the current or immediately preceding month, is derived from pay-stub information in the reporter’s possession, and the individual has received all wages for that month. A current-month report also requires that no additional wages are expected in that month.",
              "For a report made to the FO, actual processing is before the GK cutoff OR within the temporary GK period before the recurring payment cutoff. An adverse temporary-period action requires an online GK notice; an exception to online notice issuance prevents reported classification."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.b.2 and IMPORTANT",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-fo-reported-wage-classification-source-step-3",
            "title": "Issue the manual receipt when one is not generated",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For a required receipt not automatically generated, use the Monthly Wage Reporting – Receipt notice in DPS, SSA-L724, print it locally and store it in ORS.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The monthly wage amount is submitted directly to the FO without the underlying evidence being used as a verified report. Staff must assess all reported-wage conditions, not infer them from the selected route.",
              "A receipt is required and is not automatically generated."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.c",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-fo-reported-wage-classification-source-step-4",
            "title": "Keep the reported coding and later verification distinct",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "No separate action is required to document an amount identified as reported. SSR code 0 remains unless a later verification action occurs. If reported criteria are not satisfied, assess verified or alleged processing separately; this illustration does not classify the actual amount.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The monthly wage amount is submitted directly to the FO without the underlying evidence being used as a verified report. Staff must assess all reported-wage conditions, not infer them from the selected route."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.d; E opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-alleged-wage-input": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-alleged-wage-input",
        "full_route": "report-ssi-wages/ssi-alleged-wage-input",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "The actual monthly report cannot be identified as verified or reported. A cutoff example or lack of supplied evidence alone does not decide every other source condition."
        ],
        "steps": [
          {
            "id": "ssi-alleged-wage-input-source-step-1",
            "title": "Use the alleged-wage input for this recording category",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Post to the Alleged Amount column on the SSI Claims system Wages page, or use SSA-1719(B) with verification code 1 in the EN field. Input the future estimate under the separately linked SI 00820.150 instructions. This is ordinary monthly reporting, not the distinct SI 00820.130 C.8 sole-statement verification fallback.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The actual monthly report cannot be identified as verified or reported. A cutoff example or lack of supplied evidence alone does not decide every other source condition."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "B.1; F.3.a",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:B",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-alleged-wage-input-source-step-2",
            "title": "Issue an alleged-wage receipt",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Issue the receipt through eWork OR DPS using SSA-L724. The source’s receipt duty is not removed because the amount is alleged.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The actual monthly report cannot be identified as verified or reported. A cutoff example or lack of supplied evidence alone does not decide every other source condition."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.3.b",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-alleged-wage-input-source-step-3",
            "title": "Do not confuse no current documentation action with no later development",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The source requires no documentation for the monthly wage amount identified as an allegation. This does not waive a separately applicable evidence request or later verification procedure.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The actual monthly report cannot be identified as verified or reported. A cutoff example or lack of supplied evidence alone does not decide every other source condition."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.3.c",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-ineligible-child-wage-verification": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-ineligible-child-wage-verification",
        "full_route": "report-ssi-wages/ssi-ineligible-child-wage-verification",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "The wages are actually earned by an ineligible child, not by a recipient, payee or deemor whose wages are governed by another reporter rule."
        ],
        "steps": [
          {
            "id": "ssi-ineligible-child-wage-verification-source-step-1",
            "title": "Keep the ineligible child outside reported-wage automation",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Never classify an ineligible child’s wages as reported or use the section C electronic reporting tools for them. Verify under normal wage-evidence policies, including the separately linked SI 00820.135 B; this sequence does not supply that target’s detailed steps.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "The wages are actually earned by an ineligible child, not by a recipient, payee or deemor whose wages are governed by another reporter rule."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-mywr-employer-missing": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-mywr-employer-missing",
        "full_route": "report-ssi-wages/ssi-mywr-employer-missing",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "An employer is not displayed in myWageReport. Staff have not inferred that no employer, record or reporting obligation exists."
        ],
        "steps": [
          {
            "id": "ssi-mywr-employer-missing-source-step-1",
            "title": "Check the source’s employer-display requirement",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "myWageReport displays eligible employers based on an EIN match on the SSI Claims system Wages page OR in eWork. A my Social Security account is also required to use myWageReport. A missing display does not itself establish missing employment.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An employer is not displayed in myWageReport. Staff have not inferred that no employer, record or reporting obligation exists."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "B.3; C.1",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:B",
              "SI00820.143:C"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-mywr-employer-missing-source-step-2",
            "title": "Review the relevant employer information",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The source encourages completing EIN fields when establishing or updating employers. EINs may be found on wage evidence or source-named queries, and staff may use AEQY with employer information under separate access instructions. This does not perform a query or establish an EIN.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An employer is not displayed in myWageReport. Staff have not inferred that no employer, record or reporting obligation exists."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "B.3",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:B"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-mywr-employer-missing-source-step-3",
            "title": "Use another permitted reporting method if needed",
            "kind": "you",
            "actor": "Wage reporter",
            "action": "The reporter may choose another reporting method; staff must not refuse a wage report because it is not automated. The employer’s absence from myWageReport does not confirm that any report was accepted.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An employer is not displayed in myWageReport. Staff have not inferred that no employer, record or reporting obligation exists."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "D.1; F opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:D",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-telephone-tool-failure": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-telephone-tool-failure",
        "full_route": "report-ssi-wages/ssi-telephone-tool-failure",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "A monthly SSITWR submission was unsuccessful. A report to the FO is a separate source-permitted alternative, not an automatic retry or successful report."
        ],
        "steps": [
          {
            "id": "ssi-telephone-tool-failure-source-step-1",
            "title": "Contact the local office rather than repeatedly retrying",
            "kind": "you",
            "actor": "Wage reporter",
            "action": "The source permits a reporter whose SSITWR attempt failed to call their local office to report wages instead of repeatedly attempting the automated system. No retry interval or guaranteed acceptance is supplied.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A monthly SSITWR submission was unsuccessful. A report to the FO is a separate source-permitted alternative, not an automatic retry or successful report."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.3.c",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-telephone-tool-failure-source-step-2",
            "title": "Assess the actual FO report conditions",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For the resulting office contact, assess the current or prior month, gross amount from pay-stub information, all wages received, and actual cutoff or temporary-period notice conditions. A failed tool does not waive those requirements.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A monthly SSITWR submission was unsuccessful. A report to the FO is a separate source-permitted alternative, not an automatic retry or successful report."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.1-E.3.a,c; F.2.b.1",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-telephone-tool-failure-source-step-3",
            "title": "Process and receipt only the classification established",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "If all reported criteria are satisfied, use the Reported Amount column, the source-directed future estimate, and a manual DPS SSA-L724 receipt stored in ORS. Do not use SSIMWV or SSA-1719(B) for a reported amount. If reported criteria fail, assess the separate verified or alleged instructions.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A monthly SSITWR submission was unsuccessful. A report to the FO is a separate source-permitted alternative, not an automatic retry or successful report.",
              "The report concerns total gross wages for the current or immediately preceding month, is derived from pay-stub information in the reporter’s possession, and the individual has received all wages for that month. A current-month report also requires that no additional wages are expected in that month.",
              "For a report made to the FO, actual processing is before the GK cutoff OR within the temporary GK period before the recurring payment cutoff. An adverse temporary-period action requires an online GK notice; an exception to online notice issuance prevents reported classification."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.b-c; E opening",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-mobile-deemor-paystub-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-mobile-deemor-paystub-evidence",
        "full_route": "report-ssi-wages/ssi-mobile-deemor-paystub-evidence",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "A deemor is reporting their own wages through the SSA Mobile Wage Reporting application. The source’s actual reporter and prior-month rules apply; no completed authentication or report is inferred."
        ],
        "steps": [
          {
            "id": "ssi-mobile-deemor-paystub-evidence-source-step-1",
            "title": "Use the deemor’s own authentication information",
            "kind": "you",
            "actor": "Deemor",
            "action": "For the deemor’s own wage report, authenticate with the deemor’s own SSN, name and date of birth, not the recipient’s information. The source says the deemor’s SSN is connected to the recipient record; this is policy description, not a tested connection.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A deemor is reporting their own wages through the SSA Mobile Wage Reporting application. The source’s actual reporter and prior-month rules apply; no completed authentication or report is inferred."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "C.2 and NOTE",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:C"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-mobile-deemor-paystub-evidence-source-step-2",
            "title": "Enter the pay-stub details using the chosen option",
            "kind": "you",
            "actor": "Deemor",
            "action": "SSAMWR takes individual pay-stub details. Its optional photo upload or capture can populate fields through OCR and document processing, and those images are stored in the Evidence Portal for technician wage verification. A photo option does not confirm readable evidence or successful submission.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A deemor is reporting their own wages through the SSA Mobile Wage Reporting application. The source’s actual reporter and prior-month rules apply; no completed authentication or report is inferred."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "C.2",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:C"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-mobile-deemor-paystub-evidence-source-step-3",
            "title": "Keep the automated report and evidence roles separate",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Under the source’s basic automated features, a successful prior-month report posts as reported with code 0 and generates a receipt stored in ORS. C.2 separately describes transmission to DCF for Title II involvement and Evidence Portal images for verification; none of those roles is an assumed completed action here.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "A deemor is reporting their own wages through the SSA Mobile Wage Reporting application. The source’s actual reporter and prior-month rules apply; no completed authentication or report is inferred.",
              "The report was actually successful and concerns the immediately preceding month during the current reporting month."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "C opening; C.2; F.2.a",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:C",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-automated-after-cutoff-warning": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-automated-after-cutoff-warning",
        "full_route": "report-ssi-wages/ssi-automated-after-cutoff-warning",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "An automated report was actually successful after the applicable GK cutoff. The exact reporting method and prior-month scope must be established; a warning is not rejection."
        ],
        "steps": [
          {
            "id": "ssi-automated-after-cutoff-warning-source-step-1",
            "title": "Distinguish the recommended early period from availability",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Automated SSI and concurrent reporting accepts wages for the immediately preceding month on any day of the current reporting month. Reporting in the first six days is encouraged to help avoid incorrect payments; it is not the automated acceptance cutoff.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An automated report was actually successful after the applicable GK cutoff. The exact reporting method and prior-month scope must be established; a warning is not rejection."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "C opening; D.2",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:C",
              "SI00820.143:D"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-automated-after-cutoff-warning-source-step-2",
            "title": "Apply the message for the actual reporting tool",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "After a successful post-GK-cutoff SSAMWR or SSITWR report, the stated message warns that wages might not be reflected in a future SSI payment and that a notice will explain any payment changes and appeal rights. myWageReport instead displays source-described reminders to report the next month’s wages in the first six days. Do not treat the two messages as identical.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An automated report was actually successful after the applicable GK cutoff. The exact reporting method and prior-month scope must be established; a warning is not rejection."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "D.2 myWR and SSAMWR/SSITWR paragraphs",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:D"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-automated-after-cutoff-warning-source-step-3",
            "title": "Do not turn a successful automated report into a failed report",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "For the source-described automated reported amounts, the system posts reported wages, code 0 and an automated receipt, with no additional action required by F.2.a. This is not confirmation of the selected person’s posting or a promised future payment amount.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "An automated report was actually successful after the applicable GK cutoff. The exact reporting method and prior-month scope must be established; a warning is not rejection.",
              "The source’s successful automated prior-month reporting conditions are actually met."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.a",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        }
      },
      "report-ssi-wages/ssi-missing-paystub-reported-total": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ssi-missing-paystub-reported-total",
        "full_route": "report-ssi-wages/ssi-missing-paystub-reported-total",
        "entry_conditions": [
          "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
          "Some pay stubs are missing, but staff must establish the full gross amount and every other reported-wage condition. Partial pay-stub submission is not automatically a verified monthly amount."
        ],
        "steps": [
          {
            "id": "ssi-missing-paystub-reported-total-source-step-1",
            "title": "The total can be determined from year-to-date figures",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The reporter or technician may determine the monthly gross total using year-to-date amounts on other pay stubs, subject to the other reported-wage requirements.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Some pay stubs are missing, but staff must establish the full gross amount and every other reported-wage condition. Partial pay-stub submission is not automatically a verified monthly amount.",
              "Year-to-date figures on other pay stubs establish the total gross wages."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.3.a first missing-stub bullet",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ],
            "alternative_group": "missing-total"
          },
          {
            "id": "ssi-missing-paystub-reported-total-source-step-2",
            "title": "Multiple stubs plus subsequent contact establish the missing amount",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "When several pay stubs were submitted, obtain the gross amount for missing stubs through subsequent contact, such as a telephone conversation. Example 3 illustrates this combination; its dates and amounts are not a rule for this case.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Some pay stubs are missing, but staff must establish the full gross amount and every other reported-wage condition. Partial pay-stub submission is not automatically a verified monthly amount.",
              "Multiple pay stubs were submitted AND subsequent contact establishes the gross amount for the missing stubs."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.3.a second missing-stub bullet; H Example3",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:H"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ],
            "alternative_group": "missing-total"
          },
          {
            "id": "ssi-missing-paystub-reported-total-source-step-3",
            "title": "Check the remaining reported-wage conditions",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Confirm that all monthly wages have been received, the report concerns the permitted current or prior month, and FO processing meets the applicable cutoff and notice rules. For the current month, no further wages may be expected.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Some pay stubs are missing, but staff must establish the full gross amount and every other reported-wage condition. Partial pay-stub submission is not automatically a verified monthly amount.",
              "The report concerns total gross wages for the current or immediately preceding month, is derived from pay-stub information in the reporter’s possession, and the individual has received all wages for that month. A current-month report also requires that no additional wages are expected in that month.",
              "For a report made to the FO, actual processing is before the GK cutoff OR within the temporary GK period before the recurring payment cutoff. An adverse temporary-period action requires an online GK notice; an exception to online notice issuance prevents reported classification."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "E.1-E.3; F.2.b.1",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:E",
              "SI00820.143:F"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          },
          {
            "id": "ssi-missing-paystub-reported-total-source-step-4",
            "title": "If those conditions are met, record and receipt the reported amount",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Use the Reported Amount column rather than processing an incomplete monthly pay-stub total through SSIMWV as verified. Issue the manual wage receipt and store it in ORS; no separate documentation is required for an amount identified as reported. If criteria are not met, assess the separate category instead.",
            "conditions": [
              "The source concerns SSI monthly wage reporting. Staff must establish the actual reporter, wages received, evidence, month, channel and processing stage. Selecting this illustration does not establish a successful report, receipt, wage classification, benefit amount or Title II development result.",
              "Some pay stubs are missing, but staff must establish the full gross amount and every other reported-wage condition. Partial pay-stub submission is not automatically a verified monthly amount.",
              "The report concerns total gross wages for the current or immediately preceding month, is derived from pay-stub information in the reporter’s possession, and the individual has received all wages for that month. A current-month report also requires that no additional wages are expected in that month.",
              "For a report made to the FO, actual processing is before the GK cutoff OR within the temporary GK period before the recurring payment cutoff. An adverse temporary-period action requires an online GK notice; an exception to online notice issuance prevents reported classification."
            ],
            "source": "ssimonthlywageprocessing",
            "section": "F.2.b-d; H Example3",
            "source_context_refs": [
              "SI00820.143-whole",
              "SI00820.143:F",
              "SI00820.143:H"
            ],
            "qualifications": [
              "Reported, verified and alleged are source-specific recording categories, not findings made by selecting this example. Current or prior-month rules, actual cutoff conditions, and any applicable exceptions must be established.",
              "The first six days are an encouraged reporting period; automated SSI tools accept prior-month reports on any day of the current reporting month. This sequence does not calculate a deadline, cutoff date or payment result.",
              "Linked evidence, recruitment, authorization, future-estimate, GK notice and system-input procedures retain separate review limits. A source-named app, record, query or transmission is not current runtime or native identity certification."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "No successful report, posting, verification, receipt, handoff or return to another route is established by this illustration."
          ]
        },
        "alternative_groups": [
          {
            "id": "missing-total",
            "label": "Establish the missing amount through an applicable source method",
            "logic": "source_conditions_determine_branch",
            "note": "Either source method may support the total; choosing a card does not establish the missing wages or agreement."
          }
        ]
      }
    },
    "original_records": {
      "appeal-medical-cessation/incomplete-ssa789-resolution": {
        "id": "incomplete-ssa789-resolution",
        "title": "Incomplete SSA-789 and missing signature",
        "when": "FO receives an incomplete medical-cessation reconsideration form.",
        "you": "Clarify hearing attendance and interpreter or language needs when SSA contacts you.",
        "ssa": "Check appearance and language fields and date receipt; an individual or payee signature is not required on SSA-789. Call for missing information. If no phone or contact fails, send a call-in/come-in letter, set a 15-day diary and document attempts on SSA-5002 in the folder. If hearing/interpreter questions remain unanswered after 15 days, forward to DDS for resolution.",
        "route": "FO missing-information development → DDS resolution",
        "next": "The diary controls staff follow-up; it is not an automatic denial or a new appeal deadline.",
        "source": "focdrappealdeath",
        "section": "A.1.a-b",
        "timing": "15-day staff diary in the stated incomplete-form circumstances.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/incomplete-adult-child-appeal-report": {
        "id": "incomplete-adult-child-appeal-report",
        "title": "Incomplete adult or childhood appeal report",
        "when": "SSA-3441-BK is incomplete or appears incorrect, or a childhood SSA-3881-BK is incomplete.",
        "you": "Answer SSA requests to correct or complete the report.",
        "ssa": "FO contacts the individual, notes relevant auditory observations from the call, and records additional information in EDCS, SSA-3367 or SSA-5002 as applicable. Use the Title XVI Report of Contact page, or a paper SSA-5002 associated with the folder for non-MSSICS cases. Apply the same correction actions to incomplete childhood SSA-3881-BK.",
        "route": "FO correction contact → electronic / paper appeal folder",
        "next": "The completed evidence becomes part of the appeal record.",
        "source": "focdrappealdeath",
        "section": "A.4-5",
        "timing": "No 15-day diary or processing duration specified in A.4-5.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/concurrent-appeal-record-controls": {
        "id": "concurrent-appeal-record-controls",
        "title": "Concurrent appeal segments and record follow-up",
        "when": "The medical CDR appeal covers Title II and Title XVI.",
        "you": "Keep correspondence for both programs and report record or payment concerns to SSA.",
        "ssa": "FO records the appeal in MSSICS before opening EDCS, verifies both appeal segments and transfers both to DDS or DHU. After determination, review SSR and MBR posting and benefit-continuation termination for both programs. Set a five-day CDRW control in DCF. If SSR has not updated, take manual action; if MBR has not updated, verify DIBCESS on PCACS and follow up with PSC under GN 01070.440.",
        "route": "FO → DDS / DHU → FO record review / PSC follow-up",
        "next": "Five days is a record-update control, not a payment or appeal-decision guarantee.",
        "source": "focdrappealdeath",
        "section": "B.3.a-f",
        "timing": "Records should update within five days; FO establishes a five-day control and follows exceptions.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/cdr-appeal-special-destinations": {
        "id": "cdr-appeal-special-destinations",
        "title": "Railroad and foreign appeal folder destinations",
        "when": "FO determines the type of medical CDR appeal.",
        "you": "Tell SSA about railroad service or foreign case circumstances and ask which component holds the appeal.",
        "ssa": "Send ordinary cases to the servicing FO’s DDS. For career railroad cases, send the folder with the DHU copy of SSA-789 to Great Lakes Program Service Center, Disability Processing, following DI 29005.020. For foreign cases, send all folder materials to the Office of Earnings and International Operations; do not send the materials or an SSA-789 copy to the servicing DDS.",
        "route": "FO → DDS / Great Lakes Program Service Center / Office of Earnings and International Operations",
        "next": "The destination follows the case type.",
        "source": "focdrappealdeath",
        "section": "D.1-3",
        "timing": "No routing duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/appeal-posttransfer-evidence": {
        "id": "appeal-posttransfer-evidence",
        "title": "New evidence after the appeal folder moved",
        "when": "FO receives additional evidence after transfer.",
        "you": "Give SSA the new evidence and identify your pending appeal.",
        "ssa": "Document verbal information, upload material where possible and check folder location. Send paper material by SSA-408 to DDS or DHU. After reconsideration leaves DHU, send or alert DDS for relevance review; if the folder is at ALJ or Appeals Council, send to the OHO or AC office holding it.",
        "route": "FO → component holding folder / DDS relevance review",
        "next": "Evidence routing depends on the current appeal stage.",
        "source": "focdrappealdeath",
        "section": "E.3 opening; E.3.a",
        "timing": "No completion duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/appeal-posttransfer-contact": {
        "id": "appeal-posttransfer-contact",
        "title": "Address or phone changes after transfer",
        "when": "Contact information changes after the folder leaves FO.",
        "you": "Report the new address or phone number to SSA.",
        "ssa": "Update Title II and XVI records and send an update after transfer to DDS or DHU. For paper, use SSA-408 with servicing FO code. If a scheduled hearing and address change involve a new DDS/DHU site, telephone DHU and email confirmation for folder association.",
        "route": "FO record update → DDS / DHU",
        "next": "Staff coordination does not itself confirm a new hearing date.",
        "source": "focdrappealdeath",
        "section": "E.3.b",
        "timing": "No completion duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/appeal-unprovided-information-dds": {
        "id": "appeal-unprovided-information-dds",
        "title": "Requested appeal information is not provided",
        "when": "Required forms or additional evidence remain unprovided.",
        "you": "Tell SSA if you need help completing the requested information.",
        "ssa": "FO forwards or transmits the folder to DDS, identifies the missing information on SSA-5002 and associates it with the appeal folder. If DDS lacks enough evidence for a medical determination, follow the separate whereabouts-unknown or failure-to-cooperate policies cited by E.4.",
        "route": "FO missing-information documentation → DDS",
        "next": "This FO handoff does not itself decide the appeal.",
        "source": "focdrappealdeath",
        "section": "E.4",
        "timing": "No additional deadline or processing duration specified in E.4.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "appeal-medical-cessation/hearing-change-less-ten-days": {
        "id": "hearing-change-less-ten-days",
        "title": "Time or place change close to the hearing",
        "when": "The individual asks FO to change the disability hearing.",
        "you": "Explain the requested change promptly; an in-person request uses SSA-769, while FO can collect the information by phone.",
        "ssa": "Document the request and alert DDS; associate forms with the folder, using SSA-408 for paper already at DDS. If fewer than ten days remain before the hearing, notify DDS by telephone or email and forward materials as DDS directs.",
        "route": "FO → DDS urgent alert / hearing-change materials",
        "next": "DDS forwarding instructions are for staff; the request does not guarantee approval.",
        "source": "focdrappealdeath",
        "section": "E.1.a-c",
        "timing": "Fewer than ten days triggers the stated staff alert; it is not a minimum customer filing period.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "death-before-disability-hearing/fo-death-proof": {
        "id": "fo-death-proof",
        "title": "FO death evidence and affected-party leads",
        "when": "Death occurs before reconsideration determination.",
        "you": "Respond to requests for death evidence and possible affected-party information.",
        "ssa": "Record death, associate proof with the folder and review leads to affected parties. Family or estate examples are leads, not automatic substitute qualifications.",
        "route": "FO → appeal folder / substitute development",
        "next": "SSA reviews who may act.",
        "section": "E.6 opening",
        "source": "focdrappealdeath",
        "timing": "No overall completion time specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "death-before-disability-hearing/fo-substitute-scheduled-hearing": {
        "id": "fo-substitute-scheduled-hearing",
        "title": "Preserve an already scheduled appearance",
        "when": "A substitute is involved.",
        "you": "Tell FO whether you want the already scheduled hearing.",
        "ssa": "Secure SSA-770 and telephone DHU. If appearance is requested, tell DHU not to postpone and supply contact details; otherwise postpone pending the form. Upload the form and medical evidence for an electronic folder; for paper, send SSA-408 and materials to the folder component and appropriate DHU. Notify a changed DHU of the requested local hearing.",
        "route": "FO → folder component / DHU",
        "next": "The message between offices is not a promised customer call.",
        "section": "E.6.a",
        "source": "focdrappealdeath",
        "timing": "No overall completion time specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "report-ssi-wages/ssi-paystub-evidence-check": {
        "id": "ssi-paystub-evidence-check",
        "title": "SSA needs to review the paystub evidence",
        "when": "Paystubs are used to verify SSI wages under the evidence-development rules.",
        "you": "Provide the requested unaltered wage evidence to SSA.",
        "ssa": "Check worker name or full SSN, gross wages and covered period. Accept qualifying originals, electronic employer/government-site stubs, and unaltered photocopies or facsimiles as primary evidence.",
        "route": "SSI wage-evidence review → evidence documentation",
        "next": "SSA must apply the evidence priority and other applicable checks; this does not establish an individual payment amount.",
        "source": "ssiwageevidence",
        "section": "A.1.b; C",
        "timing": "No verification completion duration specified",
        "review_status": "Selected paystub requirements checked; no real wage or identity data handled here"
      },
      "report-ssi-wages/ssi-wage-evidence-unobtainable": {
        "id": "ssi-wage-evidence-unobtainable",
        "title": "Acceptable primary and secondary wage evidence cannot be obtained",
        "when": "The required evidence-development attempts do not yield acceptable primary or secondary evidence.",
        "you": "State the wage amounts, frequency and dates received when SSA requests that information.",
        "ssa": "Accept the individual’s statement signed or recorded on a Report of Contact, including those wage details.",
        "route": "SSI evidence-priority development → conditional statement documentation",
        "next": "This is a fallback after evidence development, not permission to skip available evidence. Staff records the Report of Contact.",
        "source": "ssiwageevidence",
        "section": "A.5; C",
        "timing": "No development or processing duration specified",
        "review_status": "Selected fallback checked; full evidence hierarchy and documentation exceptions remain"
      },
      "report-ssi-wages/ssi-monthly-paystub-receipts": {
        "id": "ssi-monthly-paystub-receipts",
        "title": "SSA processes paystubs for multiple months",
        "when": "Monthly paystub reports are processed using SSIMWV.",
        "you": "Keep the receipt for each reported month.",
        "ssa": "Whenever possible use SSIMWV; issue and archive receipts to ORS. Generate a separate receipt for each month when processing multiple months.",
        "route": "SSI wage processing → monthly receipt/archive",
        "next": "A receipt acknowledges the report/evidence; it does not guarantee the correct payment or posting date.",
        "source": "ssiwageevidence",
        "section": "C.2.b; C.10",
        "timing": "No processing or receipt-delivery duration specified",
        "review_status": "Selected evidence/receipt action checked; full related policy remains"
      },
      "report-ssi-wages/ssi-paystub-missing-date-copy": {
        "id": "ssi-paystub-missing-date-copy",
        "title": "Paystubs have no pay date or are copies",
        "when": "SSA reviews incomplete or copied paystubs.",
        "you": "Give the pay date if requested; provide available unaltered copies.",
        "ssa": "Record a missing pay date from the worker’s signed statement or Report of Contact. Do not demand originals unless copies are questionable or insufficient; do not obtain missing stubs when other evidence determines those wages.",
        "route": "SSI wage-evidence review → documented resolution",
        "next": "Staff documents the statement. Other evidence checks remain applicable.",
        "source": "ssiwageevidence",
        "section": "C.2.d–f",
        "timing": "No processing or receipt-delivery duration specified",
        "review_status": "Selected evidence/receipt action checked; full related policy remains"
      },
      "report-ssi-wages/ssi-work-ended-wage-evidence": {
        "id": "ssi-work-ended-wage-evidence",
        "title": "Work ended or the employer changed",
        "when": "The worker reports wage termination.",
        "you": "Give the last work date and final paycheck date.",
        "ssa": "Accept a signed statement or staff Report of Contact unless accuracy is questionable. If inaccurate or conflicting, obtain primary evidence in the prescribed priority; document and issue a work-report receipt.",
        "route": "SSI termination-evidence review → receipt",
        "next": "Last work and final paycheck dates may differ. Related unemployment-benefit development is separate.",
        "source": "ssiwageevidence",
        "section": "E; C.10",
        "timing": "No processing or receipt-delivery duration specified",
        "review_status": "Selected evidence/receipt action checked; full related policy remains"
      },
      "report-ssi-wages/ssi-nonapproved-wage-company": {
        "id": "ssi-nonapproved-wage-company",
        "title": "The employer uses a nonapproved wage-verification company",
        "when": "Higher-priority evidence is unavailable and the nonapproved-company route is considered.",
        "you": "Obtain the requested evidence directly from the company.",
        "ssa": "Treat qualifying worker-supplied information as secondary evidence subject to the linked conditions. Staff must not create accounts, enter personal information or contact/disclose to the nonapproved company.",
        "route": "Worker obtains evidence → SSA secondary-evidence review",
        "next": "The worker’s collection role differs from SSA evidence acceptance; acceptance is not automatic.",
        "source": "ssiwageevidence",
        "section": "A.2.d; C.7",
        "timing": "No evidence-development duration specified",
        "review_status": "Selected evidence/form/verification condition checked; linked detailed conditions remain"
      },
      "report-ssi-wages/ssi-wrong-titleii-wage-form": {
        "id": "ssi-wrong-titleii-wage-form",
        "title": "The wage request uses SSA-L725 for an SSI review",
        "when": "SSA is developing Title XVI wages.",
        "you": "Ask SSA which wage evidence is needed.",
        "ssa": "Do not use SSA-L725 for Title XVI verification; its Title II earned-for-services amounts differ from wages paid. Use the applicable SSI evidence-development route.",
        "route": "SSI wage-evidence review",
        "next": "A form used for Title II is not automatically suitable for SSI.",
        "source": "ssiwageevidence",
        "section": "C priority-order note",
        "timing": "No evidence-development duration specified",
        "review_status": "Selected evidence/form/verification condition checked; linked detailed conditions remain"
      },
      "report-ssi-wages/ssi-reported-wages-verification-exception": {
        "id": "ssi-reported-wages-verification-exception",
        "title": "An exception requires verifying previously reported wages",
        "when": "The B.3 diary or alleged-month exception applies during the review period.",
        "you": "Provide requested wage evidence and explain any disputed amounts.",
        "ssa": "Develop all wages in the review period. Check the specified SSR diaries, more than two consecutive alleged months, or alleged months exceeding reported/verified months combined; use diary-specific instructions if an interface alert exists, otherwise the C evidence priority.",
        "route": "SSI verification review → applicable diary/evidence development",
        "next": "Staff checks record diaries; the customer supplies wage facts. Do not assume every reported amount requires redevelopment.",
        "source": "ssiwageevidence",
        "section": "B.2–B.3; D.1–D.3",
        "timing": "No evidence-development duration specified",
        "review_status": "Selected evidence/form/verification condition checked; linked detailed conditions remain"
      },
      "report-ssi-wages/ssi-wrong-person-wages": {
        "id": "ssi-wrong-person-wages",
        "title": "The wages appear to belong to another person",
        "when": "The wage evidence appears inconsistent with the worker or deemor’s identity.",
        "you": "Explain which employer or wages you dispute.",
        "ssa": "Do not post wages that appear to belong to another person. Use the separate erroneous/duplicate earnings-development policy when applicable.",
        "route": "SSI wage-evidence review → separate earnings-record development as applicable",
        "next": "Not posting the disputed SSI wages does not itself correct an annual earnings record.",
        "source": "ssiwageevidence",
        "section": "C.6.a",
        "timing": "No evidence-resolution duration specified",
        "review_status": "Selected evidence safeguard checked; full linked correction policy remains"
      },
      "report-ssi-wages/ssi-third-party-wage-disagreement": {
        "id": "ssi-third-party-wage-disagreement",
        "title": "You disagree with the third-party wage evidence",
        "when": "SSA considers the specified secondary third-party queries.",
        "you": "State whether the wage information and work months are correct.",
        "ssa": "Document unsuccessful higher-priority evidence attempts and required worker agreement; seek other evidence when the worker disagrees.",
        "route": "SSI secondary-evidence review → alternative evidence development",
        "next": "A third-party query is not conclusive merely because it exists.",
        "source": "ssiwageevidence",
        "section": "C.4.b",
        "timing": "No evidence-resolution duration specified",
        "review_status": "Selected evidence safeguard checked; full linked correction policy remains"
      },
      "report-ssi-wages/ssi-annual-quarterly-wage-totals": {
        "id": "ssi-annual-quarterly-wage-totals",
        "title": "Only annual or quarterly totals cover the missing months",
        "when": "SSA uses period totals with previously verified months.",
        "you": "Identify the months you actually worked.",
        "ssa": "Document work-month allegations separately from Wages-page input. Preserve verified amounts unless new evidence shows error; subtract them from period totals and allocate the remainder to unverified alleged work months, documenting the calculation.",
        "route": "SSI wage documentation → supported monthly allocation",
        "next": "This describes staff calculation/documentation; no individual amount is calculated here.",
        "source": "ssiwageevidence",
        "section": "C.6.a–b",
        "timing": "No evidence-resolution duration specified",
        "review_status": "Selected evidence safeguard checked; full linked correction policy remains"
      },
      "report-ssi-wages/ssi-questionable-paystub-further-evidence": {
        "id": "ssi-questionable-paystub-further-evidence",
        "title": "SSA needs more evidence because a pay stub is unclear or inconsistent",
        "when": "SSA questions the credibility of a pay stub because of missing or altered fields, inconsistent information, apparent inaccuracies, or damage or reproduction problems that make it hard to read.",
        "you": "Explain the problem and provide available clearer records or other wage evidence SSA requests. Keep unaltered copies; ask which information needs clarification.",
        "ssa": "SI00820.130C.2.h directs further wage evidence under A.1.b through A.3 when pay-stub credibility is questioned. Its examples include field changes or omissions, inconsistencies within or across stubs, inaccurate information and illegibility from damage or reproduction problems. Continue the applicable evidence review; ordinary qualifying copies remain permitted and the separate missing-date or missing-stub rules still apply.",
        "owner": "SSA office developing SSI wage evidence",
        "route": "Questioned paystub -> clarification and further acceptable wage evidence -> SSA evidence review/documentation",
        "next": "Ask what evidence remains needed. An unclear or inconsistent pay stub alone does not establish fraud or decide your payment.",
        "source": "ssiwageevidence",
        "section": "C.2.h whole; A.1.b-A.3 and C.2.d-g evidence boundaries",
        "timing": "This subsection gives no fixed evidence-review or payment-adjustment deadline.",
        "review_status": "WholeC2h withA/Ccontext checked2026-10-27. SSI paystub evidence credibility review only; not TitleII earnedmonth or annualearningsrecordcorrection. Unaltered copies/electronicstubs remain permissible primary evidence when requiredinformation supplied; no blanketoriginal-only demand. Questionableexamples include altered/missingfields, internal/crossstub inconsistencies,inaccurateinformation,illegibledamage/printing/copying/faxproblems. Credibilityquestion requires further acceptable wage evidence underA1b-A3; not automaticfraudfinding. Missingpaydate/missingstub/YTD sufficiency retain existingseparate branches. Evidencepriority/workeragreement and required documentation remain applicable; no skip of preferredsources. Customerexplanation editorial; SSAobtains/evaluates evidence andrecords determinations, no customerdrafted internalrecord demand. No individualwage/paymentamount,overpayment,frauddecision or processingdeadline implied.",
        "source_receipt": {
          "report": "service-SSI-paystub-C2h-integration-gate.json",
          "snapshot_path": "sources/ssi-wage130-current-20261027.html",
          "snapshot_sha256": "27ba4e8a25a42e2453e09da4ff7154de1c340bc43534a656c8730e1c667deed6",
          "checked_on": "2026-10-27"
        }
      },
      "report-ssi-wages/ssi-wage-method-choice-receipt": {
        "id": "ssi-wage-method-choice-receipt",
        "title": "You choose a wage-reporting method other than an automated tool",
        "when": "A recipient or representative submits monthly wages by another method, such as mailed pay stubs.",
        "you": "Choose a suitable reporting method and retain the wage-report receipt.",
        "ssa": "Discuss automated reporting options, but accept reports made by other permitted methods. Classify wages as verified, reported or alleged for processing. Issue a receipt for every wage report by a recipient or representative, including a representative payee, regardless of classification.",
        "route": "SSA wage intake → appropriate wage processing → receipt",
        "next": "Automated reporting is a choice. Receipt issuance does not itself determine the payment amount.",
        "source": "ssimonthlywageprocessing",
        "section": "D.1; F opening",
        "timing": "These paragraphs give no universal receipt-delivery interval; method-specific rules require separate review.",
        "review_status": "Official selected subsections independently checked 2026-10-17"
      },
      "report-ssi-wages/ssi-verified-paystub-processing": {
        "id": "ssi-verified-paystub-processing",
        "title": "Pay stubs support verified monthly wages",
        "when": "SSA receives the monthly wage report with pay stubs.",
        "you": "Provide the requested pay stubs and keep the receipt.",
        "ssa": "Use SSIMWV for pay-stub input; otherwise use the SSI Wages-page Verified Amount field, or SSA-1719(B) EN code 9 for cases outside the claim system. For concurrent benefits, enter eWork for possible Title II development before SSIMWV. Enter the following-month wage estimate under SI00820.150. Issue and archive the SSIMWV receipt in ORS; fallback receipts use eWork or DPS SSA-L724. If receipt issuance or storage fails, apply the cited evidence-documentation rules.",
        "route": "SSA wage technician → eWork if concurrent → SSIMWV / applicable fallback → ORS",
        "next": "The receipt documents submitted evidence; future wage estimates remain a separate input.",
        "source": "ssimonthlywageprocessing",
        "section": "F.1.a-d",
        "timing": "For in-person reports processed with SSIMWV, generate and provide the receipt immediately. No benefit-adjustment completion time is stated.",
        "review_status": "Official selected procedure checked 2026-10-17; linked estimate/evidence manuals require separate review"
      },
      "report-ssi-wages/ssi-fo-reported-wage-classification": {
        "id": "ssi-fo-reported-wage-classification",
        "title": "You report pay-stub totals directly to the field office",
        "when": "The report concerns total gross wages for the current or immediately prior month.",
        "you": "Explain the wage period and whether totals come from pay stubs in your possession.",
        "ssa": "Check the period, pay-stub basis and processing cutoff. Current-month wages qualify only when no more wages are expected. Apply the temporary-period adverse-action notice rule and its exception. If classified as reported, enter Reported Amount, a following-month Alleged Amount estimate and transmit to SSR. Do not use SSIMWV or SSA-1719(B) for reported amounts. Issue a missing automated receipt through DPS SSA-L724 and store it in ORS.",
        "route": "Field office → classification/cutoff check → SSI Wages page → SSR and receipt",
        "next": "Staff determines the wage classification and applicable notice; customers do not operate SSA records or issue notices.",
        "source": "ssimonthlywageprocessing",
        "section": "E.1-3; F.2.b-c",
        "timing": "The cutoff controls staff classification and payment processing; it is not a promise of adjustment by a specific date.",
        "review_status": "Official selected subsections checked 2026-10-17; linked notice exceptions require separate review"
      },
      "report-ssi-wages/ssi-alleged-wage-input": {
        "id": "ssi-alleged-wage-input",
        "title": "The wage amount is classified as alleged",
        "when": "The monthly report does not qualify as verified or reported wages.",
        "you": "Keep the receipt and provide pay stubs if requested.",
        "ssa": "Post Alleged Amount on the SSI Wages page, or transmit SSA-1719(B) EN verification code 1 to SSR. Input a future estimate under SI00820.150. Issue the receipt using eWork or DPS SSA-L724. An allegation alone requires no separate documentation. In the late-cutoff example, request pay stubs after entering the allegation and issuing the receipt.",
        "route": "SSA wage technician → Alleged Amount / applicable SSR input → receipt and evidence request",
        "next": "Alleged classification does not establish verified wages or the correctness of a payment.",
        "source": "ssimonthlywageprocessing",
        "section": "F.3; H example 2",
        "timing": "The example illustrates a passed processing cutoff; its calendar day is not a universal reporting deadline.",
        "review_status": "Official selected subsections checked 2026-10-17"
      },
      "report-ssi-wages/ssi-ineligible-child-wage-verification": {
        "id": "ssi-ineligible-child-wage-verification",
        "title": "The wages are an ineligible child’s wages",
        "when": "SSA reviews wage information for an ineligible child in the SSI case.",
        "you": "Report relevant changes and provide requested wage evidence through the field office.",
        "ssa": "Do not classify these wages as reported or use the electronic reporting methods described in SI00820.143C. Follow normal wage-verification policy under SI00820.135B. This processing exception does not remove relevant household/deeming reporting duties.",
        "route": "Field office → normal wage-evidence verification",
        "next": "The reporting channel and wage classification do not by themselves decide how income affects SSI.",
        "source": "ssimonthlywageprocessing",
        "section": "E opening",
        "timing": "No verification completion interval specified.",
        "review_status": "Official subsection checked 2026-10-17; no individual deeming conclusion"
      },
      "report-ssi-wages/ssi-mywr-employer-missing": {
        "id": "ssi-mywr-employer-missing",
        "title": "Your employer does not appear in myWageReport",
        "when": "The employer cannot be selected for online wage reporting.",
        "you": "Contact SSA with the employer and wage information needed for review.",
        "ssa": "Check the employer information and EIN match in the SSI claim system or eWork. Technicians are encouraged to complete EIN fields when establishing or updating employers; missing EIN information prevents myWR reporting for that employer.",
        "route": "Customer → SSA employer/EIN review → appropriate reporting method",
        "next": "Do not assume the customer can edit SSA employer records through myWR.",
        "section": "B.3; C.1",
        "timing": "No employer-display or correction completion period specified.",
        "source": "ssimonthlywageprocessing",
        "review_status": "Official selected subsections checked 2026-10-17"
      },
      "report-ssi-wages/ssi-telephone-tool-failure": {
        "id": "ssi-telephone-tool-failure",
        "title": "The automated telephone wage report does not succeed",
        "when": "The reporter cannot submit wages through SSITWR.",
        "you": "Call the local office to report the wages rather than repeatedly trying the automated system.",
        "ssa": "Accept the direct report and apply the wage-period, pay-stub-basis and cutoff criteria for its proper classification and receipt.",
        "route": "SSITWR unsuccessful → local field office wage intake",
        "next": "Changing reporting channel does not waive verification or classification conditions.",
        "section": "E.3.c; F opening",
        "timing": "No guarantee of same-day input or payment adjustment.",
        "source": "ssimonthlywageprocessing",
        "review_status": "Official selected subsections checked 2026-10-17"
      },
      "report-ssi-wages/ssi-mobile-deemor-paystub-evidence": {
        "id": "ssi-mobile-deemor-paystub-evidence",
        "title": "A deemor reports their own wages in the mobile app",
        "when": "A person whose wages are deemed uses SSAMWR for their own wages.",
        "you": "Authenticate with your own identifying information, rather than the recipient’s. Enter individual pay-stub details; photos are an available option.",
        "ssa": "The app links the deemor wage report through the associated record. Uploaded or captured pay-stub images are stored in EP for technician access during wage verification; automated reports generate a receipt stored in ORS.",
        "route": "SSAMWR → wage record and receipt → EP evidence review when needed",
        "next": "The customer does not manage SSA’s evidence repository. A photo upload does not by itself establish every verification or payment outcome.",
        "source": "ssimonthlywageprocessing",
        "section": "C opening; C.2",
        "timing": "Qualifying automated SSI/prior-month reports are accepted during the current reporting month; first-six-day encouragement is separate from a processing guarantee.",
        "review_status": "Official selected subsections checked 2026-10-17; detailed DCF handoff not fully verified"
      },
      "report-ssi-wages/ssi-automated-after-cutoff-warning": {
        "id": "ssi-automated-after-cutoff-warning",
        "title": "The wage report succeeds after the payment cutoff",
        "when": "SSAMWR or SSITWR accepts a report after the applicable GK cutoff.",
        "you": "Keep the confirmation and receipt; read any subsequent payment-change notice.",
        "ssa": "The tool warns that the reported wages might not appear in a future payment. If the payment amount changes, SSA mails a notice explaining the change and appeal rights. Qualifying automated reported wages post to the SSI Wages page and SSR and generate an automated receipt.",
        "route": "Successful automated report → wage posting/receipt → payment-change notice when applicable",
        "next": "Successful submission does not guarantee the next payment reflects the report.",
        "source": "ssimonthlywageprocessing",
        "section": "D.2; F.2.a",
        "timing": "Reports are accepted throughout the current reporting month for qualifying prior-month wages; first-six-day encouragement does not limit that acceptance. No notice mailing interval is stated.",
        "review_status": "Official selected subsections checked 2026-10-17"
      },
      "report-ssi-wages/ssi-missing-paystub-reported-total": {
        "id": "ssi-missing-paystub-reported-total",
        "title": "Some pay stubs are missing but gross wages can be established",
        "when": "The reporter supplies only part of the month’s pay-stub information.",
        "you": "Provide available stubs and answer questions about missing pay amounts.",
        "ssa": "Determine the complete gross total from year-to-date figures on other stubs, or obtain missing gross amounts through subsequent contact when multiple stubs were submitted. Apply all reported-wage period and cutoff criteria. The cited example combines stubs with phone-supplied missing amounts, enters Reported Amount and issues a receipt.",
        "route": "Field office → complete gross-total development → proper classification and receipt",
        "next": "A partial set does not automatically establish reported wages. Existing evidence rules for missing stubs remain distinct from this classification route.",
        "source": "ssimonthlywageprocessing",
        "section": "E.3.a; H example 3",
        "timing": "The example’s reported classification depends on processing before the cutoff; no completion interval guaranteed.",
        "review_status": "Official selected subsections checked 2026-10-17"
      }
    },
    "source_contexts": [
      {
        "id": "DI12026.025:A1",
        "source_code": "DI12026.025",
        "locator": "A1",
        "start": 509,
        "end": 2667,
        "exact_text": "SSA-789 (Request for Reconsideration Disability Cessation Right to Appear)\n\nWhen processing the form SSA-789, the FO must:\n\na. \n\nCheck that the form is complete with the following information.\n\n1. \n\nThe individual indicated whether they wish to appear at the disability hearing;\n\n2. \n\nThe individual completed the block for 'interpreter' and 'language' needs, if applicable;\n\n3. \n\nThe individual or representative payee does not need to sign the form; and\n\n4. \n\nThe FO must date the SSA-789 at the top of the form upon receipt.\n\nNOTE: \n\nA completed Modernized Supplemental Security Income Claims System (MSSICS) appeals output can act in place of the SSA-789 in Title XVI and concurrent cases if the individual also provides a clear written indication of dissatisfaction with the initial CDR determination.\n\nb. \n\nIf the SSA-789 is incomplete, take the following actions.\n\n1. \n\nCall the individual for the necessary information.\n\n2. \n\nIf the individual has no phone or the attempt is not successful, send a call-in/come-in letter and set a 15-day diary.\n\n3. \n\nThe FO must document attempts to contact the individual on an SSA-5002 (Report of Contact). The FO must place a copy of the SSA-5002 in the folder.\n\n4. \n\nIf the individual does not respond within the 15 days regarding whether they want a hearing or need an interpreter, forward the case to the disability determination services (DDS) for resolution.\n\n5. \n\nProvide the individual with a copy of the SSA-789 if applicable.\n\n6. \n\nProvide the individual with the English or Spanish version of the form SSA-888 (Reconsideration/Disability Hearing Procedures). Versions of these documents are located in DI 33095.025 or DI 33095.030.\n\n7. \n\nProvide the individual with the local and toll free telephone numbers for the FO and DDS in their service area. Explain to the individual that we prefer they call the DDS with substantive questions or if they need to report a change related to the disability hearing.\n\nNOTE: \n\nThe Social Security Administration (SSA) does not expect individuals to make long distance phone calls. Individuals may call either the FO or DDS using the local or toll free number.\n\n2. \n",
        "sha256": "87c32cd59ec638bf1fca31f87c94b36a746e6c10991367c3d3640ceedfb285a8"
      },
      {
        "id": "DI12026.025:A4-5",
        "source_code": "DI12026.025",
        "locator": "A4-5",
        "start": 3103,
        "end": 4317,
        "exact_text": "SSA-3441-BK (Disability Report Appeal)\n\nThe FO must verify that form SSA-3441-BK is complete. If the form is incomplete, the FO must take the following actions:\n\na. \n\nContact the individual if the SSA-3441-BK received was not fully completed or any information appears to be incorrect.\n\nb. \n\nNote if there are any auditory observations made during the telephone conversation with the individual.\n\nc. \n\nDocument additional information that you received from the individual in the Electronic Disability Collect System (EDCS), the form-3367 (Disability Report - Field Office) or on an electronic or paper form SSA-5002 (Report of Contact).\n\n1. \n\nFor Title II cases, see MS MCS 008.007 (Report of Contact [RPOC]); and\n\n2. \n\nFor Title XVI cases, when documenting the report of contact in:\n\na. \n\nReport of Contact page.\n\nb. \n\nNon-MSSICS, prepare a paper form SSA-5002 to document the additional information and add this form to the electronic or paper folder.\n\n5. \nSSA-3881-BK (Questionnaire for Children Claiming SSI Benefits)\n\nIn Title XVI childhood disability cases, the FO must verify that form SSA-3881-BK is complete. If the form is incomplete, take the same actions described in DI 12026.025A.4 in this section.\n\n",
        "sha256": "9ad5bc1fc35c2cddbf798fa1f5045eac7a9c4e66d03ddd4f66ec9d30c4924c33"
      },
      {
        "id": "DI12026.025:B3",
        "source_code": "DI12026.025",
        "locator": "B3",
        "start": 7348,
        "end": 9099,
        "exact_text": "Concurrent (Title II and Title XVI)\n\nFor concurrent (Title II and Title XVI) cases, the FO must complete the following:\n\na. \n\nFirst, use MSSICS to document the medical determination appeal data on the SSR prior to entering EDCS.\n\nNOTE: \n\nIf the case is a concurrent appeal, the FO must first complete MSSICS prior to opening the appeal in EDCS.\n\nb. \n\nReview EDCS to verify the concurrent establishment of the appeal segments. Proceed with addressing additional appeal questions that will capture the Title II appeal data.\n\nc. \n\nIn EDCS, complete and transfer the medical determination appeal to the DDS or DHU. Ensure both the Title II and Title XVI segments are included in the case transfer.\n\nd. \n\nUpon receipt of the medical determination from the DDS or DHU:\n\n1. \n\nReview both the SSR and MBR to ensure medical appeal determination automatically posted; and\n\n2. \n\nThat SBC benefits have ended for both titled programs.\n\nNOTE: \n\nNo POS action is required for the Title II claim.\n\ne. \n\nThe MBR and SSR should both update within five days.\n\nNOTE: \n\nThe FO will place a tickle for 5 days on the CDRW in the DCF to establish a control to ensure the SSR and MBR are updated.\n\nf. \n\nIf the SSR does not automatically update in five days, the FO must proceed with manual actions to update the SSR. If the MBR does not automatically update in five days, verify that the DIBCESS issue is pending on PCACS and follow-up with the PSC as necessary. Refer to GN 01070.440 for follow-up timeframes.\n\nNOTE: \n\nTitle II updates: If there is no DIBCESS issue on PCACS, or no exception on the THIS query, the FO should submit a DCF Problem Report through their usual channels. If manual actions are necessary to terminate the SBC payments, refer to DI 12027.090.\n\n4. \n",
        "sha256": "b5faa71a84c405232fceecf677f3f5496b3c9fa152391a22aaedd9126f1d891f"
      },
      {
        "id": "DI12026.025:D",
        "source_code": "DI12026.025",
        "locator": "D",
        "start": 13548,
        "end": 14656,
        "exact_text": "D. \nRouting the CDR appeal folder\n\nTo establish where to route the CDR appeal folder, first determine the case type.\n\n1. \nCases other than career railroad or foreign cases\n\nRoute the folder to the servicing FOs DDS.\n\n2. \nCareer railroad case\n\nRoute the folder(s) to the Great Lakes Program Service Center (GLPSC):\n\n•\n\nFollow the procedures for processing railroad cases in DI 29005.020 (Career Railroad and Railroad Annuitant Reconsideration Continuing Disability Review (CDR) Requests).\n\n•\n\nInclude the DHU copy of the SSA-789 in the disability folder(s) and route the folder to:\n\nGLPSC, Disability Processing\nP.O. Box 87755\nChicago, IL 60680-0955\n3. \nForeign case\n\nDo not forward documents or information to the DDS associated with the servicing FO.\n\n•\n\nInclude all documents and information in the disability folder and route the folder to the Office of Earnings and International Operations (OEIO). Do not forward a copy of the SSA-789 to the DDS.\n\n•\n\nForward all materials to:\n\nSocial Security Administration\nOffice of Earnings and International Operations\nP.O. Box 17775\nBaltimore, Maryland 21235-7775\n",
        "sha256": "7d50ccf80cd37cd973bcc112b292cc91b002a341774aa8eb461d0d3fa24f88c6"
      },
      {
        "id": "DI12026.025:E1",
        "source_code": "DI12026.025",
        "locator": "E1",
        "start": 14741,
        "end": 16583,
        "exact_text": "Requesting a change in time or place of the disability hearing\n\nIf the disabled individual contacts the FO, rather than the DHU or the disability hearing officer (DHO), take the actions according to how the individual makes contact.\n\na. \nIndividual visits the FO\n\nEnsure the individual completes an SSA-769-U4 (Request for Change in Time/Place of Disability Hearing). For an exhibit of the form and instructions for its completion, see DI 12026.026 (Completion of the SSA-769-U4 Request for Change in Time/Place of Disability Hearing).\n\nb. \nIndividual telephones the FO\n\nObtain the information you need to complete the SSA-769-U4. The FO must document the information obtained in the telephone conversation electronically (RPOC/or Report of Contact page), or on a paper SSA-5002 (Report of Contact) and fax it into the Non-Disability Repository for Evidentiary Documents (NDRED).\n\n1. \n\nFor Title II, document the contact in an SSA-5002.\n\n2. \n\nFor Title XVI, document the report of contact in:\n\n•\n\nReport of Contact page\n\n•\n\nNon-MSSICS, prepare a paper SSA-5002 and place a copy of the document into the CDR appeal folder.\n\nc. \nRequest for a change in time or place of the disability hearing\n\nAlert the DDS to all requests to change the time or place of a disability hearing. Scan or place the forms and information about the request to change the time or place of the disability hearing in the individuals official folder. Forward the material to the DDS using an SSA-408 (Route Slip) if the folder is paper and is already at the DDS.\n\nNOTE: \n\nWhen the individual requests to change the disability hearing and it is less than 10 days before the scheduled hearing date, notify the DDS by telephone or email. Forward the forms and information about the change request based on direction from the DDS (fax, hand-deliver or scan to folder).\n\n2. \n",
        "sha256": "f37fefa92c480a63239334209af064841f57edfaf11c5621c0d2165bc9766fb7"
      },
      {
        "id": "DI12026.025:E3",
        "source_code": "DI12026.025",
        "locator": "E3",
        "start": 17923,
        "end": 20000,
        "exact_text": "Subsequent material or information received in the FO\n\nMost material and information received is in writing. However, the FO must document any information obtained verbally on an SSA-5002 (Report of Contact) or other appropriate SSA form. Upload all new material or information received after the case left the FO into the electronic folder if possible. Check the case control system to establish if the folder is located at the DDS or DHU, and complete the following instructions:\n\na. \nNew evidence\n\nWhen the FO receives subsequent evidence, including sources:\n\n•\n\nIf the official folder is paper, use an SSA-408 (Route Slip) to forward the material to the DDS or DHU.\n\n•\n\nIf we issued a reconsideration determination and the case left the DHU, forward the material to the DDS (or alert the DDS to the presence of subsequent material in the EF) to determine the relevance of the material and the action to take.\n\nNOTE: \n\nAn exception to this routing applies if the case is at an administrative law judge (ALJ) or Appeals Council (AC) location. In these instances, forward the material for folder association and review to the Office of Hearing Operation (OHO) or AC office where the folder is located.\n\nb. \nChange of address or telephone number\n\nWhen an individual reports a change of address or telephone number after the release of the folder, the FO takes the following actions:\n\n•\n\nUpdate the Title II and Title XVI records (for example, MBR, MSSICS and EDCS) with the new information.\n\n•\n\nSend an update after transfer (UAT) to the DDS or DHU with the individuals new address or telephone number.\n\n•\n\nIf the official folder is paper, use an SSA-408 to forward the change of address information to the DDS or DHU (include the office code for the FO servicing the individual's current address).\n\n•\n\nNotify the DHU by telephone if a disability hearing is scheduled and the change of address involves a change in the DDS or DHU site. Send an e-mail confirmation of the phone call to the DHU.\n\nNOTE: \n\nThe DHU forwards or associates the email confirmation to the folder.\n\n4. \n",
        "sha256": "40302d5f3a55b4b878397d8f94c7a3052b54c16b4393e72b27d905b85aa04b7b"
      },
      {
        "id": "DI12026.025:E4",
        "source_code": "DI12026.025",
        "locator": "E4",
        "start": 20000,
        "end": 20521,
        "exact_text": "Individual fails or refuses to submit additional information for the reconsideration\n\nThe FO must transmit or forward the folder to the DDS if the individual fails or refuses to complete the necessary forms or provide additional evidence needed to support the request. Indicate what information is lacking using a Form SSA-5002 and associate this form with the appeal folder. If the DDS does not have enough information to make a medical determination, follow guidelines as outlined in DI 23005.001 or DI 23007.005.\n\n5. \n",
        "sha256": "3075eb6eb3683c0e9c353113eb9c1032f236680b8ccd104deb30dc113d78057e"
      },
      {
        "id": "DI12026.025:E6opening",
        "source_code": "DI12026.025",
        "locator": "E6opening",
        "start": 22739,
        "end": 23447,
        "exact_text": "Individual dies before we make the reconsideration determination\n\nThe FO must put the death information on the individuals record(s), and forward or upload the proof of death to the folder. Review the folder(s) to determine leads to anyone who may be entitled or adversely affected by the cessation determination.\n\n•\n\nTitle II cases could include a surviving spouse, auxiliary beneficiaries, or a representative of the estate.\n\n•\n\nFor Title XVI cases, refer to SI 02101.003 (SSI Underpayment Due - Individual Deceased - General).\n\nNOTE: \n\nA death certificate has the cause(s) of the death, which can aid the DHO in making a determination if the cause of death was related to the individuals disability.\n\na. \n",
        "sha256": "a9cf8ae08019a9fcdd10b4995427c643f69383c8a75554c78bade03e50f5b919"
      },
      {
        "id": "DI12026.025:E6a",
        "source_code": "DI12026.025",
        "locator": "E6a",
        "start": 23447,
        "end": 25370,
        "exact_text": "Substitute party involved\n\nIf a substitute party involves a change in the hearing location, see instruction in DI 12026.025E.3.b. in this section. When a substitute party is involved:\n\n•\n\nSecure an SSA-770-U4 (Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation). Use this form when allowing the substitute party to pursue the appeal of a deceased individual. For instructions about this form, see DI 12026.027 (Completion of the SSA-770-U4 Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation).\n\n•\n\nInform the substitute party that a hearing may not be necessary if we are able to issue a favorable determination based on available evidence.\n\n•\n\nTelephone the DHU and report the individual's death. If the substitute party informed the FO that they wish to appear at the disability hearing scheduled for the individual, inform the DHU to not postpone the hearing. Also, provide the DHU with the substitute party's name, address, and telephone number. Otherwise, the DHU will postpone any hearing scheduled pending receipt of the SSA-770-U4.\n\n•\n\nIf the folder is electronic, upload the completed SSA-770-U4 and any additional medical information (for example, recent hospitalizations, physician's report) into the EF.\n\nNOTE: \n\nIf the DHU is different from the one that previously had the folder, create a message to the DHU stating: Substitute party requested disability hearing in your area.\n\n•\n\nIf the folder is paper, prepare an SSA-408 (Route Slip) and route the completed copies of the SSA-770-U4 to the component with the folder and to the appropriate DHU. Include any additional medical information.\n\nNOTE: \n\nIf the DHU is different from the one that previously had the folder, annotate the SSA-408 to show: Substitute party requested disability hearing in your area - Attached forwarded for folder association.\n\nb. \n",
        "sha256": "712202e3fd3a626a44f156aaf2f717896ca5056be21cc3d19caea5007ea4058d"
      },
      {
        "id": "DI12026.025-whole",
        "start": 0,
        "end": 29405,
        "exact_text": "Effective Dates: 08/12/2026 - Present\nPrevious | Next\n\nTN 19 (08-26)\n\nDI 12026.025 Field Office (FO) Processing Guidelines for Requesting a Reconsideration in a Medical Continuing Disability Review (CDR) Determination\nA. \nReviewing the CDR reconsideration appeal forms\n\nThe FO must ensure that the appropriate appeal forms are complete and filed timely (or establish 'good cause' for extending the time limit to file an appeal). All forms must be stored in the electronic or paper folder, as applicable.\n\n1. \nSSA-789 (Request for Reconsideration Disability Cessation Right to Appear)\n\nWhen processing the form SSA-789, the FO must:\n\na. \n\nCheck that the form is complete with the following information.\n\n1. \n\nThe individual indicated whether they wish to appear at the disability hearing;\n\n2. \n\nThe individual completed the block for 'interpreter' and 'language' needs, if applicable;\n\n3. \n\nThe individual or representative payee does not need to sign the form; and\n\n4. \n\nThe FO must date the SSA-789 at the top of the form upon receipt.\n\nNOTE: \n\nA completed Modernized Supplemental Security Income Claims System (MSSICS) appeals output can act in place of the SSA-789 in Title XVI and concurrent cases if the individual also provides a clear written indication of dissatisfaction with the initial CDR determination.\n\nb. \n\nIf the SSA-789 is incomplete, take the following actions.\n\n1. \n\nCall the individual for the necessary information.\n\n2. \n\nIf the individual has no phone or the attempt is not successful, send a call-in/come-in letter and set a 15-day diary.\n\n3. \n\nThe FO must document attempts to contact the individual on an SSA-5002 (Report of Contact). The FO must place a copy of the SSA-5002 in the folder.\n\n4. \n\nIf the individual does not respond within the 15 days regarding whether they want a hearing or need an interpreter, forward the case to the disability determination services (DDS) for resolution.\n\n5. \n\nProvide the individual with a copy of the SSA-789 if applicable.\n\n6. \n\nProvide the individual with the English or Spanish version of the form SSA-888 (Reconsideration/Disability Hearing Procedures). Versions of these documents are located in DI 33095.025 or DI 33095.030.\n\n7. \n\nProvide the individual with the local and toll free telephone numbers for the FO and DDS in their service area. Explain to the individual that we prefer they call the DDS with substantive questions or if they need to report a change related to the disability hearing.\n\nNOTE: \n\nThe Social Security Administration (SSA) does not expect individuals to make long distance phone calls. Individuals may call either the FO or DDS using the local or toll free number.\n\n2. \nSSA-792 (Statutory Benefit Continuation Election Statement)\n\nThe FO must provide the individual with a copy of their statutory benefit continuation (SBC) election statement. For information about the SBC election statement, see DI 12027.010.\n\n3. \nSSA-827 (Authorization to Disclose Information to the Social Security Administration)\n\nThe FO must ensure that form SSA-827 has the appropriate signature and date, as in DI 11005.056.\n\n4. \nSSA-3441-BK (Disability Report Appeal)\n\nThe FO must verify that form SSA-3441-BK is complete. If the form is incomplete, the FO must take the following actions:\n\na. \n\nContact the individual if the SSA-3441-BK received was not fully completed or any information appears to be incorrect.\n\nb. \n\nNote if there are any auditory observations made during the telephone conversation with the individual.\n\nc. \n\nDocument additional information that you received from the individual in the Electronic Disability Collect System (EDCS), the form-3367 (Disability Report - Field Office) or on an electronic or paper form SSA-5002 (Report of Contact).\n\n1. \n\nFor Title II cases, see MS MCS 008.007 (Report of Contact [RPOC]); and\n\n2. \n\nFor Title XVI cases, when documenting the report of contact in:\n\na. \n\nReport of Contact page.\n\nb. \n\nNon-MSSICS, prepare a paper form SSA-5002 to document the additional information and add this form to the electronic or paper folder.\n\n5. \nSSA-3881-BK (Questionnaire for Children Claiming SSI Benefits)\n\nIn Title XVI childhood disability cases, the FO must verify that form SSA-3881-BK is complete. If the form is incomplete, take the same actions described in DI 12026.025A.4 in this section.\n\nB. \nSystem inputs to document the reconsideration appeal\n\nThe FO must record information in the system to document the appeal and any SBC information. For more information about SBC system inputs, see DI 12027.010C. Depending upon the claim type, use the following instructions to record a CDR appeal:\n\n1. \nTitle II\n\nFor Title II cases, the FO must complete the following:\n\na. \n\nDocument the CDR appeal information, including SBC election, in EDCS.\n\nNOTE: \n\nA post-entitlement online system (POS) input is no longer necessary.\n\nb. \n\nIn EDCS, complete and transfer the CDR appeal to DDS or the Disability Hearing Unit (DHU). The Disability Control File (DCF) and Master Beneficiary Record (MBR) automatically update as a result of the EDCS transfer.\n\nc. \n\nUpon receipt of the CDR appeal determination from the DDS or DHU, review the MBR to ensure the applicable information was received from EDCS and the DCF updated automatically. Verify the SBC termination, if applicable. The MBR should automatically update within five days.\n\nNOTE: \n\nThe FO will place a tickle for five days on the CDR Development Worksheet (CDRW) in the DCF to establish a control to ensure the SSR and MBR are updated.\n\nd. \n\nIf the MBR does not automatically update in five days, verify that the DIBCESS issue is pending on PCACS and follow-up with the PSC as necessary. Refer to GN 01070.440 for follow-up timeframes.\n\nNOTE: If there is no DIBCESS issue on PCACS, or no exception on the THIS query, the FO should submit a DCF Problem Report through their usual channels. If manual actions are necessary to terminate the SBC payments, refer to DI 12027.090.\n\n2. \nTitle XVI\n\nFor Title XVI cases, the FO must complete the following:\n\na. \n\nUse MSSICS to update the Supplemental Security Record (SSR) to document the filing of the medical determination appeal as well as the SBC election, if applicable.\n\nNOTE: \n\nIf a direct SSR update is required, the FO can use the manual T-XVI case creation process in EDCS to manually enter the required fields in EDCS on the CDR Information page.\n\nb. \n\nUse EDCS to review and ensure that the appeal and the SBC election data propagated successfully from MSSICS. In EDCS, the appeal data should mirror the information that was entered in the MSSICS appeal data.\n\nc. \n\nIn EDCS, complete and transfer the medical determination appeal to DDS or DHU.\n\nd. \n\nUpon receipt of the medical determination from the DDS or DHU, review the SSR to ensure applicable information was received from EDCS and updated the DCF. Review the SSR for pertinent fields (for example, PSY or DIAR) that trigger automated cessation, if applicable.\n\nNOTE: \n\nThe FO will place a tickle for five days on the CDRW in the DCF to establish a control to ensure the SSR is updated.\n\ne. \n\nReview the SSR to ensure the SBC benefits are properly terminated, if appropriate.\n\nf. \n\nIf the SSR does not automatically update in five days, the FO must proceed with manual actions to update the SSR. To manually update the SSR, see DI 12026.025C.2 in this section.\n\n3. \nConcurrent (Title II and Title XVI)\n\nFor concurrent (Title II and Title XVI) cases, the FO must complete the following:\n\na. \n\nFirst, use MSSICS to document the medical determination appeal data on the SSR prior to entering EDCS.\n\nNOTE: \n\nIf the case is a concurrent appeal, the FO must first complete MSSICS prior to opening the appeal in EDCS.\n\nb. \n\nReview EDCS to verify the concurrent establishment of the appeal segments. Proceed with addressing additional appeal questions that will capture the Title II appeal data.\n\nc. \n\nIn EDCS, complete and transfer the medical determination appeal to the DDS or DHU. Ensure both the Title II and Title XVI segments are included in the case transfer.\n\nd. \n\nUpon receipt of the medical determination from the DDS or DHU:\n\n1. \n\nReview both the SSR and MBR to ensure medical appeal determination automatically posted; and\n\n2. \n\nThat SBC benefits have ended for both titled programs.\n\nNOTE: \n\nNo POS action is required for the Title II claim.\n\ne. \n\nThe MBR and SSR should both update within five days.\n\nNOTE: \n\nThe FO will place a tickle for 5 days on the CDRW in the DCF to establish a control to ensure the SSR and MBR are updated.\n\nf. \n\nIf the SSR does not automatically update in five days, the FO must proceed with manual actions to update the SSR. If the MBR does not automatically update in five days, verify that the DIBCESS issue is pending on PCACS and follow-up with the PSC as necessary. Refer to GN 01070.440 for follow-up timeframes.\n\nNOTE: \n\nTitle II updates: If there is no DIBCESS issue on PCACS, or no exception on the THIS query, the FO should submit a DCF Problem Report through their usual channels. If manual actions are necessary to terminate the SBC payments, refer to DI 12027.090.\n\n4. \nSystem input exclusions\n\nIf there is a system input exclusion for a Title II case, the FO must complete the actions in DI 12026.025C.2 in this section to record the appeal information. For a Title XVI system exclusion, the FO must attempt to seed the cases that are outside of MSSICS, see MS 00302.001. If the seeding attempt is unsuccessful, the FO should attempt to load the appeal using a direct SSR update. For manual DCF inputs and screen displays, see CDR 001.000, CDR 001.014, CDR 001.025 and CDR 001.026.\n\nC. \nFolder preparation for the CDR appeal\n1. \nElectronic continuing disability review (eCDR) appeals\n\nThe eCDR includes electronic folder (EF) case processing for initial continuing disability reviews (CDRs) and Age-18 redeterminations. If the disabled individual is appealing a CDR we processed in EDCS, process the reconsideration electronically. For processing appeals using eCDR in electronic folder cases refer to:\n\n•\n\nDI 81010.255 (Electronic Continuing Disability Review (eCDR) Cessation Reconsiderations); and\n\n•\n\nDI 81010.257 (Electronic Continuing Disability Review (eCDR) Cessation Appeals-ALJ Hearing).\n\n2. \neCDR appeal exclusions\n\nWhen the FO is unable to load the CDR reconsideration appeal cases into MSSICS or EDCS, the MBR and SSR are unable to automatically update the DCF. Cases that are not in the EDCS will not be visible for tracking and are only available for tracking in MI Central.\n\nThe FO must record a CDR reconsideration appeal with an exclusion for a Title XVI case using the following actions:\n\na. \n\nFor MSSICS cases, input the CDR reconsideration information in MSSICS. For more information, see MS MSSICS 020.001 (Appeals - Overview); and\n\nb. \n\nFor non-MSSICS cases, use MSSICS direct SSR update to establish the CDR reconsideration, see MS 00302.001. For more information, see MS 00302.001 (Direct SSR Update - Overview).\n\nTo record a CDR reconsideration appeal with an exclusion for a Title II only case, use the EDCS Exclusion Appeal (EEAI) screen to input the appeal request in the DCF. To see additional information on completing the EEAI screen inputs, see CDR 001.025. The DCF will pass the appeal request and SBC information to the T2R background program, which will automatically update the MBR. The Title II case will not require a POS input.\n\nFor the Title II case reconsideration, once the appeal information is loaded to the DCF, the case will become visible in MI Central. EDCS will not be able to automatically update the location of the appeal case. At the time of the cessation or continuance determination, the DCF will automatically receive the determination and will automatically update the MBR.\n\nFor a Title II case hearing appeal, after inputting the appeal request using the EEAI screen, the DCF will automatically create an ALJT2EX tickle. These cases will not appear in the DCF pending file or in MI Central. When there is a medical decision on the hearing appeal, the FO must receipt it in the tickle on the DCF. A hearing affirmation, abandonment, dismissal, or withdrawal will continue to automatically post to the MBR. Hearing reversals will require a POS input to update the MBR.\n\n3. \nPaper folders (Modular disability folder [MDF] and brown [non-MDF] folder)\n\nProcess the paper folder as follows:\n\na. \nFolder(s) available in the FO\n\nPlace the request for reconsideration, any supporting forms, and any evidence provided by the individual in the official disability folder. For document filing instructions see DI 70005.005B.\n\nb. \nFolder(s) unavailable in the FO\n\nRequest the CDR folder and annotate on the request that there is a disability hearing pending. The following references provide information about requesting an MDF:\n\n•\n\nTitle II - DI 40525.100 (Processing Center Action Control System [PCACS] Coordination).\n\n•\n\nTitle XVI (except foreign cases) - SM 01601.415 (Case Control Data CCTL), and SM 01201.035 (Alert Response [AR] Codes on the SSA-8028).\n\n•\n\nForeign Case - DI 12026.020B.5. (Field Office [FO] Responsibilities when an Individual Wants to Request a Continuing Disability Review [CDR] Reconsideration).\n\n•\n\nObtain any needed prior folder(s) - DI 13015.080 (Unable to Locate Medical Folder after Initial FO Search - Detective Work).\n\n•\n\nUnable to locate the prior folder - GN 03105.010 (Reconstruction of Destroyed or Missing Paper Claims Folders), DI 20502.030 (Folder Reconstruction), and DI 28035.000 (Processing of Lost Folders/Medical Evidence).\n\nD. \nRouting the CDR appeal folder\n\nTo establish where to route the CDR appeal folder, first determine the case type.\n\n1. \nCases other than career railroad or foreign cases\n\nRoute the folder to the servicing FOs DDS.\n\n2. \nCareer railroad case\n\nRoute the folder(s) to the Great Lakes Program Service Center (GLPSC):\n\n•\n\nFollow the procedures for processing railroad cases in DI 29005.020 (Career Railroad and Railroad Annuitant Reconsideration Continuing Disability Review (CDR) Requests).\n\n•\n\nInclude the DHU copy of the SSA-789 in the disability folder(s) and route the folder to:\n\nGLPSC, Disability Processing\nP.O. Box 87755\nChicago, IL 60680-0955\n3. \nForeign case\n\nDo not forward documents or information to the DDS associated with the servicing FO.\n\n•\n\nInclude all documents and information in the disability folder and route the folder to the Office of Earnings and International Operations (OEIO). Do not forward a copy of the SSA-789 to the DDS.\n\n•\n\nForward all materials to:\n\nSocial Security Administration\nOffice of Earnings and International Operations\nP.O. Box 17775\nBaltimore, Maryland 21235-7775\nE. \nProcessing other issues when a reconsideration disability hearing is pending\n1. \nRequesting a change in time or place of the disability hearing\n\nIf the disabled individual contacts the FO, rather than the DHU or the disability hearing officer (DHO), take the actions according to how the individual makes contact.\n\na. \nIndividual visits the FO\n\nEnsure the individual completes an SSA-769-U4 (Request for Change in Time/Place of Disability Hearing). For an exhibit of the form and instructions for its completion, see DI 12026.026 (Completion of the SSA-769-U4 Request for Change in Time/Place of Disability Hearing).\n\nb. \nIndividual telephones the FO\n\nObtain the information you need to complete the SSA-769-U4. The FO must document the information obtained in the telephone conversation electronically (RPOC/or Report of Contact page), or on a paper SSA-5002 (Report of Contact) and fax it into the Non-Disability Repository for Evidentiary Documents (NDRED).\n\n1. \n\nFor Title II, document the contact in an SSA-5002.\n\n2. \n\nFor Title XVI, document the report of contact in:\n\n•\n\nReport of Contact page\n\n•\n\nNon-MSSICS, prepare a paper SSA-5002 and place a copy of the document into the CDR appeal folder.\n\nc. \nRequest for a change in time or place of the disability hearing\n\nAlert the DDS to all requests to change the time or place of a disability hearing. Scan or place the forms and information about the request to change the time or place of the disability hearing in the individuals official folder. Forward the material to the DDS using an SSA-408 (Route Slip) if the folder is paper and is already at the DDS.\n\nNOTE: \n\nWhen the individual requests to change the disability hearing and it is less than 10 days before the scheduled hearing date, notify the DDS by telephone or email. Forward the forms and information about the change request based on direction from the DDS (fax, hand-deliver or scan to folder).\n\n2. \nSubstantial gainful activity (SGA) issues in a Title II case\n\nIn processing Title II cases with SGA issues, develop and resolve work issues discovered during DDS or DHU review using procedures in DI 10501.025, DI 13010.012, and DI 13010.025.\n\na. \n\nIf the work is SGA:\n\n•\n\nPrepare an initial SGA determination if conditions meet the requirements for FO processing, and trial work period (TWP), extended period of eligibility (EPE), or extended Medicare does not apply.\n\n•\n\nAdvise the individual in the SGA cessation determination notice that we will not conduct a disability hearing on the medical cessation issue because we found them not disabled, due to work. For information on processing SBC, see DI 12027.040 and DI 12027.050.\n\n•\n\nSend a copy of the SSA-833 (Cessation or Continuance of Disability or Blindness Determination and Transmittal) to the DHU to cancel the hearing process.\n\nb. \n\nIf the work is not SGA, or is SGA but EPE or extended Medicare applies:\n\n•\n\nComplete FO actions using existing SGA and EPE procedures.\n\n•\n\nReturn case to DDS or DHU for action on medical issue(s).\n\nThe FO must upload all work CDR documentation to EDCS for electronic cases, and forward documentation to the DDS or DHU for paper cases because the DDS and DHU does not have access to other FO programs where this information could be stored.\n\n3. \nSubsequent material or information received in the FO\n\nMost material and information received is in writing. However, the FO must document any information obtained verbally on an SSA-5002 (Report of Contact) or other appropriate SSA form. Upload all new material or information received after the case left the FO into the electronic folder if possible. Check the case control system to establish if the folder is located at the DDS or DHU, and complete the following instructions:\n\na. \nNew evidence\n\nWhen the FO receives subsequent evidence, including sources:\n\n•\n\nIf the official folder is paper, use an SSA-408 (Route Slip) to forward the material to the DDS or DHU.\n\n•\n\nIf we issued a reconsideration determination and the case left the DHU, forward the material to the DDS (or alert the DDS to the presence of subsequent material in the EF) to determine the relevance of the material and the action to take.\n\nNOTE: \n\nAn exception to this routing applies if the case is at an administrative law judge (ALJ) or Appeals Council (AC) location. In these instances, forward the material for folder association and review to the Office of Hearing Operation (OHO) or AC office where the folder is located.\n\nb. \nChange of address or telephone number\n\nWhen an individual reports a change of address or telephone number after the release of the folder, the FO takes the following actions:\n\n•\n\nUpdate the Title II and Title XVI records (for example, MBR, MSSICS and EDCS) with the new information.\n\n•\n\nSend an update after transfer (UAT) to the DDS or DHU with the individuals new address or telephone number.\n\n•\n\nIf the official folder is paper, use an SSA-408 to forward the change of address information to the DDS or DHU (include the office code for the FO servicing the individual's current address).\n\n•\n\nNotify the DHU by telephone if a disability hearing is scheduled and the change of address involves a change in the DDS or DHU site. Send an e-mail confirmation of the phone call to the DHU.\n\nNOTE: \n\nThe DHU forwards or associates the email confirmation to the folder.\n\n4. \nIndividual fails or refuses to submit additional information for the reconsideration\n\nThe FO must transmit or forward the folder to the DDS if the individual fails or refuses to complete the necessary forms or provide additional evidence needed to support the request. Indicate what information is lacking using a Form SSA-5002 and associate this form with the appeal folder. If the DDS does not have enough information to make a medical determination, follow guidelines as outlined in DI 23005.001 or DI 23007.005.\n\n5. \nIndividual wishes to withdraw a request for reconsideration of a disability cessation or adverse medical reopening\n\nThe FO should never suggest to an individual to request a withdrawal of their CDR reconsideration.\n\na. \nContact the office where the case folder is located\n\nThe FO must e-mail or call the appropriate office (DDS or DHU) and request it return the case folder to the FO. Request that the DHU postpone the hearing process, pending disposition of the withdrawal.\n\nNOTE: \n\nThe DDS or DHU forwards requests for withdrawal sent directly to them to the FO.\n\nb. \nTitle II case\n\nThe FO must follow the general withdrawal instructions in GN 03102.200B.4.\n\n•\n\nCareer Railroad Cases - GLPSC handles requests for withdrawals.\n\n•\n\nForeign Cases - OEIO handles requests for withdrawals.\n\nc. \nTitle XVI case\n\nThe FO must follow the general withdrawal instructions in SI 04020.020.\n\nd. \nRequest for withdrawal approved\n\nEnsure that we terminated benefits, and the individual repaid all SBC payments, before approving the withdrawal. For more information on conditions for withdrawal, see GN 00206.005. Send a copy of the individuals notice approving the withdrawal to the DHU to cancel the hearing process.\n\ne. \nRequest for withdrawal not approved\n\nWhen processing a denied request for withdrawal:\n\n•\n\nReturn the case to the DDS or the DHU.\n\n•\n\nInclude, or upload, a copy of the notice informing the individual that the FO did not approve their request.\n\nf. \nCancellation of the request for withdrawal\n\nWhen an individual wants to cancel the request for withdrawal:\n\n•\n\nIf the individual files a cancellation of withdrawal within 60 days from the date the individual received the notice of approval of withdrawal, process the case as though no withdrawal took place.\n\n•\n\nReinstate any previously approved SBC benefits retroactive to the month benefits stopped unless the individual indicates otherwise.\n\n•\n\nInclude a copy of the individual's cancellation of the withdrawal in the folder. Ensure the individual's (and any representatives) name, address, and telephone number, are on the request for cancellation.\n\n•\n\nReturn the folder to the DDS that had the case on the date we received the request for withdrawal.\n\n6. \nIndividual dies before we make the reconsideration determination\n\nThe FO must put the death information on the individuals record(s), and forward or upload the proof of death to the folder. Review the folder(s) to determine leads to anyone who may be entitled or adversely affected by the cessation determination.\n\n•\n\nTitle II cases could include a surviving spouse, auxiliary beneficiaries, or a representative of the estate.\n\n•\n\nFor Title XVI cases, refer to SI 02101.003 (SSI Underpayment Due - Individual Deceased - General).\n\nNOTE: \n\nA death certificate has the cause(s) of the death, which can aid the DHO in making a determination if the cause of death was related to the individuals disability.\n\na. \nSubstitute party involved\n\nIf a substitute party involves a change in the hearing location, see instruction in DI 12026.025E.3.b. in this section. When a substitute party is involved:\n\n•\n\nSecure an SSA-770-U4 (Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation). Use this form when allowing the substitute party to pursue the appeal of a deceased individual. For instructions about this form, see DI 12026.027 (Completion of the SSA-770-U4 Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation).\n\n•\n\nInform the substitute party that a hearing may not be necessary if we are able to issue a favorable determination based on available evidence.\n\n•\n\nTelephone the DHU and report the individual's death. If the substitute party informed the FO that they wish to appear at the disability hearing scheduled for the individual, inform the DHU to not postpone the hearing. Also, provide the DHU with the substitute party's name, address, and telephone number. Otherwise, the DHU will postpone any hearing scheduled pending receipt of the SSA-770-U4.\n\n•\n\nIf the folder is electronic, upload the completed SSA-770-U4 and any additional medical information (for example, recent hospitalizations, physician's report) into the EF.\n\nNOTE: \n\nIf the DHU is different from the one that previously had the folder, create a message to the DHU stating: Substitute party requested disability hearing in your area.\n\n•\n\nIf the folder is paper, prepare an SSA-408 (Route Slip) and route the completed copies of the SSA-770-U4 to the component with the folder and to the appropriate DHU. Include any additional medical information.\n\nNOTE: \n\nIf the DHU is different from the one that previously had the folder, annotate the SSA-408 to show: Substitute party requested disability hearing in your area - Attached forwarded for folder association.\n\nb. \nSubstitute party wishes to withdraw a request for reconsideration\n\nWhen a substitute party wishes to withdraw the request for reconsideration:\n\n•\n\nRoute the completed SSA-770-U4 according to instructions in DI 12026.025E.6.a. in this section.\n\n•\n\nIf the office with the case returns the case to the FO for action on the withdrawal, the FO will ensure that the conditions meet the requirement for withdrawal, see GN 00206.005. Follow the general withdrawal instructions in GN 03102.200B.\n\nc. \nSubstitute party not located\n\nDocument that you were unable to locate a substitute party electronically (RPOC/or Report of Contact page), or on a paper SSA-5002 (Report of Contact) and fax the documentation into NDRED. Include the name and address of any known next of kin of the individual in the documentation.\n\n1. \n\nFor Title II, see MS MCS 008.007 (Report of Contact (RPOC)).\n\n2. \n\nFor Title XVI, document the report of contact in:\n\n•\n\nReport of Contact page\n\n•\n\nNon-MSSICS - prepare a paper SSA-5002 to document the information obtained. Forward the SSA-5002 for folder association.\n\nd. \nReferences for electronic cases\n\nFor electronic cases:\n\n•\n\nFOs processing appeals using eCDR should refer to DI 81010.255.\n\n•\n\nDDS processing appeals using eCDR should refer to DI 81020.255.\n\ne. \nRemand, common issue, and escalated cases\n\nFor information about:\n\n•\n\nRemand cases\n\nSee DI 12010.015 (Informal Remand of Medical/Vocational Determinations) and DI 12010.025 (Action Following a Favorable Determination by the Disability Determination Service (DDS) in Informal Remand Cases).\n\n•\n\nCommon issue cases\n\nSee DI 12045.005 (Claims Under Different Titles - Common Issue - General).\n\n•\n\nEscalated cases\n\nSend escalated cases, or material for folder association, to the DHU rather than the DDS when the case is currently at the DHU or when the DHU made the reconsidered determination.\n\nF. \nReferences\n•\n\nDI 10501.025 Clearly Not SGA\n\n•\n\nDI 12010.015 Informal Remand of Medical/Vocational Determinations\n\n•\n\nDI 12010.025 Action Following a Favorable Determination by the Disability Determination Service (DDS) in Informal Remand Cases\n\n•\n\nDI 12027.010 Processing Statutory Benefit Continuation (SBC)\n\n•\n\nDI 12027.090 Processing Title II Disability Cessation (DIB CESS) Appeal Pending Alerts\n\n•\n\nDI 13010.012 Protection from Medical Review Based on Work Activity\n\n•\n\nDI 13015.005 Failure To Cooperate (FTC)/Whereabouts Unknown (WU) Procedures\n\n•\n\nDI 20502.030 Folder Reconstruction\n\n•\n\nDI 23040.001 DDS: Interpreters for Individuals with Limited English Proficiency (LEP) or Individuals Requiring Language Assistance\n\n•\n\nDI 29005.020 GLPSC - Career Railroad and Railroad Annuitant Cases\n\n•\n\nDI 70005.005 Overview of the Paper Modular Disability Folder (MDF)\n\n•\n\nDI 81001.005 Certified Electronic Folder (CEF) Overview\n\n•\n\nDI 81010.150 Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS)\n\n•\n\nDI 81010.200 Electronic Continuing Disability Review (eCDR) Short Term Process Overview\n\n•\n\nDI 81010.255 Electronic Continuing Disability Review (eCDR) Cessation Reconsiderations\n\n•\n\nDI 81010.257 Electronic Continuing Disability Review (eCDR) Cessation Appeals-ALJ Hearing\n\n•\n\nDI 81020.025 Processing Electronic Reconsideration Cases\n\n•\n\nDI 81020.255 Processing a Reconsideration Appeal of an Electronic Continuing Disability (eCDR) Cessation\n\n•\n\nGN 00304.000 Proof of Death Table of Contents\n\n•\n\nGN 01070.440 Follow-Up Timeframes\n\n•\n\nGN 03101.020 Good Cause for Extending the Time Limit to File an Appeal\n\n•\n\nGN 03102.200 Claimant Requests Reconsideration\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0412026025\n\t\nDI 12026.025 - Field Office (FO) Processing Guidelines for Requesting a Reconsideration in a Medical Continuing Disability Review (CDR) Determination - 08/12/2026\nBatch run: 09/01/2026\nRev:08/12/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "1b3edbbaedef119486db2b4c7d5dd09227983b6da607bc036bac95d3c3a871d7"
      },
      {
        "id": "SI00820.130:A",
        "source_code": "SI00820.130",
        "start": 263,
        "end": 7538,
        "exact_text": "A. \nPolicy for primary and secondary sources of wage evidence\n\nWage evidence can come in several forms and from different sources. When obtaining wage evidence, we consider sources in a priority order of primary and secondary sources. This order is based both on the general reliability of the evidence and the burdens associated with obtaining it. For Supplemental Security Income (SSI) earned income verification, primary sources are considered the most reliable and complete; whereas secondary sources may require additional scrutiny, averaging, and additional documentation.\n\n1. \nPrimary evidence of wages\n\nConsider the following items as primary evidence of wages. For the order of priority for developing wage evidence, see SI 00820.130C in this section.\n\na. \n\nWages posted or received from a payroll data provider (PDP) through the Payroll Information Exchange (PIE). For information on PIE and automated wage evidence from PDPs, see SI 00820.148.\n\nb. \n\nPay stubs. At a minimum, pay stubs must show:\n\n1. \n\nthe worker's name or full Social Security number (SSN),\n\n2. \n\ngross wages, and\n\n3. \n\nthe period covered by the earnings.\n\nAccept original pay stubs (e.g., provided as a paycheck stub or provided electronically to the worker on a company or government-sponsored website) and unaltered photocopies and facsimiles as primary evidence of wages if the pay stubs contain the information stated in this section. For additional information on photocopies of pay stubs, see SI 00820.130C.2.e in this section.\n\nc. \n\nWage information from an SSA-approved wage verification company (e.g., The Work Number (TWN)) listed in Evidence of Wages – Wage Verification Companies, SI 00820.147.\n\nNOTE: \n\nTWN provides the same wage information we receive from the current PDP through PIE. If you have obtained PDP wage information from PIE covering the entire period subject to development or verification, do not obtain additional wage information using TWN. However, you may access TWN to obtain past-month and historical wage information not supplied by the PDP through PIE.\n\nd. \n\nOral statement from the employer.* See SI 00820.130C.4.a.\n\ne. \n\nWritten statement from the employer (e.g., SSA-L4201-BK, Letter to Employer Requesting Wage Verification). * Do not send SSA-L4201s to employers that provide wage verification through an SSA-approved wage verification company.\n\nNOTE: \n\n*To minimize burdens on employers, we seek secondary evidence of wages listed in SI 00820.130A.2.a through SI 00820.130A.2.c (in this section) prior to contacting the employer for an oral or written wage verification.\n\nFor more information on:\n\n•\n\nthe order of priority in developing evidence of wages, see SI 00820.130C.\n\n•\n\nverifying wage termination events and associated evidence, see SI 00820.130E.\n\n•\n\nstep-by-step charts on developing wages, see SI 00820.135.\n\n2. \nSecondary evidence of wages\n\nConsider the following as secondary evidence of wages if wage and employment information through PIE is unavailable and attempts to obtain pay stubs, and wage evidence from an SSA-approved wage verification company are unsuccessful:\n\na. \n\nQueries obtained through the Interstate Benefits Inquiry (IBIQ), the National Directory of New Hires (NDNH), or SSA Access to State Records Online (SASRO) databases when documented according to SI 00820.130C.4 in this section;\n\nb. \n\nMaster Earnings File (MEF), Form W2 (Wage and Tax statement), or Federal or State tax forms;\n\nc. \n\nWage information from the Internet Ticket Operations Provider Support System (iTOPSS) query when documented according to SI 00820.130C.4 in this section; and\n\nd. \n\nWage information from a non-SSA approved wage verification company when provided by the individual according to SI 00820.130C.7 in this section;\n\nIMPORTANT: If the worker’s employer(s) uses a non SSA-approved wage verification company, the worker must request evidence from that company. SSA employees must not establish online accounts with non-approved wage verification companies, enter any of the worker's personally identifiable information into a non SSA-approved website, or otherwise contact or disclose information to non-approved wage verification companies.\n\nInformation obtained from third-party sources (e.g., iTOPSS and NDNH) is subject to additional documentation requirements. See instructions in this section\n\n•\n\nSI 00820.130C.4 for documenting wage evidence from third parties.\n\n•\n\nSI 00820.130C.6 for handling evidence that reflects only an annual or quarterly wage amount.\n\n3. \nCombination of types of evidence of wages\n\nAccept a combination of various forms of primary and secondary evidence if it results in a more accurate wage determination.\n\nEXAMPLE: Using a Combination of Primary and Secondary Evidence to Compute Monthly Earnings\n\nAn SSI eligible recipient receives weekly wages from working at a local deli.\n\nAt their redetermination in 01/2023, they provide SSA with pay stubs for the months of 07/2022 ($600), 08/2022 ($500), and 10/2022 ($700).\n\nWe previously posted the recipient's wages as verified for the months of 01/2022 through 06/2022 ($4,500 total).\n\nThe claims specialist (CS) obtained a Summary Earnings Query (SEQY) for the recipient that showed total earnings of $8,000 for the entire year of 2022. The CS also queried the NDNH database and found that the recipient earned $1,500 in the 3rd quarter of 2022.\n\nThe CS computed the recipient's earnings for each month by using both primary and secondary evidence as follows:\n\n \n\n\t\n\n \n\n\n\n\n$1,500\n\n\t\n\nTotal gross wages for 07/2022 thru 09/2022 (NDNH)\n\n\n\n\n  -$600\n\n\t\n\nGross wages paid in 07/2022 (pay stubs)\n\n\n\n\n-$500\n\n\t\n\nGross wages paid in 8/2022 (pay stubs)\n\n\n\n\n  $400\n\n\t\n\nComputed gross wages paid in 9/2022\n\n \n\n \n\n\t\n\n \n\n\n\n\n$8,000\n\n\t\n\nTotal gross wages paid in 2022 (SEQY)\n\n\n\n\n-$6,000\n\n\t\n\nGross wages paid from 1/2022 thru 9/2022 (previously verified, pay stubs, and computed wages)\n\n\n\n\n-$700\n\n\t\n\nGross wages paid in 10/2022 (pay stubs)\n\n\n\n\n$1,300\n\n\t\n\nRemaining gross wages for 11/2022 thru 12/2022\n\n \n\n \n\n\t\n\n \n\n\n\n\n  $1,300\n\n\t\n\nRemaining gross wages for 11/2022 thru 12/2022\n\n\n\n\n÷2\n\n\t\n\nRemaining gross wages for 11/2022 and 12/2022. (The recipient alleges that they worked both months.)\n\n\n\n\n$650\n\n\t\n\nGross wages paid in 11/2022 and 12/2022\n\nThe CS successfully computed the recipient's wages using information derived from primary evidence and secondary evidence.\n\nThe CS confirms the recipient agrees with the information obtained from NDNH and the months the individual worked in 2022 and records this information on a Report of Contact.\n\nThe CS accurately posts verified wages to the Supplemental Security Record (SSR) for the entire year of 2022, documents the same Report of Contact with the steps taken to use preferred evidence, uploads pay stubs into the Evidence Portal, and issues a receipt acknowledging the pay stub report.\n\n4. \nPrecedent files as evidence of wages\n\nAn existing precedent file may provide evidence of wages in some cases. For precedent instructions, see SI 00820.142.\n\n5. \nNo acceptable evidence of wages\n\nIf you cannot obtain acceptable primary or secondary evidence, accept the individual’s statement regarding wages, either signed or recorded on a Report of Contact page, which includes the amount, frequency of wages, and dates received.\n\n",
        "sha256": "6d9bad26e9b906265e803496662d41acea0c70872130f0736b7859dc81bbc880"
      },
      {
        "id": "SI00820.130:B",
        "source_code": "SI00820.130",
        "start": 7538,
        "end": 9932,
        "exact_text": "B. \nPolicy for “reported” wages\n1. \nWages considered \"Reported\"\n\nThe SSI record distinguishes among three categories of wage documentation: alleged, \"reported,\" and verified. For more information on this distinction, see SI 00820.143.\n\n\"Reported\" wages are reports of monthly wages submitted to SSA within a certain timeframe and sourced from pay stubs or other wage evidence in the individual’s possession. To be classified as “reported” wages, a wage amount must:\n\n•\n\nbe submitted by a recipient, representative payee or deemor without evidence;\n\n•\n\nreflect the total gross wages received for the current month or the month immediately preceding the month in which we receive the report; and\n\n•\n\nbe posted to the SSI Claims system or the SSR before the recurring payment tape cutoff for the subsequent month; or be submitted using myWR, SSAMWR, or SSITWR on any day during the current reporting month.\n\nOnce posted, the SSR will show “reported” wages with a verification code of “0.”\n\n2. \n“Reported” wages considered verified\n\nConsider \"reported\" wages as verified if they meet the criteria in SI 00820.143E (Monthly Wage Reporting).\n\nDo not routinely redevelop \"reported\" type wages by seeking wage evidence unless the reports are inaccurate or inconsistent according to the criteria in this section.\n\nIf wages are paid in a development period where one of the exceptions in this section applies, consider the \"reported\" wages as alleged; then, verify all \"reported\" and alleged wages for the entire period of review.\n\nFor a step-by-step chart on how to determine if “reported” wages can be considered verified, see SI 00820.135A.\n\n3. \nExceptions to accepting “reported” wages as verified\n\nIf any of the following exceptions apply during the development period, do not consider “reported” wages as verified. You must develop all wages, including months of “reported” wages, according to the policy in this section:\n\n•\n\nDiary data (DIAR) segment of the SSR contains an S2, K6, K7, S7, J3, or J5;\n\n•\n\nMore than two consecutive months with an alleged wage amount during the period of review; or\n\n•\n\nNumber of months with an alleged wage amount is greater than the total number of months during the period of review with a \"reported\" or verified wage, or a combination of both.\n\nFor a step-by-step chart on how to verify “reported” wages that cannot be accepted as verified, see SI 00820.135B.\n\n",
        "sha256": "58a5102648c3daf523a9659f361c174980e8e39572424fbfd994f725590e09e3"
      },
      {
        "id": "SI00820.130:Cpriority",
        "source_code": "SI00820.130",
        "start": 9932,
        "end": 11192,
        "exact_text": "C. \nPolicy and procedure for developing and documenting evidence of wages\n\nDevelop evidence of wages in the following order:\n\n1. \n\nWage evidence received from PDPs through PIE. Generally, this type of evidence automatically post to the associated SSI Claims system Wages page;\n\n2. \n\nPay stubs;\n\n3. \n\nWage evidence from an SSA-approved wage verification company;\n\n4. \n\nIBIQ/NDNH/SASRO queries when documented according to SI 00820.130C.4 in this section;\n\n5. \n\nMEF/W-2s/tax forms when documented according to SI 00820.130C.4 in this section;\n\n6. \n\niTOPSS queries when documented according to SI 00820.130C.4 in this section;\n\n7. \n\nOral statement from employer;\n\n8. \n\nWritten statement from employer (e.g., an SSA-L4201-BK – Letter to Employer Requesting Wage Information);\n\n9. \n\nEvidence from non-approved wage verification companies when obtained according to SI 00820.130C.7in this section; and\n\n10. \n\nThe individual’s allegation recorded on a signed statement or Report of Contact.\n\nNOTE: \n\nDo not use an SSA-L725, Employer Verification of Monthly Wages, for Title XVI wage verification. The SSA-L725 is a Title II wage verification form that requests the amounts earned for services performed within the calendar month, regardless of the amounts paid.\n\n1. \n",
        "sha256": "f9411eb28a96cd4a7bc013d5d94863ccc6172dd9d68c646cb4eba92b5b977ef4"
      },
      {
        "id": "SI00820.130:C2",
        "source_code": "SI00820.130",
        "start": 12173,
        "end": 17280,
        "exact_text": "Procedure for wage evidence: pay stubs\n\nProcess pay stubs according to the following:\n\na. \nSSI recipients, deemors, and representative payees must provide evidence of wages\n\nStress to SSI recipients, deemors, and representative payees that they are responsible for providing evidence of wages, retaining all pay stubs, and providing pay stubs as requested.\n\nREMINDER: \n\nIt is mandatory to recruit and train all SSI recipients, deemors, and representative payees to report wages through electronic reporting systems (i.e., myWageReport (myWR), Supplemental Security Income Telephone Wage Reporting (SSITWR) system, and the SSA Mobile Wage Reporting (SSAMWR) application) unless we are getting their wage and employment information through PIE or an exception or exclusion applies. For more information on monthly wage reporting and recruiting reporters for wage reporting, see SI 00820.143 and SI 00820.144.\n\nb. \nMonthly wage reports submitted with pay stubs\n\nFor instructions on processing monthly pay stub reports, see SI 00820.143F.\n\nWhenever possible, process monthly wage reports that the individual submits with pay stubs using the SSI Monthly Wage Verification (SSIMWV) system. Issue the receipt via SSIMWV and archive the receipt to the Online Retrieval System (ORS). Use the receipt as documentation of the wage evidence received and do not take further action to document the wages. If processing multiple months of pay stubs in SSIMWV, generate a separate receipt for each month to satisfy legal documentation requirements.\n\nc. \nDocumenting multiple months of pay stubs\n\nFor SSI Claims system cases:\n\nWhen not using SSIMWV, you must document multiple months of pay stubs by storing wage evidence in the Evidence Portal.\n\nAlternatively, you may record each pay stub on a single Evidence screen (EVID) or all pay stubs on one Report of Contact page and lock it. Identify monthly gross wages for each month in the period that you are documenting. Record the following on EVID or on a Report of Contact page:\n\n•\n\nThe source of the evidence as pay stubs;\n\n•\n\nTime period covered by the pay stubs;\n\n•\n\nGross wages paid;\n\n•\n\nPay date (if shown);\n\n•\n\nThe employer’s name; and\n\n•\n\nAny applicable deductions from gross wage (e.g., cafeteria plans, certain child support garnishments).\n\nFor non-SSI Claims system cases:\n\nWhen not using SSIMWV to document multiple months of pay stubs, you must:\n\n•\n\nStore evidence in the Evidence Portal (EP); or\n\n•\n\nRecord multiple months of pay stubs on an EVID screen (one EVID for each pay stub), SSA-5125 (Periodic Reporting Income Summary Worksheets), or SSA-5124 (Income Summary Worksheets). Store completed worksheets in the EP.\n\nFor additional information related to the SSA-5125 and SSA-5124, see SI 00820.132 and SI 00820.131.\n\nFor additional information on electronic evidence documentation and retention, see GN 00301.286.\n\nNOTE: \n\nFor information on SSIMWV and documenting pay stubs processed using SSIMWV , see SI 00820.144D and SI 00820.130C.2b. in this section.\n\nd. \nPay stub does not show pay date\n\nIf the pay date is not on the pay stub, record the worker's statement of the pay date (either signed or on a Report of Contact). For additional information on electronic evidence documentation and retention, see GN 00301.286.\n\ne. \nPhotocopied pay stubs submitted\n\nAccept copies of pay stubs as primary evidence of wages. Do not recontact the individual to request original pay stubs unless the copies are questionable (see SI 00820.130C.2.h in this section) or you cannot determine earnings from the information provided on the copies.\n\nDocument the wage information from the photocopied pay stubs in the same manner that you would document original pay stubs (e.g., SI 00820.130C.2.b and SI 00820.130C.2.c in this section).\n\nFor instructions on handling questionable wage evidence, see SI 00820.130C.2.h.\n\nf. \nMissing pay stubs\n\nIf all pay stubs are not available, but you can determine the wages attributable to the missing pay stub(s) by other evidence (e.g., wage verification company, year-to-date totals), do not obtain the missing pay stub(s).\n\ng. \nPay stubs that do not contain all the required information\n\nWhen pay stubs do not contain all the required information discussed in this section SI 00820.130A.2, use other primary or secondary evidence to resolve any discrepancies, following the priority order in SI 00820.130Cin this section. Document the evidence and the resolution using the instructions on electronic evidence documentation in GN 00301.286.\n\nh. \nPay stubs with questionable credibility\n\nIf the pay stubs are questionable, obtain further evidence of wages per SI 00820.130A.1.b, through SI 00820.130A.3. in this section.\n\nExamples of questionable pay stubs may include those with:\n\n•\n\naltered or missing data fields;\n\n•\n\ninconsistencies among fields of a single pay stub;\n\n•\n\ninconsistencies with other pay stubs from the same source;\n\n•\n\ninaccurate information shown; or\n\n•\n\ndata fields that are difficult to read or illegible due to damage to the original record or technical problems with printing, photocopying, or faxing.\n\n3. \n",
        "sha256": "f29ea59160fdc80b944e19ff13eacaea31c7f58fc4864655b02a448532aac686"
      },
      {
        "id": "SI00820.130:C4",
        "source_code": "SI00820.130",
        "start": 18179,
        "end": 21693,
        "exact_text": "Procedure for wage evidence: secondary evidence of wages\na. \nSources of secondary wage evidence\n\nIf PIE does not provide wage information and attempts to obtain original pay stubs and wage evidence from an SSA-approved wage verification company are unsuccessful, use secondary evidence of wages to develop earnings.\n\nUse the following sources as secondary evidence of wages and develop according to the priority order in the first paragraph of SI 00820.130C in this section:\n\n•\n\nIBIQ/NDNH/SASRO queries when the worker agrees with the wage information in the query;\n\n•\n\nMEF/W-2s/tax forms;\n\n•\n\niTOPSS queries (e.g., QERN tab or the Consolidated Wage Page (CWP) in the Electronic Disability Collect System (EDCS)) when the worker agrees with the wage information provided in the query;\n\n•\n\nNon SSA-approved wage verification companies. SSA staff must not access or disclose information to non-SSA approved wage verification company websites to obtain evidence but may accept such evidence when it is provided by the individual.\n\nWage information obtained from IBIQ/NDNH/SASRO and iTOPSS queries is considered third-party information and may only be used as wage evidence when the worker agrees with the information on the query. Additional documentation is required for these sources as discussed in SI 00820.130C.4.b in this section.\n\nFor more information on developing and verifying income discovered using IBIQ/NDNH/SASRO queries, see SI 00810.550C.\n\nFor iTOPSS QERN query information, see MS 07807.063.\n\nNOTE: \n\nDo not save IBIQ/NDNH/SASRO printouts or queries in the Evidence Portal. For the required documentation, see SI 00820.130C.3.b in this section.\n\nb. \nAdditional documentation requirements for certain sources of secondary evidence\n\nWhen using secondary wage evidence, document the steps taken to obtain pay stubs and wage verification company data and why they were unsuccessful on a Report of Contact. Additionally:\n\n•\n\nFor third-party sources (e.g., NDNH, OCSS, IBIQ, SASRO, iTOPSS), document that the worker agrees with the wage information prior to using the evidence. Seek other evidence if the worker does not agree with the third-party evidence.\n\n•\n\nFor secondary sources in which averaging is required to obtain monthly amounts (e.g., OCSS, MEF, W-2s), document the worker's allegation concerning the months worked. For more information on calculating monthly wage amounts when using these queries, see SI 00820.130C.6. in this section.\n\n•\n\nWhen using a combination of primary and secondary evidence as described in SI 00820.130A.3 in this section, document the combination of primary and secondary evidence that you used to develop and verify the monthly earnings on a Report of Contact. For more information on electronic evidence documentation and retention, see GN 00301.286.\n\nExamples:\n\n•\n\nMEF queries, W-2 and other tax forms that provide annual amounts: Document steps to obtain higher priority evidence and allegation of months worked on a Report of Contact or signed statement.\n\n•\n\nIBIQ/NDNH/SASRO/OCSS queries that provide quarterly amounts: Document on a Report of Contact or signed statement steps taken to obtain higher priority evidence, the person's acceptance of the wage amounts provided on the query, and the months in which the person alleges working.\n\n•\n\niTOPSS queries: Document steps taken to obtain higher priority evidence and that the person agrees with the pay stub details reported through the Ticket to Work program on a Report of Contact or signed statement.\n\n5. \n",
        "sha256": "bcf79e742b32a014fc0dbf3640f31b30b8cc45eba6bd90a6def020ea294e57bc"
      },
      {
        "id": "SI00820.130:C6",
        "source_code": "SI00820.130",
        "start": 23361,
        "end": 25241,
        "exact_text": "Procedure for wage evidence: evidence reflects only an annual or quarterly wage amount\n\nIf the evidence (e.g., queries, tax forms) reflects only an annual or quarterly wage amount, process the evidence according to the following:\n\na. \nCalculating monthly wage amounts\n\nAsk the worker to state the work months covered by the annual or quarterly wage amount and document their allegations on a signed statement or a Report of Contact. Posting the alleged work months to the corresponding SSI Claims system Wages page alone is insufficient documentation.\n\nDivide the annual or quarterly wage amount by the number of alleged work months to calculate the monthly wage amounts for the alleged work months. When determining whether to average either quarterly or yearly earnings, give preference to the quarterly earnings.\n\nIf it appears that the wages belong to someone other than the individual worker or deemor (e.g., the name shown on the NHDH query is different), do not post the wages to the record.\n\nFor instructions on handling potentially erroneous or duplicate earnings postings on SSA earnings records, see RS 01404.140.\n\nb. \nCalculating monthly wage amounts when previous months verified\n\nWhen the system shows previously verified wages for a particular employer for a portion of the year or quarter that you are developing, do not change the verified amounts unless new evidence indicates that the prior determination was erroneous.\n\nDetermine the wages for the unverified months by subtracting the previously verified amounts from the annual or quarterly totals for the employer and dividing the remaining amount by the number of unverified months of work alleged.\n\nDocument that you subtracted the previously verified amounts from the annual or quarterly totals and divided the remaining amount by the number of unverified alleged work months on a Report of Contact.\n\n7. \n",
        "sha256": "7f29a47dccffbb3fe568b1a6560bfe8bd2fe25b25ca5432a7245d1b2496383a3"
      },
      {
        "id": "SI00820.130:C7-10",
        "source_code": "SI00820.130",
        "start": 25241,
        "end": 27526,
        "exact_text": "Procedure for using wage evidence from non SSA-approved wage verification companies\n\nYou may accept wage evidence from non SSA-approved wage verification companies as secondary evidence of wages only under certain conditions per SI 00820.147C.1.c. If an employer will not provide wage verification and refers you to a non-SSA approved company for wage information, ask the worker to obtain the evidence from the company directly.\n\nIMPORTANT: \n\nSSA employees must not establish online accounts with non-approved wage verification companies or enter any personal or worker information in non-SSA approved wage verification websites, or otherwise contact or disclose information to the non-approved wage verification company.\n\n8. \nProcedure for wage evidence: no acceptable evidence of wages is available\n\nIf evidence of wages is not available, obtain the individual's statement either signed (i.e., SSA-795) or recorded on a Report of Contact that includes the gross amount, frequency, and duration of wages.\n\nIf the sole evidence of wages is the individual’s statement, document the steps taken to obtain acceptable primary and secondary evidence, and why they were unsuccessful on a Report of Contact. Post the alleged wages in the verified column of the SSI Claims system Wages page or via 1719b using a verification code of “9.” For instructions on electronic evidence documentation and retention, see GN 00301.286.\n\n9. \nProcedure for wage evidence: suspected fraud cases\n\nIn any suspected fraud case, obtain the employer’s written statement regarding wages using the SSA-L4201-BK.\n\nFor information on obtaining evidence in suspected fraud cases, see GN 04115.005.\n\nFor information on obtaining additional overpayment notification procedures related to collection of overpayments when fraud is suspected, see SI 02201.007.\n\n10. \nProcedure for wage evidence: work report receipts\n\nSSA is required by law to issue a receipt when we receive a report of a change in an SSI recipient’s work activity or earnings. This policy applies to work-related reports received from the recipient, or from the recipient’s or beneficiary’s representative payee or authorized representative. For further information related to work reports and situations where we require a receipt, see DI 13010.020.\n\n",
        "sha256": "4209e0c087c0ac1cf201901a819a7c6d5df5ae1751ee9e93781c417ba4f55578"
      },
      {
        "id": "SI00820.130:D",
        "source_code": "SI00820.130",
        "start": 27526,
        "end": 28641,
        "exact_text": "D. \nProcedure for verifying “reported” wages\n1. \nDo not routinely verify wages that meet criteria to be considered “reported” wages unless an exception applies\n\nConsider “reported” wages as verified if they meet the criteria in SI 00820.143E (Monthly Wage Reporting). Do not routinely verify “reported” wages, unless one of the exceptions applies to the period that you are developing, see SI 00820.130B.3 in this section.\n\n2. \nNo wage interface alert on the SSR\n\nIf an exception applies during the development period and a wage interface alert is not present in the DIAR segment of the SSR, verify the wages using the procedures in SI 00820.130C in this section.\n\n3. \nWage interface alert on the SSR\n\nIf a wage interface alert applying to the period that you are developing is present in the DIAR segment of the SSR, develop for evidence of wages using the instructions:\n\n•\n\nSI 02310.055 Master Earnings File (MEF) Match (K6 and K7 Diary)\n\n•\n\nSI 02310.056 Master Earnings File (MEF) Match (J3 and J5 Diaries)\n\n•\n\nSI 02310.062 State Wage Record Match (S2 Diary)\n\n•\n\nSI 02310.063 State Wage Record Match (S7 Diary)\n\n",
        "sha256": "cd320054916067703622eb28f329cdeeeb208b1ca10614ea62fc5cf66e5192bc"
      },
      {
        "id": "SI00820.130:E",
        "source_code": "SI00820.130",
        "start": 28641,
        "end": 30264,
        "exact_text": "E. \nTermination of wages\n\nDevelop termination of wages whenever workers allege that they have stopped working or changed jobs. Accept a worker’s report of wage termination on a signed statement or Report of Contact page unless you have reason to question the accuracy of the statement (e.g., claimant frequently fails to report work information accurately). The statement must include:\n\n•\n\nthe date last worked; and\n\n•\n\nthe date of the final paycheck paid by the employer.\n\nIf the individual is not able to provide an accurate statement or evidence on the record conflicts with the statement, obtain primary evidence of wage termination. In order of priority, as evidence of termination of wages, accept the following:\n\n•\n\nInformation from an SSA-approved wage verification company listed in SI 00820.147 (Evidence of Wages – Wage Verification Companies) indicating the date employment ceased;\n\n•\n\nOral statement from the employer; or\n\n•\n\nWritten or faxed evidence from the employer.\n\nStore wage termination evidence in the Evidence Portal or document the evidence on a Report of Contact page. When recipients, their representative payees, or their authorized representatives report a wage termination event, issue a work report receipt according to SI 00820.130C.10 in this section.\n\nCAUTION: \n\nDevelop for receipt of unemployment benefits when an individual alleges termination of wages. For more information about unemployment benefits, see SI 00830.230. If the individual is an SSI recipient and they are not receiving unemployment benefits, refer the recipient for unemployment benefits as described in SI 00510.005.\n\n",
        "sha256": "a8724b14b93d73792d160d4eb565b0256994e27a8f324a1ddeb0e2985af7c7a6"
      },
      {
        "id": "SI00820.130-whole",
        "source_code": "SI00820.130",
        "start": 0,
        "end": 32173,
        "exact_text": "Effective Dates: 03/25/2025 - Present\nPrevious | Next\n\nTN 99 (03-25)\n\nSI 00820.130 Evidence of Wages or Termination of Wages\n\nCITATIONS:\n\nSocial Security Act §1612 and §1631;\n20 CFR §416.1102, §416.1110 thru 416.1112; Social Security Protection Act of 2004, §202\nA. \nPolicy for primary and secondary sources of wage evidence\n\nWage evidence can come in several forms and from different sources. When obtaining wage evidence, we consider sources in a priority order of primary and secondary sources. This order is based both on the general reliability of the evidence and the burdens associated with obtaining it. For Supplemental Security Income (SSI) earned income verification, primary sources are considered the most reliable and complete; whereas secondary sources may require additional scrutiny, averaging, and additional documentation.\n\n1. \nPrimary evidence of wages\n\nConsider the following items as primary evidence of wages. For the order of priority for developing wage evidence, see SI 00820.130C in this section.\n\na. \n\nWages posted or received from a payroll data provider (PDP) through the Payroll Information Exchange (PIE). For information on PIE and automated wage evidence from PDPs, see SI 00820.148.\n\nb. \n\nPay stubs. At a minimum, pay stubs must show:\n\n1. \n\nthe worker's name or full Social Security number (SSN),\n\n2. \n\ngross wages, and\n\n3. \n\nthe period covered by the earnings.\n\nAccept original pay stubs (e.g., provided as a paycheck stub or provided electronically to the worker on a company or government-sponsored website) and unaltered photocopies and facsimiles as primary evidence of wages if the pay stubs contain the information stated in this section. For additional information on photocopies of pay stubs, see SI 00820.130C.2.e in this section.\n\nc. \n\nWage information from an SSA-approved wage verification company (e.g., The Work Number (TWN)) listed in Evidence of Wages – Wage Verification Companies, SI 00820.147.\n\nNOTE: \n\nTWN provides the same wage information we receive from the current PDP through PIE. If you have obtained PDP wage information from PIE covering the entire period subject to development or verification, do not obtain additional wage information using TWN. However, you may access TWN to obtain past-month and historical wage information not supplied by the PDP through PIE.\n\nd. \n\nOral statement from the employer.* See SI 00820.130C.4.a.\n\ne. \n\nWritten statement from the employer (e.g., SSA-L4201-BK, Letter to Employer Requesting Wage Verification). * Do not send SSA-L4201s to employers that provide wage verification through an SSA-approved wage verification company.\n\nNOTE: \n\n*To minimize burdens on employers, we seek secondary evidence of wages listed in SI 00820.130A.2.a through SI 00820.130A.2.c (in this section) prior to contacting the employer for an oral or written wage verification.\n\nFor more information on:\n\n•\n\nthe order of priority in developing evidence of wages, see SI 00820.130C.\n\n•\n\nverifying wage termination events and associated evidence, see SI 00820.130E.\n\n•\n\nstep-by-step charts on developing wages, see SI 00820.135.\n\n2. \nSecondary evidence of wages\n\nConsider the following as secondary evidence of wages if wage and employment information through PIE is unavailable and attempts to obtain pay stubs, and wage evidence from an SSA-approved wage verification company are unsuccessful:\n\na. \n\nQueries obtained through the Interstate Benefits Inquiry (IBIQ), the National Directory of New Hires (NDNH), or SSA Access to State Records Online (SASRO) databases when documented according to SI 00820.130C.4 in this section;\n\nb. \n\nMaster Earnings File (MEF), Form W2 (Wage and Tax statement), or Federal or State tax forms;\n\nc. \n\nWage information from the Internet Ticket Operations Provider Support System (iTOPSS) query when documented according to SI 00820.130C.4 in this section; and\n\nd. \n\nWage information from a non-SSA approved wage verification company when provided by the individual according to SI 00820.130C.7 in this section;\n\nIMPORTANT: If the worker’s employer(s) uses a non SSA-approved wage verification company, the worker must request evidence from that company. SSA employees must not establish online accounts with non-approved wage verification companies, enter any of the worker's personally identifiable information into a non SSA-approved website, or otherwise contact or disclose information to non-approved wage verification companies.\n\nInformation obtained from third-party sources (e.g., iTOPSS and NDNH) is subject to additional documentation requirements. See instructions in this section\n\n•\n\nSI 00820.130C.4 for documenting wage evidence from third parties.\n\n•\n\nSI 00820.130C.6 for handling evidence that reflects only an annual or quarterly wage amount.\n\n3. \nCombination of types of evidence of wages\n\nAccept a combination of various forms of primary and secondary evidence if it results in a more accurate wage determination.\n\nEXAMPLE: Using a Combination of Primary and Secondary Evidence to Compute Monthly Earnings\n\nAn SSI eligible recipient receives weekly wages from working at a local deli.\n\nAt their redetermination in 01/2023, they provide SSA with pay stubs for the months of 07/2022 ($600), 08/2022 ($500), and 10/2022 ($700).\n\nWe previously posted the recipient's wages as verified for the months of 01/2022 through 06/2022 ($4,500 total).\n\nThe claims specialist (CS) obtained a Summary Earnings Query (SEQY) for the recipient that showed total earnings of $8,000 for the entire year of 2022. The CS also queried the NDNH database and found that the recipient earned $1,500 in the 3rd quarter of 2022.\n\nThe CS computed the recipient's earnings for each month by using both primary and secondary evidence as follows:\n\n \n\n\t\n\n \n\n\n\n\n$1,500\n\n\t\n\nTotal gross wages for 07/2022 thru 09/2022 (NDNH)\n\n\n\n\n  -$600\n\n\t\n\nGross wages paid in 07/2022 (pay stubs)\n\n\n\n\n-$500\n\n\t\n\nGross wages paid in 8/2022 (pay stubs)\n\n\n\n\n  $400\n\n\t\n\nComputed gross wages paid in 9/2022\n\n \n\n \n\n\t\n\n \n\n\n\n\n$8,000\n\n\t\n\nTotal gross wages paid in 2022 (SEQY)\n\n\n\n\n-$6,000\n\n\t\n\nGross wages paid from 1/2022 thru 9/2022 (previously verified, pay stubs, and computed wages)\n\n\n\n\n-$700\n\n\t\n\nGross wages paid in 10/2022 (pay stubs)\n\n\n\n\n$1,300\n\n\t\n\nRemaining gross wages for 11/2022 thru 12/2022\n\n \n\n \n\n\t\n\n \n\n\n\n\n  $1,300\n\n\t\n\nRemaining gross wages for 11/2022 thru 12/2022\n\n\n\n\n÷2\n\n\t\n\nRemaining gross wages for 11/2022 and 12/2022. (The recipient alleges that they worked both months.)\n\n\n\n\n$650\n\n\t\n\nGross wages paid in 11/2022 and 12/2022\n\nThe CS successfully computed the recipient's wages using information derived from primary evidence and secondary evidence.\n\nThe CS confirms the recipient agrees with the information obtained from NDNH and the months the individual worked in 2022 and records this information on a Report of Contact.\n\nThe CS accurately posts verified wages to the Supplemental Security Record (SSR) for the entire year of 2022, documents the same Report of Contact with the steps taken to use preferred evidence, uploads pay stubs into the Evidence Portal, and issues a receipt acknowledging the pay stub report.\n\n4. \nPrecedent files as evidence of wages\n\nAn existing precedent file may provide evidence of wages in some cases. For precedent instructions, see SI 00820.142.\n\n5. \nNo acceptable evidence of wages\n\nIf you cannot obtain acceptable primary or secondary evidence, accept the individual’s statement regarding wages, either signed or recorded on a Report of Contact page, which includes the amount, frequency of wages, and dates received.\n\nB. \nPolicy for “reported” wages\n1. \nWages considered \"Reported\"\n\nThe SSI record distinguishes among three categories of wage documentation: alleged, \"reported,\" and verified. For more information on this distinction, see SI 00820.143.\n\n\"Reported\" wages are reports of monthly wages submitted to SSA within a certain timeframe and sourced from pay stubs or other wage evidence in the individual’s possession. To be classified as “reported” wages, a wage amount must:\n\n•\n\nbe submitted by a recipient, representative payee or deemor without evidence;\n\n•\n\nreflect the total gross wages received for the current month or the month immediately preceding the month in which we receive the report; and\n\n•\n\nbe posted to the SSI Claims system or the SSR before the recurring payment tape cutoff for the subsequent month; or be submitted using myWR, SSAMWR, or SSITWR on any day during the current reporting month.\n\nOnce posted, the SSR will show “reported” wages with a verification code of “0.”\n\n2. \n“Reported” wages considered verified\n\nConsider \"reported\" wages as verified if they meet the criteria in SI 00820.143E (Monthly Wage Reporting).\n\nDo not routinely redevelop \"reported\" type wages by seeking wage evidence unless the reports are inaccurate or inconsistent according to the criteria in this section.\n\nIf wages are paid in a development period where one of the exceptions in this section applies, consider the \"reported\" wages as alleged; then, verify all \"reported\" and alleged wages for the entire period of review.\n\nFor a step-by-step chart on how to determine if “reported” wages can be considered verified, see SI 00820.135A.\n\n3. \nExceptions to accepting “reported” wages as verified\n\nIf any of the following exceptions apply during the development period, do not consider “reported” wages as verified. You must develop all wages, including months of “reported” wages, according to the policy in this section:\n\n•\n\nDiary data (DIAR) segment of the SSR contains an S2, K6, K7, S7, J3, or J5;\n\n•\n\nMore than two consecutive months with an alleged wage amount during the period of review; or\n\n•\n\nNumber of months with an alleged wage amount is greater than the total number of months during the period of review with a \"reported\" or verified wage, or a combination of both.\n\nFor a step-by-step chart on how to verify “reported” wages that cannot be accepted as verified, see SI 00820.135B.\n\nC. \nPolicy and procedure for developing and documenting evidence of wages\n\nDevelop evidence of wages in the following order:\n\n1. \n\nWage evidence received from PDPs through PIE. Generally, this type of evidence automatically post to the associated SSI Claims system Wages page;\n\n2. \n\nPay stubs;\n\n3. \n\nWage evidence from an SSA-approved wage verification company;\n\n4. \n\nIBIQ/NDNH/SASRO queries when documented according to SI 00820.130C.4 in this section;\n\n5. \n\nMEF/W-2s/tax forms when documented according to SI 00820.130C.4 in this section;\n\n6. \n\niTOPSS queries when documented according to SI 00820.130C.4 in this section;\n\n7. \n\nOral statement from employer;\n\n8. \n\nWritten statement from employer (e.g., an SSA-L4201-BK – Letter to Employer Requesting Wage Information);\n\n9. \n\nEvidence from non-approved wage verification companies when obtained according to SI 00820.130C.7in this section; and\n\n10. \n\nThe individual’s allegation recorded on a signed statement or Report of Contact.\n\nNOTE: \n\nDo not use an SSA-L725, Employer Verification of Monthly Wages, for Title XVI wage verification. The SSA-L725 is a Title II wage verification form that requests the amounts earned for services performed within the calendar month, regardless of the amounts paid.\n\n1. \nProcedure for wage and employment evidence received from PDPs through PIE\n\nSSA is now using wage and employment information from a PDP through PIE for recipients, deemors, and ineligible children who:\n\n•\n\nprovide SSA with authorization to obtain wage and employment information; and\n\n•\n\nwork for an employer that participates in payroll services with the PDP.\n\nWage and employment information received from PDPs through PIE automatically posts to the SSI Claims system Wages page if the identifying information (e.g., EIN) matches the SSA record. Generally, wage and employment information updates monthly before the Goldberg-Kelly Notice Cutoff. For more information about PIE, see SI 00820.148.\n\nFor information on processing EE diaries and related limited issues that are generated when the exchange cannot post information automatically, see SI 02310.200.\n\nNOTE: \n\nFor more information on requesting wage and employment information authorization (WEIA), see GN 00204.150.\n\n2. \nProcedure for wage evidence: pay stubs\n\nProcess pay stubs according to the following:\n\na. \nSSI recipients, deemors, and representative payees must provide evidence of wages\n\nStress to SSI recipients, deemors, and representative payees that they are responsible for providing evidence of wages, retaining all pay stubs, and providing pay stubs as requested.\n\nREMINDER: \n\nIt is mandatory to recruit and train all SSI recipients, deemors, and representative payees to report wages through electronic reporting systems (i.e., myWageReport (myWR), Supplemental Security Income Telephone Wage Reporting (SSITWR) system, and the SSA Mobile Wage Reporting (SSAMWR) application) unless we are getting their wage and employment information through PIE or an exception or exclusion applies. For more information on monthly wage reporting and recruiting reporters for wage reporting, see SI 00820.143 and SI 00820.144.\n\nb. \nMonthly wage reports submitted with pay stubs\n\nFor instructions on processing monthly pay stub reports, see SI 00820.143F.\n\nWhenever possible, process monthly wage reports that the individual submits with pay stubs using the SSI Monthly Wage Verification (SSIMWV) system. Issue the receipt via SSIMWV and archive the receipt to the Online Retrieval System (ORS). Use the receipt as documentation of the wage evidence received and do not take further action to document the wages. If processing multiple months of pay stubs in SSIMWV, generate a separate receipt for each month to satisfy legal documentation requirements.\n\nc. \nDocumenting multiple months of pay stubs\n\nFor SSI Claims system cases:\n\nWhen not using SSIMWV, you must document multiple months of pay stubs by storing wage evidence in the Evidence Portal.\n\nAlternatively, you may record each pay stub on a single Evidence screen (EVID) or all pay stubs on one Report of Contact page and lock it. Identify monthly gross wages for each month in the period that you are documenting. Record the following on EVID or on a Report of Contact page:\n\n•\n\nThe source of the evidence as pay stubs;\n\n•\n\nTime period covered by the pay stubs;\n\n•\n\nGross wages paid;\n\n•\n\nPay date (if shown);\n\n•\n\nThe employer’s name; and\n\n•\n\nAny applicable deductions from gross wage (e.g., cafeteria plans, certain child support garnishments).\n\nFor non-SSI Claims system cases:\n\nWhen not using SSIMWV to document multiple months of pay stubs, you must:\n\n•\n\nStore evidence in the Evidence Portal (EP); or\n\n•\n\nRecord multiple months of pay stubs on an EVID screen (one EVID for each pay stub), SSA-5125 (Periodic Reporting Income Summary Worksheets), or SSA-5124 (Income Summary Worksheets). Store completed worksheets in the EP.\n\nFor additional information related to the SSA-5125 and SSA-5124, see SI 00820.132 and SI 00820.131.\n\nFor additional information on electronic evidence documentation and retention, see GN 00301.286.\n\nNOTE: \n\nFor information on SSIMWV and documenting pay stubs processed using SSIMWV , see SI 00820.144D and SI 00820.130C.2b. in this section.\n\nd. \nPay stub does not show pay date\n\nIf the pay date is not on the pay stub, record the worker's statement of the pay date (either signed or on a Report of Contact). For additional information on electronic evidence documentation and retention, see GN 00301.286.\n\ne. \nPhotocopied pay stubs submitted\n\nAccept copies of pay stubs as primary evidence of wages. Do not recontact the individual to request original pay stubs unless the copies are questionable (see SI 00820.130C.2.h in this section) or you cannot determine earnings from the information provided on the copies.\n\nDocument the wage information from the photocopied pay stubs in the same manner that you would document original pay stubs (e.g., SI 00820.130C.2.b and SI 00820.130C.2.c in this section).\n\nFor instructions on handling questionable wage evidence, see SI 00820.130C.2.h.\n\nf. \nMissing pay stubs\n\nIf all pay stubs are not available, but you can determine the wages attributable to the missing pay stub(s) by other evidence (e.g., wage verification company, year-to-date totals), do not obtain the missing pay stub(s).\n\ng. \nPay stubs that do not contain all the required information\n\nWhen pay stubs do not contain all the required information discussed in this section SI 00820.130A.2, use other primary or secondary evidence to resolve any discrepancies, following the priority order in SI 00820.130Cin this section. Document the evidence and the resolution using the instructions on electronic evidence documentation in GN 00301.286.\n\nh. \nPay stubs with questionable credibility\n\nIf the pay stubs are questionable, obtain further evidence of wages per SI 00820.130A.1.b, through SI 00820.130A.3. in this section.\n\nExamples of questionable pay stubs may include those with:\n\n•\n\naltered or missing data fields;\n\n•\n\ninconsistencies among fields of a single pay stub;\n\n•\n\ninconsistencies with other pay stubs from the same source;\n\n•\n\ninaccurate information shown; or\n\n•\n\ndata fields that are difficult to read or illegible due to damage to the original record or technical problems with printing, photocopying, or faxing.\n\n3. \nProcedure for wage evidence: SSA-approved wage verification companies\n\nIf PIE does not provide wage and employment information and pay stubs are unavailable, accept wage evidence from an SSA-approved wage verification company, such as The Work Number, as primary evidence of wages, unless there is evidence to the contrary (e.g., evidence of a cafeteria plan not included in the verification company's response).\n\nIf there is evidence to the contrary, obtain additional evidence to resolve the discrepancy. For documentation requirements, see SI 00820.147D.4. For wage verification procedures when wages are over $65 per month, see SI 00820.135.\n\nImportant: You must have a signed authorization via the SSA-8240 to obtain wage information from electronic wage verification companies. Obtain Authorization to Obtain Wage and Employment Information from Payroll Data Providers per GN 00204.150C.\n\n4. \nProcedure for wage evidence: secondary evidence of wages\na. \nSources of secondary wage evidence\n\nIf PIE does not provide wage information and attempts to obtain original pay stubs and wage evidence from an SSA-approved wage verification company are unsuccessful, use secondary evidence of wages to develop earnings.\n\nUse the following sources as secondary evidence of wages and develop according to the priority order in the first paragraph of SI 00820.130C in this section:\n\n•\n\nIBIQ/NDNH/SASRO queries when the worker agrees with the wage information in the query;\n\n•\n\nMEF/W-2s/tax forms;\n\n•\n\niTOPSS queries (e.g., QERN tab or the Consolidated Wage Page (CWP) in the Electronic Disability Collect System (EDCS)) when the worker agrees with the wage information provided in the query;\n\n•\n\nNon SSA-approved wage verification companies. SSA staff must not access or disclose information to non-SSA approved wage verification company websites to obtain evidence but may accept such evidence when it is provided by the individual.\n\nWage information obtained from IBIQ/NDNH/SASRO and iTOPSS queries is considered third-party information and may only be used as wage evidence when the worker agrees with the information on the query. Additional documentation is required for these sources as discussed in SI 00820.130C.4.b in this section.\n\nFor more information on developing and verifying income discovered using IBIQ/NDNH/SASRO queries, see SI 00810.550C.\n\nFor iTOPSS QERN query information, see MS 07807.063.\n\nNOTE: \n\nDo not save IBIQ/NDNH/SASRO printouts or queries in the Evidence Portal. For the required documentation, see SI 00820.130C.3.b in this section.\n\nb. \nAdditional documentation requirements for certain sources of secondary evidence\n\nWhen using secondary wage evidence, document the steps taken to obtain pay stubs and wage verification company data and why they were unsuccessful on a Report of Contact. Additionally:\n\n•\n\nFor third-party sources (e.g., NDNH, OCSS, IBIQ, SASRO, iTOPSS), document that the worker agrees with the wage information prior to using the evidence. Seek other evidence if the worker does not agree with the third-party evidence.\n\n•\n\nFor secondary sources in which averaging is required to obtain monthly amounts (e.g., OCSS, MEF, W-2s), document the worker's allegation concerning the months worked. For more information on calculating monthly wage amounts when using these queries, see SI 00820.130C.6. in this section.\n\n•\n\nWhen using a combination of primary and secondary evidence as described in SI 00820.130A.3 in this section, document the combination of primary and secondary evidence that you used to develop and verify the monthly earnings on a Report of Contact. For more information on electronic evidence documentation and retention, see GN 00301.286.\n\nExamples:\n\n•\n\nMEF queries, W-2 and other tax forms that provide annual amounts: Document steps to obtain higher priority evidence and allegation of months worked on a Report of Contact or signed statement.\n\n•\n\nIBIQ/NDNH/SASRO/OCSS queries that provide quarterly amounts: Document on a Report of Contact or signed statement steps taken to obtain higher priority evidence, the person's acceptance of the wage amounts provided on the query, and the months in which the person alleges working.\n\n•\n\niTOPSS queries: Document steps taken to obtain higher priority evidence and that the person agrees with the pay stub details reported through the Ticket to Work program on a Report of Contact or signed statement.\n\n5. \nProcedure for wage evidence: employer statement\n\nTo minimize burden on businesses, we prioritize many sources of primary and secondary evidence over employer contact. If wage and employment information from PIE, pay stubs, wage evidence from an SSA-approved wage verification company, and secondary evidence are unavailable, as listed in the first three bullets under SI 00820.130A.2 in this section, contact the employer to develop and verify wages.\n\nDocument the steps to obtain pay stubs, wage verification company data, or secondary evidence and why they were unsuccessful on a Report of Contact. For instructions on electronic evidence documentation and retention, see GN 00301.286.\n\na. \nRequesting employer statement\n\nRequest employer statements to develop and verify wages in the following order:\n\n•\n\nOral statement from the employer (e.g., telephone) recorded on either an SSA-5002 form or Report of Contact page.\n\nNOTE: \n\nDo not disclose an individual’s PII on voicemail messages to employers.\n\n•\n\nWritten statement from the employer (e.g., SSA-L4201-BK, Letter to Employer Requesting Wage Information). Do not send SSA-L4201s to employers that provide wage evidence through an SSA-approved wage verification company.\n\nInclude the following information when recording an employer's statement on an SSA-5002 or Report of Contact:\n\n•\n\nThe source of the evidence, person contacted;\n\n•\n\nThe employer’s name\n\n•\n\nTime period covered by oral/written statement;\n\n•\n\nGross wages paid;\n\n•\n\nPay date (if known); and\n\n•\n\nAny applicable deductions or exclusions from gross wages.\n\nFor additional information related to wage verification procedures, see SI 00820.135.\n\n6. \nProcedure for wage evidence: evidence reflects only an annual or quarterly wage amount\n\nIf the evidence (e.g., queries, tax forms) reflects only an annual or quarterly wage amount, process the evidence according to the following:\n\na. \nCalculating monthly wage amounts\n\nAsk the worker to state the work months covered by the annual or quarterly wage amount and document their allegations on a signed statement or a Report of Contact. Posting the alleged work months to the corresponding SSI Claims system Wages page alone is insufficient documentation.\n\nDivide the annual or quarterly wage amount by the number of alleged work months to calculate the monthly wage amounts for the alleged work months. When determining whether to average either quarterly or yearly earnings, give preference to the quarterly earnings.\n\nIf it appears that the wages belong to someone other than the individual worker or deemor (e.g., the name shown on the NHDH query is different), do not post the wages to the record.\n\nFor instructions on handling potentially erroneous or duplicate earnings postings on SSA earnings records, see RS 01404.140.\n\nb. \nCalculating monthly wage amounts when previous months verified\n\nWhen the system shows previously verified wages for a particular employer for a portion of the year or quarter that you are developing, do not change the verified amounts unless new evidence indicates that the prior determination was erroneous.\n\nDetermine the wages for the unverified months by subtracting the previously verified amounts from the annual or quarterly totals for the employer and dividing the remaining amount by the number of unverified months of work alleged.\n\nDocument that you subtracted the previously verified amounts from the annual or quarterly totals and divided the remaining amount by the number of unverified alleged work months on a Report of Contact.\n\n7. \nProcedure for using wage evidence from non SSA-approved wage verification companies\n\nYou may accept wage evidence from non SSA-approved wage verification companies as secondary evidence of wages only under certain conditions per SI 00820.147C.1.c. If an employer will not provide wage verification and refers you to a non-SSA approved company for wage information, ask the worker to obtain the evidence from the company directly.\n\nIMPORTANT: \n\nSSA employees must not establish online accounts with non-approved wage verification companies or enter any personal or worker information in non-SSA approved wage verification websites, or otherwise contact or disclose information to the non-approved wage verification company.\n\n8. \nProcedure for wage evidence: no acceptable evidence of wages is available\n\nIf evidence of wages is not available, obtain the individual's statement either signed (i.e., SSA-795) or recorded on a Report of Contact that includes the gross amount, frequency, and duration of wages.\n\nIf the sole evidence of wages is the individual’s statement, document the steps taken to obtain acceptable primary and secondary evidence, and why they were unsuccessful on a Report of Contact. Post the alleged wages in the verified column of the SSI Claims system Wages page or via 1719b using a verification code of “9.” For instructions on electronic evidence documentation and retention, see GN 00301.286.\n\n9. \nProcedure for wage evidence: suspected fraud cases\n\nIn any suspected fraud case, obtain the employer’s written statement regarding wages using the SSA-L4201-BK.\n\nFor information on obtaining evidence in suspected fraud cases, see GN 04115.005.\n\nFor information on obtaining additional overpayment notification procedures related to collection of overpayments when fraud is suspected, see SI 02201.007.\n\n10. \nProcedure for wage evidence: work report receipts\n\nSSA is required by law to issue a receipt when we receive a report of a change in an SSI recipient’s work activity or earnings. This policy applies to work-related reports received from the recipient, or from the recipient’s or beneficiary’s representative payee or authorized representative. For further information related to work reports and situations where we require a receipt, see DI 13010.020.\n\nD. \nProcedure for verifying “reported” wages\n1. \nDo not routinely verify wages that meet criteria to be considered “reported” wages unless an exception applies\n\nConsider “reported” wages as verified if they meet the criteria in SI 00820.143E (Monthly Wage Reporting). Do not routinely verify “reported” wages, unless one of the exceptions applies to the period that you are developing, see SI 00820.130B.3 in this section.\n\n2. \nNo wage interface alert on the SSR\n\nIf an exception applies during the development period and a wage interface alert is not present in the DIAR segment of the SSR, verify the wages using the procedures in SI 00820.130C in this section.\n\n3. \nWage interface alert on the SSR\n\nIf a wage interface alert applying to the period that you are developing is present in the DIAR segment of the SSR, develop for evidence of wages using the instructions:\n\n•\n\nSI 02310.055 Master Earnings File (MEF) Match (K6 and K7 Diary)\n\n•\n\nSI 02310.056 Master Earnings File (MEF) Match (J3 and J5 Diaries)\n\n•\n\nSI 02310.062 State Wage Record Match (S2 Diary)\n\n•\n\nSI 02310.063 State Wage Record Match (S7 Diary)\n\nE. \nTermination of wages\n\nDevelop termination of wages whenever workers allege that they have stopped working or changed jobs. Accept a worker’s report of wage termination on a signed statement or Report of Contact page unless you have reason to question the accuracy of the statement (e.g., claimant frequently fails to report work information accurately). The statement must include:\n\n•\n\nthe date last worked; and\n\n•\n\nthe date of the final paycheck paid by the employer.\n\nIf the individual is not able to provide an accurate statement or evidence on the record conflicts with the statement, obtain primary evidence of wage termination. In order of priority, as evidence of termination of wages, accept the following:\n\n•\n\nInformation from an SSA-approved wage verification company listed in SI 00820.147 (Evidence of Wages – Wage Verification Companies) indicating the date employment ceased;\n\n•\n\nOral statement from the employer; or\n\n•\n\nWritten or faxed evidence from the employer.\n\nStore wage termination evidence in the Evidence Portal or document the evidence on a Report of Contact page. When recipients, their representative payees, or their authorized representatives report a wage termination event, issue a work report receipt according to SI 00820.130C.10 in this section.\n\nCAUTION: \n\nDevelop for receipt of unemployment benefits when an individual alleges termination of wages. For more information about unemployment benefits, see SI 00830.230. If the individual is an SSI recipient and they are not receiving unemployment benefits, refer the recipient for unemployment benefits as described in SI 00510.005.\n\nF. \nReferences\n•\n\nSI 00510.005 Types of Other Program Benefits\n\n•\n\nSI 00810.550 Developing Income Discovered in Negative Verification\n\n•\n\nSI 00820.131 Income Summary Worksheets\n\n•\n\nSI 00820.132 Periodic Reporting Income Summary Worksheets\n\n•\n\nSI 00820.135 Wage Verification-Over $65 Per Month\n\n•\n\nSI 00820.142 Alternative Wage Verification – Sheltered Workshop Pays $65 or Less Per Month to All\n\n•\n\nSI 00820.143 Monthly Wage Reporting\n\n•\n\nSI 00820.144 Monthly Wage Reporting – Recruiting Reporters\n\n•\n\nSI 00820.145 Form SSA-L4201-BK (Letter to Employer Requesting Wage Information)\n\n•\n\nSI 00820.147 Evidence of Wages – Wage Verification Companies\n\n•\n\nSI 00820.148 Automated Wage Verifications from Payroll Data Providers Received through the Payroll Information Exchange (PIE)\n\n•\n\nSI 00830.230 Unemployment Insurance Benefits\n\n•\n\nSI 02201.005 SSI – What Is an Overpayment?\n\n•\n\nSI 02310.200 Payroll Data Provider Wages Received through the Payroll Information Exchange (PIE) (EE Diary)\n\n•\n\nDI 13010.020 Work Reports\n\n•\n\nGN 00204.150 Authorization to Obtain Wage and Employment Information from Payroll Data Providers via an Information Exchange for the Social Security Disability Insurance (SSDI) and Supplemental Security Income (SSI) Programs\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nGN 04115.005 Obtaining Evidence in the Development of Violations\n\n•\n\nMS 08509.001 Interstate Benefit Inquiry (IBIQ)\n\n•\n\nMS 05203.015National Directory New Hire, Wage, Unemployment Menu (NDNH)\n\n•\n\nMS 01701.003 Evidence Screen\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500820130\n\t\nSI 00820.130 - Evidence of Wages or Termination of Wages - 03/25/2025\nBatch run: 09/11/2026\nRev:03/25/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "52c3484dd22f2635c86b47a094a2a2f3f427c6c4247e05fc393d9ac58bab72d5"
      },
      {
        "id": "SI00820.143:B",
        "source_code": "SI00820.143",
        "start": 987,
        "end": 5319,
        "exact_text": "B. \nGlossary of terms for SSI wage reporting\n1. \nAlleged\n\nAn “alleged” monthly wage amount is any:\n\n•\n\nmonthly wage report an individual submits without evidence that does not meet the criteria for us to consider it “reported;” or\n\n•\n\nwage report submitted without evidence for a month other than the current month, or the month immediately preceding the current month.\n\n2. \nAutomated wage reporting methods\n\nAutomated wage reporting methods are electronic tools or systems that recipients, deemors, and representative payees may use to report monthly wages. These methods of wage reporting:\n\n•\n\neliminate the need for field office (FO) intervention in processing most monthly wage reports; and\n\n•\n\npost wages to the SSI claim system (i.e., MSSICS or CCE) and the Supplemental Security Record (SSR) as “reported” wages.\n\nThe SSA Mobile Wage Reporting application (SSAMWR), the SSI Telephone Wage Reporting system (SSITWR), and the myWageReport application (myWR) are all automated wage-reporting methods.\n\n3. \nEmployer Identification Number (EIN)\n\nEINs are unique identification numbers assigned to employers by the Internal Revenue Service (IRS) for tax purposes. SSA uses EINs to record employer wage reports and associate an individual’s earnings with a particular employer. EINs are present on W-2 forms and may be included on pay stubs. Additionally, SSA records EINs on wage-related queries like the Detailed Earnings Query (DEQY) and New Hire Data Query (NDNH). Using the Alpha Access to the Employment Information File (AEQY), technicians may locate EINs using employer information.\n\nEINs are becoming increasingly important for automation in SSI wage reporting. For example, myWR requires an EIN match in the SSI claim system or eWork in order to display eligible employers to users. If the EIN field is not completed, myWR users will not be able to report wages for that employer. For this reason, technicians are encouraged to complete EIN fields on all Wages pages in the SSI Claim system (i.e., CCE) when establishing new employers and updating information for existing employers.\n\nSee MS 08114.027 for more information about the Wages page.\n\n4. \nJ3 diary\n\nThe J3 diary detects discrepancies between the Master Earnings File (MEF) and the SSR where a recipient or deemor’s wage amount on the SSR is more than what the MEF reflects.\n\nThe system generates an alert for over-tolerance discrepancies of more than $1,000 annually.\n\nRefer to development instructions in SI 02310.056.\n\n5. \nJ5 diary\n\nThe J5 diary detects discrepancies between the MEF and the SSR where a deemor’s wage amount on the SSR is more than what the MEF reflects.\n\nThe system generates an alert for over-tolerance discrepancies of more than $2,000 annually.\n\nRefer to development instructions in SI 02310.056.\n\n6. \nReported\n\nA “reported” monthly wage amount is submitted by a recipient, representative payee or deemor and is derived from pay stub wage information; the individual making the report need not submit the underlying pay stub(s) at the time of the report. The reported wage amount must be:\n\n•\n\nposted to the SSI claim system or the SSR before the recurring payment tape cutoff for the subsequent month; or\n\n•\n\nsubmitted using myWR, SSAMWR, or SSITWR on any day during the current reporting month.\n\nTo consider wages “reported,” the submitted wage amount must include the total gross wages received for the current month or the month immediately preceding the month in which we receive the report.\n\n7. \nS7 diary\n\nThe S7 diary detects discrepancies between the Office of Child Support Enforcement (OCSE) database and the SSR where a recipient or deemor’s wage amount on the SSR is more than what the OCSE reflects. The system generates an alert for over-tolerance discrepancies of more than $250 per quarter for recipients and $500 per quarter for deemors.\n\n8. \nSSI Monthly Wage Verification Application (SSIMWV)\n\nSSIMWV is an Intranet-based application that automates SSA staff's input of monthly wage reports submitted with pay stubs for electronic cases and cases outside of the SSI claim system (i.e., non-MSSICS or non-CCE).\n\n9. \nVerified\n\nA “verified” monthly wage amount is accompanied by evidence of wages (e.g., pay stubs). See SI 00820.130 for more information on wage evidence and SI 00820.135 for procedures on verifying wages.\n\n",
        "sha256": "48aa0e9eb706622024ddf9eab8904bf9d500c80cebdebe6d9daa8ac75f029cbd"
      },
      {
        "id": "SI00820.143:C",
        "source_code": "SI00820.143",
        "start": 5319,
        "end": 9897,
        "exact_text": "C. \nAutomated wage reporting methods\n\nSSA offers several electronic tools that SSI recipients, deemors, and representative payees may use to report wages to SSA. Each tool has slightly different features, but all share the following basic features:\n\n•\n\naccept monthly wage reports based on pay stub wage information in the reporter’s possession from both SSI only and concurrent recipients, as well as their representative payees and deemors;\n\n•\n\npost the wage amount in the “Reported Amount” column on the Wages page and indicates the amount with a “0” wage verification code on the SSR;\n\n•\n\naccept wage reports for only the month immediately preceding the report on any day during the current reporting month for SSI and concurrent reporters;\n\n•\n\ngenerate a wage receipt for the SSI recipient, deemor, or their representative payee and stores a copy of the receipt in the Online Retrieval System (ORS).\n\nIMPORTANT: Encourage users of any of the automated wage reporting tools to report wages in the first six days of the month to help prevent improper payments.\n\n1. \nmyWageReport (myWR)\n\nAvailable behind the my Social Security (mySSA) portal, myWR is an automated wage reporting application for Title II disability (SSDI), SSI, and concurrent beneficiaries.\n\nIn addition to the basic features, myWR:\n\n•\n\nrequires the reporting individual to have a mySSA account;\n\n•\n\naccepts wage reports for SSDI only beneficiaries as well as SSI and concurrent recipients;\n\n•\n\nSSDI-only beneficiaries may report up to 24 months of past wages;\n\n•\n\npasses wage information to eWork when SSDI is involved;\n\n•\n\ndisplays employers for which the reporter can submit wage information based on an EIN match either on a Wages page in the SSI claim system or in eWork;\n\n•\n\naccommodates recipients and deemors with multiple employers; and\n\n•\n\nrequires input of pay stub details instead of a calculated monthly gross wage total.\n\nIMPORTANT: Whenever possible, strongly encourage concurrent reporters to use myWR over SSAMWR and SSITWR as myWR is designed to efficiently pass information to Title II systems. Since the various electronic wage-reporting systems ask for information in different formats (e.g., totaling gross wages or entering pay stub data directly), encourage users to pick one method and continually report using that method. For additional information on automated reporting options, see SI 00820.144.\n\n2. \nSSA Mobile Wage Reporting application (SSAMWR)\n\nThe SSAMWR application allows recipients, representative payees, and deemors to report monthly wages using a mobile device. Wage reporters can download and install the free SSAMWR application on an Apple or Android mobile device.\n\nIn addition to the basic features, the SSAMWR system:\n\n•\n\nrequires input of each individual pay stub instead of a calculated a monthly gross wage total;\n\n•\n\nallows users the option of uploading or capturing photos of their pay stubs, which the app reads and propagates to data fields using Optical Character Recognition and Intelligent Document Processing technologies;\n\n•\n\nstores uploaded or captured photo images in the Evidence Portal (EP), which technicians may access for wage verification purposes;\n\n•\n\ntransmits wage data to Title II by posting to the Disability Control File (DCF). For more information about how these monthly wage reports post to the DCF, see DI 13010.605D.2; and\n\n•\n\nrequires the reporting individual to authenticate using their Social Security Number, name, and date of birth.\n\nNOTE: \n\nDeemors reporting their own wages authenticate using their own information in the app, and do not enter the recipient’s information. The deemor’s SSN is connected to the recipient’s record; so, the report is posted properly.\n\n3. \nSSI Telephone Wage Reporting system (SSITWR)\n\nThe SSITWR system is an automated monthly wage reporting system that allows recipients, their representative payees, and deemors to call a toll-free number to report the prior month’s gross wages.\n\nIn addition to the basic features, SSITWR:\n\n•\n\nrequires wage reporters to talk into the phone to submit wages instead of keying data on computer or smart device screens;\n\n•\n\nrequires users to calculate their gross monthly wages and report a single dollar amount each month;\n\n•\n\nallows wage reporters to include deductions, such as cafeteria plans, when trained and directed to do so by SSA staff according to SI 00820.144C; and\n\n•\n\ntransmits wage data to Title II by posting to the Disability Control File (DCF). For more information about how these monthly wage reports post to the DCF, see DI 13010.605D.2.\n\n",
        "sha256": "f7c6e18eb7ddf8e748512fed90eb6f33a6de87dccebb4220fc2ba3e435aa1673"
      },
      {
        "id": "SI00820.143:D",
        "source_code": "SI00820.143",
        "start": 9897,
        "end": 12395,
        "exact_text": "D. \nRecruitment for automated wage reporting methods (myWR, SSAMWR, and SSITWR)\n1. \nRecruitment discussions are mandatory\n\nRecruitment discussions are mandatory. Recruit all recipients, their representative payees, and deemors to report monthly wage amounts using automated reporting tools (e.g., myWR, SSAMWR, and SSITWR). Individuals may choose their reporting method and are not required to report by using an automated reporting method. Do not refuse to accept monthly wage reports submitted using a method other than an automated wage reporting method (e.g., mailing pay stubs).\n\nFor specific instructions on how to recruit wage reporters to use automated reporting methods and case characteristics that may influence the choice of reporting method, see SI 00820.144C.\n\n2. \nDisclaimer language provided in the electronic reporting methods to encourage reports during the first 6 days of the month\n\nTo be considered in time to process a particular month’s payment, SSI recipients or their representative payees generally must report income changes within the first ten days of the month following the month of change, as described in SI 02301.005. While myWR, SSAMWR, and SSITWR accept wage reports on any day during the current reporting month, regular reporting prior to the Goldberg Kelly (GK) cutoff can affect payment in time to prevent improper payments. Therefore, while recruiting participants to use electronic wage reporting methods, emphasize the importance of reporting wages during the first 6 days of the month to avoid incorrect payments.\n\nmyWR\n\n \n\nTo encourage submission of SSI and concurrent wage reports within the first six days of the reporting month, myWR displays informational messages in the wage-reporting path. For example, individuals reporting May’s wages in June see the following message on the Wage Report Confirmation screen as they are submitting their report: \"Please report your wages for June in the first six days of July to avoid incorrect payments.”\n\nSSAMWR and SSITWR\n\n \n\nIf the reporter makes a successful wage report after the GK systems cutoff date, SSAMWR or SSITWR present the following language: \"Because we received the report after (Automated fill in of the current month and GK cutoff day), the wages you reported today might not be reflected in a future SSI payment. We will mail a notice if there are changes to the payment amount explaining these changes and your right to appeal.”\n\nFor more information on GK processing, see SI 02301.301.\n\n",
        "sha256": "5752e411b62fb49fea35ad323e1259194a9041a2d318589f41fa0229dba6050f"
      },
      {
        "id": "SI00820.143:E",
        "source_code": "SI00820.143",
        "start": 12395,
        "end": 16144,
        "exact_text": "E. \nPolicy for “reported” wage amounts\n\nTo consider wages “reported,” a monthly wage report must meet several criteria discussed in SI 00820.143E.3.\n\nBy default, wages we cannot consider “reported” must be identified as “verified” or “alleged.”\n\nNever consider wages earned by an ineligible child as “reported.” Wages earned by ineligible children cannot be reported through electronic wage reporting methods discussed in SI 00820.143C and must be verified following normal wage verification policies (e.g., SI 00820.135B).\n\n1. \nMonths we may identify wages as “reported”\n\nOnly identify total gross wage amounts for the current month or the month immediately preceding as “reported” wages.\n\nWage reports pertaining to any period more than one month prior to the current month must be identified as “verified” or “alleged.”\n\nConsider wage amounts for the current month “reported” only if the recipient or deemor is not expected to receive any additional wages in the reporting month.\n\n2. \nNo evidence is required for “reported” wages\n\nNo wage evidence must accomany the wage report at the time of submission to identify a monthly wage report as “reported;” however, the reported amount must be derived from pay stub wage information in the wage reporter's possession. The reported wage amount must be equal to the total gross wages indicated on the individual’s pay stubs and meet all other criteria to be considered “reported.”\n\n3. \nMethods for submitting “reported” wages and criteria for considering wages as “reported”\na. \nWages derived from pay stubs\n\nWe consider a monthly wage amount derived from pay stubs “reported” when it is:\n\n•\n\nderived from the gross wages indicated on the individual’s pay stubs for the month; and\n\n•\n\nsubmitted once the individual has received all wages for the reported month.\n\nWe consider a monthly wage report submitted when pay stubs are missing as a “reported” amount if:\n\n•\n\nthe reporter (or technician documenting the report) can determine the total gross wages using year-to-date figures on other pay stubs; or\n\n•\n\nthe reporter submits multiple pay stubs for the month and we obtain the gross wage amount for the missing pay stubs through subsequent contact with the individual (e.g., telephone contact).\n\nb. \nWages reported through myWR, SSAMWR, and SSITWR\n\nWe deem monthly wages to be “reported” when submitted for a prior month using automated wage reporting tools (e.g., myWR, SSAMWR, or SSITWR) on any day during the current reporting month.\n\nc. \nWages “reported” through telephone or field office (FO) contact\n\nSometimes wage reporters may call in or bring their wage report to their local office. For example, if a wage reporter is unsuccessful submitting their wages for the month through the SSITWR system, they may call their local office to submit their report instead of making repeated attempts with the automated system. Monthly wages submitted in person or through telephone contact with the FO that otherwise meet the requirements in SI 00820.143E.3.a for the current or prior month are “reported” wages if the FO processes the report before:\n\n•\n\nthe GK cutoff date in the month the report is received; or\n\n•\n\nthe recurring payment tape cutoff in the month the report is received (i.e., during the GK temporary period).\n\nIf a monthly wage report submitted during the GK temporary period results in an adverse action, issue an online GK notice to the recipient to consider the wage amount “reported.”\n\nEXCEPTION: If the case is an exception to online GK notice issuance, do not consider the wage amount as “reported.” For additional information related to online GK notices, see SI 02301.305.\n\nFor processing instructions when such reports are accompanied by wage evidence, see SI 00820.143F.1\n\n",
        "sha256": "05e70148cca4e1b40cae5f6bacefe4f9a0bdf29b078b600e72f566c8905cb068"
      },
      {
        "id": "SI00820.143:F",
        "source_code": "SI00820.143",
        "start": 16144,
        "end": 23069,
        "exact_text": "F. \nProcedure for processing monthly wage reports\n\nProcess wage reports according to whether we identify the wages as “verified,” “reported,” or “alleged.”\n\nThe wage reporter may choose any method in this section to report wages, regardless of the level of automation. Do not refuse to accept monthly wage reports submitted using a method other than an automated wage reporting methods (e.g., mailing pay stubs).\n\nSection 202 of the Social Security Protection Act of 2004 requires that we issue a receipt for all wage reports submitted by recipients or their representatives (including representative payees). Issue a receipt regardless of whether we identify the wage report as “verified,” “alleged,” or “reported.”\n\n1. \n“Verified” wages\na. \nUsing SSIMWV to streamline pay stub inputs\n\nSSIMWV streamlines the input of pay stubs by propagating wage information to the Wages page (i.e., IWAG) in the SSI claim system or the SSR. SSIMWV posts wage amounts in the “Verified Amount” column of the appropriate Wages page or on the SSR with a verification code of “9.” Do not use SSIMWV to process monthly wage reports submitted without pay stubs.\n\nTo access the SSIMWV Users Guide and for additional information related to SSIMWV, refer to SI 00820.144D.\n\nb. \nProcessing the wage report\n\nUse the Intranet-based SSIMWV system to input monthly wage amounts submitted with pay stubs.\n\nIf you cannot process the case using SSIMWV, input the wage amount in the “Verified Amount” column on the SSI claim system Wages page.\n\nFor cases outside the SSI claim system (i.e., non-MSSICS or non-CCE cases), transmit the EN field via SSA-1719(B) with a verification code of “9”. For more information on the EN field, see SM 01305.101.\n\nInput an estimate of future wages according to SI 00820.150, beginning with the month after the reported month.\n\nUse one of the following methods to post an estimate:\n\n•\n\nSSIMWV - the system prompts the user for information to derive an estimate and posts the estimate to the “Alleged Amount” column on the Wages page.\n\n•\n\nSSI claim system/SSA-1719(B) - post an estimate of future wages, per instructions in SI 00820.150D.\n\nProcess verified wage amounts submitted by a concurrent beneficiary by entering the eWork application for possible Title II development. eWork subsequently transfers you to SSIMWV to input the SSI monthly wage amount. For more information about using eWork to process wage reports, see DI 13010.020.\n\nc. \nReceipt issuance\n\nIssue a wage report receipt to the recipient or their representative payee when using SSIMWV. For in-person reports, generate a receipt immediately, and provide the receipt to the recipient or their representative payee. SSIMWV automatically prints and dates the receipt.\n\nIf you cannot process the wage report using SSIMWV, issue the receipt using either:\n\n•\n\neWork; or\n\n•\n\nthe Document Processing System (DPS) via the SSA-L724 (Work Report Receipt).\n\nFor additional information related to issuance of receipts for “verified” wage reports that you cannot process using SSIMWV, see DI 13010.020.\n\nd. \nDocumentation of a verified wage amount\n\nArchive the SSIMWV receipt in ORS. The ORS-stored receipt serves as documentation of the pay stub evidence submitted by the reporter.\n\nNo separate action is necessary to document the report.\n\nIf SSIMWV does not issue a receipt, or the receipt is not stored in ORS, document the wage report using the procedures:\n\n•\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n2. \n“Reported” wages\na. \nProcessing a reported wage amount submitted via myWR, SSAMWR, and SSITWR\n\nWages reported using myWR, SSAMWR, or SSITWR automatically:\n\n•\n\npost to the “Reported Amount” column of the Wages page in the SSI claim system;\n\n•\n\ntransmit to the SSR with a verification code of “0;”\n\n•\n\ngenerate an automated wage report receipt; and\n\n•\n\nrequire no additional actions.\n\nb. \nProcessing a monthly wage report received outside of myWR, SSAMWR, and SSITWR\n\nWhen you receive a monthly wage amount directly from a reporter (e.g., via telephone contact), you must:\n\n1. \n\nConfirm whether you can process the monthly wage amount submitted as a “reported” wage by determining if the:\n\n•\n\nwage earner received the reported wages in the current month or the month immediately preceding it;\n\n•\n\ngross wage amount submitted is based on pay stub wage evidence in the individual’s possession (Ask the reporter.); and\n\n•\n\nwage report is submitted and you can process the report either before the GK cutoff, or during the temporary GK period in the month that we receive the report.\n\n2. \n\nIf you can consider the gross wages as “reported”:\n\n•\n\ninput the wages on the Wages page in the SSI claim system in the “Reported Amount” column;\n\n•\n\npost an estimate of future wages in the “Alleged Amount” column starting with the month after the reported month; and\n\n•\n\nsend the transaction to the SSR.\n\nFor instructions on estimating future wages, see SI 00820.150.\n\nIMPORTANT: You cannot transmit monthly wage amounts identified as a “reported” amount via SSA-1719(B) input. Therefore, you cannot transmit “reported” wages to the SSR for cases outside the SSI claim system (i.e., non-MSSICS or non-CCE). Never use SSIMWV to process amounts representing “reported” wages.\n\nc. \nReceipt issuance\n\nWhile myWR, SSAMWR, and SSITWR automatically generate receipts, wage reports made via contact with the FO generally require a manual receipt.\n\nTake the following actions whenever a receipt is required but not automatically generated:\n\n•\n\nIssue a receipt to the SSI beneficiary or their representative payee using the notice titled, “Monthly Wage Reporting – Receipt” in DPS (SSA-L724).\n\n•\n\nPrint the receipt locally and store the receipt in ORS.\n\nFor more information on receipt issuance, see DI 13010.020.\n\nd. \nDocumentation of “reported” wage amounts\n\nSeparate action is not required to document a wage amount that we identify as “reported.”\n\nThe wage amount is indicated on the SSR with a “0” verification code.\n\nThe “0” verification code remains on the SSR unless a subsequent action is taken to verify the “reported” wage amounts.\n\n3. \n“Alleged” wages\na. \nProcessing “Alleged” wage reports\n\nProcess a monthly wage report not identified as “verified” or “reported” as follows:\n\n•\n\nPost the wages in the “Alleged Amount” column on the SSI claim system Wages page or to the SSR using an SSA-1719(B) input with a verification code of “1” in the EN field.\n\n•\n\nInput an estimate of future wages per instructions in SI 00820.150.\n\nb. \nReceipt issuance\n\nIssue the receipt for an alleged monthly wage amount using either:\n\n•\n\neWork; or\n\n•\n\nDPS via the SSA-L724 (Work Report Receipt).\n\nTo issue receipts for alleged monthly wage amounts, see DI 13010.020C.\n\nc. \nDocumentation of alleged wage amounts\n\nDocumentation is not required for a monthly wage report identified as an allegation.\n\n",
        "sha256": "8ebadb6c42936dab9ff6339988c7437f3b2e5fa5ad52cfe783691dc2d6087df5"
      },
      {
        "id": "SI00820.143:H",
        "source_code": "SI00820.143",
        "start": 23655,
        "end": 27155,
        "exact_text": "H. \nExamples of SSI wage reports\n\nExample 1 - Monthly wage amount meeting the criteria to be considered “reported”\n\nJane works at ABC Company and earns $250 bi-weekly. Jane receives their last paycheck for January on day 26 of the month. Jane computes their monthly gross wages for January as $500 and calls the FO on February 7 to report wages.\n\nWhile speaking with Jane, the FO representative confirms that the monthly wage amount Jane submitted is based on information from all the pay stubs Jane received for the month before the report, recognizes the GK cutoff has not yet occurred and the wage input can be made before the cutoff. The FO representative opens a stand-alone post-eligibility event in the SSI claim system. The FO representative enters the $500 Jane earned in January in the “Reported Amount” column on the Wages page for ABC Company, prints a “Monthly Wage Reporting – Receipt” from DPS, and mails the receipt to Jane.\n\nSince the monthly wage amount Jane submitted meets the criteria to be considered a “reported” monthly wage amount, no documentation is necessary at the time of the report.\n\nExample 2 - Monthly wage report determined to be an “alleged” wage amount\n\nJane (from example 1) computes the wages for January to be $500. However, Jane does not call the FO to report the wages until February 20. The FO representative recognizes that Jane’s monthly wage report is based on information from the pay stubs and corresponds to the month prior to the month of report. However, the FO representative cannot consider the wage amount “reported” since the recurring payment tape cutoff has passed.\n\nThe FO representative correctly enters the monthly wage report in the “Alleged Amount” column on the Wages page for ABC Company, issues a wage report receipt to Jane, and requests that Jane send in their pay stubs for the month of January.\n\nExample 3 - Combination of pay stubs and a “reported” wage amount\n\nTom works for the local school system and earns $200 per week. Every month Tom sends pay stubs for the prior month into the local FO for processing via SSIMWV. The FO receives the pay stubs for March on April 5.\n\nThe FO representative examines the pay stubs and determines that Tom neglected to send in pay stubs for the last two weeks of March. The FO representative contacts Tom by phone and asks them to provide pay stub information for the missing pay stubs. Tom finds the missing pay stubs and tells the FO representative that Tom earned $200 each week. The FO representative uses the combination of the pay stubs Tom provided and Tom's “reported” wage amount for the missing pay stubs to determine the gross monthly wages for March. Since the report is completed before the GK cutoff, the FO representative enters the wage amount in the “Reported Amount” column of the SSI claim system Wages page and sends Tom a receipt. Documentation is not required because the FO representative considers the monthly wage amount as “reported.”\n\nExample 4 - Monthly wage report input using SSIMWV\n\nTom (from example 3) submits all pay stubs for March to the FO on April 5. The FO representative enters the pay stubs in SSIMWV and correctly identifies each of them as “verified.” The FO representative prints a receipt through SSIMWV and archives the receipt in ORS before transmitting the wage amount.\n\nThe wage report receipt that is stored in ORS serves as documentation of the wage evidence Tom submitted for March. No further action is necessary by the FO representative.\n\n",
        "sha256": "1a38f4ec970bd9ad9658bbae77c5d1b00e87231aa5086c93c0ebdeffa9354569"
      },
      {
        "id": "SI00820.143:I",
        "source_code": "SI00820.143",
        "start": 27155,
        "end": 28811,
        "exact_text": "I. \nSummary of wage reporting methods\n\nThe following chart contains:\n\n•\n\na summary of monthly wage reporting methods;\n\n•\n\nthe date we must receive the reports; and\n\n•\n\nactions we must take to input the wages and issue a receipt.\n\nMonthly Report Type\n\n\t\n\nReporting Timeframe\n\n\t\n\nWhich Month(s) Wages Can Be Reported\n\n\t\n\nNecessary Action to Post Wages\n\n\t\n\nNotices\n\n\t\n\nSSR Coding\n\n\n\n\n \n\n\t\n\n \n\n\t\n\n \n\n\t\n\n \n\n\t​\t​\n\n\nmyWR\n\n\t\n\nPreferably by day 6 of the month, but available on any day during the current reporting month.\n\n\t\n\nFor SSI and concurrent: wages for the month immediately preceding ONLY.\n\n \n\nFor SSDI: Wages up to 24 months in the past.\n\n\t\n\nNone\n\n\t\n\nAutomated receipt and GK notice.\n\n\t\n\n“0”\n\n\n\n\nSSITWR system\n\n \n\n \n\n \n\nand\n\n \n\n \n\n \n\nSSAMWR application\n\n \n\n \n\n\t\n\nPreferably by day 6 of the month, but available on any day during the current reporting month.\n\n\t\n\nWages for the month immediately preceding ONLY.\n\n \n\n \n\n\t\n\nNone\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\t\n\nAutomated receipt and GK notice.\n\n \n\n \n\n\t\n\n“0”\n\n \n\n \n\n \n\n \n\n\n\n\nPay stubs\n\n\t\n\nNo timeframe\n\n\t\n\nAny month\n\n\t\n\nInput wages using SSIMWV or the “Verified Amount” column on the Wages page in the SSI claim system.\n\n\t\n\nSSIMWV generates receipt GK either automated or manual. If not using SSIMWV, manually issue the receipt.\n\n\t\n\n“9”\n\n\n\n\nOral report\n\n \n\nor\n\nWritten wage report faxed or mailed to the FO.\n\n\t\n\nBefore recurring tape cutoff each month.\n\n\t\n\nCurrent month and the month immediately preceding.\n\n\t\n\nInput wages to “Reported Amount” column on Wages page in the SSI claim system.\n\n\t\n\nEmployee must issue a manual receipt. Manual GK notice may be necessary depending on the case characteristics.\n\n\t\n\n“0”\n\n",
        "sha256": "61964f1c538f0c4834f59e90e2ddd5915a20be3f872278d19e56d9d03e8dcef3"
      },
      {
        "id": "SI00820.143-whole",
        "source_code": "SI00820.143",
        "start": 0,
        "end": 30042,
        "exact_text": "Effective Dates: 09/26/2013 - Present\nPrevious | Next\n\nTN 91 (05-24)\n\nSI 00820.143 Monthly Wage Reporting\nA. \nIntroduction to monthly wage reporting\n\nSupplemental Security Income (SSI) recipients, their representative payees, and deemors must report changes in wages when changes occur or when the agency requests a report. We request that changes in wages are reported consistently, usually on a monthly basis. We process wage reports received via input to the SSI claim system (i.e., MSSICS or Consolidated Claims Experience (CCE)) or via the SSA-1719(B) (SSI Post-Eligibility Data Input). The specific method used to input the report depends on whether we consider the wage amount as “alleged,” “reported,” or “verified.”\n\nSee Also:\n\n•\n\nSI 02301.005 for information about reporting responsibilities specifically related to who must report, what they must report, when to report, and how to report.\n\n•\n\nDI 13010.020D for establishing a work report in eWork with Title II involvement.\n\nB. \nGlossary of terms for SSI wage reporting\n1. \nAlleged\n\nAn “alleged” monthly wage amount is any:\n\n•\n\nmonthly wage report an individual submits without evidence that does not meet the criteria for us to consider it “reported;” or\n\n•\n\nwage report submitted without evidence for a month other than the current month, or the month immediately preceding the current month.\n\n2. \nAutomated wage reporting methods\n\nAutomated wage reporting methods are electronic tools or systems that recipients, deemors, and representative payees may use to report monthly wages. These methods of wage reporting:\n\n•\n\neliminate the need for field office (FO) intervention in processing most monthly wage reports; and\n\n•\n\npost wages to the SSI claim system (i.e., MSSICS or CCE) and the Supplemental Security Record (SSR) as “reported” wages.\n\nThe SSA Mobile Wage Reporting application (SSAMWR), the SSI Telephone Wage Reporting system (SSITWR), and the myWageReport application (myWR) are all automated wage-reporting methods.\n\n3. \nEmployer Identification Number (EIN)\n\nEINs are unique identification numbers assigned to employers by the Internal Revenue Service (IRS) for tax purposes. SSA uses EINs to record employer wage reports and associate an individual’s earnings with a particular employer. EINs are present on W-2 forms and may be included on pay stubs. Additionally, SSA records EINs on wage-related queries like the Detailed Earnings Query (DEQY) and New Hire Data Query (NDNH). Using the Alpha Access to the Employment Information File (AEQY), technicians may locate EINs using employer information.\n\nEINs are becoming increasingly important for automation in SSI wage reporting. For example, myWR requires an EIN match in the SSI claim system or eWork in order to display eligible employers to users. If the EIN field is not completed, myWR users will not be able to report wages for that employer. For this reason, technicians are encouraged to complete EIN fields on all Wages pages in the SSI Claim system (i.e., CCE) when establishing new employers and updating information for existing employers.\n\nSee MS 08114.027 for more information about the Wages page.\n\n4. \nJ3 diary\n\nThe J3 diary detects discrepancies between the Master Earnings File (MEF) and the SSR where a recipient or deemor’s wage amount on the SSR is more than what the MEF reflects.\n\nThe system generates an alert for over-tolerance discrepancies of more than $1,000 annually.\n\nRefer to development instructions in SI 02310.056.\n\n5. \nJ5 diary\n\nThe J5 diary detects discrepancies between the MEF and the SSR where a deemor’s wage amount on the SSR is more than what the MEF reflects.\n\nThe system generates an alert for over-tolerance discrepancies of more than $2,000 annually.\n\nRefer to development instructions in SI 02310.056.\n\n6. \nReported\n\nA “reported” monthly wage amount is submitted by a recipient, representative payee or deemor and is derived from pay stub wage information; the individual making the report need not submit the underlying pay stub(s) at the time of the report. The reported wage amount must be:\n\n•\n\nposted to the SSI claim system or the SSR before the recurring payment tape cutoff for the subsequent month; or\n\n•\n\nsubmitted using myWR, SSAMWR, or SSITWR on any day during the current reporting month.\n\nTo consider wages “reported,” the submitted wage amount must include the total gross wages received for the current month or the month immediately preceding the month in which we receive the report.\n\n7. \nS7 diary\n\nThe S7 diary detects discrepancies between the Office of Child Support Enforcement (OCSE) database and the SSR where a recipient or deemor’s wage amount on the SSR is more than what the OCSE reflects. The system generates an alert for over-tolerance discrepancies of more than $250 per quarter for recipients and $500 per quarter for deemors.\n\n8. \nSSI Monthly Wage Verification Application (SSIMWV)\n\nSSIMWV is an Intranet-based application that automates SSA staff's input of monthly wage reports submitted with pay stubs for electronic cases and cases outside of the SSI claim system (i.e., non-MSSICS or non-CCE).\n\n9. \nVerified\n\nA “verified” monthly wage amount is accompanied by evidence of wages (e.g., pay stubs). See SI 00820.130 for more information on wage evidence and SI 00820.135 for procedures on verifying wages.\n\nC. \nAutomated wage reporting methods\n\nSSA offers several electronic tools that SSI recipients, deemors, and representative payees may use to report wages to SSA. Each tool has slightly different features, but all share the following basic features:\n\n•\n\naccept monthly wage reports based on pay stub wage information in the reporter’s possession from both SSI only and concurrent recipients, as well as their representative payees and deemors;\n\n•\n\npost the wage amount in the “Reported Amount” column on the Wages page and indicates the amount with a “0” wage verification code on the SSR;\n\n•\n\naccept wage reports for only the month immediately preceding the report on any day during the current reporting month for SSI and concurrent reporters;\n\n•\n\ngenerate a wage receipt for the SSI recipient, deemor, or their representative payee and stores a copy of the receipt in the Online Retrieval System (ORS).\n\nIMPORTANT: Encourage users of any of the automated wage reporting tools to report wages in the first six days of the month to help prevent improper payments.\n\n1. \nmyWageReport (myWR)\n\nAvailable behind the my Social Security (mySSA) portal, myWR is an automated wage reporting application for Title II disability (SSDI), SSI, and concurrent beneficiaries.\n\nIn addition to the basic features, myWR:\n\n•\n\nrequires the reporting individual to have a mySSA account;\n\n•\n\naccepts wage reports for SSDI only beneficiaries as well as SSI and concurrent recipients;\n\n•\n\nSSDI-only beneficiaries may report up to 24 months of past wages;\n\n•\n\npasses wage information to eWork when SSDI is involved;\n\n•\n\ndisplays employers for which the reporter can submit wage information based on an EIN match either on a Wages page in the SSI claim system or in eWork;\n\n•\n\naccommodates recipients and deemors with multiple employers; and\n\n•\n\nrequires input of pay stub details instead of a calculated monthly gross wage total.\n\nIMPORTANT: Whenever possible, strongly encourage concurrent reporters to use myWR over SSAMWR and SSITWR as myWR is designed to efficiently pass information to Title II systems. Since the various electronic wage-reporting systems ask for information in different formats (e.g., totaling gross wages or entering pay stub data directly), encourage users to pick one method and continually report using that method. For additional information on automated reporting options, see SI 00820.144.\n\n2. \nSSA Mobile Wage Reporting application (SSAMWR)\n\nThe SSAMWR application allows recipients, representative payees, and deemors to report monthly wages using a mobile device. Wage reporters can download and install the free SSAMWR application on an Apple or Android mobile device.\n\nIn addition to the basic features, the SSAMWR system:\n\n•\n\nrequires input of each individual pay stub instead of a calculated a monthly gross wage total;\n\n•\n\nallows users the option of uploading or capturing photos of their pay stubs, which the app reads and propagates to data fields using Optical Character Recognition and Intelligent Document Processing technologies;\n\n•\n\nstores uploaded or captured photo images in the Evidence Portal (EP), which technicians may access for wage verification purposes;\n\n•\n\ntransmits wage data to Title II by posting to the Disability Control File (DCF). For more information about how these monthly wage reports post to the DCF, see DI 13010.605D.2; and\n\n•\n\nrequires the reporting individual to authenticate using their Social Security Number, name, and date of birth.\n\nNOTE: \n\nDeemors reporting their own wages authenticate using their own information in the app, and do not enter the recipient’s information. The deemor’s SSN is connected to the recipient’s record; so, the report is posted properly.\n\n3. \nSSI Telephone Wage Reporting system (SSITWR)\n\nThe SSITWR system is an automated monthly wage reporting system that allows recipients, their representative payees, and deemors to call a toll-free number to report the prior month’s gross wages.\n\nIn addition to the basic features, SSITWR:\n\n•\n\nrequires wage reporters to talk into the phone to submit wages instead of keying data on computer or smart device screens;\n\n•\n\nrequires users to calculate their gross monthly wages and report a single dollar amount each month;\n\n•\n\nallows wage reporters to include deductions, such as cafeteria plans, when trained and directed to do so by SSA staff according to SI 00820.144C; and\n\n•\n\ntransmits wage data to Title II by posting to the Disability Control File (DCF). For more information about how these monthly wage reports post to the DCF, see DI 13010.605D.2.\n\nD. \nRecruitment for automated wage reporting methods (myWR, SSAMWR, and SSITWR)\n1. \nRecruitment discussions are mandatory\n\nRecruitment discussions are mandatory. Recruit all recipients, their representative payees, and deemors to report monthly wage amounts using automated reporting tools (e.g., myWR, SSAMWR, and SSITWR). Individuals may choose their reporting method and are not required to report by using an automated reporting method. Do not refuse to accept monthly wage reports submitted using a method other than an automated wage reporting method (e.g., mailing pay stubs).\n\nFor specific instructions on how to recruit wage reporters to use automated reporting methods and case characteristics that may influence the choice of reporting method, see SI 00820.144C.\n\n2. \nDisclaimer language provided in the electronic reporting methods to encourage reports during the first 6 days of the month\n\nTo be considered in time to process a particular month’s payment, SSI recipients or their representative payees generally must report income changes within the first ten days of the month following the month of change, as described in SI 02301.005. While myWR, SSAMWR, and SSITWR accept wage reports on any day during the current reporting month, regular reporting prior to the Goldberg Kelly (GK) cutoff can affect payment in time to prevent improper payments. Therefore, while recruiting participants to use electronic wage reporting methods, emphasize the importance of reporting wages during the first 6 days of the month to avoid incorrect payments.\n\nmyWR\n\n \n\nTo encourage submission of SSI and concurrent wage reports within the first six days of the reporting month, myWR displays informational messages in the wage-reporting path. For example, individuals reporting May’s wages in June see the following message on the Wage Report Confirmation screen as they are submitting their report: \"Please report your wages for June in the first six days of July to avoid incorrect payments.”\n\nSSAMWR and SSITWR\n\n \n\nIf the reporter makes a successful wage report after the GK systems cutoff date, SSAMWR or SSITWR present the following language: \"Because we received the report after (Automated fill in of the current month and GK cutoff day), the wages you reported today might not be reflected in a future SSI payment. We will mail a notice if there are changes to the payment amount explaining these changes and your right to appeal.”\n\nFor more information on GK processing, see SI 02301.301.\n\nE. \nPolicy for “reported” wage amounts\n\nTo consider wages “reported,” a monthly wage report must meet several criteria discussed in SI 00820.143E.3.\n\nBy default, wages we cannot consider “reported” must be identified as “verified” or “alleged.”\n\nNever consider wages earned by an ineligible child as “reported.” Wages earned by ineligible children cannot be reported through electronic wage reporting methods discussed in SI 00820.143C and must be verified following normal wage verification policies (e.g., SI 00820.135B).\n\n1. \nMonths we may identify wages as “reported”\n\nOnly identify total gross wage amounts for the current month or the month immediately preceding as “reported” wages.\n\nWage reports pertaining to any period more than one month prior to the current month must be identified as “verified” or “alleged.”\n\nConsider wage amounts for the current month “reported” only if the recipient or deemor is not expected to receive any additional wages in the reporting month.\n\n2. \nNo evidence is required for “reported” wages\n\nNo wage evidence must accomany the wage report at the time of submission to identify a monthly wage report as “reported;” however, the reported amount must be derived from pay stub wage information in the wage reporter's possession. The reported wage amount must be equal to the total gross wages indicated on the individual’s pay stubs and meet all other criteria to be considered “reported.”\n\n3. \nMethods for submitting “reported” wages and criteria for considering wages as “reported”\na. \nWages derived from pay stubs\n\nWe consider a monthly wage amount derived from pay stubs “reported” when it is:\n\n•\n\nderived from the gross wages indicated on the individual’s pay stubs for the month; and\n\n•\n\nsubmitted once the individual has received all wages for the reported month.\n\nWe consider a monthly wage report submitted when pay stubs are missing as a “reported” amount if:\n\n•\n\nthe reporter (or technician documenting the report) can determine the total gross wages using year-to-date figures on other pay stubs; or\n\n•\n\nthe reporter submits multiple pay stubs for the month and we obtain the gross wage amount for the missing pay stubs through subsequent contact with the individual (e.g., telephone contact).\n\nb. \nWages reported through myWR, SSAMWR, and SSITWR\n\nWe deem monthly wages to be “reported” when submitted for a prior month using automated wage reporting tools (e.g., myWR, SSAMWR, or SSITWR) on any day during the current reporting month.\n\nc. \nWages “reported” through telephone or field office (FO) contact\n\nSometimes wage reporters may call in or bring their wage report to their local office. For example, if a wage reporter is unsuccessful submitting their wages for the month through the SSITWR system, they may call their local office to submit their report instead of making repeated attempts with the automated system. Monthly wages submitted in person or through telephone contact with the FO that otherwise meet the requirements in SI 00820.143E.3.a for the current or prior month are “reported” wages if the FO processes the report before:\n\n•\n\nthe GK cutoff date in the month the report is received; or\n\n•\n\nthe recurring payment tape cutoff in the month the report is received (i.e., during the GK temporary period).\n\nIf a monthly wage report submitted during the GK temporary period results in an adverse action, issue an online GK notice to the recipient to consider the wage amount “reported.”\n\nEXCEPTION: If the case is an exception to online GK notice issuance, do not consider the wage amount as “reported.” For additional information related to online GK notices, see SI 02301.305.\n\nFor processing instructions when such reports are accompanied by wage evidence, see SI 00820.143F.1\n\nF. \nProcedure for processing monthly wage reports\n\nProcess wage reports according to whether we identify the wages as “verified,” “reported,” or “alleged.”\n\nThe wage reporter may choose any method in this section to report wages, regardless of the level of automation. Do not refuse to accept monthly wage reports submitted using a method other than an automated wage reporting methods (e.g., mailing pay stubs).\n\nSection 202 of the Social Security Protection Act of 2004 requires that we issue a receipt for all wage reports submitted by recipients or their representatives (including representative payees). Issue a receipt regardless of whether we identify the wage report as “verified,” “alleged,” or “reported.”\n\n1. \n“Verified” wages\na. \nUsing SSIMWV to streamline pay stub inputs\n\nSSIMWV streamlines the input of pay stubs by propagating wage information to the Wages page (i.e., IWAG) in the SSI claim system or the SSR. SSIMWV posts wage amounts in the “Verified Amount” column of the appropriate Wages page or on the SSR with a verification code of “9.” Do not use SSIMWV to process monthly wage reports submitted without pay stubs.\n\nTo access the SSIMWV Users Guide and for additional information related to SSIMWV, refer to SI 00820.144D.\n\nb. \nProcessing the wage report\n\nUse the Intranet-based SSIMWV system to input monthly wage amounts submitted with pay stubs.\n\nIf you cannot process the case using SSIMWV, input the wage amount in the “Verified Amount” column on the SSI claim system Wages page.\n\nFor cases outside the SSI claim system (i.e., non-MSSICS or non-CCE cases), transmit the EN field via SSA-1719(B) with a verification code of “9”. For more information on the EN field, see SM 01305.101.\n\nInput an estimate of future wages according to SI 00820.150, beginning with the month after the reported month.\n\nUse one of the following methods to post an estimate:\n\n•\n\nSSIMWV - the system prompts the user for information to derive an estimate and posts the estimate to the “Alleged Amount” column on the Wages page.\n\n•\n\nSSI claim system/SSA-1719(B) - post an estimate of future wages, per instructions in SI 00820.150D.\n\nProcess verified wage amounts submitted by a concurrent beneficiary by entering the eWork application for possible Title II development. eWork subsequently transfers you to SSIMWV to input the SSI monthly wage amount. For more information about using eWork to process wage reports, see DI 13010.020.\n\nc. \nReceipt issuance\n\nIssue a wage report receipt to the recipient or their representative payee when using SSIMWV. For in-person reports, generate a receipt immediately, and provide the receipt to the recipient or their representative payee. SSIMWV automatically prints and dates the receipt.\n\nIf you cannot process the wage report using SSIMWV, issue the receipt using either:\n\n•\n\neWork; or\n\n•\n\nthe Document Processing System (DPS) via the SSA-L724 (Work Report Receipt).\n\nFor additional information related to issuance of receipts for “verified” wage reports that you cannot process using SSIMWV, see DI 13010.020.\n\nd. \nDocumentation of a verified wage amount\n\nArchive the SSIMWV receipt in ORS. The ORS-stored receipt serves as documentation of the pay stub evidence submitted by the reporter.\n\nNo separate action is necessary to document the report.\n\nIf SSIMWV does not issue a receipt, or the receipt is not stored in ORS, document the wage report using the procedures:\n\n•\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n2. \n“Reported” wages\na. \nProcessing a reported wage amount submitted via myWR, SSAMWR, and SSITWR\n\nWages reported using myWR, SSAMWR, or SSITWR automatically:\n\n•\n\npost to the “Reported Amount” column of the Wages page in the SSI claim system;\n\n•\n\ntransmit to the SSR with a verification code of “0;”\n\n•\n\ngenerate an automated wage report receipt; and\n\n•\n\nrequire no additional actions.\n\nb. \nProcessing a monthly wage report received outside of myWR, SSAMWR, and SSITWR\n\nWhen you receive a monthly wage amount directly from a reporter (e.g., via telephone contact), you must:\n\n1. \n\nConfirm whether you can process the monthly wage amount submitted as a “reported” wage by determining if the:\n\n•\n\nwage earner received the reported wages in the current month or the month immediately preceding it;\n\n•\n\ngross wage amount submitted is based on pay stub wage evidence in the individual’s possession (Ask the reporter.); and\n\n•\n\nwage report is submitted and you can process the report either before the GK cutoff, or during the temporary GK period in the month that we receive the report.\n\n2. \n\nIf you can consider the gross wages as “reported”:\n\n•\n\ninput the wages on the Wages page in the SSI claim system in the “Reported Amount” column;\n\n•\n\npost an estimate of future wages in the “Alleged Amount” column starting with the month after the reported month; and\n\n•\n\nsend the transaction to the SSR.\n\nFor instructions on estimating future wages, see SI 00820.150.\n\nIMPORTANT: You cannot transmit monthly wage amounts identified as a “reported” amount via SSA-1719(B) input. Therefore, you cannot transmit “reported” wages to the SSR for cases outside the SSI claim system (i.e., non-MSSICS or non-CCE). Never use SSIMWV to process amounts representing “reported” wages.\n\nc. \nReceipt issuance\n\nWhile myWR, SSAMWR, and SSITWR automatically generate receipts, wage reports made via contact with the FO generally require a manual receipt.\n\nTake the following actions whenever a receipt is required but not automatically generated:\n\n•\n\nIssue a receipt to the SSI beneficiary or their representative payee using the notice titled, “Monthly Wage Reporting – Receipt” in DPS (SSA-L724).\n\n•\n\nPrint the receipt locally and store the receipt in ORS.\n\nFor more information on receipt issuance, see DI 13010.020.\n\nd. \nDocumentation of “reported” wage amounts\n\nSeparate action is not required to document a wage amount that we identify as “reported.”\n\nThe wage amount is indicated on the SSR with a “0” verification code.\n\nThe “0” verification code remains on the SSR unless a subsequent action is taken to verify the “reported” wage amounts.\n\n3. \n“Alleged” wages\na. \nProcessing “Alleged” wage reports\n\nProcess a monthly wage report not identified as “verified” or “reported” as follows:\n\n•\n\nPost the wages in the “Alleged Amount” column on the SSI claim system Wages page or to the SSR using an SSA-1719(B) input with a verification code of “1” in the EN field.\n\n•\n\nInput an estimate of future wages per instructions in SI 00820.150.\n\nb. \nReceipt issuance\n\nIssue the receipt for an alleged monthly wage amount using either:\n\n•\n\neWork; or\n\n•\n\nDPS via the SSA-L724 (Work Report Receipt).\n\nTo issue receipts for alleged monthly wage amounts, see DI 13010.020C.\n\nc. \nDocumentation of alleged wage amounts\n\nDocumentation is not required for a monthly wage report identified as an allegation.\n\nG. \nProcedure for over-reported wage alerts effective 6/28/2008\n\nS7, J3, and J5 alerts detect situations where the SSR reflects more wages for a recipient, deemor, or essential person than are indicated by either the OCSE or the MEF.\n\nThese alerts ensure that individuals whose monthly wage reports are not subject to further verification are not erroneously underpaid SSI benefits due to an error in the reported wage amount.\n\nRefer to development instructions:\n\n•\n\nSI 02310.063 State Wage Record Match (S7 Diary)\n\n•\n\nSI 02310.056 Master Earnings File (MEF) Match (J3 and J5 Diaries)\n\nH. \nExamples of SSI wage reports\n\nExample 1 - Monthly wage amount meeting the criteria to be considered “reported”\n\nJane works at ABC Company and earns $250 bi-weekly. Jane receives their last paycheck for January on day 26 of the month. Jane computes their monthly gross wages for January as $500 and calls the FO on February 7 to report wages.\n\nWhile speaking with Jane, the FO representative confirms that the monthly wage amount Jane submitted is based on information from all the pay stubs Jane received for the month before the report, recognizes the GK cutoff has not yet occurred and the wage input can be made before the cutoff. The FO representative opens a stand-alone post-eligibility event in the SSI claim system. The FO representative enters the $500 Jane earned in January in the “Reported Amount” column on the Wages page for ABC Company, prints a “Monthly Wage Reporting – Receipt” from DPS, and mails the receipt to Jane.\n\nSince the monthly wage amount Jane submitted meets the criteria to be considered a “reported” monthly wage amount, no documentation is necessary at the time of the report.\n\nExample 2 - Monthly wage report determined to be an “alleged” wage amount\n\nJane (from example 1) computes the wages for January to be $500. However, Jane does not call the FO to report the wages until February 20. The FO representative recognizes that Jane’s monthly wage report is based on information from the pay stubs and corresponds to the month prior to the month of report. However, the FO representative cannot consider the wage amount “reported” since the recurring payment tape cutoff has passed.\n\nThe FO representative correctly enters the monthly wage report in the “Alleged Amount” column on the Wages page for ABC Company, issues a wage report receipt to Jane, and requests that Jane send in their pay stubs for the month of January.\n\nExample 3 - Combination of pay stubs and a “reported” wage amount\n\nTom works for the local school system and earns $200 per week. Every month Tom sends pay stubs for the prior month into the local FO for processing via SSIMWV. The FO receives the pay stubs for March on April 5.\n\nThe FO representative examines the pay stubs and determines that Tom neglected to send in pay stubs for the last two weeks of March. The FO representative contacts Tom by phone and asks them to provide pay stub information for the missing pay stubs. Tom finds the missing pay stubs and tells the FO representative that Tom earned $200 each week. The FO representative uses the combination of the pay stubs Tom provided and Tom's “reported” wage amount for the missing pay stubs to determine the gross monthly wages for March. Since the report is completed before the GK cutoff, the FO representative enters the wage amount in the “Reported Amount” column of the SSI claim system Wages page and sends Tom a receipt. Documentation is not required because the FO representative considers the monthly wage amount as “reported.”\n\nExample 4 - Monthly wage report input using SSIMWV\n\nTom (from example 3) submits all pay stubs for March to the FO on April 5. The FO representative enters the pay stubs in SSIMWV and correctly identifies each of them as “verified.” The FO representative prints a receipt through SSIMWV and archives the receipt in ORS before transmitting the wage amount.\n\nThe wage report receipt that is stored in ORS serves as documentation of the wage evidence Tom submitted for March. No further action is necessary by the FO representative.\n\nI. \nSummary of wage reporting methods\n\nThe following chart contains:\n\n•\n\na summary of monthly wage reporting methods;\n\n•\n\nthe date we must receive the reports; and\n\n•\n\nactions we must take to input the wages and issue a receipt.\n\nMonthly Report Type\n\n\t\n\nReporting Timeframe\n\n\t\n\nWhich Month(s) Wages Can Be Reported\n\n\t\n\nNecessary Action to Post Wages\n\n\t\n\nNotices\n\n\t\n\nSSR Coding\n\n\n\n\n \n\n\t\n\n \n\n\t\n\n \n\n\t\n\n \n\n\t​\t​\n\n\nmyWR\n\n\t\n\nPreferably by day 6 of the month, but available on any day during the current reporting month.\n\n\t\n\nFor SSI and concurrent: wages for the month immediately preceding ONLY.\n\n \n\nFor SSDI: Wages up to 24 months in the past.\n\n\t\n\nNone\n\n\t\n\nAutomated receipt and GK notice.\n\n\t\n\n“0”\n\n\n\n\nSSITWR system\n\n \n\n \n\n \n\nand\n\n \n\n \n\n \n\nSSAMWR application\n\n \n\n \n\n\t\n\nPreferably by day 6 of the month, but available on any day during the current reporting month.\n\n\t\n\nWages for the month immediately preceding ONLY.\n\n \n\n \n\n\t\n\nNone\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\t\n\nAutomated receipt and GK notice.\n\n \n\n \n\n\t\n\n“0”\n\n \n\n \n\n \n\n \n\n\n\n\nPay stubs\n\n\t\n\nNo timeframe\n\n\t\n\nAny month\n\n\t\n\nInput wages using SSIMWV or the “Verified Amount” column on the Wages page in the SSI claim system.\n\n\t\n\nSSIMWV generates receipt GK either automated or manual. If not using SSIMWV, manually issue the receipt.\n\n\t\n\n“9”\n\n\n\n\nOral report\n\n \n\nor\n\nWritten wage report faxed or mailed to the FO.\n\n\t\n\nBefore recurring tape cutoff each month.\n\n\t\n\nCurrent month and the month immediately preceding.\n\n\t\n\nInput wages to “Reported Amount” column on Wages page in the SSI claim system.\n\n\t\n\nEmployee must issue a manual receipt. Manual GK notice may be necessary depending on the case characteristics.\n\n\t\n\n“0”\n\nJ. \nReferences\n•\n\nDI 13010.020 Work Reports and Receipts\n\n•\n\nDI 13010.605 The CDR Development Worksheet (CDRW) Screen\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nQUERIES 003.005 Detail Earnings Query (DEQY)\n\n•\n\nQUERIES 003.015 National Directory New Hire, Wage & Unemployment Menu (NDNH)\n\n•\n\nQUERIES 005.004 EIF Access (AEQY)\n\n•\n\nSI 00820.130 Evidence of Wages or Termination of Wages\n\n•\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\n\n•\n\nSI 00820.144 Monthly Wage Reporting for Recruiting Reporters\n\n•\n\nSI 00820.150 Estimating Future Wages\n\n•\n\nSI 02301.005 SSI Posteligibility - Recipient Reporting\n\n•\n\nSI 02301.301 Overview of Goldberg Kelly (GK) Processing\n\n•\n\nSI 02301.305 Online Goldberg Kelly (GK) Notices\n\n•\n\nSI 02310.056 Master Earnings File (MEF) Match (J3 and J5 Diaries)\n\n•\n\nSI 02310.063 State Wage Record Match (S7 Diary)\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500820143\n\t\nSI 00820.143 - Monthly Wage Reporting - 09/26/2013\nBatch run: 03/11/2026\nRev:09/26/2013\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "sha256": "a48270798a430e1e01086277ca3118febf33c4ddde3fd72276a65f5dffbdc37e"
      }
    ],
    "source_reviews": [
      {
        "package_sha256": "b8ee880ac7dc8232c260da47e9c14681c9172b9b25eb246a288b7e9ba90eb5d1",
        "independent_source_review_sha256": "d3cb64d62ee48aa1f6f753b4aef3d8916f28b1fd54a7cd5781e6b1b8dac0b955"
      },
      {
        "package_sha256": "d0865cfdb45bb42ab1900df5352715a0a1e63e981e15d88854d396a97accc211",
        "independent_source_review_sha256": "8602793c787ae94021787f2da3fcf45040cdcfd7b7f6bf32c8050f9522928db1"
      },
      {
        "package_sha256": "3a3f26f4251aa1d4f74da276355b74b289eeb2c5217ae5578271e0d289c97a42",
        "independent_source_review_sha256": "72b95c6333595ca7b01dbb94bd08fbeae99f0ce3d4a3fc7b5c69fcf3edb493a2"
      }
    ],
    "captures": [
      {
        "source_code": "DI12026.025",
        "url": "/service/sources/DI12026.025-main.txt",
        "sha256": "1b3edbbaedef119486db2b4c7d5dd09227983b6da607bc036bac95d3c3a871d7",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "DI12026.025",
        "url": "/service/sources/DI12026.025-DOM-snapshot.txt",
        "sha256": "9be66894694fdf06f784fada93830ad20376782c147412cde1a890cdcb2c56c5",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "DI12026.025",
        "url": "/service/sources/DI12026.025-metadata.json",
        "sha256": "f88e20fd92a5844a6068cb5229456cc14c6e59b47cdc4ffc98e69e200aa0dbc2",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.130",
        "url": "/service/sources/SI00820.130-main.txt",
        "sha256": "52c3484dd22f2635c86b47a094a2a2f3f427c6c4247e05fc393d9ac58bab72d5",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.130",
        "url": "/service/sources/SI00820.130-DOM.json",
        "sha256": "c404965b5c31991d53aa4a7755be43ce800a0460941e459c0ab517b42b37e92c",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.130",
        "url": "/service/sources/SI00820.130-AX.txt",
        "sha256": "7eb0b1eb6748b31c2e4434a727fd62d7f6aa1982c6324fdcb0c8e9d9808a0867",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.130",
        "url": "/service/sources/SI00820.130-meta.json",
        "sha256": "09af7048478a30ad299eb29f29710c5b7a936dfcd48935420dc0faabf77e43cd",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.143",
        "url": "/service/sources/SI00820.143-main.txt",
        "sha256": "a48270798a430e1e01086277ca3118febf33c4ddde3fd72276a65f5dffbdc37e",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.143",
        "url": "/service/sources/SI00820.143-DOM.json",
        "sha256": "bdcc7f0a4cd00d416e14ce1c5c780289137452c5481bba8611f3282921dec970",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.143",
        "url": "/service/sources/SI00820.143-AX.txt",
        "sha256": "cac88b9bb155aafde70d4d9edbbfaf804d9166d9405153296fc6ec63de287c7e",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      },
      {
        "source_code": "SI00820.143",
        "url": "/service/sources/SI00820.143-meta.json",
        "sha256": "415a6dee80e5c5c4d9919263ed0a990f70bc4b76f1d684799aade56ee986c54e",
        "capture_semantics": "Actual saved browser rendered main, parsed DOM/AX or metadata. Not raw HTTP bytes."
      }
    ],
    "holds": [
      "Medical CDR reconsideration/DHO hearing scope is distinct from ALJ .001/.257 hearing pathways; no rule transfer solely from similar names.",
      "B system five-day expectation/tickle is not measured processing time or a customer deadline; separate .257 posting-language comparison remains unresolved.",
      "C2 TitleII reconsideration no-POS and later hearing reversal POS branches have distinct stage predicates; no date-only contradiction resolution.",
      "Current publication names MSSICS/EDCS/DCF/MBR/SSR/PCACS/THIS/T2R/MI Central; no runtime identity, service execution or new native edges/aliases are inferred.",
      "Merely linked forms, reconstruction, withdrawal, good-cause, SGA, insufficient-evidence, relationship/deceased-underpayment and eCDR processing targets retain separately recorded review limits.",
      "The source retains overall FO appeal timeliness or good-cause review and applicable electronic or paper folder storage. This selected sequence does not perform or replace those checks.",
      "The C.4.a documentation note points to C.3.b, which is not a corresponding subsection in the captured page. Actual C.4.b is supplied; preserve the pointer limitation without silently correcting the publisher.",
      "C.2.g points to A.2 for required information, while explicit minimum pay-stub fields are in A.1.b. Both source statements remain preserved.",
      "C.8 sole-statement verification fallback after failed acceptable-evidence development is distinct from routine alleged monthly reports in SI 00820.143 F.3. Do not collapse code9 and code1 scopes or infer classification from the dropdown.",
      "Detailed SI 00820.135/142/144/145/147/148, payroll authorization, diary development, unemployment, earnings corrections and external-retention procedures are merely linked unless separately supplied and reviewed.",
      "C.9 suspected-fraud employer statement instructions are not triggered by selecting questionable pay-stub evidence. Their interaction with approved-company employer-contact limits is not reconciled by this proposal.",
      "SI 00820.130 C.8 documented sole-statement verification fallback uses code9 under its own conditions; ordinary SI 00820.143 alleged reporting uses code1. The categories are not collapsed or chosen automatically.",
      "Automated SSI tools accept the prior month only, while qualifying FO reported-wage input may concern the current or prior month. SSDI-only myWR up-to24-month scope is separate and not extended to SSI.",
      "First-six-day encouragement, generally stated ten-day reporting responsibility, actual GK cutoff and recurring-payment cutoff are distinct; no date calculator or universal deadline is supplied.",
      "Detailed SI 00820.135/144/150, GK notice exceptions, payroll authorization, TitleII work development, evidence-retention and system-input screens retain their separate review limits.",
      "Source-listed MSSICS/CCE, eWork, SSIMWV, myWR, SSAMWR, SSITWR, ORS, DPS, EP and DCF roles are not native aliases, telemetry or current deployment certification."
    ],
    "related_record_context_registry": {
      "url": "/service/r27-source-step-context-registry.json",
      "sha256": "352243aeb6d7606c3793f9487107b32fb6db21ba019a95b0a891616f83ba526a",
      "scope": "Thirteen passive, qualified existing-record research references, with current status checks required before UI anchors. Not source or native adoption."
    },
    "scope": "Ten medical CDR reconsideration sequences, twelve SSI wage-evidence sequences and ten monthly-wage-report sequences only. Earlier source dates, records, statuses and unmodeled conditions remain history; this is not complete policy, a case determination, measured processing time or an automatic transition."
  },
  "r28_existing_DDS8": {
    "schema": "securitystat.future-source-flow-proposal/1",
    "status": "SELECTED_EIGHT_DDS_SOURCE_SEQUENCES_REVIEWED_NOT_COMPLETE_POLICY_OR_CASE_FINDING",
    "baseline_manifest_sha256": "e3fb3a4cf10e8be25a8a5f8eaed06ca75abccf2991bc2361650f280d66e4ce0e",
    "baseline_freeze_sha256": "226e4f6424f3287161cecacb681412e699783dc86d25b3dfc2b95c3f64044b6d",
    "whole_sources_and_capture_pins": [
      {
        "capture_artifact_name": "DI31001.010-main.txt",
        "sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b"
      },
      {
        "capture_artifact_name": "DI31001.010-dom.txt",
        "sha256": "668e9bd6186ce262d427fe199fdd62f272a99bfa249e743a470fd338e8d60030"
      },
      {
        "capture_artifact_name": "DI31001.010-capture.json",
        "sha256": "c4d8f3475542ab02b6f9b3057f31a79808767b8faece6d48f3753c265111f75d"
      },
      {
        "capture_artifact_name": "DI31005.005-main.txt",
        "sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b"
      },
      {
        "capture_artifact_name": "DI31005.005-dom.txt",
        "sha256": "b8bff24f878a250b5c620c6b72ac2c8350bade8d967415ac31c328c7917523ba"
      },
      {
        "capture_artifact_name": "DI31005.005-capture.json",
        "sha256": "139825e74deed61e7f75fadcd3e6b01ca3527397aad1ce4e406a011788da1e45"
      },
      {
        "capture_artifact_name": "DI31001.001-main.txt",
        "sha256": "92f551ee572645841752075793f96eb6dee10d51b423c3a5394ccd028af13281"
      },
      {
        "capture_artifact_name": "DI81020.130-main.txt",
        "sha256": "d3bad9636e52cde0178286d8d22ac00a225913b485977d3c0a94ea259cf871e8"
      }
    ],
    "capture_type": "Rendered main text plus browser DOM/accessibility snapshot; not raw HTTP response bytes. Existing captured instruction header: effective07/26/2022-Present TN26(07-26), batch10/13/2026; no new publisher currency finding.",
    "original_records": {
      "DDS-represented-case-contact/DDS-claimant-initiates-specific-issue": {
        "id": "DDS-claimant-initiates-specific-issue",
        "title": "You contact SSA or DDS about a specific issue",
        "when": "A represented claimant starts the contact about a specific issue.",
        "you": "You do not need your representative’s permission merely to contact SSA or DDS directly.",
        "ssa": "Staff may discuss the specific issue you raised.",
        "next": "Starting this contact is different from asking to change ongoing communication or end representation.",
        "condition_logic": "all",
        "conditions": [
          "The claimant has an appointed representative.",
          "The claimant initiates contact with SSA or DDS about a specific issue."
        ],
        "source_case_conditions": [
          "The claimant has an appointed representative.",
          "The claimant initiates contact with SSA or DDS about a specific issue."
        ],
        "source_instruction_summary": "B1 incoming represented claimant contact may discuss specific issue; permission from representative not needed merely to initiate contact.",
        "source_context_refs": [
          "A-B"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 185,
            "end": 1882,
            "span_sha256": "3e7df23c553e56b5743ac20c46873204218f18e579becd65c769e5a03f06f4d4",
            "exact_text": "A. \nEvents that end a representative's appointment\n\nFor actions and events that end the appointment of a representative and his or her authority, see GN 03910.060A.\n\nNOTE: If a claimant files a new disability claim, they and their representative must complete a new written notice of appointment (i.e., Form SSA-1696 (Claimant's Appointment of a Representative)) and submit it to the Field Office (FO).\n\nB. \nContacting represented claimants\n\nA represented claimant may continue to participate in the development of his or her claim, through the appointed representative or directly with SSA or the DDS.\n\n1. \nClaimant initiates contact\n\nIf a represented claimant contacts SSA or the DDS, SSA or the DDS may discuss his or her specific issue. A represented claimant does not need permission from the appointed representative to contact SSA or the DDS directly.\n\n2. \nSSA or DDS initiates contact\n\nIf the claimant appoints a representative, generally the DDS initiates all contacts connected to that claim through, or with the permission of, the appointed representative. For information about when to contact represented claimants directly, see GN 03910.050.\n\nWhen the claimant has appointed multiple representatives and it is not clear who is currently appointed or who is the principal representative, DDS may contact the represented claimant directly to clarify the situation. For more information about multiple representative situations, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times and the representatives do not appear to be working together. In this instance, SSA will contact the claimant directly to clarify the situation.\n\nC. \nPotential issues",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "A-B",
        "additional_sources": [],
        "ui_display_conditions": [
          "The claimant has an appointed representative.",
          "The claimant initiates contact with SSA or DDS about a specific issue."
        ],
        "systems": [],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact": {
        "id": "DDS-initiates-contact",
        "title": "DDS starts the contact",
        "when": "DDS intends to contact a represented claimant about the claim.",
        "you": "Ask SSA or your representative to explain the contact arrangement.",
        "ssa": "DDS generally makes claim-related contacts through your representative or with the representative’s permission.",
        "next": "Other source-defined direct-contact circumstances need their own established conditions.",
        "condition_logic": "all",
        "conditions": [
          "The claimant has appointed a representative.",
          "DDS is initiating contact connected to that claim."
        ],
        "source_case_conditions": [
          "The claimant has appointed a representative.",
          "DDS is initiating contact connected to that claim."
        ],
        "source_instruction_summary": "B2 general rule through/with permission. GN03910.050 is linked for circumstances; not a blanket permission finding or rule for every SSA staff workflow.",
        "source_context_refs": [
          "A-B"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 185,
            "end": 1882,
            "span_sha256": "3e7df23c553e56b5743ac20c46873204218f18e579becd65c769e5a03f06f4d4",
            "exact_text": "A. \nEvents that end a representative's appointment\n\nFor actions and events that end the appointment of a representative and his or her authority, see GN 03910.060A.\n\nNOTE: If a claimant files a new disability claim, they and their representative must complete a new written notice of appointment (i.e., Form SSA-1696 (Claimant's Appointment of a Representative)) and submit it to the Field Office (FO).\n\nB. \nContacting represented claimants\n\nA represented claimant may continue to participate in the development of his or her claim, through the appointed representative or directly with SSA or the DDS.\n\n1. \nClaimant initiates contact\n\nIf a represented claimant contacts SSA or the DDS, SSA or the DDS may discuss his or her specific issue. A represented claimant does not need permission from the appointed representative to contact SSA or the DDS directly.\n\n2. \nSSA or DDS initiates contact\n\nIf the claimant appoints a representative, generally the DDS initiates all contacts connected to that claim through, or with the permission of, the appointed representative. For information about when to contact represented claimants directly, see GN 03910.050.\n\nWhen the claimant has appointed multiple representatives and it is not clear who is currently appointed or who is the principal representative, DDS may contact the represented claimant directly to clarify the situation. For more information about multiple representative situations, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times and the representatives do not appear to be working together. In this instance, SSA will contact the claimant directly to clarify the situation.\n\nC. \nPotential issues",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "A-B",
        "additional_sources": [],
        "ui_display_conditions": [
          "The claimant has appointed a representative.",
          "DDS is initiating contact connected to that claim."
        ],
        "systems": [],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        }
      },
      "DDS-represented-case-contact/DDS-representative-requests-specific-issue": {
        "id": "DDS-representative-requests-specific-issue",
        "title": "Your representative asks DDS to contact you on one issue",
        "when": "The representative asks for direct communication about a specific issue.",
        "you": "Check which issue the request covers and keep any communication records.",
        "ssa": "Staff document the request using one of the source’s three record alternatives, keep it in the file and notify the field office. A paper case also needs the specified copy.",
        "next": "A record or message instruction is not proof the contact happened.",
        "condition_logic": "all",
        "conditions": [
          "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
        ],
        "source_case_conditions": [
          "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
        ],
        "source_instruction_summary": "Prepare SSA5002 OR eCAT Claims Communication OR DCPS Case Note; include in file; paper copy to FO; eView message to notify FO.",
        "source_context_refs": [
          "C1"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 2124,
            "end": 2799,
            "span_sha256": "ed1cf91a1ea860f6a32f7b46d269d7f426f8bcc5e1b8cfdb5178129f27c5c972",
            "exact_text": "1. \nAppointed representative requests SSA or the DDS to communicate directly with the claimant regarding a specific issue\n\nIf the representative requests that we communicate directly with the claimant regarding a specific issue:\n\n•\n\nPrepare an SSA-5002 (Report of Contact), Electronic Claims Analysis Tool (eCAT) Claims Communication, or Disability Case Processing System (DCPS) Case Note to document that the DDS will deal directly with the claimant on the specific issue;\n\n•\n\nInclude the SSA-5002, eCAT Claims Communication, or DCPS Case Note in the file. For paper cases, send a copy to the FO;\n\n•\n\nPost a message in eView to notify the FO of the representative's request.",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [
          "FORM_SSA5002",
          "APP_ECAT",
          "APP_DCPS",
          "APP_EVIEW"
        ],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "C1",
        "additional_sources": [],
        "ui_display_conditions": [
          "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
        ],
        "systems": [
          "SSA-5002 Report of Contact",
          "Electronic Claims Analysis Tool",
          "Disability Case Processing System",
          "eView"
        ],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        },
        "record_context_registry_ref": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false,
          "record_id": "DDS-representative-requests-specific-issue"
        }
      },
      "DDS-represented-case-contact/DDS-claimant-requests-specific-issue": {
        "id": "DDS-claimant-requests-specific-issue",
        "title": "You ask DDS to speak with you about one issue",
        "when": "A represented claimant asks for direct communication about a particular issue.",
        "you": "Your request does not revoke your representative’s appointment. The representative continues to have file access, which may include this issue.",
        "ssa": "Staff record your request on the specified form, keep it with the case and notify the field office. Paper-case copies follow the source instruction.",
        "next": "The contact request does not establish privacy from your representative or completed communication.",
        "condition_logic": "all",
        "conditions": [
          "The represented claimant requests direct communication about a particular issue."
        ],
        "source_case_conditions": [
          "The represented claimant requests direct communication about a particular issue."
        ],
        "source_instruction_summary": "Prepare SSA5002 with claimant desire/specific issue; include in electronic folder; paper copy FO; eView message FO. Remind not revocation and continued representative access. C1 alternative eCAT/DCPS record choices are not automatically imported.",
        "source_context_refs": [
          "C2"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 2801,
            "end": 3636,
            "span_sha256": "ea233ac73f8b7cacbb56ac3ee7803ad9d23e687bda149641c1a4594d7ecadcaf",
            "exact_text": "2. \nRepresented claimant requests SSA or the DDS to communicate directly with him or her regarding a specific issue\n\nIf a represented claimant requests that we communicate directly with him or her regarding a particular issue:\n\n•\n\nPrepare an SSA-5002 describing the claimants desire to communicate directly with the DDS on that specific issue;\n\n•\n\nInclude the SSA-5002 in the electronic folder. For paper cases, send a copy to the FO;\n\n•\n\nPost a message in eView to notify the FO of the claimant's request.\n\nIMPORTANT: A represented claimant's request that the agency communicate directly with him or her on a specific issue is not a revocation of the representative's appointment. Remind the claimant that the representative continues to have access to the file, which may include information regarding the issue he or she identified.",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [
          "FORM_SSA5002",
          "APP_EVIEW"
        ],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "C2",
        "additional_sources": [],
        "ui_display_conditions": [
          "The represented claimant requests direct communication about a particular issue."
        ],
        "systems": [
          "SSA-5002 Report of Contact",
          "eView"
        ],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        },
        "record_context_registry_ref": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false,
          "record_id": "DDS-claimant-requests-specific-issue"
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-before-PDE-at-DDS": {
        "id": "DDS-representative-inquiry-before-PDE-at-DDS",
        "title": "The representative asks while the case is still at DDS",
        "when": "The representative asks about a case that is pending at DDS before its disability explanation is issued.",
        "you": "Your representative can ask about relevant evidence and development.",
        "ssa": "Staff can explain relevant evidence sources, development and requests, and the right to review or receive file material. They do not disclose the disability determination until processing is complete.",
        "next": "The inquiry and staff record do not show an approved claim, a denial or completed processing.",
        "condition_logic": "all",
        "conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has not been issued.",
          "The case is pending at DDS."
        ],
        "source_case_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has not been issued.",
          "The case is pending at DDS."
        ],
        "source_instruction_summary": "C3a relevant medical sources/development/request clarification/review-copy rights; do not disclose determination until processing complete; SSA5002 OR eCAT Claims Communication OR DCPS Case Note documents request/actions.",
        "source_context_refs": [
          "C3"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 3638,
            "end": 5577,
            "span_sha256": "0808931c3622b9e00b063652e9e1175b2c452c98ec6c237e29faec2434c1ece0",
            "exact_text": "3. \nAppointed representative contacts the DDS\n\nIf the representative contacts the DDS, subsequent actions taken depend on whether the DDS has issued the Personalized Disability Explanation (PDE). To determine the PDE's date of issue, see DI 81020.130D.\n\na. \nBefore PDE issuance and case is pending at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case before PDE issuance and the case is at the DDS, provide the following information that is relevant to the contact:\n\n•\n\nIdentify sources of medical information.\n\n•\n\nIndicate development undertaken or outstanding.\n\n•\n\nClarify the need for a development request, if necessary.\n\n•\n\nAdvise the representative of his or her right to both review or receive copies of material in the claimant's file.\n\n•\n\nDo not disclose information about the disability claim determination to an appointed representative until claim processing is complete.\n\n•\n\nPrepare an SSA-5002 or document the nature of the appointed representative's request in an eCAT Claims Communication or a DCPS Case Note, and the actions taken to comply with the request.\n\nb. \nWhen the case is no longer at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case after PDE issuance and the case is no longer at the DDS, inform the inquirer that the DDS forwarded the claim to another office, and take the following action(s):\n\n•\n\nForward the inquiry to the office with jurisdiction of the claim for a response;\n\n•\n\nAdvise the inquirer to contact the servicing FO if he or she has further questions about the claim; and either\n\n•\n\nAdd an alert to the electronic folder for electronic claims according to the instructions in DI 81020.080; or\n\n•\n\nComplete an SSA-408 (Route Slip) for paper claims and annotate with the comment: Inquiry Action Needed.\n\nFor more information about handling inquiries when the case is no longer at the DDS, see DI 31005.005.",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [
          "FORM_SSA5002",
          "APP_ECAT",
          "APP_DCPS"
        ],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "C3",
        "additional_sources": [],
        "ui_display_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The case’s disability explanation has not been issued.",
          "The case is pending at DDS."
        ],
        "systems": [
          "SSA-5002 Report of Contact",
          "Electronic Claims Analysis Tool",
          "Disability Case Processing System"
        ],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        },
        "record_context_registry_ref": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false,
          "record_id": "DDS-representative-inquiry-before-PDE-at-DDS"
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-after-PDE-not-at-DDS": {
        "id": "DDS-representative-inquiry-after-PDE-not-at-DDS",
        "title": "The representative asks after the case has left DDS",
        "when": "The explanation has been issued and DDS no longer has the case.",
        "you": "The representative may need to speak with the office now handling the case.",
        "ssa": "DDS forwards the inquiry to the office with jurisdiction and advises the inquirer to contact the servicing field office for further questions. Staff use the electronic or paper notification route appropriate to the case. Under the separate another-office inquiry instruction, they also forward a copy of the reply and the inquiry to the office that has the claim.",
        "next": "Forwarding the inquiry does not show that another office received or answered it.",
        "condition_logic": "all",
        "conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has been issued.",
          "The case is no longer at DDS."
        ],
        "source_case_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has been issued.",
          "The case is no longer at DDS."
        ],
        "source_instruction_summary": "C3b explain claim forwarded; forward inquiry to office with jurisdiction; advise servicingFO; electronic-folder alert under DI81020.080 OR paper SSA408 annotated Inquiry Action Needed. DI31005.005B is now separately reviewed for the another-office inquiry scope; other target procedures are not modeled. Separately applicable DI31005.005B requires forwarding a copy of the reply and the inquiry to the office in possession of the claim; preserve that destination role separately from office with jurisdiction.",
        "source_context_refs": [
          "C3",
          "005-B"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 3638,
            "end": 5577,
            "span_sha256": "0808931c3622b9e00b063652e9e1175b2c452c98ec6c237e29faec2434c1ece0",
            "exact_text": "3. \nAppointed representative contacts the DDS\n\nIf the representative contacts the DDS, subsequent actions taken depend on whether the DDS has issued the Personalized Disability Explanation (PDE). To determine the PDE's date of issue, see DI 81020.130D.\n\na. \nBefore PDE issuance and case is pending at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case before PDE issuance and the case is at the DDS, provide the following information that is relevant to the contact:\n\n•\n\nIdentify sources of medical information.\n\n•\n\nIndicate development undertaken or outstanding.\n\n•\n\nClarify the need for a development request, if necessary.\n\n•\n\nAdvise the representative of his or her right to both review or receive copies of material in the claimant's file.\n\n•\n\nDo not disclose information about the disability claim determination to an appointed representative until claim processing is complete.\n\n•\n\nPrepare an SSA-5002 or document the nature of the appointed representative's request in an eCAT Claims Communication or a DCPS Case Note, and the actions taken to comply with the request.\n\nb. \nWhen the case is no longer at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case after PDE issuance and the case is no longer at the DDS, inform the inquirer that the DDS forwarded the claim to another office, and take the following action(s):\n\n•\n\nForward the inquiry to the office with jurisdiction of the claim for a response;\n\n•\n\nAdvise the inquirer to contact the servicing FO if he or she has further questions about the claim; and either\n\n•\n\nAdd an alert to the electronic folder for electronic claims according to the instructions in DI 81020.080; or\n\n•\n\nComplete an SSA-408 (Route Slip) for paper claims and annotate with the comment: Inquiry Action Needed.\n\nFor more information about handling inquiries when the case is no longer at the DDS, see DI 31005.005.",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          },
          {
            "id": "005-B",
            "source_code": "DI31005.005",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
            "start": 1782,
            "end": 2488,
            "exact_text": "B. \nResponding to an inquiry if the claim is in another office\n\nInform the inquirer the DDS forwarded the claim to another office and take the following action(s):\n\n•\n\nforward the inquiry to the office with jurisdiction of the claim for a response;\n\n•\n\nadvise the inquirer to contact the servicing FO if he or she has further questions about the claim; and\n\n•\n\nfor electronic claims add an alert to the electronic folder according to the instructions in DI 81020.080; or\n\n•\n\nfor paper claims complete an SSA-408 (Route Slip) and annotate with the comment: “Inquiry – Action Needed;” and\n\n•\n\nforward a copy of the reply and the inquiry to the office in possession of the claim.\n\nC. \nResponding to an inquiry",
            "span_sha256": "feeb64ab58c09c9278153dbd2a31781cb72243bc5bd663f032598d135fc1879f",
            "whole_maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "The PDE issue predicate remains the source010 C3b condition. PDN dates/EF Received are not automatically used to establish it.",
          "The additional 005B instruction is separately scoped to a claim in another office, not proof that PDE was issued."
        ],
        "system_context_candidate_ids": [
          "FORM_SSA408"
        ],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "C3; 005-B",
        "additional_sources": [
          {
            "source": "r19_DDS_inquiry005",
            "section": "005-B"
          }
        ],
        "ui_display_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The case’s disability explanation has been issued.",
          "The case is no longer at DDS."
        ],
        "systems": [
          "SSA-408 Route Slip"
        ],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        },
        "record_context_registry_ref": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false,
          "record_id": "DDS-representative-inquiry-after-PDE-not-at-DDS"
        }
      },
      "DDS-represented-case-contact/DDS-development-request-and-notice-copies": {
        "id": "DDS-development-request-and-notice-copies",
        "title": "DDS sends a selected request or notice",
        "when": "DDS sends a development request, attendance request or determination notice for a represented claimant.",
        "you": "Keep your copy and check the request with your representative.",
        "ssa": "The selected DDS correspondence goes to the claimant with a copy to the appointed representative.",
        "next": "A copied request does not show that evidence was supplied, an examination was attended or a case was decided.",
        "condition_logic": "all",
        "conditions": [
          "The claimant has an appointed representative.",
          "DDS is sending a development-evidence/action request, CE/disability-hearing attendance request or determination notice listed in C7."
        ],
        "source_case_conditions": [
          "The claimant has an appointed representative.",
          "DDS is sending a development-evidence/action request, CE/disability-hearing attendance request or determination notice listed in C7."
        ],
        "source_instruction_summary": "C7 development work-history/disability reports/questionnaires/deferment/call-in requests, CE/hearing attendance and determination notices claimant+copyrep. FO/OHO cross-references are separate. No universal all-agency routing rule.",
        "source_context_refs": [
          "C7"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 7337,
            "end": 8245,
            "span_sha256": "c391f703439ffbb9178cb3d8069a4535c0a4fd03e36c3bd954e504167c804110",
            "exact_text": "7. \nNotices and correspondence\n\nSend all notices and correspondence to both the claimant and the appointed representative, as follows:\n\n•\n\nSend requests for developmental evidence or action (e.g., work history or disability reports, questionnaires, medical deferment, call-in letters) to the claimant and a copy to the representative.\n\n•\n\nSend requests to attend a consultative examination (CE) or a disability hearing to the claimant and a copy to the representative.\n\n•\n\nSend determination notices to the claimant and a copy to the representative.\n\nNOTE: Sending requests to attend a CE or other requests for evidence or action to both the claimant and the representative ensures that both parties are made aware of the requests.\n\nFor notices and correspondence specific to the FO, see GN 03910.050B. For notices and correspondence specific to the Office of Hearing Operations (OHO), see HALLEX I-1-1-20.E.",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "C7",
        "additional_sources": [],
        "ui_display_conditions": [
          "The claimant has an appointed representative.",
          "DDS is sending a development-evidence/action request, CE/disability-hearing attendance request or determination notice listed in C7."
        ],
        "systems": [],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact/DDS-multiple-representatives-principal-unclear": {
        "id": "DDS-multiple-representatives-principal-unclear",
        "title": "The representative records are unclear",
        "when": "The claimant has multiple representatives and the current or principal representative is unclear.",
        "you": "DDS may contact you to clarify who currently represents you or who is the principal representative.",
        "ssa": "The source allows that clarification contact in this multiple-representative situation.",
        "next": "This does not decide an appointment has ended or permit unrelated evidence questions.",
        "condition_logic": "all",
        "conditions": [
          "DDS is initiating contact under the parent scenario.",
          "The claimant appointed multiple representatives.",
          "DDS records do not clearly show who is currently appointed or who is the principal representative."
        ],
        "source_case_conditions": [
          "DDS is initiating contact under the parent scenario.",
          "The claimant appointed multiple representatives.",
          "DDS records do not clearly show who is currently appointed or who is the principal representative."
        ],
        "source_instruction_summary": "B2 permits direct contact to clarify multiple-representative/current/principal ambiguity. This is not appointment termination or unrestricted evidence collection.",
        "source_context_refs": [
          "A-B"
        ],
        "source_provenance": [
          {
            "source_code": "DI31001.010",
            "start": 185,
            "end": 1882,
            "span_sha256": "3e7df23c553e56b5743ac20c46873204218f18e579becd65c769e5a03f06f4d4",
            "exact_text": "A. \nEvents that end a representative's appointment\n\nFor actions and events that end the appointment of a representative and his or her authority, see GN 03910.060A.\n\nNOTE: If a claimant files a new disability claim, they and their representative must complete a new written notice of appointment (i.e., Form SSA-1696 (Claimant's Appointment of a Representative)) and submit it to the Field Office (FO).\n\nB. \nContacting represented claimants\n\nA represented claimant may continue to participate in the development of his or her claim, through the appointed representative or directly with SSA or the DDS.\n\n1. \nClaimant initiates contact\n\nIf a represented claimant contacts SSA or the DDS, SSA or the DDS may discuss his or her specific issue. A represented claimant does not need permission from the appointed representative to contact SSA or the DDS directly.\n\n2. \nSSA or DDS initiates contact\n\nIf the claimant appoints a representative, generally the DDS initiates all contacts connected to that claim through, or with the permission of, the appointed representative. For information about when to contact represented claimants directly, see GN 03910.050.\n\nWhen the claimant has appointed multiple representatives and it is not clear who is currently appointed or who is the principal representative, DDS may contact the represented claimant directly to clarify the situation. For more information about multiple representative situations, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times and the representatives do not appear to be working together. In this instance, SSA will contact the claimant directly to clarify the situation.\n\nC. \nPotential issues",
            "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
            "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
          }
        ],
        "qualifications": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "system_context_candidate_ids": [],
        "timing": "No measured duration, universal response clock or case-completion estimate is established.",
        "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual case facts, completed communication and successful return to another workflow remain unverified."
          ]
        },
        "source_native_acceptance": false,
        "source_holds": [
          "DDS-incoming-representation-document-disposition",
          "DDS-PDE-PDN-notice-identity-date"
        ],
        "source": "r19_DDS_contact010",
        "section": "A-B",
        "additional_sources": [],
        "ui_display_conditions": [
          "DDS is initiating contact under the parent scenario.",
          "The claimant appointed multiple representatives.",
          "DDS records do not clearly show who is currently appointed or who is the principal representative."
        ],
        "systems": [],
        "entity_ids": [],
        "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
        "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
        "source_qualified_branch": {
          "kind": "selected_source_qualified_staff_scenario",
          "case_facts_not_determined": true,
          "new_native_edges_or_aliases": false
        },
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
          "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
          "report": "/service/r19-DDS-selected-claim-ledger.json"
        }
      }
    },
    "flows": {
      "DDS-represented-case-contact/DDS-claimant-initiates-specific-issue": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-claimant-initiates-specific-issue",
        "full_route": "DDS-represented-case-contact/DDS-claimant-initiates-specific-issue",
        "entry_conditions": [
          "The claimant has an appointed representative.",
          "The claimant initiates contact with SSA or DDS about a specific issue."
        ],
        "steps": [
          {
            "id": "DDS-claimant-initiates-specific-issue-source-step-1",
            "title": "You can raise the specific issue",
            "kind": "you",
            "actor": "Claimant",
            "action": "A represented claimant may contact SSA or DDS directly about a specific issue without obtaining the representative’s permission. SSA or DDS may discuss that issue. This is not a request to revoke the appointment.",
            "conditions": [
              "The claimant has an appointed representative.",
              "The claimant initiates contact with SSA or DDS about a specific issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 B.1",
            "source_context_refs": [
              "A-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-initiates-contact",
        "full_route": "DDS-represented-case-contact/DDS-initiates-contact",
        "entry_conditions": [
          "The claimant has appointed a representative.",
          "DDS is initiating contact connected to that claim."
        ],
        "steps": [
          {
            "id": "DDS-initiates-contact-source-step-1",
            "title": "Contact through the representative or with permission",
            "kind": "ssa",
            "actor": "DDS",
            "action": "DDS generally starts contacts connected to the represented claim through the appointed representative or with that representative’s permission. Other direct-contact circumstances need their own established conditions; this card does not grant permission.",
            "conditions": [
              "The claimant has appointed a representative.",
              "DDS is initiating contact connected to that claim."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 B.2",
            "source_context_refs": [
              "A-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact/DDS-multiple-representatives-principal-unclear": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-multiple-representatives-principal-unclear",
        "full_route": "DDS-represented-case-contact/DDS-initiates-contact/DDS-multiple-representatives-principal-unclear",
        "entry_conditions": [
          "The claimant has appointed a representative.",
          "DDS is initiating contact connected to that claim.",
          "DDS is initiating contact under the parent scenario.",
          "The claimant appointed multiple representatives.",
          "DDS records do not clearly show who is currently appointed or who is the principal representative."
        ],
        "steps": [
          {
            "id": "DDS-multiple-representatives-principal-unclear-source-step-1",
            "title": "Clarify the representative arrangement",
            "kind": "ssa",
            "actor": "DDS",
            "action": "DDS may contact the claimant directly to clarify who is currently appointed or who is the principal representative when multiple representatives have been appointed and that information is unclear. The permission is for clarification, not unrelated evidence questions or an appointment-termination finding.",
            "conditions": [
              "The claimant has appointed a representative.",
              "DDS is initiating contact connected to that claim.",
              "DDS is initiating contact under the parent scenario.",
              "The claimant appointed multiple representatives.",
              "DDS records do not clearly show who is currently appointed or who is the principal representative."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 B.2",
            "source_context_refs": [
              "A-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-representative-requests-specific-issue": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-representative-requests-specific-issue",
        "full_route": "DDS-represented-case-contact/DDS-representative-requests-specific-issue",
        "entry_conditions": [
          "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
        ],
        "steps": [
          {
            "id": "DDS-representative-requests-specific-issue-source-step-1",
            "title": "Record the representative’s specific request",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Document that DDS will deal directly with the claimant on the specific issue using an SSA-5002, an eCAT Claims Communication, or a DCPS Case Note. These are source alternatives, not three required records.",
            "conditions": [
              "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.1",
            "source_context_refs": [
              "C1"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-representative-requests-specific-issue-source-step-2",
            "title": "Keep the record and the required paper-case copy",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Include the selected record in the file. For a paper case, also send a copy to the field office. The paper-copy condition does not apply merely because a request was made.",
            "conditions": [
              "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.1",
            "source_context_refs": [
              "C1"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-representative-requests-specific-issue-source-step-3",
            "title": "Notify the field office",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Post a message in eView to notify the field office of the representative’s request. A message instruction does not prove delivery or completed direct contact.",
            "conditions": [
              "The appointed representative requests that SSA or DDS communicate directly with the claimant regarding a specific issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.1",
            "source_context_refs": [
              "C1"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-claimant-requests-specific-issue": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-claimant-requests-specific-issue",
        "full_route": "DDS-represented-case-contact/DDS-claimant-requests-specific-issue",
        "entry_conditions": [
          "The represented claimant requests direct communication about a particular issue."
        ],
        "steps": [
          {
            "id": "DDS-claimant-requests-specific-issue-source-step-1",
            "title": "Record the claimant’s specific request",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare an SSA-5002 describing the claimant’s wish to communicate directly with DDS about the particular issue. The eCAT/DCPS alternatives in the representative-request instruction do not replace this form instruction.",
            "conditions": [
              "The represented claimant requests direct communication about a particular issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.2",
            "source_context_refs": [
              "C2"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-claimant-requests-specific-issue-source-step-2",
            "title": "Keep the form and the required paper-case copy",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Include the SSA-5002 in the electronic folder. For a paper case, send a copy to the field office. These instructions do not establish that a record was filed or received.",
            "conditions": [
              "The represented claimant requests direct communication about a particular issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.2",
            "source_context_refs": [
              "C2"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-claimant-requests-specific-issue-source-step-3",
            "title": "Notify the field office",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Post a message in eView to notify the field office of the claimant’s request.",
            "conditions": [
              "The represented claimant requests direct communication about a particular issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.2",
            "source_context_refs": [
              "C2"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-claimant-requests-specific-issue-source-step-4",
            "title": "Explain that representation continues",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Remind the claimant that this specific-issue request does not revoke the representative’s appointment. The representative continues to have access to the file, which may include information about the issue. No confidentiality from the representative is promised.",
            "conditions": [
              "The represented claimant requests direct communication about a particular issue."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.2 IMPORTANT",
            "source_context_refs": [
              "C2"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-before-PDE-at-DDS": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-representative-inquiry-before-PDE-at-DDS",
        "full_route": "DDS-represented-case-contact/DDS-representative-inquiry-before-PDE-at-DDS",
        "entry_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has not been issued.",
          "The case is pending at DDS."
        ],
        "steps": [
          {
            "id": "DDS-representative-inquiry-before-PDE-at-DDS-source-step-1",
            "title": "Explain relevant development",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Identify medical-information sources, describe development undertaken or outstanding, and clarify a development request if necessary, insofar as relevant to the contact.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has not been issued.",
              "The case is pending at DDS."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.a",
            "source_context_refs": [
              "C3"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-representative-inquiry-before-PDE-at-DDS-source-step-2",
            "title": "Explain file access and preserve the disclosure limit",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Advise the appointed representative of the right to review or receive copies of file material. Do not disclose information about the disability determination until claim processing is complete. This card does not decide that processing is complete or a disclosure is authorized.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has not been issued.",
              "The case is pending at DDS."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.a",
            "source_context_refs": [
              "C3"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-representative-inquiry-before-PDE-at-DDS-source-step-3",
            "title": "Document the request and actions",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Prepare an SSA-5002 or document the nature of the request and actions taken in an eCAT Claims Communication or a DCPS Case Note. These record alternatives do not establish that the requested material was received.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has not been issued.",
              "The case is pending at DDS."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.a",
            "source_context_refs": [
              "C3"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-after-PDE-not-at-DDS": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-representative-inquiry-after-PDE-not-at-DDS",
        "full_route": "DDS-represented-case-contact/DDS-representative-inquiry-after-PDE-not-at-DDS",
        "entry_conditions": [
          "An appointed representative contacts DDS about the client’s case.",
          "The Personalized Disability Explanation (PDE) has been issued.",
          "The case is no longer at DDS."
        ],
        "steps": [
          {
            "id": "DDS-representative-inquiry-after-PDE-not-at-DDS-source-step-1",
            "title": "Explain the forwarding and direct the inquiry",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Inform the inquirer that DDS forwarded the claim to another office. Forward the inquiry to the office with jurisdiction for a response, and advise the inquirer to contact the servicing field office with further questions. Office roles do not prove receipt or identity.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has been issued.",
              "The case is no longer at DDS."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.b",
            "source_context_refs": [
              "C3",
              "005-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          },
          {
            "id": "DDS-representative-inquiry-after-PDE-not-at-DDS-source-step-2",
            "title": "Electronic case: add the prescribed alert",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Add an alert to the electronic folder under the linked DI81020.080 instructions. The detailed linked alert procedure is not supplied or newly reviewed in this packet. An alert is not an automatic response or completed handoff.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has been issued.",
              "The case is no longer at DDS.",
              "The actual case is electronic."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.b",
            "source_context_refs": [
              "C3",
              "005-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ],
            "alternative_group": "case-format"
          },
          {
            "id": "DDS-representative-inquiry-after-PDE-not-at-DDS-source-step-3",
            "title": "Paper case: prepare the route slip",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Complete an SSA-408 and annotate it with the source comment: Inquiry Action Needed. This paper instruction is not an electronic-message substitute.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has been issued.",
              "The case is no longer at DDS.",
              "The actual case is paper."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.3.b",
            "source_context_refs": [
              "C3",
              "005-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ],
            "alternative_group": "case-format"
          },
          {
            "id": "DDS-representative-inquiry-after-PDE-not-at-DDS-source-step-4",
            "title": "Send both copies under the another-office instruction",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Under the separately scoped another-office inquiry instruction, forward a copy of the reply and the inquiry to the office in possession of the claim. This destination role is not automatically the same office as the office with jurisdiction, and this is not the acknowledgement-copy route for an unknown servicing office.",
            "conditions": [
              "An appointed representative contacts DDS about the client’s case.",
              "The Personalized Disability Explanation (PDE) has been issued.",
              "The case is no longer at DDS.",
              "DDS receives an inquiry and the claim is in another office under the separately applicable DI31005.005 B instruction."
            ],
            "source": "r19_DDS_inquiry005",
            "section": "DI31005.005 B",
            "source_context_refs": [
              "005-B"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        },
        "alternative_groups": [
          {
            "id": "case-format",
            "label": "Use the instruction for the actual case format",
            "logic": "source_conditions_determine_branch",
            "note": "Electronic-folder alert and paper route slip are conditional alternatives. Unclear case format establishes neither instruction; no automatic case classification or completed handoff."
          }
        ]
      },
      "DDS-represented-case-contact/DDS-development-request-and-notice-copies": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "DDS-development-request-and-notice-copies",
        "full_route": "DDS-represented-case-contact/DDS-development-request-and-notice-copies",
        "entry_conditions": [
          "The claimant has an appointed representative.",
          "DDS is sending a development-evidence/action request, CE/disability-hearing attendance request or determination notice listed in C7."
        ],
        "steps": [
          {
            "id": "DDS-development-request-and-notice-copies-source-step-1",
            "title": "Send the request or notice to both recipients",
            "kind": "ssa",
            "actor": "DDS",
            "action": "Send the selected development-evidence or action request, consultative-examination or disability-hearing attendance request, or determination notice to the claimant with a copy to the appointed representative. A copied request does not show that evidence was supplied, attendance occurred or a determination was made. FO and OHO correspondence use their separately linked instructions.",
            "conditions": [
              "The claimant has an appointed representative.",
              "DDS is sending a development-evidence/action request, CE/disability-hearing attendance request or determination notice listed in C7."
            ],
            "source": "r19_DDS_contact010",
            "section": "DI31001.010 C.7",
            "source_context_refs": [
              "C7"
            ],
            "qualifications": [
              "The actual represented-case contact facts required by this scenario must be established; selecting the walkthrough does not establish them.",
              "Incoming appointment/fee-document disposition and PDE/PDN dating identity remain unresolved; these cards do not supply a document-disposal or notice-date procedure.",
              "No actual contact, record entry, message receipt, case transfer, permission grant or completed outcome is established."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual communication, record handling, office receipt, response and successful continuation remain unverified."
          ]
        }
      }
    },
    "source_contexts": [
      {
        "source_code": "DI31001.010",
        "start": 185,
        "end": 1882,
        "span_sha256": "3e7df23c553e56b5743ac20c46873204218f18e579becd65c769e5a03f06f4d4",
        "exact_text": "A. \nEvents that end a representative's appointment\n\nFor actions and events that end the appointment of a representative and his or her authority, see GN 03910.060A.\n\nNOTE: If a claimant files a new disability claim, they and their representative must complete a new written notice of appointment (i.e., Form SSA-1696 (Claimant's Appointment of a Representative)) and submit it to the Field Office (FO).\n\nB. \nContacting represented claimants\n\nA represented claimant may continue to participate in the development of his or her claim, through the appointed representative or directly with SSA or the DDS.\n\n1. \nClaimant initiates contact\n\nIf a represented claimant contacts SSA or the DDS, SSA or the DDS may discuss his or her specific issue. A represented claimant does not need permission from the appointed representative to contact SSA or the DDS directly.\n\n2. \nSSA or DDS initiates contact\n\nIf the claimant appoints a representative, generally the DDS initiates all contacts connected to that claim through, or with the permission of, the appointed representative. For information about when to contact represented claimants directly, see GN 03910.050.\n\nWhen the claimant has appointed multiple representatives and it is not clear who is currently appointed or who is the principal representative, DDS may contact the represented claimant directly to clarify the situation. For more information about multiple representative situations, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times and the representatives do not appear to be working together. In this instance, SSA will contact the claimant directly to clarify the situation.\n\nC. \nPotential issues",
        "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP",
        "id": "A-B"
      },
      {
        "source_code": "DI31001.010",
        "start": 2124,
        "end": 2799,
        "span_sha256": "ed1cf91a1ea860f6a32f7b46d269d7f426f8bcc5e1b8cfdb5178129f27c5c972",
        "exact_text": "1. \nAppointed representative requests SSA or the DDS to communicate directly with the claimant regarding a specific issue\n\nIf the representative requests that we communicate directly with the claimant regarding a specific issue:\n\n•\n\nPrepare an SSA-5002 (Report of Contact), Electronic Claims Analysis Tool (eCAT) Claims Communication, or Disability Case Processing System (DCPS) Case Note to document that the DDS will deal directly with the claimant on the specific issue;\n\n•\n\nInclude the SSA-5002, eCAT Claims Communication, or DCPS Case Note in the file. For paper cases, send a copy to the FO;\n\n•\n\nPost a message in eView to notify the FO of the representative's request.",
        "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP",
        "id": "C1"
      },
      {
        "source_code": "DI31001.010",
        "start": 2801,
        "end": 3636,
        "span_sha256": "ea233ac73f8b7cacbb56ac3ee7803ad9d23e687bda149641c1a4594d7ecadcaf",
        "exact_text": "2. \nRepresented claimant requests SSA or the DDS to communicate directly with him or her regarding a specific issue\n\nIf a represented claimant requests that we communicate directly with him or her regarding a particular issue:\n\n•\n\nPrepare an SSA-5002 describing the claimants desire to communicate directly with the DDS on that specific issue;\n\n•\n\nInclude the SSA-5002 in the electronic folder. For paper cases, send a copy to the FO;\n\n•\n\nPost a message in eView to notify the FO of the claimant's request.\n\nIMPORTANT: A represented claimant's request that the agency communicate directly with him or her on a specific issue is not a revocation of the representative's appointment. Remind the claimant that the representative continues to have access to the file, which may include information regarding the issue he or she identified.",
        "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP",
        "id": "C2"
      },
      {
        "source_code": "DI31001.010",
        "start": 3638,
        "end": 5577,
        "span_sha256": "0808931c3622b9e00b063652e9e1175b2c452c98ec6c237e29faec2434c1ece0",
        "exact_text": "3. \nAppointed representative contacts the DDS\n\nIf the representative contacts the DDS, subsequent actions taken depend on whether the DDS has issued the Personalized Disability Explanation (PDE). To determine the PDE's date of issue, see DI 81020.130D.\n\na. \nBefore PDE issuance and case is pending at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case before PDE issuance and the case is at the DDS, provide the following information that is relevant to the contact:\n\n•\n\nIdentify sources of medical information.\n\n•\n\nIndicate development undertaken or outstanding.\n\n•\n\nClarify the need for a development request, if necessary.\n\n•\n\nAdvise the representative of his or her right to both review or receive copies of material in the claimant's file.\n\n•\n\nDo not disclose information about the disability claim determination to an appointed representative until claim processing is complete.\n\n•\n\nPrepare an SSA-5002 or document the nature of the appointed representative's request in an eCAT Claims Communication or a DCPS Case Note, and the actions taken to comply with the request.\n\nb. \nWhen the case is no longer at the DDS\n\nWhen an appointed representative contacts the DDS to discuss his or her client's case after PDE issuance and the case is no longer at the DDS, inform the inquirer that the DDS forwarded the claim to another office, and take the following action(s):\n\n•\n\nForward the inquiry to the office with jurisdiction of the claim for a response;\n\n•\n\nAdvise the inquirer to contact the servicing FO if he or she has further questions about the claim; and either\n\n•\n\nAdd an alert to the electronic folder for electronic claims according to the instructions in DI 81020.080; or\n\n•\n\nComplete an SSA-408 (Route Slip) for paper claims and annotate with the comment: Inquiry Action Needed.\n\nFor more information about handling inquiries when the case is no longer at the DDS, see DI 31005.005.",
        "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP",
        "id": "C3"
      },
      {
        "id": "005-B",
        "source_code": "DI31005.005",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
        "start": 1782,
        "end": 2488,
        "exact_text": "B. \nResponding to an inquiry if the claim is in another office\n\nInform the inquirer the DDS forwarded the claim to another office and take the following action(s):\n\n•\n\nforward the inquiry to the office with jurisdiction of the claim for a response;\n\n•\n\nadvise the inquirer to contact the servicing FO if he or she has further questions about the claim; and\n\n•\n\nfor electronic claims add an alert to the electronic folder according to the instructions in DI 81020.080; or\n\n•\n\nfor paper claims complete an SSA-408 (Route Slip) and annotate with the comment: “Inquiry – Action Needed;” and\n\n•\n\nforward a copy of the reply and the inquiry to the office in possession of the claim.\n\nC. \nResponding to an inquiry",
        "span_sha256": "feeb64ab58c09c9278153dbd2a31781cb72243bc5bd663f032598d135fc1879f",
        "whole_maintext_sha256": "6f6c8c956cfb689dae6817bdcd1b1600c4cc960e6798f9e8d714ea11ddc1c25b"
      },
      {
        "source_code": "DI31001.010",
        "start": 7337,
        "end": 8245,
        "span_sha256": "c391f703439ffbb9178cb3d8069a4535c0a4fd03e36c3bd954e504167c804110",
        "exact_text": "7. \nNotices and correspondence\n\nSend all notices and correspondence to both the claimant and the appointed representative, as follows:\n\n•\n\nSend requests for developmental evidence or action (e.g., work history or disability reports, questionnaires, medical deferment, call-in letters) to the claimant and a copy to the representative.\n\n•\n\nSend requests to attend a consultative examination (CE) or a disability hearing to the claimant and a copy to the representative.\n\n•\n\nSend determination notices to the claimant and a copy to the representative.\n\nNOTE: Sending requests to attend a CE or other requests for evidence or action to both the claimant and the representative ensures that both parties are made aware of the requests.\n\nFor notices and correspondence specific to the FO, see GN 03910.050B. For notices and correspondence specific to the Office of Hearing Operations (OHO), see HALLEX I-1-1-20.E.",
        "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP",
        "id": "C7"
      }
    ],
    "prior_source_objects": {
      "r19_DDS_contact010": {
        "code": "DI 31001.010",
        "title": "DDS represented-case contact — selected issue/request/inquiry scopes",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
        "revision": "07/26/2022 - Present",
        "transmittal": "TN 26 (07-26)",
        "kind": "Captured official POMS — selected DDS staff context",
        "checked_on": "2026-10-31",
        "review_status": "selected_contexts_checked_not_whole_page",
        "verification_scope": "Selected DDS contact/inquiry/copy instructions only; C5 incoming-document disposition explicitly held."
      },
      "r19_DDS_inquiry005": {
        "code": "DI 31005.005",
        "title": "DDS another-office inquiry — selected B routing and reply-copy scope",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431005005",
        "revision": "04/15/2013 - Present",
        "transmittal": "Basic (04-13)",
        "kind": "Captured official POMS — selected DDS staff context",
        "checked_on": "2026-10-31",
        "review_status": "selected_contexts_checked_not_whole_page",
        "verification_scope": "B another-office inquiry route and added reply+inquiry copy; A regional/routing context only. Other response-subject/paper-record/program routes not modeled."
      },
      "r19_DDS_PDN_comparison130": {
        "code": "DI 81020.130",
        "title": "PDN dating comparison — PDE/PDN identity unresolved",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0481020130#d",
        "revision": "07/18/2022 - Present",
        "transmittal": "TN 28 (07-22)",
        "kind": "Selected published source comparison — application held",
        "checked_on": "2026-10-31",
        "review_status": "selected_source_comparison_hold",
        "verification_scope": "A/D PDN naming/dating source comparison only; no PDE identity mapping or timestamp calculation applied."
      },
      "r19_DDS_document_comparison001": {
        "code": "DI 31001.001",
        "title": "Incoming representation-document comparison — disposition overlap unresolved",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001001#b1",
        "revision": "05/06/2025 - Present",
        "transmittal": "TN 24 (05-25)",
        "kind": "Selected published source comparison — application held",
        "checked_on": "2026-10-31",
        "review_status": "selected_source_comparison_hold",
        "verification_scope": "B/B1/B5 incoming-document comparison only; no chosen reconciliation or new appointment/update/revocation workflow."
      }
    },
    "journey_scope_bindings": {
      "DDS-represented-case-contact/DDS-claimant-initiates-specific-issue": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-representative-requests-specific-issue": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-claimant-requests-specific-issue": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-before-PDE-at-DDS": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-representative-inquiry-after-PDE-not-at-DDS": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-development-request-and-notice-copies": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      },
      "DDS-represented-case-contact/DDS-initiates-contact/DDS-multiple-representatives-principal-unclear": {
        "id": "DDS-represented-case-contact",
        "title": "Contact about a disability case with a representative",
        "story": "DDS may handle a contact or inquiry about a person who has an appointed representative. Who starts the contact, what is requested and where the case is now affect the instructions. This example does not show that any contact or request has occurred.",
        "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
          "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
          "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
          "Choosing this walkthrough does not establish those facts or complete any communication."
        ],
        "condition_logic": "all",
        "upfront_limits": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
        ],
        "unmatched_source_states": [
          "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
          "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
          "PDE/PDN identity and issue date not established from the linked dating page.",
          "Incoming representation/fee-document disposal/forward/return action remains held."
        ],
        "automatic_transition_from_R18": false,
        "new_native_edges": false,
        "original_research_conditions": [
          "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative.",
          "The actual initiator, request purpose, issue, appointment and case location/stage must be established for the chosen scenario.",
          "Selecting this illustration does not establish those case facts or complete a contact."
        ],
        "category": "Disability evidence and staff contact",
        "short": "Contact about a disability case with a representative",
        "scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
        "level": "Selected public-source DDS scenario",
        "review_status": "Selected source-linked research; actual case facts, internal execution and outcomes unverified.",
        "path": [
          "Identify who started the contact",
          "Record a specific-issue request when one is made",
          "Keep the required record and inform the field office",
          "Use the right response and notice recipients"
        ],
        "channels": {
          "online": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "phone": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action.",
          "office": "This walkthrough describes DDS staff handling. You may contact SSA or DDS about a specific issue; choosing a channel here does not complete a contact, change representation or establish the conditions for a staff action."
        },
        "checklist": [
          "Keep correspondence and any request from SSA.",
          "Check which issue and contact arrangement apply to your case.",
          "Ask SSA which office currently has the claim if that is unclear."
        ],
        "timing": "These are source instructions, not measured processing times, customer deadlines or a notice-date calculator.",
        "timing_type": "Source procedure; duration not measured",
        "outcome": "The source describes contact and inquiry handling; actual communication, evidence receipt, case routing and outcomes are not established.",
        "gaps": [
          "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
          "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
          "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
          "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
          "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
          "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
          "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
          "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
          "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite.",
          "Remaining inquiry subject restrictions, paper-record search, appointment-document processing and other linked targets are not a complete workflow here."
        ],
        "source_ids": [
          "r19_DDS_contact010",
          "r19_DDS_inquiry005",
          "r19_DDS_PDN_comparison130",
          "r19_DDS_document_comparison001",
          "DDS_paper_inquiry005C_selected"
        ],
        "source_applicability": {
          "conditions": [
            "DDS is handling contact, correspondence or an inquiry about a disability case with an appointed representative; the claim may now be in another office.",
            "Only the case facts required by the chosen scenario must be established. Contact initiator, request purpose, appointment and case location are distinct facts.",
            "The separate inquiry route for a claim in another office does not require a notice-issue-date finding.",
            "Choosing this walkthrough does not establish those facts or complete any communication."
          ],
          "condition_logic": "all",
          "actor_scope": "DDS handling of represented-case contact, correspondence and inquiries, including an inquiry reaching DDS after the claim has moved. No global current-DDS or PDE-stage requirement is imposed on all scenarios.",
          "limits": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "case_facts_not_determined": true
        },
        "source_comparison_holds": [
          {
            "id": "DDS-incoming-representation-document-disposition",
            "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
            "source_context_refs": [
              "010-C5",
              "001-B-intro",
              "001-B1",
              "001-B5"
            ],
            "observations": [
              "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
              "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
              "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
              "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
            ],
            "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
            "why_not_resolved": [
              "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
              "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
              "Different effective dates/TN labels alone establish no governing precedence.",
              "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
            ],
            "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
            "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
            "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
          },
          {
            "id": "DDS-PDE-PDN-notice-identity-date",
            "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
            "source_context_refs": [
              "010-C3",
              "130-A",
              "130-D"
            ],
            "observations": [
              "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
              "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
              "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
            ],
            "why_not_resolved": [
              "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
              "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
              "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
            ],
            "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
            "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
          }
        ],
        "native_source_acceptance": false,
        "existing_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r19-DDS-existing-record-context.json",
          "registry_sha256": "90e738dc573ab42baaf38d1a0e008ca88690e41e1f8f1a8fb830bf6770b3802e",
          "source_native_acceptance": false
        },
        "paper_inquiry_source_applicability": {
          "kind": "additional_selected_paper_inquiry_context",
          "checked_on": "2026-10-31",
          "records": 2,
          "ledger_url": "/service/r21-DDS-paper-inquiry-selected-claim-ledger.json",
          "top_record_id": "DDS-paper-record-not-found-after-thorough-search",
          "nested_full_route": "DDS-represented-case-contact/DDS-paper-record-not-found-after-thorough-search/DDS-paper-record-servicing-FO-unknown",
          "thorough_paper_search_required": true,
          "unknown_servicing_FO_condition_only_for_nested_record": true,
          "local_missing_record_not_no_claim_finding": true,
          "old_global_conditions_and_source_holds_unchanged": true,
          "source_native_acceptance": false
        },
        "paper_inquiry_record_context_navigation": {
          "kind": "source_qualified_existing_record_context_not_native_edge",
          "registry_url": "/service/r21-DDS-paper-inquiry-existing-record-context.json",
          "registry_sha256": "2a01e284f31cae758391079fe46ecdba84ac0dc4766038a5d2943da959dbd465",
          "source_native_acceptance": false
        }
      }
    },
    "ancestor_bindings": {
      "DDS-represented-case-contact/DDS-claimant-initiates-specific-issue": [],
      "DDS-represented-case-contact/DDS-initiates-contact": [],
      "DDS-represented-case-contact/DDS-representative-requests-specific-issue": [],
      "DDS-represented-case-contact/DDS-claimant-requests-specific-issue": [],
      "DDS-represented-case-contact/DDS-representative-inquiry-before-PDE-at-DDS": [],
      "DDS-represented-case-contact/DDS-representative-inquiry-after-PDE-not-at-DDS": [],
      "DDS-represented-case-contact/DDS-development-request-and-notice-copies": [],
      "DDS-represented-case-contact/DDS-initiates-contact/DDS-multiple-representatives-principal-unclear": [
        {
          "id": "DDS-initiates-contact",
          "title": "DDS starts the contact",
          "when": "DDS intends to contact a represented claimant about the claim.",
          "you": "Ask SSA or your representative to explain the contact arrangement.",
          "ssa": "DDS generally makes claim-related contacts through your representative or with the representative’s permission.",
          "next": "Other source-defined direct-contact circumstances need their own established conditions.",
          "condition_logic": "all",
          "conditions": [
            "The claimant has appointed a representative.",
            "DDS is initiating contact connected to that claim."
          ],
          "source_case_conditions": [
            "The claimant has appointed a representative.",
            "DDS is initiating contact connected to that claim."
          ],
          "source_instruction_summary": "B2 general rule through/with permission. GN03910.050 is linked for circumstances; not a blanket permission finding or rule for every SSA staff workflow.",
          "source_context_refs": [
            "A-B"
          ],
          "source_provenance": [
            {
              "source_code": "DI31001.010",
              "start": 185,
              "end": 1882,
              "span_sha256": "3e7df23c553e56b5743ac20c46873204218f18e579becd65c769e5a03f06f4d4",
              "exact_text": "A. \nEvents that end a representative's appointment\n\nFor actions and events that end the appointment of a representative and his or her authority, see GN 03910.060A.\n\nNOTE: If a claimant files a new disability claim, they and their representative must complete a new written notice of appointment (i.e., Form SSA-1696 (Claimant's Appointment of a Representative)) and submit it to the Field Office (FO).\n\nB. \nContacting represented claimants\n\nA represented claimant may continue to participate in the development of his or her claim, through the appointed representative or directly with SSA or the DDS.\n\n1. \nClaimant initiates contact\n\nIf a represented claimant contacts SSA or the DDS, SSA or the DDS may discuss his or her specific issue. A represented claimant does not need permission from the appointed representative to contact SSA or the DDS directly.\n\n2. \nSSA or DDS initiates contact\n\nIf the claimant appoints a representative, generally the DDS initiates all contacts connected to that claim through, or with the permission of, the appointed representative. For information about when to contact represented claimants directly, see GN 03910.050.\n\nWhen the claimant has appointed multiple representatives and it is not clear who is currently appointed or who is the principal representative, DDS may contact the represented claimant directly to clarify the situation. For more information about multiple representative situations, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times and the representatives do not appear to be working together. In this instance, SSA will contact the claimant directly to clarify the situation.\n\nC. \nPotential issues",
              "whole_maintext_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0431001010",
              "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot; not raw HTTP"
            }
          ],
          "qualifications": [
            "This is DDS-specific staff handling, not a new filing service or a general permission rule for every SSA office.",
            "An incoming claimant contact, an agency-initiated contact, a representative-requested direct contact and a claimant-requested direct contact have different premises.",
            "The current R18 GN050 MCS/CCE/RASR workflow remains separate. These sources do not create an automatic transition between the journeys.",
            "No actual contact, record entry, message receipt, office handoff, entitlement determination, sanction or successful rejoin is established.",
            "Misconduct/referral, failure-to-cooperate adjudication and claim denial instructions are outside this proposal.",
            "Incoming representation/fee-document return, forwarding and disposal instructions have an unresolved scope/wording overlap. This walkthrough does not choose an action for those documents or combine the conflicting instructions.",
            "Linked instructions use PDE and PDN labels without an established record-identity mapping for this walkthrough. No notice issue date is calculated from EF Received or Notice Release Date.",
            "These holds do not turn the separate contact and inquiry scenarios into document-disposition or date-calculation procedures.",
            "Only actual case facts required by each source scenario apply. A case-in-another-office inquiry under DI31005.005B has no added PDE-date prerequisite."
          ],
          "system_context_candidate_ids": [],
          "timing": "No measured duration, universal response clock or case-completion estimate is established.",
          "owner": "DDS staff; FO or office with jurisdiction only where the selected source condition requires it.",
          "rejoin": {
            "status": "not_established",
            "automatic_transition": false,
            "unknowns": [
              "Actual case facts, completed communication and successful return to another workflow remain unverified."
            ]
          },
          "source_native_acceptance": false,
          "source_holds": [
            "DDS-incoming-representation-document-disposition",
            "DDS-PDE-PDN-notice-identity-date"
          ],
          "source": "r19_DDS_contact010",
          "section": "A-B",
          "additional_sources": [],
          "ui_display_conditions": [
            "The claimant has appointed a representative.",
            "DDS is initiating contact connected to that claim."
          ],
          "systems": [],
          "entity_ids": [],
          "route": "Selected source-qualified DDS handling; no automatic return or completed handoff",
          "review_status": "Selected source-linked DDS scenario; actual case facts, internal execution and completed outcomes unverified.",
          "source_qualified_branch": {
            "kind": "selected_source_qualified_staff_scenario",
            "case_facts_not_determined": true,
            "new_native_edges_or_aliases": false
          },
          "source_receipt": {
            "checked_on": "2026-10-31",
            "snapshot_sha256": "dcd21a088a49766406ae6a6911934e5b9d3cb32c3a77a7b9d8710f6189a2919b",
            "snapshot_path": "/service/sources/DI31001.010-r19-main.txt",
            "report": "/service/r19-DDS-selected-claim-ledger.json"
          }
        }
      ]
    },
    "holds_exact": [
      {
        "id": "DDS-incoming-representation-document-disposition",
        "status": "UNRESOLVED_PRIMARY_WORDING_SCOPE_HOLD",
        "source_context_refs": [
          "010-C5",
          "001-B-intro",
          "001-B1",
          "001-B5"
        ],
        "observations": [
          "010 C5 says DDS returns representative information or fee-related documents received by mail/fax to sender and directs to 001 B1.",
          "001 B broadly says fax representation documents to FO, with SSA1699 special destination; document actions via SSA5002 in DCPS, destroy unprocessed paper after scanning and do not update DCPS representative information.",
          "001 B1 separately distinguishes exact duplicate SSA1696 local destruction versus new/updated appointment fax to FO plus assistance request identifying WorkTrack fax/date; development continues where possible.",
          "001 B5 again describes forwarding other representation/fee documents to FO and document destruction, while actual revocation/withdrawal uses its specific scan/AR instruction."
        ],
        "overlap": "Both pages address DDS receipt of representation documents by mail/fax and the 010 C5 reference explicitly points into 001 B1. The broader 001 B text also overlaps fee/other representation documents.",
        "why_not_resolved": [
          "The supplied primary text contains no explicit supersession, priority or return-versus-forward exception that reconciles the broad overlap.",
          "Do not invent a combined fax-copy-to-FO plus return-original routine. Destruction and exact-duplicate handling require their own predicates and may overlap the broad return instruction.",
          "Different effective dates/TN labels alone establish no governing precedence.",
          "Do not relabel appointment/fee intake as the C1/C2 staff-created specific-issue contact record solely to avoid the hold."
        ],
        "safe_current_scope": "Keep incoming appointment/fee/registration document disposition outside the proposed R19 contact request workflow. Where an input mixes those matters, do not automatically choose a disposal/forward/return action.",
        "unheld_facts": "The separate source-specific 001 B1 duplicate/new appointment predicates and named downstream FO/RASR/EDCS/UAT context may be recorded as source-qualified observations, not a unified adopted route.",
        "resolution_evidence_needed": "Explicit official clarification/change instruction or directly supported scope distinction addressing this overlap; not inferred deployment or a date-only preference."
      },
      {
        "id": "DDS-PDE-PDN-notice-identity-date",
        "status": "UNRESOLVED_RECORD_IDENTITY_AND_DATING_APPLICABILITY_HOLD",
        "source_context_refs": [
          "010-C3",
          "130-A",
          "130-D"
        ],
        "observations": [
          "010 C3 uses Personalized Disability Explanation (PDE), asks whether it was issued, and directs to 130 D to determine the issue date.",
          "130 A/D use Personalized Disability Notices (PDNs), describe print-upon-closure dating, and when the paper/electronic PDN has no date direct to its EF Received column under Section B.",
          "130 D OQR note says PDN not dated until OQR review completes; after completion notice release date is in the Notice Release Date field under Case Review on the Case Data screen."
        ],
        "why_not_resolved": [
          "The direct cross-reference is meaningful primary dating context but does not itself identify which actual document is the PDE/PDN or prove the labels refer to the same record in every case.",
          "No supplied text explicitly defines PDE equals PDN, nor treats every EF Received timestamp as PDE issue date.",
          "EF Received is a missing-date PDN instruction, not a universal notice-date field; the separate OQR condition remains material."
        ],
        "safe_current_scope": "Preserve exact PDE-labelled 010 C3 predicates and PDN-labelled 130 D instructions separately. No automatic PDE issue date calculation or assignment from EF Received/Notice Release Date until notice identity and applicable conditions are supported.",
        "resolution_evidence_needed": "Primary terminology/record-identity basis and applicable dating conditions; actual case stage still requires case evidence."
      }
    ],
    "unmatched_source_states_exact": [
      "PDE issued but case still at DDS remains unassigned under the two010 C3 alternatives; other005A response scope requires its own subject/processing predicates.",
      "Before PDE issuance but case no longer at DDS is not automatically010 C3b; the separate005B another-office route may apply only if its own facts are established.",
      "PDE/PDN identity and issue date not established from the linked dating page.",
      "Incoming representation/fee-document disposal/forward/return action remains held."
    ],
    "scope_limits": [
      "Eight existing unsequenced paths only, no new route or child, no core rewrite.",
      "No C.4 general-correspondence, C.5 incoming-document, C.6 evidence submission, C.8/9 adjudication or D/E misconduct workflow expansion.",
      "The before/after PDE conjunctions are not exhaustive; unresolved combinations stay unmatched.",
      "Existing separately modeled .005 B and paper .005 C paths and source holds remain unchanged.",
      "No new native contextual references, aliases, edges, nodes or source flags.",
      "No prescribed timing interval, SLA, case outcome or successful rejoin is supplied by these selected instructions."
    ],
    "projection_contract": "Future migration may append only the exact approved exception_flow field to these eight exact fullpath/original-record objects. All eight original fields, journey/global/source objects, source flags, ancestor metadata and other old152flows remain exact; derived binding/catalog mirrors and affected exports need a separately approved strict contract. No integration authorized by this draft.",
    "negative_QA": [
      {
        "id": "N01",
        "case": "Claimant initiates contact without representative permission",
        "required_boundary": "Do not impose the DDS-initiated permission rule on B.1."
      },
      {
        "id": "N02",
        "case": "DDS initiates ordinary contact without permission",
        "required_boundary": "B.1 does not supply a direct-contact exception for DDS-initiated contact."
      },
      {
        "id": "N03",
        "case": "Only one representative or principal is clear",
        "required_boundary": "Do not select the multiple-representative ambiguity clarification branch."
      },
      {
        "id": "N04",
        "case": "Multiple representatives but unrelated evidence questions",
        "required_boundary": "Clarification permission is not unrestricted evidence-question authority."
      },
      {
        "id": "N05",
        "case": "Representative makes specific-issue request",
        "required_boundary": "C.1 record options are OR; do not require all three."
      },
      {
        "id": "N06",
        "case": "Claimant makes specific-issue request",
        "required_boundary": "Do not replace C.2 SSA-5002 with the C.1 eCAT/DCPS alternatives."
      },
      {
        "id": "N07",
        "case": "Claimant requests direct contact and expects privacy",
        "required_boundary": "Do not infer revocation or loss of representative file access."
      },
      {
        "id": "N08",
        "case": "Electronic versus paper case unknown",
        "required_boundary": "Select neither conditional alert nor route-slip alternative."
      },
      {
        "id": "N09",
        "case": "PDE not issued but case has moved",
        "required_boundary": "Neither C.3.a nor C.3.b conjunction is established; separate .005 B may apply only on its own facts."
      },
      {
        "id": "N10",
        "case": "PDE issued but case still at DDS",
        "required_boundary": "Neither modeled C.3 conjunction is established; do not invent insertion/rejoin."
      },
      {
        "id": "N11",
        "case": "Only an EF Received or PDN date is known",
        "required_boundary": "Do not infer PDE identity or issue date; preserve the existing dating hold."
      },
      {
        "id": "N12",
        "case": "Unknown servicing office after no paper record found",
        "required_boundary": "Do not substitute C.3.b/.005 B reply-copy instruction for .005 C acknowledgement-copy/parallel-FO instruction."
      },
      {
        "id": "N13",
        "case": "Incoming appointment or fee documents mixed into contact",
        "required_boundary": "Do not apply C.1/C.2 as a workaround for unresolved .010 C.5/.001 B disposition overlap."
      },
      {
        "id": "N14",
        "case": "Copy of development request exists",
        "required_boundary": "Do not infer evidence receipt, attendance, case determination or successful rejoin."
      },
      {
        "id": "N15",
        "case": "Linked DI81020.080 alert details missing",
        "required_boundary": "Do not invent exact alert fields, delivery/receipt or current runtime."
      },
      {
        "id": "N16",
        "case": "eCAT label or historical native record exists",
        "required_boundary": "Do not infer current platform deployment, new alias or automatic case execution."
      },
      {
        "id": "N17",
        "case": "A new flow, raw record, ancestor, source or hold is changed",
        "required_boundary": "Future binding must fail closed; no generic ignore-exception-flow or metadata waiver."
      },
      {
        "id": "N18",
        "case": "A user chooses a source branch",
        "required_boundary": "No actual appointment, request, location, issue stage or permission is established."
      }
    ],
    "counts": {
      "existing_routes": 8,
      "cards": 18,
      "new_routes": 0,
      "alternatives_groups": 1,
      "negative_cases": 18
    },
    "author_checks_not_independent_approval": true,
    "frozen_R27_changed": false,
    "revision": {
      "prior_package_sha256": "61f3a5816404f319b3ea14ccd1a5f9aaef0a48511d20bd242f645f8f4e21a479",
      "only_change": "Register actual existing A-B/C1/C2/C3/C7 context IDs explicitly on derived source-context objects, retaining exact source spans and all original-record provenance."
    },
    "independent_source_review_sha256": "5dd810936897c70952eb56106fb2689a5eee55183b65c3a8a339a23ba3c3f294",
    "public_capture_links": [
      {
        "code": "DI31001.010",
        "maintext_url": "/service/sources/DI31001.010-r19-main.txt",
        "snapshot_url": "/service/sources/DI31001.010-r19-DOM-snapshot.txt"
      },
      {
        "code": "DI31005.005",
        "maintext_url": "/service/sources/DI31005.005-r19-main.txt",
        "snapshot_url": "/service/sources/DI31005.005-r19-DOM-snapshot.txt"
      },
      {
        "code": "DI31001.001",
        "maintext_url": "/service/sources/DI31001.001-r19-main.txt",
        "snapshot_url": "/service/sources/DI31001.001-r19-DOM-snapshot.txt"
      },
      {
        "code": "DI81020.130",
        "maintext_url": "/service/sources/DI81020.130-r19-main.txt",
        "snapshot_url": "/service/sources/DI81020.130-r19-DOM-snapshot.txt"
      }
    ]
  },
  "r29_wage_followup18": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "EIGHTEEN_SELECTED_EXISTING_SEQUENCES_SOURCE_REVIEWED_NOT_COMPLETE_POLICY_OR_CASE_FINDING",
    "selected_flow_count": 18,
    "checked_on": "2026-10-31",
    "packages": {
      "wage10": {
        "flows": {
          "report-ssi-wages/ssi-pie-reduced-reporting-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-pie-reduced-reporting-notice",
            "full_route": "report-ssi-wages/ssi-pie-reduced-reporting-notice",
            "entry_conditions": [
              "SSA has sent a reduced-reporting notice for the particular employer because it receives that employer’s wage and employment information through PIE. Authorization alone is not this notice.",
              "The named employer and the notice’s actual reporting instructions must be established; other SSI reporting duties remain separate."
            ],
            "steps": [
              {
                "id": "ssi-pie-reduced-reporting-notice-source-step-1",
                "title": "Follow the notice for the named employer",
                "kind": "you",
                "actor": "Worker",
                "action": "Follow the reduced-reporting notice for the particular employer named in it. Do not treat an authorization receipt as proof that payroll information arrived or that reporting requirements changed.",
                "conditions": [
                  "SSA has sent a reduced-reporting notice for the particular employer because it receives that employer’s wage and employment information through PIE. Authorization alone is not this notice.",
                  "The named employer and the notice’s actual reporting instructions must be established; other SSI reporting duties remain separate."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.4 Reduced Reporting",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-pie-reduced-reporting-notice-source-step-2",
                "title": "Keep reporting other information",
                "kind": "you",
                "actor": "Worker",
                "action": "Continue reporting wages from other employers and information PIE does not provide, including applicable work expenses related to your medical condition. Other SSI reporting duties are not waived. Ask SSA to clarify the employer or notice if needed.",
                "conditions": [
                  "SSA has sent a reduced-reporting notice for the particular employer because it receives that employer’s wage and employment information through PIE. Authorization alone is not this notice.",
                  "The named employer and the notice’s actual reporting instructions must be established; other SSI reporting duties remain separate."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.4 Reduced Reporting; C.3 note",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/right-employer-wrong-amount": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "right-employer-wrong-amount",
            "full_route": "ssi-payroll-wage-dispute/right-employer-wrong-amount",
            "entry_conditions": [
              "A recipient, deemor or payee questions payroll-provider wage evidence or alleges an amount discrepancy, and the employer information is accurate.",
              "This is an amount dispute, not an allegation that the earnings or employment do not belong to the worker or that identity theft occurred."
            ],
            "steps": [
              {
                "id": "right-employer-wrong-amount-source-step-1",
                "title": "Explain how to dispute the provider’s information",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Advise the worker to contact the payroll data provider to correct the error using the notice’s provider information. The provider did not make SSA’s benefit determination.",
                "conditions": [
                  "A recipient, deemor or payee questions payroll-provider wage evidence or alleges an amount discrepancy, and the employer information is accurate.",
                  "This is an amount dispute, not an allegation that the earnings or employment do not belong to the worker or that identity theft occurred."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 D.2.a; D.4",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "right-employer-wrong-amount-source-step-2",
                "title": "Handle an appeal when one is requested",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the individual requested an appeal, use the separately linked reconsideration instructions. A reconsideration may be express or implied but must be in writing; this walkthrough does not complete an appeal or decide timeliness.",
                "conditions": [
                  "A recipient, deemor or payee questions payroll-provider wage evidence or alleges an amount discrepancy, and the employer information is accurate.",
                  "This is an amount dispute, not an allegation that the earnings or employment do not belong to the worker or that identity theft occurred.",
                  "An appeal was requested."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 D.2.b; D.1",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "right-employer-wrong-amount-source-step-3",
                "title": "Develop and compare wage evidence",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Request paystubs and develop other wage evidence as necessary under the wage-evidence instructions. Use other acceptable evidence if it supports a more accurate determination; if it confirms the provider’s evidence, continue using that information. Do not apply this paystub request to earnings the worker disclaims as not theirs.",
                "conditions": [
                  "A recipient, deemor or payee questions payroll-provider wage evidence or alleges an amount discrepancy, and the employer information is accurate.",
                  "This is an amount dispute, not an allegation that the earnings or employment do not belong to the worker or that identity theft occurred."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 D.2.c; contrast D.3 NOTE",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/mef-also-wrong": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "mef-also-wrong",
            "full_route": "ssi-payroll-wage-dispute/mef-also-wrong",
            "entry_conditions": [
              "The matter includes a wage inaccuracy or employment discrepancy involving the Master Earnings File, in addition to the payroll-evidence issue.",
              "An SSI wage-entry correction alone does not establish a correction to the Master Earnings File."
            ],
            "steps": [
              {
                "id": "mef-also-wrong-source-step-1",
                "title": "Use the separate earnings-record instructions",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "For an inaccuracy or employment discrepancy involving the Master Earnings File, use the linked earnings-inaccuracy procedure. The full linked correction and identity-theft procedures are not supplied here; this card does not determine whose earnings they are or complete a permanent-record correction.",
                "conditions": [
                  "The matter includes a wage inaccuracy or employment discrepancy involving the Master Earnings File, in addition to the payroll-evidence issue.",
                  "An SSI wage-entry correction alone does not establish a correction to the Master Earnings File."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 D.3.c",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/pie-reconsideration-authorization-gap": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "pie-reconsideration-authorization-gap",
            "full_route": "ssi-payroll-wage-dispute/pie-reconsideration-authorization-gap",
            "entry_conditions": [
              "A timely reconsideration is filed after the calendar month in which the denial posted, but within the applicable appeal period described by the source.",
              "The authorization is inactive in the system due to the stated system limitation; actual appeal stage and timeliness must be established. This is not the late-appeal new-authorization instruction."
            ],
            "steps": [
              {
                "id": "pie-reconsideration-authorization-gap-source-step-1",
                "title": "Record the authorization when loading the appeal",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Input the authorization manually when loading the timely reconsideration. Do not contact the individual for new authorization solely because of this system limitation. The source distinguishes a system-inactive entry from the original authorization, which remains active from reconsideration processing until a final adverse agency decision.",
                "conditions": [
                  "A timely reconsideration is filed after the calendar month in which the denial posted, but within the applicable appeal period described by the source.",
                  "The authorization is inactive in the system due to the stated system limitation; actual appeal stage and timeliness must be established. This is not the late-appeal new-authorization instruction."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 B.2 reconsideration bullet 2",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "pie-reconsideration-authorization-gap-source-step-2",
                "title": "Identify missing payroll months",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "A gap in information may occur until authorization is reloaded or obtained again. Do not assume that an active authorization proves data for each month was received.",
                "conditions": [
                  "A timely reconsideration is filed after the calendar month in which the denial posted, but within the applicable appeal period described by the source.",
                  "The authorization is inactive in the system due to the stated system limitation; actual appeal stage and timeliness must be established. This is not the late-appeal new-authorization instruction."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 B.2 final paragraph",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "pie-reconsideration-authorization-gap-source-step-3",
                "title": "Develop evidence for the missing months when required",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the appeal filed after the denial-posting month is eventually approved, use other wage-verification methods for months for which PIE information was not received. The source’s appeal periods are filing rules, not a new clock or deadline calculator in this walkthrough.",
                "conditions": [
                  "A timely reconsideration is filed after the calendar month in which the denial posted, but within the applicable appeal period described by the source.",
                  "The authorization is inactive in the system due to the stated system limitation; actual appeal stage and timeliness must be established. This is not the late-appeal new-authorization instruction.",
                  "The appeal is eventually approved and relevant months lack PIE information."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 B.2 final paragraph",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/pie-reporting-restart-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "pie-reporting-restart-notice",
            "full_route": "ssi-payroll-wage-dispute/pie-reporting-restart-notice",
            "entry_conditions": [
              "SSA previously issued a reduced-reporting notice for this employer.",
              "SSA stopped receiving that employer’s wage and employment information through PIE for three consecutive months; a specific increased-reporting notice applies."
            ],
            "steps": [
              {
                "id": "pie-reporting-restart-notice-source-step-1",
                "title": "Use the employer-specific increased-reporting notice",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The automated notice tells the individual to begin reporting wage and employment information again for that employer after the stated three-month condition. A single missing feed does not by itself establish this notice condition.",
                "conditions": [
                  "SSA previously issued a reduced-reporting notice for this employer.",
                  "SSA stopped receiving that employer’s wage and employment information through PIE for three consecutive months; a specific increased-reporting notice applies."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.4 Increased Reporting",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "pie-reporting-restart-notice-source-step-2",
                "title": "Follow the changed instructions and retain other duties",
                "kind": "you",
                "actor": "Worker",
                "action": "Follow the notice for the named employer. Continue reporting other employers and information PIE does not supply; the notice does not determine your SSI payment or waive other required reporting.",
                "conditions": [
                  "SSA previously issued a reduced-reporting notice for this employer.",
                  "SSA stopped receiving that employer’s wage and employment information through PIE for three consecutive months; a specific increased-reporting notice applies."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.4",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/pie-ein-pending": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "pie-ein-pending",
            "full_route": "ssi-payroll-wage-dispute/pie-ein-pending",
            "entry_conditions": [
              "Payroll-provider wage information is received for a record with an existing Wages page whose employer identifier does not match.",
              "The situation is not the separate no-Wages-page new-employment instruction or a successful identifier match."
            ],
            "steps": [
              {
                "id": "pie-ein-pending-source-step-1",
                "title": "Recognize the pending wage page and diary",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source describes creation of a PDP Pending Wage page and an EE diary when the existing Wages page lacks a matching employer identifier. This does not establish that the wages posted or that the worker’s employer is wrong.",
                "conditions": [
                  "Payroll-provider wage information is received for a record with an existing Wages page whose employer identifier does not match.",
                  "The situation is not the separate no-Wages-page new-employment instruction or a successful identifier match."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.3.b",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "pie-ein-pending-source-step-2",
                "title": "Check the employer identifier and use the diary procedure",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Check that employer identifiers for active employers are accurate on the Wages pages. Follow the linked EE diary resolution procedure for an unsuccessful match; its detailed workflow is not supplied here. No automatic correction or completed posting is inferred.",
                "conditions": [
                  "Payroll-provider wage information is received for a record with an existing Wages page whose employer identifier does not match.",
                  "The situation is not the separate no-Wages-page new-employment instruction or a successful identifier match."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.2 IMPORTANT; C.3.b",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "ssi-payroll-wage-dispute/pie-manual-deeming-pending": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "pie-manual-deeming-pending",
            "full_route": "ssi-payroll-wage-dispute/pie-manual-deeming-pending",
            "entry_conditions": [
              "Payroll-provider wages are received for a record with Force Due or Manual Deeming present.",
              "The pending wage report, manual staff action and reduced-reporting notice are distinct source events."
            ],
            "steps": [
              {
                "id": "pie-manual-deeming-pending-source-step-1",
                "title": "Review the pending report and development issue",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source describes a PDP Pending Wage Report page marked Force Due or Manual Deeming and an issue on the Development Worksheet. Review the claim and take the appropriate wage-posting actions. This does not certify a current screen or that wages posted.",
                "conditions": [
                  "Payroll-provider wages are received for a record with Force Due or Manual Deeming present.",
                  "The pending wage report, manual staff action and reduced-reporting notice are distinct source events."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.3.d",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "pie-manual-deeming-pending-source-step-2",
                "title": "Keep the reduced-reporting notice conditional",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Do not send a manual reduced wage-reporting notice for these records. The specified notice is sent when the recipient is in another active payment status and the Wages page and SSR are updated with provider wages through automation; neither step is presumed complete.",
                "conditions": [
                  "Payroll-provider wages are received for a record with Force Due or Manual Deeming present.",
                  "The pending wage report, manual staff action and reduced-reporting notice are distinct source events.",
                  "The source’s active-payment-status and automated Wages-page/SSR update conditions govern issuance of the specified notice."
                ],
                "source": "ssipayroll",
                "section": "SI00820.148 C.4 NOTE",
                "source_context_refs": [
                  "SI00820.148:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "report-ssi-wages/ssi-provider-authorization-before-search": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-provider-authorization-before-search",
            "full_route": "report-ssi-wages/ssi-provider-authorization-before-search",
            "entry_conditions": [
              "Paystubs are not readily available and staff are considering an SSA-approved wage-verification company search.",
              "The worker’s actual authorization must be checked before any company request; authorization is voluntary, not an SSI payment condition."
            ],
            "steps": [
              {
                "id": "ssi-provider-authorization-before-search-source-step-1",
                "title": "Check the authorization first",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Access WEIA to check whether the wage earner authorized the request. Authorization is obtained through WEIA or a paper SSA-8240; paper responses use the separately linked recording and file-documentation instructions. Do not request company information after refusal or revocation.",
                "conditions": [
                  "Paystubs are not readily available and staff are considering an SSA-approved wage-verification company search.",
                  "The worker’s actual authorization must be checked before any company request; authorization is voluntary, not an SSI payment condition."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 D.1",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-provider-authorization-before-search-source-step-2",
                "title": "Check approved-provider employer participation",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Only after proper authorization has been established, check with the SSA-approved wage-verification companies to determine employer participation and run the authorized search. A nonapproved company has separate worker-provided-evidence safeguards; this is not permission for staff access to its website.",
                "conditions": [
                  "Paystubs are not readily available and staff are considering an SSA-approved wage-verification company search.",
                  "The worker’s actual authorization must be checked before any company request; authorization is voluntary, not an SSI payment condition.",
                  "Proper authorization has been established and paystubs are not readily available."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 D.2; C.1.c",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-provider-authorization-before-search-source-step-3",
                "title": "Document the evidence without assuming completeness",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Document evidence under the company-evidence instructions. Company information is primary evidence under the specified unavailable-paystub conditions unless it is missing or discrepant; actual evidence and its limits must still be reviewed.",
                "conditions": [
                  "Paystubs are not readily available and staff are considering an SSA-approved wage-verification company search.",
                  "The worker’s actual authorization must be checked before any company request; authorization is voluntary, not an SSI payment condition.",
                  "A company response has been obtained."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 C.1.a; D.2; D.4",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "report-ssi-wages/ssi-provider-missing-conflicting-components": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-provider-missing-conflicting-components",
            "full_route": "report-ssi-wages/ssi-provider-missing-conflicting-components",
            "entry_conditions": [
              "Wage-verification-company information is missing components or conflicts with other wage evidence.",
              "Actual authorization and evidence-development prerequisites remain applicable; a company total does not establish all wage components."
            ],
            "steps": [
              {
                "id": "ssi-provider-missing-conflicting-components-source-step-1",
                "title": "Resolve an actual discrepancy",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "When the company information conflicts with other wage evidence, obtain other primary or secondary evidence to resolve the discrepancy. Do not choose a wage amount merely because one source is a provider.",
                "conditions": [
                  "Wage-verification-company information is missing components or conflicts with other wage evidence.",
                  "Actual authorization and evidence-development prerequisites remain applicable; a company total does not establish all wage components.",
                  "A discrepancy exists between company information and other wage evidence."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 C.1.a; D.4",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-provider-missing-conflicting-components-source-step-2",
                "title": "Develop indicated cafeteria-plan amounts",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the record or company evidence indicates a cafeteria plan may exist and exact amounts are missing, use the linked cafeteria-plan development procedure. Its detailed rules are not newly reviewed here.",
                "conditions": [
                  "Wage-verification-company information is missing components or conflicts with other wage evidence.",
                  "Actual authorization and evidence-development prerequisites remain applicable; a company total does not establish all wage components.",
                  "Evidence indicates a cafeteria plan may exist AND the wage evidence lacks exact amounts."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 D.3",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-provider-missing-conflicting-components-source-step-3",
                "title": "Develop indicated unreported tips",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the record or company evidence indicates unreported tips, obtain additional primary or secondary evidence. This condition can coexist with a cafeteria-plan issue; these are not mutually exclusive alternatives.",
                "conditions": [
                  "Wage-verification-company information is missing components or conflicts with other wage evidence.",
                  "Actual authorization and evidence-development prerequisites remain applicable; a company total does not establish all wage components.",
                  "Record or company evidence indicates unreported tips."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 D.3",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-provider-missing-conflicting-components-source-step-4",
                "title": "Record verified wages and the evidence determination",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Record verified wages on the Wages page or SSR. For ordinary verified information, store it in CEF, or NDRED if a CEF is unavailable in eView, using EP when faxing to NDRED; alternatively use a locked Report of Contact or EVID. For an actual discrepancy, summarize and lock the determination on Report of Contact or EVID, or use SSA-5002 outside the claim system, and store the evidence and determination in CEF or NDRED through EP. Do not infer that storage, verification or a determination has occurred.",
                "conditions": [
                  "Wage-verification-company information is missing components or conflicts with other wage evidence.",
                  "Actual authorization and evidence-development prerequisites remain applicable; a company total does not establish all wage components.",
                  "The relevant wages and determination have actually been verified/developed under the applicable source conditions."
                ],
                "source": "ssiwageverificationcompanies",
                "section": "SI00820.147 D.4",
                "source_context_refs": [
                  "SI00820.147:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          },
          "report-ssi-wages/ssi-ticket-wages-incomplete-employer-followthrough": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-ticket-wages-incomplete-employer-followthrough",
            "full_route": "report-ssi-wages/ssi-ticket-wages-incomplete-employer-followthrough",
            "entry_conditions": [
              "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
              "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
              "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established."
            ],
            "steps": [
              {
                "id": "ssi-ticket-wages-incomplete-employer-followthrough-source-step-1",
                "title": "Ask the employer about wages paid",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Phone the employer to develop and verify wages paid, rather than wages merely earned. Do not disclose the individual’s personal information in an employer voicemail. If an employer participates with an approved wage-verification company, the earlier provider route and its authorization conditions remain material.",
                "conditions": [
                  "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
                  "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
                  "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established."
                ],
                "source": "ssiwage135run72",
                "section": "SI00820.135 B chart entry; B.1 steps 8-11",
                "source_context_refs": [
                  "SI00820.135:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-ticket-wages-incomplete-employer-followthrough-source-step-2",
                "title": "Document employer evidence without deferred wages",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the employer supplies wage information and no deferred wages are involved, post wages when received and document a locked Report of Contact with the call date, employer, contact name/title/phone, gross wages paid, known pay date, covered period and applicable deductions or exclusions. Outside the SSI Claims system, use SSA-5002 and store it in EP.",
                "conditions": [
                  "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
                  "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
                  "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established.",
                  "The employer supplies wage information AND no deferred wages are involved."
                ],
                "source": "ssiwage135run72",
                "section": "SI00820.135 B.1 step 11",
                "source_context_refs": [
                  "SI00820.135:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-ticket-wages-incomplete-employer-followthrough-source-step-3",
                "title": "Keep deferred-wage handling separate",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the employer supplies information and deferred wages are involved, use the separately linked deferred-wage instructions, post the remaining wages when received and document the verified deferred wages on locked EVID or Report of Contact; outside the claim system use SSA-5002 with the employer-contact information and store it in EP. The linked deferred-wage rules are not supplied here.",
                "conditions": [
                  "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
                  "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
                  "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established.",
                  "The employer supplies wage information AND deferred wages are involved."
                ],
                "source": "ssiwage135run72",
                "section": "SI00820.135 B.1 step 11",
                "source_context_refs": [
                  "SI00820.135:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-ticket-wages-incomplete-employer-followthrough-source-step-4",
                "title": "Use written employer development when required",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the employer cannot be reached, is uncooperative, or provides evidence for which an oral statement is insufficient, continue to the chart’s written employer-development step. This is not permission to bypass the earlier approved-provider or evidence-priority conditions. No letter response or successful continuation is presumed.",
                "conditions": [
                  "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
                  "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
                  "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established.",
                  "The employer cannot be reached OR is uncooperative OR the oral statement is insufficient."
                ],
                "source": "ssiwage135run72",
                "section": "SI00820.135 B.1 steps 11-12",
                "source_context_refs": [
                  "SI00820.135:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              },
              {
                "id": "ssi-ticket-wages-incomplete-employer-followthrough-source-step-5",
                "title": "Keep a nonapproved-company referral worker-led",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the employer refuses wage evidence and refers staff to a nonapproved company, use the separately conditioned worker-provided evidence route. Staff must not access or establish accounts, enter the worker’s personal information, otherwise contact the company or disclose information to it. Only evidence provided by the individual may be accepted under the source’s conditions.",
                "conditions": [
                  "The source’s wage-verification chart subject and applicable over-$65 threshold are established.",
                  "Staff have reached the iTOPSS evidence step through the applicable earlier chart choices. Preferred evidence for the relevant period has not resolved the wage verification; multiple evidence types may be needed for partial periods.",
                  "The iTOPSS information is missing, incomplete or inconsistent; an actual query result or missing-information condition must be established.",
                  "The employer will not provide wage evidence AND refers staff or the worker to a nonapproved wage-verification company."
                ],
                "source": "ssiwage135run72",
                "section": "SI00820.135 B.1 steps 11-13; SI00820.147 C.1.c",
                "source_context_refs": [
                  "SI00820.135:whole"
                ],
                "qualifications": [
                  "The case facts in these conditions are not established by selecting the illustration.",
                  "The cards describe source instructions, not actual authorization, a completed search or correction, successful transmission, benefit eligibility, receipt or case completion.",
                  "Linked detailed procedures remain separately bounded unless their complete captured source is explicitly supplied in this packet. No automatic rejoin or native identity/edge is established."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual reporting instructions, evidence, action completion, record correction and continuation remain case-specific and unverified."
              ]
            }
          }
        },
        "original_records": {
          "report-ssi-wages/ssi-provider-authorization-before-search": {
            "id": "ssi-provider-authorization-before-search",
            "title": "SSA considers a wage-provider search when pay stubs are unavailable",
            "when": "Staff seeks wage verification from an approved provider.",
            "you": "Give your voluntary authorization decision and continue requested wage reporting.",
            "ssa": "Check WEIA for authorization before provider use; authorization may be obtained through WEIA or SSA-8240 with the cited paper-response documentation. Do not request company information after refusal or revocation. With proper authorization and unavailable pay stubs, check approved-provider employer participation and document evidence.",
            "route": "SSA → WEIA authorization check → approved-provider search / other evidence route",
            "next": "Existing payroll-data-authorization guidance covers who may authorize, recording, revocation and receipts. Provider access requires its own authorization check.",
            "source": "ssiwageverificationcompanies",
            "section": "D.1-2",
            "timing": "No completion duration specified.",
            "review_status": "Official selected subsections checked 2026-10-17"
          },
          "report-ssi-wages/ssi-provider-missing-conflicting-components": {
            "id": "ssi-provider-missing-conflicting-components",
            "title": "Provider wage data omits details or conflicts with other evidence",
            "when": "Wage-provider evidence is incomplete or inconsistent.",
            "you": "Explain discrepancies and provide requested wage evidence.",
            "ssa": "Obtain other wage evidence to resolve discrepancies. Develop indicated cafeteria-plan amounts under SI00820.102 when exact amounts are missing, and obtain additional evidence for indicated unreported tips. Record verified wages on the Wages page or SSR. Document the determination in a locked Report of Contact/EVID, or SSA-5002 outside the claim system; store evidence and determination in CEF or NDRED through EP as applicable.",
            "route": "SSA wage review → additional evidence / benefit-plan development → documented determination",
            "next": "Provider totals do not settle missing components or conflicting wage facts.",
            "source": "ssiwageverificationcompanies",
            "section": "C.1.a; D.3-4",
            "timing": "No discrepancy-resolution completion period specified.",
            "review_status": "Official selected subsections checked 2026-10-17"
          },
          "report-ssi-wages/ssi-pie-reduced-reporting-notice": {
            "id": "ssi-pie-reduced-reporting-notice",
            "title": "SSA tells you it receives wages from a particular employer",
            "when": "You receive SSA notice that it is obtaining a named employer wage and employment information through PIE; authorization alone is not this notice.",
            "you": "Follow the notice for the named employer. Continue reporting other employers and information PIE does not supply, including applicable work expenses related to your medical condition. Report a new employer, return to work, improvement in your condition, and other required SSI changes. Ask SSA to clarify any employer or reporting question.",
            "ssa": "Notify the individual through the specified automated notice when PIE receipt changes reporting requirements. Reduced reporting applies only to employer information received through PIE; other employers and information not supplied by PIE remain reportable.",
            "route": "Automated employer-specific reporting notice to recipient; SSA clarification if needed.",
            "next": "Keep the notice and current reporting instructions. This does not waive every SSI reporting duty, decide payment eligibility, or assume an authorization receipt proves payroll data arrived.",
            "source": "ssipayroll",
            "section": "C.4 Reduced Reporting; compare GN00204.150A and B.4.b",
            "timing": "Reporting change depends on the SSA notice and employer receipt; no fixed notice-delivery or case-processing deadline established.",
            "review_status": "Selected official C.4 and GN00204.150B.4.b source text reviewed2026-10-25; customer explanation editorial; no operational execution or full-page coverage claim.",
            "supporting_source_ids": [
              "payrollauthorization"
            ],
            "source_receipt": {
              "report": "service-pie-notice-branch-proposal.json",
              "snapshot_path": "sources/pie148-reporting-current-20261025.html",
              "snapshot_sha256": "23f2e946026e2cd2f3a9709f23b8818ec07b70cd19f83268eb3041f863d252d6",
              "checked_on": "2026-10-25",
              "secondary_snapshot_path": "sources/weia150-reporting-current-20261025.html",
              "secondary_snapshot_sha256": "62db9b0705e7d1ab10803f5ef7235701e2d293ff83e92091c8defb3e6a45ea39"
            }
          },
          "report-ssi-wages/ssi-ticket-wages-incomplete-employer-followthrough": {
            "id": "ssi-ticket-wages-incomplete-employer-followthrough",
            "title": "Ticket to Work wage information is incomplete or inconsistent",
            "when": "SSA reaches the iTOPSS evidence step while verifying SSI wages over $65 per month, but the available Ticket to Work wage information is missing, incomplete or inconsistent.",
            "you": "Identify the months or wage details that need clarification and provide available wage records SSA requests. Ask what evidence remains needed.",
            "ssa": "SI00820.135B.1step10 sends missing, incomplete or inconsistent iTOPSS information to step11. SSA phones the employer to develop wages paid and documents the contact and wage evidence. Apply the separate deferred-wage rules when needed; if the employer cannot be reached, is uncooperative or oral evidence is insufficient, continue to step12. A referral to a nonapproved wage company follows the separate step13 safeguards. When phoning the employer, SSA staff must not disclose the individual’s PII on employer voicemail.",
            "owner": "SSA staff developing SSI wage evidence",
            "route": "Incomplete/inconsistent iTOPSS evidence -> SSA employer contact and documentation -> further prescribed evidence development if needed",
            "next": "Ask which wage months or records still need verification. A Ticket wage report alone does not settle your SSI payment.",
            "source": "ssiwage135run72",
            "section": "SI00820.135B.1steps10-11whole; Bchartentry/steps1-9 and12-16/B2 boundaries retained",
            "timing": "These evidence steps give no completion or SSI payment-adjustment deadline.",
            "review_status": "WholeB1steps10-11 andA-C current source checked2026-10-27. Only SSI wage verification in the over65dollar chart when this evidence step is reached; not TitleIIworkCDR or automaticbenefit adjudication. Missing, incomplete or inconsistent iTOPSS information proceeds to step11; no conclusion of fraud or invalid Ticket participation. Complete iTOPSS use still requires worker agreement/preferred-evidenceattempts/monthlystaffrecording and signedstatement/ROC documentation understep10. EmploymentNetwork/TPM input is not conclusive or automatically posted SSI verification. SSA staff contact employer about wages paid, not earned; customer is not assigned internal records or employer calls required ofstaff. Step11 employer oral information requires documentation including contact/date/wageperiod and lock; deferredwages keep separateposting rules. Uncooperative/unreachable employer or insufficient oral evidence followsstep12; referraltononapprovedcompany followsstep13. Do not infer that SSA may access nonapproved provider accounts; step13prohibitions remain. No individual SSI calculation, payment adjustment, deadline, appeal or penalty outcome is established. Retained135revision2023-11-20/TN99(03-25)/batch2026-10-15/capture2026-10-27 distinct; reuseTechcapture is not independent corroboration.",
            "source_receipt": {
              "report": "service-SSI135-ticket-incomplete-integration-gate.json",
              "snapshot_path": "sources/ssi-wage135-current-20261027.html",
              "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
              "checked_on": "2026-10-27"
            },
            "staff_privacy_review": {
              "report": "service-SSI135-voicemail-field-proposal.json",
              "CPU_audit": "service-SSI135-privacy-linux-cpu195-audit.json",
              "snapshot_path": "sources/ssi-wage135-current-20261027.html",
              "snapshot_sha256": "980d8eda4f0cb6695325935f2359cc9fb6124a93cb8e5837db71799d49767023",
              "checked_on": "2026-10-27",
              "scope": "B1 step11 staff-only employer-voicemail PII prohibition; prior wage/evidence/customer qualifications retained"
            }
          },
          "ssi-payroll-wage-dispute/right-employer-wrong-amount": {
            "id": "right-employer-wrong-amount",
            "title": "The employer is right but the wage amount is wrong",
            "when": "The dispute concerns amount rather than employment.",
            "you": "Supply requested paystubs or other wage evidence.",
            "ssa": "Develop acceptable wage evidence and use the more accurate supported amount.",
            "route": "SSI wage development",
            "next": "Do not apply the no-paystub rule for disclaimed jobs to every amount dispute.",
            "source": "ssipayroll",
            "section": "D.2",
            "timing": "No completion duration specified",
            "review_status": "Selected branch checked; detailed exceptions remain"
          },
          "ssi-payroll-wage-dispute/mef-also-wrong": {
            "id": "mef-also-wrong",
            "title": "The permanent earnings record is also affected",
            "when": "The issue reaches MEF beyond SSI payroll evidence.",
            "you": "Identify the disputed record as well.",
            "ssa": "Use earnings-inaccuracy procedures for the MEF issue.",
            "route": "SSI → earnings-record investigation",
            "next": "A corrected SSI wage entry does not necessarily fix MEF.",
            "source": "ssipayroll",
            "section": "D.3.c",
            "timing": "No completion duration specified",
            "review_status": "Selected branch checked; detailed exceptions remain"
          },
          "ssi-payroll-wage-dispute/pie-reconsideration-authorization-gap": {
            "id": "pie-reconsideration-authorization-gap",
            "title": "A timely reconsideration crosses the denial month",
            "when": "Timely request after the denial-posting calendar month, within the applicable appeal period.",
            "you": "Keep appeal and wage records.",
            "ssa": "Manually input authorization when loading the appeal; do not recontact for new consent solely because of this system limitation. If later approved, develop wage evidence for months missing PIE data.",
            "route": "SSI appeal loading → authorization / wage development",
            "next": "This month boundary is not a new customer appeal deadline.",
            "source": "ssipayroll",
            "section": "B.2",
            "timing": "Source describes60 days plus5 mailing days; actual appeal timeliness requires SSA review",
            "review_status": "Selected official subsection checked; individual appeal/payment outcome not determined"
          },
          "ssi-payroll-wage-dispute/pie-reporting-restart-notice": {
            "id": "pie-reporting-restart-notice",
            "title": "SSA stops receiving an employer payroll feed",
            "when": "Reduced-reporting notice previously issued; no employer information for three consecutive months.",
            "you": "Follow the new reporting notice.",
            "ssa": "Automated notice directs resumed reporting for that employer.",
            "route": "Automated notice → recipient",
            "next": "Continue reporting other employers and information PIE does not supply.",
            "source": "ssipayroll",
            "section": "C.4",
            "timing": "Three consecutive missing-feed months triggers this notice condition; no delivery guarantee",
            "review_status": "Selected official subsection checked; individual appeal/payment outcome not determined"
          },
          "ssi-payroll-wage-dispute/pie-ein-pending": {
            "id": "pie-ein-pending",
            "title": "Payroll wages do not match the employer identifier",
            "when": "Existing Wages page lacks a matching EIN.",
            "you": "Identify the actual employer when SSA asks.",
            "ssa": "Check accurate EIN entries for active employers. Unmatched data creates a PDP Pending Wage page and EE diary; follow SI02310.200 for resolution.",
            "route": "SSI technician → pending-wage review",
            "next": "A payroll feed can require staff development before posting.",
            "source": "ssipayroll",
            "section": "C.2; C.3.b",
            "timing": "No completion duration specified",
            "review_status": "Selected official condition checked; detailed EE diary procedure separately pending"
          },
          "ssi-payroll-wage-dispute/pie-manual-deeming-pending": {
            "id": "pie-manual-deeming-pending",
            "title": "Payroll wages require manual processing",
            "when": "Force Due or Manual Deeming condition exists.",
            "you": "Keep current reporting instructions.",
            "ssa": "Review the pending wage report and Development Worksheet issue; take appropriate wage-posting action. Do not issue a manual reduced-reporting notice; the specified automated notice follows active-pay-status and automated wage/SSR updates.",
            "route": "SSI technician → manual wage action",
            "next": "Pending wages and reduced-reporting notice are separate events.",
            "source": "ssipayroll",
            "section": "C.3.d; C.4 note",
            "timing": "No completion duration specified",
            "review_status": "Selected official condition checked; detailed EE diary procedure separately pending"
          }
        },
        "source_contexts": [
          {
            "id": "SI00820.148:whole",
            "source_code": "SI00820.148",
            "locator": "Whole captured rendered #content main including full tables, notes and linked-reference labels",
            "start": 0,
            "end": 19304,
            "exact_text": "Effective Dates: 03/25/2025 - Present\nPrevious | Next\n\nTN 99 (03-25)\n\nSI 00820.148 Automated Wage and Employment Information from Payroll Data Providers (PDP) Received through the Payroll Information Exchange (PIE)\n\nCITATIONS: Public Law 114-74 The Bipartisan Budget Act of 2015, Section 824; Social Security Act §§ 225, 1184(a), 1631 (42 U.S.C. §§ 425, 1320e-3, 1383) 20 CFR 404.702, 404.703, 404.1588, 416.701, 416.702, 416.708, 416.709, 416.988, 422.150.\n\nA. \nIntroduction to PIE\n\nSection 824 of the Bipartisan Budget Act (BBA) of 2015 enacted section 1184 of the Social Security Act (Act), which allows the Social Security Administration (SSA) to enter into an information exchange with payroll data providers (PDPs) to obtain wage and employment information. Employers who participate in a payroll service with a PDP send their wage and employment information to the PDP. The payroll information exchange (PIE) automates the reporting process by transmitting information from the PDP and helps reduce improper payments by ensuring timely and accurate submission of wage and employment reports.\n\nTo obtain information through PIE, the recipient, deemor or ineligible child must provide authorization and work for an employer that reports payroll information to a participating PDP.\n\n \n\nB. \nCollecting wage and employment authorization for new participants\n1. \nGeneral information about collecting wage and employment authorizations\n\nBefore we receive wage and employment information from a PDP, we must obtain authorization from the recipient, deemor, or ineligible child. See Wage and Employment Information Authorization MS 09401.002. Providing authorization is voluntary and not an SSI eligibility requirement. For more information on the authorization to receive wage and employment information, see GN 00204.150.\n\n2. \nSpecial considerations for wage and employment authorizations when appeals are involved\n\nThe system will only request information for recipients, deemors, and ineligible children who have an active authorization during the monthly PIE run. In cases where a claim is denied for any reason and terminates in the SSI Claims system, the authorization will effectively end if it is beyond the appeals period for the claim (i.e., 60 days plus 5 mailing days). Due to a system limitation, authorization may also end in the system if a reconsideration is not requested or processed by the end of the calendar month in which a denial posts to the record. Handle wage and employment authorizations during appeals as follows:\n\nFor reconsideration requests:\n\n•\n\nIf a reconsideration is filed and the request is processed within the same calendar month that the denial posts, the authorization remains active. No additional steps are required to record authorization.\n\n•\n\nIf a timely reconsideration is filed after the calendar month in which the denial posts but within the appeal period (60 days plus 5 mailing days), input authorization manually when the appeal is loaded. However, technicians do NOT need to contact the recipient, deemor, or ineligible child to request authorization again. In these cases, the original authorization is only inactive due to a system limitation and the original authorization itself remains active from the time the request for reconsideration is processed until the Agency makes a final adverse decision on the claim.\n\nFor all other appeal requests:\n\n•\n\nFor hearings before an administrative law judge, appeals council requests, and court reviews filed and processed within the appeal period (60 days plus 5 mailing days), the authorization remains active until the Agency or a court makes a final adverse decision on the claim. No additional steps are required to record authorization.\n\n•\n\nFor late filing of an appeal (after 60 days plus 5 mailing days), the authorization will end after the appeal period expires. Contact the individual to request a new authorization. The Wage and Employment Information Authorization (WEIA) questions automatically appear in the SSI Claims system path.\n\nWhen appeals are involved, there may be a gap in wage and employment information received until we reload or obtain authorization again. If the appeal is filed after the calendar month in which the denial posts and eventually approved, the technician must use other wage verification methods to request wage evidence for any months we did not receive information from PIE. For more information on evidence of wages, see SI 00820.130.\n\nC. \nPIE process\n1. \nRequest\n\nAt the beginning of each month, prior to the Goldberg-Kelly Notice Cutoff, we request wage and employment information for the prior month from the PDP for individuals who have an active authorization. The PDP returns wage and employment information through PIE for individuals whose employer(s) participate in the PDP service.\n\nNOTE: \n\nAs part of this automated exchange, we will request wage and employment information for the prior month's wages ONLY. This data will accumulate in the Wage and Employment Information (WEI) repository for as long as we have an active authorization.\n\n2. \nReceive\n\nInformation received through PIE automatically post to records and may also be accessed manually through the WEI repository. The WEI repository is accessed from IMAIN and displays results based on search criteria for wage and employment information provided by a technician, see MS 09601.001 and MS 09601.002. This information is used for matching purposes in the SSI Claims system to determine whether to post the wage and employment information to the Wages page on the appropriate record. For SSI cases, wages update to the record before the Goldberg-Kelly Notice Cutoff date each month.\n\nIMPORTANT: When taking claims, processing redeterminations, or handling wage-related workloads, be sure to complete the Employer Identification Number (EIN) field on the Wages page accurately for all active employers listed in the SSI Claims system, see SI 00820.143B.3.\n\n3. \nAutomate\n\nAs part of PIE’s automated process, the SSI Claims system attempts to match employer information to an individual’s record. The EIN from the PDP attempts to match to any EIN on an individual’s SSI Claims system Wages pages for SSI and concurrent cases.\n\na. \n\nSuccessful Match\n\nWhen a successful match occurs, (i.e., the SSI Claims system record contains a Wages page with a matching EIN):\n\n•\n\nThe Wages page that contains income or wage data with a matching EIN automatically updates with the wage information received from the PDP through PIE.; and\n\n•\n\nThe wages will be submitted to the Supplemental Security Income record (SSR) to affect payment prior to the Goldberg-Kelly Notice Cutoff. In adverse action cases, the system automatically sends the Notice of Planned Action including information about appeal rights, payment continuation, and any applicable Fair Credit Reporting Act (FCRA) disclosures. See Overview of Goldberg/Kelly (GK) Processing, SI 02301.301.\n\nb. \n\nNo Match Between SSI Claims system Wages Page and EIN\n\nWhen the SSI record contains a Wages page without a matching EIN, a PDP Pending Wage page and an EE diary are created.\n\nFor more information on the EE diary, see MS 08114.123.\n\nFor instructions on how to process the EE diary when there is an unsuccessful EIN match, see SI 02310.200.\n\nNOTE: \n\nAs common practice, technicians should review Wage pages and verify that the EIN is on the record to prevent future PDP Pending Wages pages and EE diaries from being created.\n\nc. \n\nNew Employment\n\nWhen we receive wages for records that do not contain any Wages pages:\n\n•\n\nA new Wages page is created using the information from the PDP;\n\n•\n\nThe Work Expenses and Substantial Gainful Activity pages are added with a page status of \"Unfinished\" where applicable. The technician must complete these pages with the appropriate information;\n\n•\n\nThe Quarterly Wages Summary page will be added; and\n\n•\n\nThe wages will be submitted to the SSR to affect payment prior to the Goldberg-Kelly Notice Cutoff. In adverse action cases, the system automatically sends the Notice of Planned Action including information about appeal rights, payment continuation, and any applicable Fair Credit Reporting Act (FCRA) disclosures. See Overview of Goldberg/Kelly (GK) Processing, SI 02301.301.\n\nd. \n\nForce Due or Manual Deeming\n\nWhen we receive wages for the records with Force Due or Manual Deeming present:\n\n•\n\nThe PDP Pending Wage Report page is added with a reason of \"Force Due\" or \"Manual Deeming\" (as appropriate);\n\n•\n\nThe appropriate issue is added to the Development Worksheet; and\n\n•\n\nThe technician needs to review the claim and take the appropriate action(s) to post the wages.\n\nNOTE: \n\nIndividuals are still required to report monthly wages for employers that do not participate with the PDP. This includes any employer who stops participating with the PDP service. When appropriate, encourage individuals to submit their wages using other electronic wage reporting methods to report wages for any employer that does not subscribe to a PDP's service. For more information on available reporting methods, see SI 00820.144.\n\n4. \nNotify\n\nWe will notify the individual when their wage reporting requirements change through an automated notice. This notification is based on whether we receive wage and employment information from the PDP through PIE.\n\n•\n\nReduced Reporting\n\nThe system will send an automated notice informing the individual that they no longer need to report their wage and employment information for a particular employer(s) if we receive it through PIE. Recipients and representative payees are still required to report wages from all other employers. They should also report, for all employers, wage and employment information we would not receive through PIE, such as work expenses related to their medical conditions.\n\n•\n\nIncreased Reporting\n\nThe system will send an automated notice informing the individual that they must begin reporting their wage and employment information again for a particular employer(s) if we stop receiving that information through PIE for three consecutive months. This notice is sent in instances where a reduced reporting notice was previously issued.\n\nNOTE: \n\nFor force due or manual deeming cases, the notice will be sent when the recipient is placed in another active pay status (for example C01 or N01) and the Wage page and the SSR are updated with PDP wage information through automation. Technicians do not send a manual reduced wage reporting notice for force due or manual deeming records.\n\nD. \nHow to resolve reporting discrepancies with the PDP for SSI\n1. \nAppeal requests related to wage evidence from PDPs\n\nIndividuals may contact us if they believe PDP wage evidence is incorrect.\n\nIf the individual disagrees with the payment for a month based on wage evidence from PDP that presented in a Notice of Planned Action (NOPA), they may file a request for reconsideration. A request for reconsideration can be express or implied, but it must be in writing.\n\nIf a request for reconsideration is filed, process the request per SI 04005.020 and SI 04020.000.\n\nFor guidance on initiating the appeals process with someone who has contacted the agency by phone or in person, see SI 04020.020.\n\nSee Also: \n\n•\n\nSI 02301.310 Appeal and the Right to Goldberg Kelly (GK) Payment Continuation  \n\n•\n\nGN 03102.000 Reconsideration (Title II and Entitlement Under Title XVIII) - Table of Contents  \n\n•\n\nDI 13010.145 Reconsideration or Reopening of Continuing Disability Work Issue Cases - Title II \n\n DI 13010.185 Due Process in Work Issue Cases\n\n2. \nDiscrepancy in wage amount alleged but employer is accurate\n\nIf a recipient, deemor, or payee questions PDP wage evidence or alleges a discrepancy, including receiving inaccurate information from a PDP:\n\na. \n\nAdvise the worker to contact the payroll data provider to correct the error following SI 00820.148D.4.\n\nb. \n\nIf an appeal was requested, process the request according to SI 00820.148D.1.\n\nc. \n\nRequest paystubs from the individual and develop other evidence of wages as necessary according to SI 00820.130C. When other acceptable evidence would result in a more accurate determination, use that evidence to document the wages. If other acceptable evidence confirms the PDP evidence, continue to use the PDP information.\n\nNOTE: \n\nWe will not subject individuals who give authorization to certain administrative sanctions for errors or omissions in wage and employment information a PDP gives us through PIE. For more information, refer to GN 00204.150B.4.\n\n3. \nHandling disclaimed earnings\n\nIn cases where the worker alleges the wage and employment information from the PDP does not belong to them or alleges identity theft:\n\na. \n\nAdvise the worker to contact the payroll data provider to correct the error following SI 00820.148D.4.\n\nb. \n\nUsing a signed statement or Report of Contact, obtain the worker's allegation disclaiming the earnings.\n\nNOTE: \n\n Do not request the worker provide pay stubs or evidence of the wages and employment information they are disclaiming.\n\nc. \n\nInvestigate the allegation of erroneous or discrepant wage and employment information per RM 03870.060B.2. Attempt to obtain other wage evidence per SI 00820.130C.\n\n•\n\nFor wage inaccuracies and employment discrepancies involving the Master Earnings File (MEF), see RM 03870.001.\n\n•\n\nFor identity theft allegations, see RM 10220.055 and RM 10220.060.\n\nd. \n\nAccept the worker's allegation unless other primary wage evidence exists to refute the allegation. Correct the record.\n\nSee also:\n\n•\n\nRM 10220.055 Identity Theft and Social Security Number (SSN) Fraud\n\n•\n\nRM 10220.060 Assisting Identity Theft Victims.\n\n•\n\nRM 03870.045 Scrambled Earnings - General\n\n•\n\nRM 03870.048 Development of Scrambled Wages\n\ne. \n\nIf an appeal was requested, process the request according to SI 00820.148D.1.\n\n4. \nAdvising the individual to correct or dispute information with a PDP\n\nDepending on the agency’s PDP arrangement, the agency may include information about how the worker can correct or dispute information provided by the PDP to SSA within its notices. Text related to the Fair Credit Reporting Act (FCRA) will also be included in any adverse action or change in payment notices, instructing individuals on who to contact to correct their wage and employment information if they believe it is incorrect. A copy of the notice which includes the name and contact information for the PDP, can be located in the Online Retrieval System (ORS). The English and Spanish versions read as follows:\n\nEnglish\n\nWe may receive wage and employment information from [PDP] that is part of a consumer report. We may have used all or some of the wage and employment information we received from [ PDP] to determine benefit eligibility, make a benefit decision, or calculate a benefit amount. [PDP] played no part in our determination and is unable to supply specific reasons for the determination we made.\n\n[Wage Reporter's Name] has a right under the FCRA to know the information contained in the consumer report. [Wage Reporter's Name] has a right to a free copy of the consumer report from [PDP] if you request it no later than 60 days after you receive this notice. In addition, if you find that any information contained in the consumer report is inaccurate or incomplete, you have the right to dispute the matter with [PDP]. To obtain a copy of or dispute your consumer report, contact [PDP] at:\n\n[PDP Contact information]\n\nSpanish\n\nPodemos recibir la información de sus salarios y empleador de [PDP] que forma parte de un informe al consumidor. Es posible que hayamos utilizado toda o parte de la información de su salario y de su empleo que recibimos de [PDP] para decidir si tiene derecho a los beneficios, tomar una decisión sobre sus beneficios o calcular la cantidad de sus beneficios. [PDP] no jugó ningún papel en nuestra decisión y no puede proveer razones específicas para la decisión que realizamos.\n\n[Persona que ha reportado los salarios] tiene derecho bajo la Ley FCRA a conocer la información que contiene su informe al consumidor. [Persona que ha reportado los salarios] tiene el derecho a una copia gratuita del informe al consumidor de [PDP] si lo solicita dentro de 60 días después de recibir este aviso. Además, si encuentra que cualquier información contenida en el informe al consumidor es incorrecta o incompleta, tiene el derecho a disputar el asunto con [PDP]. Para obtener una copia o disputar informe al consumidor, póngase en contacto con [PDP] en:\n\n[PDP Contact Information]\n\nNOTE: \n\nWhile we do not encourage revocation as a means to resolve discrepancies with wage and employment information received from PDPs, individuals have the option to revoke their authorization at any time. This revocation applies at the time the technician processes it through the system and a receipt is generated. Revoking authorization for PIE also revokes authorization for manual wage verification with SSA-approved companies like The Work Number. See SI 00820.147 for more information on wage verification companies.  For information about revocation and instructions for processing a revocation request, see GN 00204.150.D. \n\nE. \nSystems requirements\n\nFor SSI purposes, PIE is designed to automatically request and receive wage and employment information whenever active authorization exists and the SSI Claims system contains an active claim.\n\nThe following systems conditions stop successful transmission of wage and employment information through PIE, either by preventing the exchange or by preventing the automatic updating of wage and employment information to the SSI Claims system:\n\n•\n\nThe case is not active in the SSI Claims system (i.e. non-MSSICS case);\n\n•\n\nTermination of the current Supplemental Security Record (SSR) (RIC: T);\n\n•\n\nSSR has a payment status code of N12 or N27 through N54; or\n\n•\n\nData discrepancies exist between the SSI Claims system and the PDP information.\n\nNOTE: \n\nRecords that have one of the characteristics above will not qualify for the PIE process. Follow SI 00820.130 and SI 00820.135 to develop wages for these records.\n\nF. \nReferences\n\nGN 00204.150 Authorization to Obtain Wage and Employment Information from Payroll Data Providers via an Information Exchange for the Social Security Disability Insurance (SSDI) and Supplemental Security Income (SSI) Programs\n\nSI 00820.130 Evidence of Wages or Termination of Wages\n\nSI 00820.135 Wage Verification - Over $65 Per Month\n\nSI 00820.143 Monthly Wage Reporting\n\nSI 00820.144 Monthly Wage Reporting for Recruiting Reporters\n\nSI 00820.147 Wage Evidence from Wage Verification Companies\n\nSI 02301.100 Assessing Penalties\n\nSI 02301.301 Overview of Goldberg/Kelly (GK) Processing\n\nSI 02310.200 Payroll Data Provider (PDP) Wages Received through the Payroll Information Exchange (PIE) - EE Diary\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500820148\n\t\nSI 00820.148 - Automated Wage and Employment Information from Payroll Data Providers (PDP) Received through the Payroll Information Exchange (PIE) - 03/25/2025\nBatch run: 03/19/2026\nRev:03/25/2025\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "sha256": "5bae78f69af7672dd235f696591064cf92597242f268af7f3bd45d6e37f14977"
          },
          {
            "id": "SI00820.147:whole",
            "source_code": "SI00820.147",
            "locator": "Whole captured rendered #content main including full tables, notes and linked-reference labels",
            "start": 0,
            "end": 18735,
            "exact_text": "Effective Dates: 11/20/2023 - Present\nPrevious | Next\n\nTN 91 (05-24)\n\nSI 00820.147 Evidence of Wages from Wage Verification Companies\nA. \nIntroduction of wage verification companies\n\nEmployment and wage verification companies generally maintain an up-to-date database of wage information for employers who subscribe to the service. They provide an efficient means for SSA to verify wages. Obtaining information from wage verification companies may reduce time-consuming contacts with participating employers when pay stubs are not readily available. Procedures vary for requesting wage information from wage verification companies. The amount of information provided may vary as well. Technicians must be alert to situations that may require them to seek other evidence of wages (i.e., cafeteria plans or tips not included on the report; or there are discrepancies in the report).\n\nB. \nTypes of service from wage verification companies\n\nWage verification companies may provide different types of service. Some provide SSA with immediate online access; others may fax information to SSA within a few days. Requirements for accessing wage verifications differ among the various companies. Some wage verification companies may ask SSA to register with the company or have specific requirements for a wage earner’s signed authorization to release the information.\n\nC. \nPolicy for wage verification companies\n1. \nProbative value of evidence\na. \nSSA-approved wage verification company\n\nConsider wage information from an SSA-approved wage verification company as primary evidence of wages when pay stubs are unavailable, unless the evidence contains missing or discrepant information.\n\nIf you discover a discrepancy in the wage data, resolve the discrepancy by obtaining additional primary or secondary evidence.\n\nSee Also:\n\nSI 00820.130 Evidence of Wages or Termination of Wages.\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\n\nb. \nList of SSA-approved wage verification companies\n\nSSA’s Central Office (CO) must approve wage verification companies before their wage evidence may count as primary evidence of wages under certain conditions.\n\nNOTE: Regional and field offices must not refer new potential wage verification companies to CO for evaluation, as CO is no longer evaluating and approving new wage verification companies.\n\nSSA has approved the following companies as providing primary evidence of wages when pay slips are unavailable:\n\n•\n\nthe Work Number (TWN) Express Verification, and\n\n•\n\nVerifyAdvantage.\n\nc. \nNon-SSA approved wage verification company\n\nWe do not consider wage information that we receive from a non-SSA-approved wage verification company as primary evidence of wages. If all of the following requirements are met, accept the non-SSA-approved wage verification as secondary evidence of wages:\n\n•\n\nNo primary evidence of wages exists (e.g., pay stubs, wage verification from an SSA-approved wage verification company) per SI 00820.130A.1.\n\n•\n\nThe wage earner’s employer does not participate with an SSA-approved wage verification company.\n\n•\n\nNo secondary evidence per the first three bullets in SI 00820.130A.2 exists to sufficiently document the wages (i.e., photocopies of pay stubs, IBIQ/NDNH/SASRO queries, or MEF/W-2s/tax forms).\n\n•\n\nThe employer refers you or the worker to a non-SSA-approved wage verification company; and\n\n•\n\nThe non-SSA-approved wage verification company provides wage information to the worker.\n\nImportant: SSA technicians must not access non-SSA approved wage verification websites. Only accept evidence from these sources when the worker furnishes the information.\n\nD. \nProcedure for obtaining information from wage verification companies\n1. \nObtaining wage and employment information authorization\n\nSSA must obtain the wage earner's authorization prior to using wage verification companies to verify wages. Authorization must be obtained via the Wage and Employment Information Authorization (WEIA) application or via paper form SSA-8240. If wage and employment authorization was obtained using the paper SSA-8240, follow instructions in GN 00204.150C.3 to record the response and properly document the file. To check whether a person has provided authorization, access the WEIA application.\n\nFor more information on the Wage and Employment Information Authorization application, see:\n\n•\n\nGN 00204.150 - Authorization to Obtain Wage and Employment Information from Payroll Data Providers via an Information Exchange for the Social Security Disability Insurance (SSDI) and Supplemental Security Income (SSI) Programs\n\n•\n\nMS 09401.001 Wage Authorization - Overview\n\nIMPORTANT: SSI recipients and deemors are not required to provide this authorization. Do not request information from wage verification companies for individuals who refuse to provide or who have revoked wage and employment information authorization.\n\n2. \nContacting the wage verification company\n\nWhen pay stubs are not readily available, always check with the SSA-approved wage verification company(ies) to determine if the employer subscribes to the wage verification service. To do so, first ensure we have obtained proper authorization from the wage earner by checking the WEIA application. Then, run a search using the worker’s information. Document the evidence according to SI 00820.147D.4. in this section.\n\nFor instructions on running searches using SSA-approved wage verifications companies see:\n\n•\n\nSI 00820.147E for The Work Number (TWN), and\n\n•\n\nSI 00820.147F for VerifyAdvantage.\n\n3. \nCafeteria benefit plans and income from tips\n\nWage verification companies do not always provide SSA with cafeteria plan information and income from tips.\n\nIf evidence on the record (e.g., the Wages page, prior pay stubs, etc.) or evidence from the wage verification company indicates that a cafeteria plan may exist, and the wage evidence does not provide exact amounts, follow the procedures to develop cafeteria benefit plan amounts in SI 00820.102.\n\nIf evidence on record or evidence from the wage verification company indicates unreported tips, obtain additional primary or secondary evidence. See the information on evidence of wages or termination of wages in SI 00820.130.\n\n4. \nDocumenting evidence from wage verification companies\n\nDocument evidence from a wage verification company as follows:\n\n•\n\nRecord the verified wages on the SSI Claims system (i.e., MSSICS) Wages page or input to the Supplemental Security Record (SSR).\n\n•\n\nStore the verified wage information in the certified electronic folder (CEF) or the Non-Disability Repository for Evidentiary Documents (NDRED) if a CEF is not available in eView. Use the Evidence Portal when faxing information into NDRED. Alternatively, you may document the verified wage information on a Report of Contact or Evidence (EVID) screen and lock it. For information to include on the Report of Contact or EVID, see SI 00820.130C.1.b.\n\n•\n\nIf wage and employment authorization was obtained using the paper SSA-8240, follow instructions in GN 00204.150C.3 to record the response and properly document the file.\n\nIf a discrepancy exists between the information provided by the wage verification company and other wage evidence obtained, you must:\n\n•\n\nResolve the discrepancy by obtaining other wage evidence per SI 00820.135B.\n\n•\n\nSummarize the wage determination on a Report of Contact or EVID screen and lock it. For cases outside the SSI Claims system (i.e., non-MSSICS), complete an SSA-5002 (Report of Contact).\n\n•\n\nStore wage evidence and any accompanying wage determination information in the CEF or NDRED via EP.\n\nE. \nProcedure for the Work Number (TWN) Express Verification\n\nUse the following procedures for obtaining wage verification from TWN.\n\n1. \nHow to establish Administrators (web managers) of TWN\n\nSome FO staff, typically management, may obtain administrative access to TWN, enabling them to add and manage TWN user profiles locally. To request administrative access, District Managers, Assistant District Managers, Operations Supervisors, and individuals who supervise technicians using TWN must contact their Regional Coordinator (RC) through established regional procedures or via the vHelp portal. We call individuals who obtain administrative access “administrators” or “web managers.”\n\nAdministrators without previous access will receive two emails from TWN.\n\n•\n\nThe first email provides the administrator with TWN access rights.\n\n•\n\nThe second email contains a temporary password.\n\nNew administrators must log into TWN using the temporary password and set a new password.\n\n2. \nTWN administrator (web manager) roles\n\nAdministrators may view the TWN step-by-step tutorial, , for instructions on:\n\n•\n\nadding new users;\n\n•\n\nfinding and managing users;\n\n•\n\naccessing a list of all users in a particular location;\n\n•\n\nresetting a user’s pin (password);\n\n•\n\ndeactivating accounts for users who retire, leave the agency, or change to a job that does not have a job-related need for access to TWN; and\n\n•\n\nreactivating inactive users.\n\nSSA employees may have only one TWN account. Do not list users under multiple locations. Administrators should review and update their office listing periodically and contact their RC through established regional procedures or via the vHelp portal if:\n\n•\n\na user moves to a different location or field office (FO) within or outside the Region;              \n\n•\n\nadministrator rights must be established, transferred, or removed; or\n\n•\n\nan administrator is unable to resolve a TWN issue.\n\nTo submit TWN questions in vHelp, select from the drop down boxes:     \n\n•\n\nPrimary Topic: SSI       \n\n•\n\nSub-Topic: The Work Number.\n\n3. \nEstablishing new users in TWN\n\nAdministrators may add new users in TWN by following the instructions in the step-by-step tutorial Web Manager for Social Service Agencies.\n\nWhen creating user accounts, administrators must use the employee’s SSA.gov email address for both the email address and username fields. TWN changed the way usernames are established in its network and no longer accepts the “at sign” (@) as a character in the username field. Administrators must format the username so that the “@ ” symbol in the SSA email address is replaced with a hyphen symbol (-).\n\nFor example:\n\n•\n\nUsername: John.Doe-ssa.gov\n\n•\n\nEmail: John.Doe@ssa.gov\n\nNOTE: This policy change does not affect active usernames in the system that contain an @ symbol.\n\n4. \nHandling name changes in TWN\n\nAn SSA employee must always login using the original username established upon registering for TWN, regardless of subsequent name changes. Administrators must not create new accounts for employees who legally change their name.\n\nIn the event of a name change, TWN administrators may:\n\n•\n\nupdate the user’s email address in the user’s profile to ensure they receive the proper notifications; and\n\n•\n\nchange the user’s display name in the user profile.\n\n5. \nTWN user access\na. \nOne-time enhanced security enrollment\n\nAfter the administrator adds a user to TWN, the user receives an email containing a temporary password. Users must wait 10-15 minutes after receipt of the email before attempting to log in with the temporary password.\n\nBefore using TWN service, all new users must complete a one-time security enrollment the first time logging into the system. The Enhanced Security Enrollment process verifies a user’s identity.\n\nTo enroll successfully, users must:\n\n•\n\nEnter user name;\n\n•\n\nEnter temporary password received by email;\n\n•\n\nAnswer “yes” to “remember me on this computer” and save;\n\n•\n\nComplete additional information pages, which ask users to update SSA phone and email information, and establish six security questions. Do not add personal phone and email information; and\n\n•\n\nCreate a new password noting the password requirements that appear on the screen. Users must remember this password for subsequent access to TWN.\n\nA successful log in takes you to the Equifax “New Order” home page. For more information on enrolling and requesting verifications, see the TWN tutorial.\n\nNOTE: The username and temporary password are case sensitive and you must enter them exactly as provided in the initial emails from TWN. For best results, copy and paste the username and temporary password into the website during the first log in, taking care not to copy a trailing space at the end. We recommend users select the “Remember my Username” option by checking the associated box on Login screen.\n\nb. \nHow to regain access to TWN\n\nIf a current user hasn’t logged in for over 15 days or  chooses “Forgot User ID or Password”, the user will be prompted to authenticate their identity and account via the use of a One Time Passcode (OTP) process. As part of OTP, a user will receive a code via email that is required to create a new password. User will be able to login in TWN successfully after taking this action.\n\nc. \nQuestions about TWN\n\nUsers must direct all questions and web-related issues to their local TWN administrator. This is usually the manager or supervisor in the user’s office.\n\nIf administrators are unable to resolve the issues, they must contact their RC through established regional procedures or via the vHelp portal.\n\n6. \nHow to request wage verifications from TWN\n\nPrior to requesting wage information using TWN, ensure that the individual has provided wage and employment authorization following SI 00820.147D.1 in this section.\n\nIMPORTANT: We do not condition SSI payments on providing this authorization. Do not request information from TWN for individuals who refuse to provide or who have revoked wage and employment information authorization.\n\nTWN Express Service verification provides employment and income verification with instant delivery on the user’s computer screen. To request information from TWN:\n\n1. \n\nLog in to the TWN Web Site.\n\n2. \n\nOn the New Order screen, enter the wage earner’s Social Security Number (SSN). Do not enter your SSN or any SSA employee’s SSN.\n\n3. \n\nSelect the permissible purpose, “Employee’s eligibility for a benefit granted by governmental agency; - we are required by law to consider the employee’s financial responsibility or status.”\n\n4. \n\nSelect Verification Type(s), “Social Services Verification.”\n\n5. \n\nSelect Start Order\n\n6. \n\nSelect the employer(s) you want to view; proceed to the verification screen.\n\n7. \n\nYou may click on the PDF icon to open the response in PDF format, then print or save the verification report. Document the evidence per SI 00820.147D.4. in this section.\n\nREMINDER: If an employer participates with TWN or any other SSA-approved wage verification company, do not send the employer form SSA-L4201-BK (Letter to Employer Requesting Wage Information). Verify the wage information using the procedures in SI 00820.130.\n\nF. \nProcedure for VerifyAdvantage\n\nTo obtain a wage verification from VerifyAdvantage, use the following procedures.\n\nPrior to requesting wage information using VerifyAdvantage, ensure that the individual has provided wage and employment authorization following SI 00820.147D.1 in this section.\n\nIMPORTANT: We do not condition SSI payments on providing this authorization. Do not request information from VerifyAdvantage for individuals who refuse to provide or have revoked wage and employment information authorization.\n\n1. \nEstablish an account with VerifyAdvantage.\n\nTo use VerifyAdvantage, you must set up an account. Take the following steps:\n\n1. \n\nFrom your Internet browser, go to www.verifyadvantage.com.\n\n2. \n\nSelect the “Create an Account” link under the “Government Requestor” section.\n\n3. \n\nOn the “Requestor Account Setup” page, complete the required fields and click “Save.” A screen displays a new user account has been set up for you under the company name of Social Security Administration.\n\nNOTE: Enter your government email address and fax number with area code.\n\n4. \n\nYou will receive an email containing instructions to complete the setup process; complete as instructed.\n\n5. \n\nIf you have not received an email from VerifyAdvantage containing instructions to complete account setup within 24 hours, contact VerifyAdvantage at (866) 894-7687.\n\nIMPORTANT: When you create a VerifyAdvantage account:\n\n•\n\nThe username must be between 3 and 16 characters, begin with a letter and contain only letters, numbers and a hyphen (-).\n\n•\n\nThe username created is used as your login to VerifyAdvantage.\n\n•\n\nThe password must be minimum of 8 characters in length and contain at least one lower case letter, one digit, and one special character (e.g. an asterisk).\n\n•\n\nTo use VerifyAdvantage on your government computer, you must register individually.\n\n•\n\nDo not use your LAN/Mainframe PIN or password when creating an account.\n\n2. \nObtaining wage verification\n\nTake the following steps to request wage information from VerifyAdvantage:\n\n•\n\nLog onto the VerifyAdvantage website .\n\n•\n\nSelect “Log in” in the Government Requestor section.\n\n•\n\nType username and password and click “Log in.”\n\n•\n\nSelect “Request Report.”\n\n•\n\nFind the “Select Employer” box. From the list of employers, “select” the appropriate employer.\n\n•\n\nEnter the wage earner’s SSN (only enter the nine digits, do not include the dashes), then select “Next.”\n\n•\n\nSelect “Next” upon confirmation that the wage earner was located.\n\n•\n\nAgree to the “Terms and Conditions” and select “I Agree” and “I Accept.”\n\n•\n\nPrint the report.\n\n3. \nObtaining help using VerifyAdvantage\n\nTo get assistance using VerifyAdvantage, contact VerifyAdvantage in one of the following ways:\n\n•\n\ngo to http://www.verifyadvantage.com and click “help,” or\n\n•\n\nemail evsupport@fadv.com, or\n\n•\n\ncall (866) 894-7687.\n\nG. \nReferences\n•\n\nSI 00820.102 Cafeteria Benefit Plans\n\n•\n\nSI 00820.130 Evidence of Wages or Termination of Wages\n\n•\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\n\n•\n\nSI 00820.143 Monthly Wage Reporting\n\n•\n\nSI 00820.145 Form SSA-L4201-BK (Letter to Employer Requesting Wage Information)\n\n•\n\nGN 00204.150 Authorization to Obtain Wage and Employment Information from Payroll Data Providers via an Information Exchange for the Social Security Disability Insurance (SSDI) and Supplemental Security Income (SSI) Programs\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nSI 00601.100 Information/Evidence - General\n\n•\n\nDI 10505.005 Determining and Verifying Gross Earnings from Employment\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500820147\n\t\nSI 00820.147 - Evidence of Wages from Wage Verification Companies - 11/20/2023\nBatch run: 04/27/2026\nRev:11/20/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "sha256": "cb85962f69b7a64e9648855f6a89b5ca0e16da5b7308e5fbe61cd3562803fc62"
          },
          {
            "id": "SI00820.135:whole",
            "source_code": "SI00820.135",
            "locator": "Whole captured rendered #content main including full tables, notes and linked-reference labels",
            "start": 0,
            "end": 17832,
            "exact_text": "Effective Dates: 11/20/2023 - Present\nPrevious | Next\n\nTN 99 (03-25)\n\nSI 00820.135 Wage Verification and Reported Wages Over $65 per Month\nA. \nProcedure for developing “reported” wages\n\nTo determine whether verification is necessary for “reported” wages (i.e., those indicated on the Supplemental Security Record (SSR) by a verification code of “0”) over $65 per month for a recipient or a deemor use this chart.\n\nStep\n\n\t\n\nAction\n\n\n\n\n1\n\n\t\n\nDoes the diary data (DIAR) segment of the SSR contain an S2, K6, K7, S7, J3, or J5?\n\nIf yes, go to Step 2.\n\nIf no, go to Step 3.\n\n\n\n\n2\n\n\t\n\nDevelop the wage interface diary according to relevant instructions.\n\nDevelop all wages during the period being developed according to wage development and verification procedures in SI 00820.130C.\n\nRefer to a step-by-step chart SI 00820.135B in this section.\n\n•\n\nSI 02310.055 Master Earnings File (MEF) Match (K6 and K7 Diary)\n\n•\n\nSI 02310.056 Master Earnings File (MEF) Match (J3 and J5 Diaries)\n\n•\n\nSI 02310.062 State Wage Record Match (S2 Diary)\n\n•\n\nSI 02310.063 State Wage Record Match (S7 Diary)\n\nProceed to Step 8 to develop IRWE or BWE when applicable.\n\nSTOP.\n\n\n\n\n3\n\n\t\n\nDoes the earned income (ENIH) segment of the SSR contain wages with a verification code of “0”?\n\nIf yes, go to Step 4.\n\nIf no, and wage verification is required per SI 00820.125, “When Wage Verification Is and Is not Required,” refer to the next chart in this section.\n\nREMINDER: It is mandatory to attempt to recruit and train all recipients, deemors, and representative payees to report wages through electronic wage reporting systems (i.e., myWageReport, Supplemental Security Income Telephone Wage Reporting system (SSITWR), and the SSA Mobile Wage Reporting application (SSAMWR)), unless we are getting their wage and employment information through PIE, or an exception or exclusion applies. For more information about recruiting wage reporters and monthly wage reporting, see SI 00820.143 and SI 00820.144.\n\n\n\n\n4\n\n\t\n\nAre there more than two consecutive months with an alleged wage amount (verification code of “1”) at any time during the period you are developing?\n\nIf yes, go to Step 6.\n\nIf no, go to Step 5.\n\n\n\n\n5\n\n\t\n\nIs the total number of months with an “alleged” (1) wage greater than the total number of months with a “reported” (0) wage and/or a “verified” (9) wage during the period you are developing?\n\nIf yes, go to Step 6.\n\nIf no, go to Step 7.\n\n\n\n\n6\n\n\t\n\nDevelop all wages during the period being developed according to the procedures in SI 00820.130C.\n\nRefer to a step-by-step chart SI 00820.135B in this section\n\nSTOP.\n\n\n\n\n7\n\n\t\n\nThe wages for the period being developed do not require verification. Consider the wages verified unless the system later posts a wage interface alert to the SSR.\n\nDoes the worker have impairment-related work expenses (IRWE), blind work expenses (BWE), or any other earned income exclusions that apply during the period that you are developing?\n\nIf yes, go to Step 8.\n\nIf no, then no further action is necessary. STOP.\n\n\n\n\n8\n\n\t\n\nVerify the IRWE or BWE according to the following instructions:\n\n•\n\nSI 00820.540 Impairment-Related Work Expenses (IRWE)\n\n•\n\nSI 00820.535 Blind Work Expenses (BWE)\n\nDevelop any Student Earned Income Exclusions according to SI 00820.510.\n\nB. \nProcedure for verifying wages over $65\n\nUse this chart to determine what steps are necessary to verify wages over $65 per month for a recipient or deemor.\n\nAlso, use this chart for an ineligible child, student, or a member of an eligible couple (if such wages, when combined with wages of the spouse, exceed $65).\n\nIf at any point, a single source of wage evidence does not cover the entire period of review, develop for a combination of evidence types per SI 00820.130A.3.\n\n1. \nChart for verifying wages over $65 per month\n\nStep\n\n\t\n\nAction\n\n\n\n\n1\n\n\t\n\nHave we received complete wage and employment information for the employer(s) from a payroll data provider (PDP) through the payroll information exchange (PIE) for the entire period being verified? For information on the procedure for wage and employment evidence received from a PDP through PIE, see SI 00820.130C.1.\n\nIf yes, proceed to Step 15.\n\nIf no, go to Step 2.\n\n\n\n\n2\n\n\t\n\nDoes the individual have acceptable pay stubs for some or all of the period being verified? For information that must be shown on a pay stub for us to consider it acceptable evidence of wages, see the first bullet in SI 00820.130A.1.\n\nIf yes, go to Step 3.\n\nIf no, go to Step 8.\n\n\n\n\n3\n\n\t\n\nWere any wages deferred or set aside during the period covered by the pay stubs rather than paid on the normal payment date? For more information regarding wage advances and deferred wages, see SI 00820.115.\n\nIf yes, go to Step 4.\n\nIf no, go to Step 5.\n\n\n\n\n4\n\n\t\n\nPost and document deferred wages per SI 00820.115C.2. When posting wages to the SSI Claims system Wages page, complete the employer identification number (EIN) field when EIN information is available (e.g., listed on the wage evidence, available on the Detailed Earnings Query, etc.).\n\nGo to Step 6.\n\n\n\n\n5\n\n\t\n\nUse SSI Monthly Wage Verification (SSIMWV) intranet application to:\n\n•\n\ninput and document a wage report submitted with pay stubs. SSIMWV will automate the wage input to the SSI Claims system Wages page or (for non-SSI Claims system (i.e., non-MSSICS) cases) to the SSR via the 1719(b) (SSI Post-Eligibility Input);\n\n•\n\nprint and issue a work report receipt via SSIMWV and archive it to the Online Retrieval System (ORS) to serve as documentation of wages. For in-person and telephone reports, generate a receipt immediately, and give or mail to the reporter; and\n\n•\n\nestablish the work report for mailed, faxed, or dropped off reports in the FO, and mail the receipt to the reporter within 5 days of receipt of the information.\n\nIf available, complete the employer identification number (EIN) field in SSIMWV and on the Wages page in the SSI Claims system.\n\nNo other action is necessary to document the report.\n\nIMPORTANT: If processing multiple months of pay stubs in SSIMWV, you must issue a separate work report receipt for each month to meet the documentation requirements.\n\nWas SSIMWV used to input all wages and document the wage report(s)?\n\nIf yes, ,go to Step 15\n\nIf no, go to Step 6.\n\n\n\n\n6\n\n\t\n\nDo the pay stubs cover earnings for the entire period that you are verifying? Or, if not, can you determine the wages attributable to the missing pay stub(s) by other evidence (e.g., year-to-date totals)?\n\nIf yes, go to Step 7.\n\nIf no, go to Step 8.\n\n\n\n\n7\n\n\t\n\nFor documenting wages based on pay stubs, follow the procedures in SI 00820.130C.1.\n\nPost the wages when received using the SSI Claims system Wages page or a 1719(b) (SSI Post-Eligibility Input).\n\nAnnotate the remarks of the SSI Claims system Wages page or a Report of Contact with the source of verification.\n\nIssue a receipt to the reporter through the Document Processing System (DPS) via the SSA-L724 (Work Report Receipt). .\n\nGo to Step 15.\n\n\n\n\n8\n\n\t\n\nDoes the employer participate in payroll services with an SSA-approved wage verification company listed in SI 00820.147C.2?\n\nIf yes, follow the procedures to obtain and document wage verification SI 00820.147 and then proceed to step 15.\n\nNOTE: \n\nIf the EIN is available, complete the EIN field on the Wages page in the SSI Claims system.\n\nIf no, go to step 9.\n\n\n\n\n9\n\n\t\n\nDoes the individual have evidence showing annual wage amounts, such as W-2 forms or Federal or State income tax forms? Is there a Master Earnings File (MEF)?\n\nOR\n\nIs quarterly wage information displayed in the National Directory of New Hires (NDNH), Interstate Benefits Inquiry (IBIQ), or SSA Access to State Records Online (SASRO)?\n\nIf yes,\n\nConfirm with the worker the months worked and, for evidence treated as a third-party lead, whether they agree with the wage information on the query. If the worker does not agree with the third-party lead, you must develop other wage evidence. For more information about documenting evidence from secondary sources, see SI 00820.130C.3.\n\nDivide the annual or quarterly amount by the number of alleged months worked, to arrive at a “verified” wage amount to post for each month.\n\nOn an Evidence Screen (EVID), signed statement or Report of Contact, document:\n\n•\n\nthe annual or quarterly wage amounts and the source of the evidence;\n\n•\n\nthe individual’s allegation of the number of months worked: and\n\n•\n\nwhether the worker agrees with the wage information when the evidence is from third-party sources like NDNH; and\n\n•\n\nthe steps taken to request primary evidence and why those efforts were unsuccessful.\n\nLock documentation pages or store signed statements in the Evidence Portal (EP). However, do not save IBIQ/NDNH/SASRO printouts or queries in EP. For the required documentation, see SI 00820.130C.3.b in this section\n\nIMPORTANT: Posting the alleged months worked to the SSI Claims system Wages page alone is insufficient documentation when using quarterly or annual wage amounts. You must also record the allegation, wage amounts, and source on a signed statement, Report of Contact, SSA-795, or SSA-5002 to satisfy documentation requirements. This includes statements regarding whether the worker agrees with any third-party reports. See SI 00820.130C.3 for more information about documenting evidence from secondary sources.\n\nNOTE: \n\nIf the EIN is available, complete the EIN field on the Wages page in the SSI Claims System.\n\nProceed to Step 15.\n\nIf no, go to Step 10.\n\n\n\n\n10\n\n\t\n\nDoes the person have wage information recorded in the Internet Ticket Operations Provider Support System (iTOPSS)? iTOPSS contains pay stub-level wage information for Ticket to Work users. The wage data is provided by employment networks and input by Ticket Program Managers. See more information SI 00820.130C.3.\n\nIf yes:\n\nCompute and record monthly wages on the SSI Claims system Wages page or a 1719(b) (SSI Post-Eligibility Input).\n\nOn a signed statement, or Report of Contact:\n\n•\n\nconfirm that the worker agrees with the wage information provided; and\n\n•\n\ndocument iTOPSS as the evidence source and the steps taken to obtain preferred evidence;\n\nLock documentation pages or store signed statements in EP.\n\nProceed to Step 15.\n\nIf no or if iTOPSS information is incomplete or inconsistent, go to Step 11.\n\n\n\n\n11\n\n\t\n\nPhone the employer to develop and verify wages. Request information regarding when wages were paid, not earned, see SI 00810.030.\n\nIf the employer provides wage information, consider that information to be verified. If no deferred wages are involved:\n\n•\n\npost the wages when received, and\n\n•\n\ndocument the wage information obtained from the employer on a Report of Contact and lock it. Include:\n\n•\n\nthe date of the call;\n\n•\n\nemployer name;\n\n•\n\nthe contact person’s name, title, and telephone number;\n\n•\n\ngross wages paid;\n\n•\n\nthe pay date (if known);\n\n•\n\ntime period covered by the oral statement; and\n\n•\n\nif applicable, any deductions or exclusions from gross wages (e.g., cafeteria plans, certain child support garnishments, etc.)\n\nIn non SSI Claims system (i.e., non-MSSICS) situations, document this information on an SSA-5002 (Report of Contact) and store it in EP.\n\nIf the employer provides wage information and deferred wages are involved:\n\n•\n\npost deferred wages per SI 00820.115B.2,\n\n•\n\npost the remainder of wages when received, and\n\n•\n\ndocument the verified deferred wages on EVID, or on a Report of Contact page and lock it; or, in non-SSI Claims system (i.e., non-MSSICS) situations, document the deferred wages and the employer contact information (i.e., date, contact person’s name, title, and telephone number) on an SSA-5002 and store it in EP.\n\nNOTE: \n\nIf the EIN is available, complete the EIN field on the Wages page in the SSI Claims System.\n\nDo not disclose an individual’s PII on voicemail messages to employers. If the employer will not provide wage evidence and refers you to a non-SSA approved wage verification company for wage information, go to Step 13.\n\nIf the employer provides evidence of wages, but you determine that an oral statement is insufficient, go to Step 12.\n\nIf the employer is uncooperative, or you cannot reach the employer by phone, go to Step 12.\n\n\n\n\n12\n\n\t\n\nSend the employer an SSA-L4201-BK (Letter to Employer Requesting Wage Information).\n\nIf the employer completes the form and no deferred wages are involved:\n\n•\n\npost wages when received,\n\n•\n\nstore the SSA-L4201-BK in EP. Alternatively, document SSA-L4201-BK evidence on EVID or on a Report of Contact and lock it, or in non-SSI Claims system (i.e., non MSSICS) situations, document this information on an SSA-5002 (Report of Contact) and store it in EP.\n\nProceed to Step 15.\n\nIf the employer completes the form and deferred wages are involved:\n\n•\n\npost deferred wages per SI 00820.115C,\n\n•\n\ncharge the remainder of wages when received,\n\n•\n\nstore the SSA-L4201-BK in EP. Alternatively, document the information extracted from the SSA-L4201-BK on EVID, a Report of Contact and lock it. In non-SSI Claims system (i.e., non MSSICS) situations, document this information on an SSA-5002 (Report of Contact) and store it in EP.\n\nProceed to Step 15.\n\nIf the employer will not provide wage evidence and refers you to a non-SSA approved wage verification company for wage information, go to Step 13.\n\nIf the employer is uncooperative, does not provide all the information requested on the SSA-L4201-BK, or cannot be located, go to Step 14.\n\n\n\n\n13\n\n\t\n\nIs the wage evidence available from a non-SSA approved wage verification company?\n\nIf yes, request that the worker obtain the wage evidence from the non-approved company. Accept the wage evidence from the non-SSA approved wage verification company only when provided by the individual.\n\nIMPORTANT: SSA employees must not access or establish online accounts with non-approved wage verification companies or enter any of the wage earner's personally identifiable information into a non-SSA approved website, or otherwise contact or disclose information to the non-approved wage verification company.\n\nProceed to Step 15.\n\nIf no, go to Step 14.\n\n\n\n\n14\n\n\t\n\nObtain the individual's allegation of the amount and frequency of wages.\n\nNOTE: \n\nIf the only evidence is an individual's allegation of annual wages, divide the annual wage amount by the number of months of alleged work to arrive at a “verified” wage amount to post for each of those months.\n\nPost the verified wages as verified in this step. Code the wage amount with “9” verification indicator.\n\nRecord the individual's statement on either a signed Person Statement (SSA-795) or Report of Contact page (SSA-5002). Include the following:\n\n•\n\ngross amount, frequency, and duration of wages; and\n\n•\n\nthe steps taken to obtain acceptable primary and secondary evidence, and why they were unsuccessful.\n\nLock documentation pages or store signed SSA-795 form statements in EP. For instructions on electronic evidence documentation and retention, see GN 00301.286.\n\nProceed to Step 15.\n\n\n\n\n15\n\n\t\n\nDoes the individual have impairment-related work expenses (IRWE), blind work expenses (BWE), or other earned income exclusions that apply during the period that you are developing?\n\nIf yes, go to Step 16.\n\nIf no, STOP.\n\n\n\n\n16\n\n\t\n\nVerify the IRWE or BWE according to the following instructions:\n\n•\n\nSI 00820.540 Impairment-Related Work Expenses (IRWE)\n\n•\n\nSI 00820.535 Blind Work Expenses (BWE)\n\nDevelop any Student Earned Income Exclusions according to SI 00820.510.\n\n2. \nEvidence lacks credibility or discrepancy\n\nIf you question the credibility of pay stubs or an oral or written statement from an employer and the employer does not participate in payroll services with a wage verification company, or if the annual amount of wages reported by an employer differs from the annual amount on a detailed earnings query (DEQY) in file you must:\n\n•\n\nuse other acceptable evidence of wages to resolve the wage amount and any discrepancy by obtaining acceptable evidence of wages per SI 00820.130, and\n\n•\n\ndocument the wage determination on a Report of Contact and lock it; in non-SSI Claims system situations, use an SSA-553 (Special Determination) and store it in EP.\n\nC. \nReferences\n•\n\nSI 00820.115 Wage Advances and Deferred Wages\n\n•\n\nSI 00820.130 Evidence of Wages or Termination of Wages\n\n•\n\nSI 00820.131 Income Summary Worksheets\n\n•\n\nSI 00820.140 Wage Verification - $65 or Less\n\n•\n\nSI 00820.141 Alternative Wage Verification – Periodic Reports With Evidence\n\n•\n\nSI 00820.142 Alternative Wage Verification – Sheltered Workshop Pays $65 or Less Per Month to All\n\n•\n\nSI 00820.143 Monthly Wage Reporting\n\n•\n\nSI 00820.144 Monthly Wage Reporting — Recruiting Reporters \n\n•\n\nSI 00820.147 Evidence of Wages – Wage Verification Companies\n\n•\n\nSI 00820.148 Automated Wage Verifications from Payroll Data Providers Received Via Information Exchange\n\n•\n\nSI 02302.060 Quarterly Verification of Earnings\n\n•\n\nGN 00301.286 Electronic Evidence Documentation and Retention\n\n•\n\nGN 00301.287 How Evidence is Recorded on EVID and Report of Contact page in the Consolidated Claims Experience (CCE) in PE Situations\n\n•\n\nGN 00301.288 What Information is Needed on EVID and the Report of Contact page in the Consolidated Claims Experience (CCE) in PE Situations to Identify the Type of Evidence Submitted\n\n•\n\nMS 05209.001 Interstate Benefit Inquiry (IBIQ)\n\n•\n\nMS 05203.015 National Directory New Hire, Wage, Unemployment Menu (NDNH)\n\n•\n\nMS 01701.003 Evidence Screen (EVID)\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500820135\n\t\nSI 00820.135 - Wage Verification and Reported Wages Over $65 per Month - 11/20/2023\nBatch run: 10/15/2026\nRev:11/20/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "sha256": "8e1f21256f41cc91db051a6d1b7d173895a67e82735d3893ed535a1905c7a2ce"
          }
        ],
        "holds": [
          {
            "id": "provider-primary-and-secondary-not-equivalent",
            "scope": "Company-approved status, unavailable paystubs, authorization, discrepancies and nonapproved-company five-part gate are separate. No provider API, credentials, access or native system identity is inferred."
          },
          {
            "id": "PDP-amount-versus-disclaimed-earnings",
            "scope": "148 D.2 requests paystubs for an amount dispute with accurate employer; D.3 explicitly does not request the wages the worker disclaims. D.3 statement/ROC, investigation, primary-evidence-refutation exception and separate appeal remain unchanged. No disclaimed-earnings core rewrite in these seven flows."
          },
          {
            "id": "authorization-system-state-versus-legal-effect",
            "scope": "Timely cross-month reconsideration system limitation does not equal a fresh consent requirement; late appeal and other appeal stages have their separately stated rules. No appeal/date calculator or actual timeliness finding."
          },
          {
            "id": "linked-technical-procedures-not-supplied",
            "scope": "WEIA and WEI MS screens, EE diary SI02310.200, GN00204.150 authorization details, cafeteria SI00820.102, deferred SI00820.115, earnings correction RM targets and appeal/GK procedures are linked, not whole-target-approved here."
          },
          {
            "id": "publisher-cross-reference-mispointers",
            "scope": "135 B.1 step8 points to147 C.2 but the captured147 approved-company list is in C.1.b; 135 secondary-documentation references130 C.3 while current130 secondary procedures use C.4. Preserve observed source links/labels and actual paragraph predicates rather than silently fixing publisher locators. 147 D.4 also references130 C.1.b for RC/EVID details; no expanded documentary content inferred from that locator."
          },
          {
            "id": "exact-screen-identity",
            "scope": "Current135 names iTOPSS but not QERN or an EDCS Consolidated Wage Page. Historical native QERN context is not certification that the current page names that exact screen. No new Atlas links."
          }
        ],
        "negative_QA": [
          {
            "id": "P01",
            "case": "Authorization receipt but no reduced-reporting notice",
            "required_boundary": "Do not infer employer reporting relief."
          },
          {
            "id": "P02",
            "case": "One employer reduced reporting",
            "required_boundary": "Other employers and PIE-missing information remain reportable."
          },
          {
            "id": "P03",
            "case": "Feed absent for one or two months",
            "required_boundary": "Do not infer the three-consecutive-month increased-notice trigger."
          },
          {
            "id": "P04",
            "case": "Worker disclaims employment/earnings or alleges identity theft",
            "required_boundary": "Do not use amount-dispute paystub request; retain separate D.3 scope."
          },
          {
            "id": "P05",
            "case": "Other evidence confirms provider wage evidence",
            "required_boundary": "Do not automatically replace the provider evidence."
          },
          {
            "id": "P06",
            "case": "System-inactive original authorization during timely cross-month reconsideration",
            "required_boundary": "No new consent request solely for the stated limitation."
          },
          {
            "id": "P07",
            "case": "Late appeal after source period",
            "required_boundary": "Do not apply timely cross-month no-new-consent handling."
          },
          {
            "id": "P08",
            "case": "Existing Wages page with no matching EIN",
            "required_boundary": "Do not apply new-employment no-Wages-page automation or assume successful posting."
          },
          {
            "id": "P09",
            "case": "Force Due/manual deeming pending wages",
            "required_boundary": "Do not issue a manual reduced-reporting notice or assume automated update."
          },
          {
            "id": "P10",
            "case": "Authorization refused or revoked",
            "required_boundary": "No company information request, even when paystubs are unavailable."
          },
          {
            "id": "P11",
            "case": "Nonapproved provider website exists",
            "required_boundary": "Staff must not create/access accounts or enter/disclose worker information."
          },
          {
            "id": "P12",
            "case": "Cafeteria possibility but exact amounts present",
            "required_boundary": "Do not assume missing-amount cafeteria development predicate."
          },
          {
            "id": "P13",
            "case": "Both tips and cafeteria information missing",
            "required_boundary": "Both conditional component instructions can apply; no exclusive fork."
          },
          {
            "id": "P14",
            "case": "CEF available",
            "required_boundary": "Do not universalize NDRED as the ordinary verified-information destination."
          },
          {
            "id": "P15",
            "case": "iTOPSS reached without earlier chart development",
            "required_boundary": "Do not silently bypass source priorities or applicable >$65 subject scope."
          },
          {
            "id": "P16",
            "case": "Employer supplied complete adequate oral information",
            "required_boundary": "No automatic written-request fallback."
          },
          {
            "id": "P17",
            "case": "Employer voicemail",
            "required_boundary": "Do not leave individual personal information."
          },
          {
            "id": "P18",
            "case": "Corrected SSI entry",
            "required_boundary": "Do not infer permanent MEF correction."
          },
          {
            "id": "P19",
            "case": "Native QERN record exists",
            "required_boundary": "Do not infer exact current screen identity from source iTOPSS name."
          },
          {
            "id": "P20",
            "case": "User chooses a flow or action card",
            "required_boundary": "No established case fact, successful continuation, eligibility or native acceptance."
          }
        ]
      },
      "followup8": {
        "flows": {
          "interoffice-assistance-followup/followup-c-1": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-c-1",
            "full_route": "interoffice-assistance-followup/followup-c-1",
            "entry_conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Routine requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "steps": [
              {
                "id": "followup-c-1-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CA/CTE, BA/BTE as requester and CR/SR as recipient for this follow-up: 60 calendar days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CA/CTE, BA/BTE to CR/SR; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.1 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-1-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CA/CTE as requester and CR/SR as recipient for this follow-up: 30 calendar days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CA/CTE to CR/SR; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.1 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-1-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists AMM, MM as requester and DM, ADM as recipient for this follow-up: 30 calendar days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s AMM, MM to DM, ADM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.1 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-1-source-row-4",
                "title": "Fourth follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists OM as requester and DM as recipient for this follow-up: 30 calendar days after 3rd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s fourth follow-up; its anchor is the actual 3rd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s OM to DM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.1 Fourth row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-c-2": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-c-2",
            "full_route": "interoffice-assistance-followup/followup-c-2",
            "entry_conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the High priority requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "steps": [
              {
                "id": "followup-c-2-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CA/CTE as requester and CR/SR as recipient for this follow-up: 20 calendar days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CA/CTE to CR/SR; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.2 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-2-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists AMM as requester and OS as recipient for this follow-up: 10 calendar days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s AMM to OS; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.2 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-2-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists MM as requester and DM, ADM as recipient for this follow-up: 15 calendar days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s MM to DM, ADM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.2 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-2-source-row-4",
                "title": "Fourth follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists OM as requester and DM, AD as recipient for this follow-up: 15 calendar days after 3rd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s fourth follow-up; its anchor is the actual 3rd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s OM to DM, AD; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.2 Fourth row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-c-3": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-c-3",
            "full_route": "interoffice-assistance-followup/followup-c-3",
            "entry_conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
              "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility."
            ],
            "steps": [
              {
                "id": "followup-c-3-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists AMM, MM, US as requester and DM, ADM as recipient for this follow-up: 5 business days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s AMM, MM, US to DM, ADM; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.3 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-3-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists AMM, MM, US as requester and DM, ADM as recipient for this follow-up: 3 business days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s AMM, MM, US to DM, ADM; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.3 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-c-3-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists OM, SM as requester and AD, DAD as recipient for this follow-up: 2 business days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is PC/TSC to FO.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s OM, SM to AD, DAD; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 C.3 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-C.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-1": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-d-1",
            "full_route": "interoffice-assistance-followup/followup-d-1",
            "entry_conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Routine requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "steps": [
              {
                "id": "followup-d-1-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CR/SR as requester and CA/CTE, BA/BTE as recipient for this follow-up: 60 calendar days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CR/SR to CA/CTE, BA/BTE; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.1 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-1-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CR/SR as requester and CA/CTE as recipient for this follow-up: 30 calendar days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CR/SR to CA/CTE; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.1 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-1-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM, ADM as requester and AMM, MM as recipient for this follow-up: 30 calendar days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM, ADM to AMM, MM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.1 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-1-source-row-4",
                "title": "Fourth follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM as requester and OM as recipient for this follow-up: 30 calendar days after 3rd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Routine requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s fourth follow-up; its anchor is the actual 3rd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM to OM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.1 Fourth row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.1"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-2": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-d-2",
            "full_route": "interoffice-assistance-followup/followup-d-2",
            "entry_conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the High priority requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "steps": [
              {
                "id": "followup-d-2-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists CR, SR as requester and CA/CTE as recipient for this follow-up: 20 calendar days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s CR, SR to CA/CTE; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.2 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-2-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists OS as requester and AMM as recipient for this follow-up: 10 calendar days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s OS to AMM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.2 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-2-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM, ADM as requester and MM as recipient for this follow-up: 15 calendar days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM, ADM to MM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.2 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-2-source-row-4",
                "title": "Fourth follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM, AD as requester and OM as recipient for this follow-up: 15 calendar days after 3rd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the High priority requests table and applicable staff-role context.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "The applicable stage is the source’s fourth follow-up; its anchor is the actual 3rd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM, AD to OM; their actual role context must be established."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.2 Fourth row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.2"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-3": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-d-3",
            "full_route": "interoffice-assistance-followup/followup-d-3",
            "entry_conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
              "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility."
            ],
            "steps": [
              {
                "id": "followup-d-3-check-active-work-control",
                "title": "Check the source’s work-control indicator",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Query PCACS or Evidence Portal for an active REQ/EMFO TOEL that shows the processing center is working on the request. These are alternative query sources. This instruction neither creates a PCACS assistance request nor proves completion, and it does not specify stopping or resetting a follow-up clock.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.3 NOTE",
                "source_context_refs": [
                  "GN01070.440-D.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate.",
                  "The source gives no endpoint, permissions or detailed query fields. GN01070.228 limits the PCACS request method to PSCs; this separate query instruction does not turn that method into a default FO request-creation route."
                ]
              },
              {
                "id": "followup-d-3-source-row-1",
                "title": "First follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM, ADM, US as requester and AMM, MM as recipient for this follow-up: 5 business days after initial request. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s first follow-up; its anchor is the actual initial request, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM, ADM, US to AMM, MM; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.3 First row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-3-source-row-2",
                "title": "Second follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists DM, ADM, US as requester and AMM,MM as recipient for this follow-up: 3 business days after 1st F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s second follow-up; its anchor is the actual 1st F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s DM, ADM, US to AMM,MM; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.3 Second row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-d-3-source-row-3",
                "title": "Third follow-up",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source lists AD, DAD, SM as requester and OM as recipient for this follow-up: 2 business days after 2nd F/U. Keep this direction and staff-role pairing. This is a follow-up reference, not a time promised for completing the case.",
                "conditions": [
                  "Established assistance direction is FO/TSC to PC.",
                  "The request is within the Manager to Manager table and applicable staff-role context.",
                  "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
                  "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
                  "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility.",
                  "The applicable stage is the source’s third follow-up; its anchor is the actual 2nd F/U, not a benefit application or a presumed prior card action.",
                  "The applicable requester and recipient roles are the source row’s AD, DAD, SM to OM; their actual role context must be established.",
                  "There has been no communication after the first request, as required by this Manager-to-Manager note."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.3 Third row; A",
                "source_context_refs": [
                  "GN01070.440-A",
                  "GN01070.440-B",
                  "GN01070.440-D.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d3-active-req-emfo-query": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-d3-active-req-emfo-query",
            "full_route": "interoffice-assistance-followup/followup-d3-active-req-emfo-query",
            "entry_conditions": [
              "FO/TSC-to-PC Manager-to-Manager D.3 context applies.",
              "The source no-communication condition and applicable row/staff prerequisites are established.",
              "The actual Manager-to-Manager method/priority and staff-authority prerequisites are established; this example grants no access or permissions."
            ],
            "steps": [
              {
                "id": "followup-d3-active-req-emfo-query-source-query",
                "title": "Query the active work-control indicator",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Query PCACS or Evidence Portal for an active REQ/EMFO TOEL showing the processing center is working on the request. The source uses OR, not a requirement to query both. An active indicator does not establish a completed action, nor does the paragraph prescribe suppressing, restarting or resetting the follow-up schedule.",
                "conditions": [
                  "FO/TSC-to-PC Manager-to-Manager D.3 context applies.",
                  "The source no-communication condition and applicable row/staff prerequisites are established.",
                  "The actual Manager-to-Manager method/priority and staff-authority prerequisites are established; this example grants no access or permissions."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 D.3 NOTE",
                "source_context_refs": [
                  "GN01070.440-D.3"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate.",
                  "Keep the status query distinct from PSC-only PCACS request creation in GN01070.228. DATA_TOEL is generic existing metadata; no new code, screen identity or native relationship is inferred."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-delay-two-way-communication": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "followup-delay-two-way-communication",
            "full_route": "interoffice-assistance-followup/followup-delay-two-way-communication",
            "entry_conditions": [
              "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe."
            ],
            "steps": [
              {
                "id": "followup-delay-two-way-communication-advise-delay",
                "title": "Advise the requester about a delay",
                "kind": "ssa",
                "actor": "Receiving FO or PC",
                "action": "When a delay is anticipated, advise the requester so alternative development sources can be discussed if necessary. This does not establish that another source is available or that any development is complete.",
                "conditions": [
                  "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe.",
                  "The receiving field office or processing center anticipates a delay."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 A",
                "source_context_refs": [
                  "GN01070.440-A"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-delay-two-way-communication-discuss-dates",
                "title": "Discuss the follow-up date",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Discuss follow-up dates with the field office or processing center to avoid misunderstanding. If the actual follow-up date falls on a weekend or other non-workday, use the next workday. A particular holiday calendar or automatically calculated due date is not supplied.",
                "conditions": [
                  "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe.",
                  "An actual follow-up date is being discussed for this request."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 A",
                "source_context_refs": [
                  "GN01070.440-A"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              },
              {
                "id": "followup-delay-two-way-communication-notify-timeframe",
                "title": "Notify the other office if the request cannot be answered",
                "kind": "ssa",
                "actor": "Receiving FO or PC",
                "action": "If the request cannot be answered within the prescribed follow-up timeframe, notify the field office or processing center by telephone or email. These are alternative delay-notification channels; they are not a new customer filing route or a prescribed initial assistance-submission method.",
                "conditions": [
                  "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe.",
                  "The request cannot be answered within the prescribed follow-up timeframe."
                ],
                "source": "assist_GN01070_440",
                "section": "GN01070.440 A",
                "source_context_refs": [
                  "GN01070.440-A"
                ],
                "qualifications": [
                  "This is a prescribed staff follow-up reference, not measured processing time, a customer deadline, a payment guarantee or a universal service-level agreement.",
                  "An interval starts from the source’s stated initial request or actual preceding follow-up. Reading an earlier card does not perform that follow-up or establish the next stage.",
                  "Discuss follow-up dates with the other office. If an actual follow-up date is a weekend or other non-workday, use the next workday. No holiday calendar, day-zero convention, cumulative escalation date or automatic date calculator is supplied.",
                  "Literal requester/recipient role codes are retained. The glossary’s AD versus the tables’ ADM wording is not silently reconciled or expanded into an unsupported role identity.",
                  "No actual request, authority, communication, query result, response, office transfer or successful continuation is established. Generic MDW is not identified with APP_MDW_AI; current native status and older holds remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          }
        },
        "original_records": {
          "interoffice-assistance-followup/followup-c-1": {
            "id": "followup-c-1",
            "title": "PC/TSC to FO — Routine requests",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
            "source": "assist_GN01070_440",
            "section": "A; C.1",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-C.1",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 1245,
                "end": 1578,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "6fd1280bc1765cf7847c86f87fe605699f79a82f8d414b54c84d2693af1108cf",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "C.1",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "Intercomponent Assistance Request Process"
            ],
            "entity_ids": [
              "PROC_INTERCOMP_ASSIST"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed Routine requests follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Routine requests table and applicable staff-role context."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is PC/TSC to FO.; The request is within the Routine requests table and applicable staff-role context.",
            "source_qualified_branch": {
              "id": "followup-c-1",
              "title": "PC/TSC to FO — Routine requests",
              "conditions": [
                "Established assistance direction is PC/TSC to FO.",
                "The request is within the Routine requests table and applicable staff-role context."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CA/CTE, BA/BTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "60 calendar days after initial request",
                  "interval": {
                    "value": 60,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 4628,
                  "DOM_row_end": 5005,
                  "DOM_row_sha256": "bc09783f3d5769f111e76eda0c730ba3fe8ae640ed780d317537295bd9524fc3"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "CA/CTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "30 calendar days after 1st F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5005,
                  "DOM_row_end": 5337,
                  "DOM_row_sha256": "8bce3ec68b57c915235cfb269bfa6f0a3b496c07e866e9e2f776dcb5767b0184"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "AMM, MM",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "30 calendar days after 2nd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5337,
                  "DOM_row_end": 5675,
                  "DOM_row_sha256": "3bf7bc0d39e6f9d69e3168b17a07f93f70e61c31e82c8383e27b15aa6f25efbc"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "OM",
                  "recipient_as_published": "DM",
                  "when_as_published": "30 calendar days after 3rd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5675,
                  "DOM_row_end": 5986,
                  "DOM_row_sha256": "87a1e133c3528bb1c66ff8dd273b2759f332e6c2c8d06d90c3ed5e05b8020a7c"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "PROC_INTERCOMP_ASSIST"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-C.1",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 1245,
                  "end": 1578,
                  "exact_text": "1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\nCR/SR\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAMM, MM\n\n\t\n\nDM, ADM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM\n\n\t\n\n30 calendar days after 3rd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "6fd1280bc1765cf7847c86f87fe605699f79a82f8d414b54c84d2693af1108cf",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "C.1",
              "direction": "PC/TSC to FO",
              "request_class": "Routine requests",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CA/CTE, BA/BTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "60 calendar days after initial request",
                  "interval": {
                    "value": 60,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 4628,
                  "DOM_row_end": 5005,
                  "DOM_row_sha256": "bc09783f3d5769f111e76eda0c730ba3fe8ae640ed780d317537295bd9524fc3"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "CA/CTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "30 calendar days after 1st F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5005,
                  "DOM_row_end": 5337,
                  "DOM_row_sha256": "8bce3ec68b57c915235cfb269bfa6f0a3b496c07e866e9e2f776dcb5767b0184"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "AMM, MM",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "30 calendar days after 2nd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5337,
                  "DOM_row_end": 5675,
                  "DOM_row_sha256": "3bf7bc0d39e6f9d69e3168b17a07f93f70e61c31e82c8383e27b15aa6f25efbc"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "OM",
                  "recipient_as_published": "DM",
                  "when_as_published": "30 calendar days after 3rd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 5675,
                  "DOM_row_end": 5986,
                  "DOM_row_sha256": "87a1e133c3528bb1c66ff8dd273b2759f332e6c2c8d06d90c3ed5e05b8020a7c"
                }
              ],
              "source_context_id": "GN01070.440-C.1"
            }
          },
          "interoffice-assistance-followup/followup-c-2": {
            "id": "followup-c-2",
            "title": "PC/TSC to FO — High priority requests",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
            "source": "assist_GN01070_440",
            "section": "A; C.2",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-C.2",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 1578,
                "end": 1902,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "8c4b68c5300743471aae4b98a32b7f11c9e19743bc2f47cbd2938ca034fed371",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "C.2",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "Intercomponent Assistance Request Process"
            ],
            "entity_ids": [
              "PROC_INTERCOMP_ASSIST"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed High priority requests follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the High priority requests table and applicable staff-role context."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is PC/TSC to FO.; The request is within the High priority requests table and applicable staff-role context.",
            "source_qualified_branch": {
              "id": "followup-c-2",
              "title": "PC/TSC to FO — High priority requests",
              "conditions": [
                "Established assistance direction is PC/TSC to FO.",
                "The request is within the High priority requests table and applicable staff-role context."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CA/CTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "20 calendar days after initial request",
                  "interval": {
                    "value": 20,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6320,
                  "DOM_row_end": 6673,
                  "DOM_row_sha256": "a9b0e0212db9c83954b43fa0f720d79bf159c41ffe61d38b5688aa593d576b46"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "AMM",
                  "recipient_as_published": "OS",
                  "when_as_published": "10 calendar days after 1st F/U",
                  "interval": {
                    "value": 10,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6673,
                  "DOM_row_end": 6987,
                  "DOM_row_sha256": "a8d5390ef933864f070c623b5fd0187bf004ab638cd4a2d83695d2a3d459842f"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "MM",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "15 calendar days after 2nd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6987,
                  "DOM_row_end": 7310,
                  "DOM_row_sha256": "d6aeeac66f5eb51c6edaf0c2f6b5180fc3596637356949a7248647ffebfb9941"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "OM",
                  "recipient_as_published": "DM, AD",
                  "when_as_published": "15 calendar days after 3rd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 7310,
                  "DOM_row_end": 7633,
                  "DOM_row_sha256": "6074a5277fbdc7bfa06eef123de3f548890980c9c8311c7819842805eab49cdc"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "PROC_INTERCOMP_ASSIST"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-C.2",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 1578,
                  "end": 1902,
                  "exact_text": "2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM\n\n\t\n\nOS\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nMM\n\n\t\n\nDM, ADM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM, AD\n\n\t\n\n15 calendar days after 3rd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "8c4b68c5300743471aae4b98a32b7f11c9e19743bc2f47cbd2938ca034fed371",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "C.2",
              "direction": "PC/TSC to FO",
              "request_class": "High priority requests",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CA/CTE",
                  "recipient_as_published": "CR/SR",
                  "when_as_published": "20 calendar days after initial request",
                  "interval": {
                    "value": 20,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6320,
                  "DOM_row_end": 6673,
                  "DOM_row_sha256": "a9b0e0212db9c83954b43fa0f720d79bf159c41ffe61d38b5688aa593d576b46"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "AMM",
                  "recipient_as_published": "OS",
                  "when_as_published": "10 calendar days after 1st F/U",
                  "interval": {
                    "value": 10,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6673,
                  "DOM_row_end": 6987,
                  "DOM_row_sha256": "a8d5390ef933864f070c623b5fd0187bf004ab638cd4a2d83695d2a3d459842f"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "MM",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "15 calendar days after 2nd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 6987,
                  "DOM_row_end": 7310,
                  "DOM_row_sha256": "d6aeeac66f5eb51c6edaf0c2f6b5180fc3596637356949a7248647ffebfb9941"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "OM",
                  "recipient_as_published": "DM, AD",
                  "when_as_published": "15 calendar days after 3rd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 7310,
                  "DOM_row_end": 7633,
                  "DOM_row_sha256": "6074a5277fbdc7bfa06eef123de3f548890980c9c8311c7819842805eab49cdc"
                }
              ],
              "source_context_id": "GN01070.440-C.2"
            }
          },
          "interoffice-assistance-followup/followup-c-3": {
            "id": "followup-c-3",
            "title": "PC/TSC to FO — Manager to Manager",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged. No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context.",
            "source": "assist_GN01070_440",
            "section": "A; C.3",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-C.3",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 1902,
                "end": 2276,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "1d2872dd4cf6fa4b2d09d99720cf0b75aea4632423c54e88f762c89bd547ff62",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "C.3",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "M2M"
            ],
            "entity_ids": [
              "APP_M2M"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed Manager to Manager follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
              "No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is PC/TSC to FO.; The request is within the Manager to Manager table and applicable staff-role context.; The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
            "source_qualified_branch": {
              "id": "followup-c-3",
              "title": "PC/TSC to FO — Manager to Manager",
              "conditions": [
                "Established assistance direction is PC/TSC to FO.",
                "The request is within the Manager to Manager table and applicable staff-role context.",
                "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "AMM, MM, US",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "5 business days after initial request",
                  "interval": {
                    "value": 5,
                    "day_kind": "business",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8071,
                  "DOM_row_end": 8442,
                  "DOM_row_sha256": "56a5cea7c91a62c7e40181ef56b985a09e82afb194149d9708c51e77399f5f32"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "AMM, MM, US",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "3 business days after 1st F/U",
                  "interval": {
                    "value": 3,
                    "day_kind": "business",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8442,
                  "DOM_row_end": 8792,
                  "DOM_row_sha256": "b854f4789f35d4c8a7e0e704c905d747bb6650317a559b90999581f437ac4c8b"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "OM, SM",
                  "recipient_as_published": "AD, DAD",
                  "when_as_published": "2 business days after 2nd F/U",
                  "interval": {
                    "value": 2,
                    "day_kind": "business",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8792,
                  "DOM_row_end": 9124,
                  "DOM_row_sha256": "a9709420f3ac520f7c44a692337cbaa072939e1afac7ff7efa42c9264f195b89"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "APP_M2M"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-C.3",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 1902,
                  "end": 2276,
                  "exact_text": "3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nOM, SM\n\n\t\n\nAD, DAD\n\n\t\n\n2 business days after 2nd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "1d2872dd4cf6fa4b2d09d99720cf0b75aea4632423c54e88f762c89bd547ff62",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
                "No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "C.3",
              "direction": "PC/TSC to FO",
              "request_class": "Manager to Manager",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "AMM, MM, US",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "5 business days after initial request",
                  "interval": {
                    "value": 5,
                    "day_kind": "business",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8071,
                  "DOM_row_end": 8442,
                  "DOM_row_sha256": "56a5cea7c91a62c7e40181ef56b985a09e82afb194149d9708c51e77399f5f32"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "AMM, MM, US",
                  "recipient_as_published": "DM, ADM",
                  "when_as_published": "3 business days after 1st F/U",
                  "interval": {
                    "value": 3,
                    "day_kind": "business",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8442,
                  "DOM_row_end": 8792,
                  "DOM_row_sha256": "b854f4789f35d4c8a7e0e704c905d747bb6650317a559b90999581f437ac4c8b"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "OM, SM",
                  "recipient_as_published": "AD, DAD",
                  "when_as_published": "2 business days after 2nd F/U",
                  "interval": {
                    "value": 2,
                    "day_kind": "business",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 8792,
                  "DOM_row_end": 9124,
                  "DOM_row_sha256": "a9709420f3ac520f7c44a692337cbaa072939e1afac7ff7efa42c9264f195b89"
                }
              ],
              "source_context_id": "GN01070.440-C.3"
            }
          },
          "interoffice-assistance-followup/followup-d-1": {
            "id": "followup-d-1",
            "title": "FO/TSC to PC — Routine requests",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
            "source": "assist_GN01070_440",
            "section": "A; D.1",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-D.1",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 2293,
                "end": 2626,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "d1f4ad95e0ca3a4e2f2704e565479687df9082e2fe6539b4fe7e38ecd0532b50",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "D.1",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "Intercomponent Assistance Request Process"
            ],
            "entity_ids": [
              "PROC_INTERCOMP_ASSIST"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed Routine requests follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Routine requests table and applicable staff-role context."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is FO/TSC to PC.; The request is within the Routine requests table and applicable staff-role context.",
            "source_qualified_branch": {
              "id": "followup-d-1",
              "title": "FO/TSC to PC — Routine requests",
              "conditions": [
                "Established assistance direction is FO/TSC to PC.",
                "The request is within the Routine requests table and applicable staff-role context."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CR/SR",
                  "recipient_as_published": "CA/CTE, BA/BTE",
                  "when_as_published": "60 calendar days after initial request",
                  "interval": {
                    "value": 60,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 9530,
                  "DOM_row_end": 9907,
                  "DOM_row_sha256": "966b2a72ffe21e1621b39ea92a2400da3e3946408113dcf67a6ca0a8631f3eb8"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "CR/SR",
                  "recipient_as_published": "CA/CTE",
                  "when_as_published": "30 calendar days after 1st F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 9907,
                  "DOM_row_end": 10239,
                  "DOM_row_sha256": "c8767462ffa13702bcbe1bfb19735b28c2a5597ed4cb0e9f6b648a816abe67e7"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "DM, ADM",
                  "recipient_as_published": "AMM, MM",
                  "when_as_published": "30 calendar days after 2nd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 10239,
                  "DOM_row_end": 10577,
                  "DOM_row_sha256": "6338f0720d4271183d6409c05cab27c5209666bc49439fc150351a3479fe8f41"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "DM",
                  "recipient_as_published": "OM",
                  "when_as_published": "30 calendar days after 3rd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 10577,
                  "DOM_row_end": 10888,
                  "DOM_row_sha256": "469cf0d4fe6dd96b4a66be21fc09f5c2972c2fa024c43c31052119b97137cbfc"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "PROC_INTERCOMP_ASSIST"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-D.1",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 2293,
                  "end": 2626,
                  "exact_text": "1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nAMM, MM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM\n\n\t\n\nOM\n\n\t\n\n30 calendar days after 3rd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "d1f4ad95e0ca3a4e2f2704e565479687df9082e2fe6539b4fe7e38ecd0532b50",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "D.1",
              "direction": "FO/TSC to PC",
              "request_class": "Routine requests",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CR/SR",
                  "recipient_as_published": "CA/CTE, BA/BTE",
                  "when_as_published": "60 calendar days after initial request",
                  "interval": {
                    "value": 60,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 9530,
                  "DOM_row_end": 9907,
                  "DOM_row_sha256": "966b2a72ffe21e1621b39ea92a2400da3e3946408113dcf67a6ca0a8631f3eb8"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "CR/SR",
                  "recipient_as_published": "CA/CTE",
                  "when_as_published": "30 calendar days after 1st F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 9907,
                  "DOM_row_end": 10239,
                  "DOM_row_sha256": "c8767462ffa13702bcbe1bfb19735b28c2a5597ed4cb0e9f6b648a816abe67e7"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "DM, ADM",
                  "recipient_as_published": "AMM, MM",
                  "when_as_published": "30 calendar days after 2nd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 10239,
                  "DOM_row_end": 10577,
                  "DOM_row_sha256": "6338f0720d4271183d6409c05cab27c5209666bc49439fc150351a3479fe8f41"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "DM",
                  "recipient_as_published": "OM",
                  "when_as_published": "30 calendar days after 3rd F/U",
                  "interval": {
                    "value": 30,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 10577,
                  "DOM_row_end": 10888,
                  "DOM_row_sha256": "469cf0d4fe6dd96b4a66be21fc09f5c2972c2fa024c43c31052119b97137cbfc"
                }
              ],
              "source_context_id": "GN01070.440-D.1"
            }
          },
          "interoffice-assistance-followup/followup-d-2": {
            "id": "followup-d-2",
            "title": "FO/TSC to PC — High priority requests",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
            "source": "assist_GN01070_440",
            "section": "A; D.2",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-D.2",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 2626,
                "end": 2951,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "255f3061dd00282bd48c096857f267a54c1f10b1c04b1b3500400d343b9eba08",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "D.2",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "Intercomponent Assistance Request Process"
            ],
            "entity_ids": [
              "PROC_INTERCOMP_ASSIST"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed High priority requests follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the High priority requests table and applicable staff-role context."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is FO/TSC to PC.; The request is within the High priority requests table and applicable staff-role context.",
            "source_qualified_branch": {
              "id": "followup-d-2",
              "title": "FO/TSC to PC — High priority requests",
              "conditions": [
                "Established assistance direction is FO/TSC to PC.",
                "The request is within the High priority requests table and applicable staff-role context."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CR, SR",
                  "recipient_as_published": "CA/CTE",
                  "when_as_published": "20 calendar days after initial request",
                  "interval": {
                    "value": 20,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11222,
                  "DOM_row_end": 11578,
                  "DOM_row_sha256": "ca8b58ded703cf16847fb45ebfec46531bee866640b1c091a15a700496ada2d6"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "OS",
                  "recipient_as_published": "AMM",
                  "when_as_published": "10 calendar days after 1st F/U",
                  "interval": {
                    "value": 10,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11578,
                  "DOM_row_end": 11892,
                  "DOM_row_sha256": "57b0e4c0dfa2e0d724eb46ce30e1932bdb1d3a4e7743e60fa30759ccdfaa6274"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "DM, ADM",
                  "recipient_as_published": "MM",
                  "when_as_published": "15 calendar days after 2nd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11892,
                  "DOM_row_end": 12215,
                  "DOM_row_sha256": "b14a0ae68216c07fc7abb2b51d5c969af69b6345155e687e73ab2a5f0d53a990"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "DM, AD",
                  "recipient_as_published": "OM",
                  "when_as_published": "15 calendar days after 3rd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 12215,
                  "DOM_row_end": 12538,
                  "DOM_row_sha256": "63632eab4887b28076822e921131db1b774b11292fd2c473a0b2299685259c39"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "PROC_INTERCOMP_ASSIST"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-D.2",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 2626,
                  "end": 2951,
                  "exact_text": "2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR, SR\n\n\t\n\nCA/CTE\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nOS\n\n\t\n\nAMM\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nMM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM, AD\n\n\t\n\nOM\n\n\t\n\n15 calendar days after 3rd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "255f3061dd00282bd48c096857f267a54c1f10b1c04b1b3500400d343b9eba08",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "D.2",
              "direction": "FO/TSC to PC",
              "request_class": "High priority requests",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "CR, SR",
                  "recipient_as_published": "CA/CTE",
                  "when_as_published": "20 calendar days after initial request",
                  "interval": {
                    "value": 20,
                    "day_kind": "calendar",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11222,
                  "DOM_row_end": 11578,
                  "DOM_row_sha256": "ca8b58ded703cf16847fb45ebfec46531bee866640b1c091a15a700496ada2d6"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "OS",
                  "recipient_as_published": "AMM",
                  "when_as_published": "10 calendar days after 1st F/U",
                  "interval": {
                    "value": 10,
                    "day_kind": "calendar",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11578,
                  "DOM_row_end": 11892,
                  "DOM_row_sha256": "57b0e4c0dfa2e0d724eb46ce30e1932bdb1d3a4e7743e60fa30759ccdfaa6274"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "DM, ADM",
                  "recipient_as_published": "MM",
                  "when_as_published": "15 calendar days after 2nd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 11892,
                  "DOM_row_end": 12215,
                  "DOM_row_sha256": "b14a0ae68216c07fc7abb2b51d5c969af69b6345155e687e73ab2a5f0d53a990"
                },
                {
                  "followup": "Fourth",
                  "requester_as_published": "DM, AD",
                  "recipient_as_published": "OM",
                  "when_as_published": "15 calendar days after 3rd F/U",
                  "interval": {
                    "value": 15,
                    "day_kind": "calendar",
                    "anchor_as_published": "3rd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 12215,
                  "DOM_row_end": 12538,
                  "DOM_row_sha256": "63632eab4887b28076822e921131db1b774b11292fd2c473a0b2299685259c39"
                }
              ],
              "source_context_id": "GN01070.440-D.2"
            }
          },
          "interoffice-assistance-followup/followup-d-3": {
            "id": "followup-d-3",
            "title": "FO/TSC to PC — Manager to Manager",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged. No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context.",
            "source": "assist_GN01070_440",
            "section": "A; D.3",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              },
              {
                "id": "GN01070.440-D.3",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 2951,
                "end": 3492,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "7cee096fbb1000733a0d2d949796fb36211fe7ff90a13a891ada9b18322fe38f",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "D.3",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "M2M"
            ],
            "entity_ids": [
              "APP_M2M"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Prescribed Manager to Manager follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
              "No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established."
            ],
            "condition_logic": "all",
            "when": "Established assistance direction is FO/TSC to PC.; The request is within the Manager to Manager table and applicable staff-role context.; The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
            "source_qualified_branch": {
              "id": "followup-d-3",
              "title": "FO/TSC to PC — Manager to Manager",
              "conditions": [
                "Established assistance direction is FO/TSC to PC.",
                "The request is within the Manager to Manager table and applicable staff-role context.",
                "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established."
              ],
              "condition_logic": "all",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "DM, ADM, US",
                  "recipient_as_published": "AMM, MM",
                  "when_as_published": "5 business days after initial request",
                  "interval": {
                    "value": 5,
                    "day_kind": "business",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13144,
                  "DOM_row_end": 13515,
                  "DOM_row_sha256": "a4626f233c2add08f5f4259e39b04d5f75653fc659f331b5245f888fc23c4fb6"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "DM, ADM, US",
                  "recipient_as_published": "AMM,MM",
                  "when_as_published": "3 business days after 1st F/U",
                  "interval": {
                    "value": 3,
                    "day_kind": "business",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13515,
                  "DOM_row_end": 13862,
                  "DOM_row_sha256": "3c81c79d0e383bebd1a82666527e88eb88e3e5e49dedc87e5cb50695502782f4"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "AD, DAD, SM",
                  "recipient_as_published": "OM",
                  "when_as_published": "2 business days after 2nd F/U",
                  "interval": {
                    "value": 2,
                    "day_kind": "business",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13862,
                  "DOM_row_end": 14194,
                  "DOM_row_sha256": "8b79b8c97c206eb66c455c569e1e69d245571015efd1e931cea2cd6ccabba531"
                }
              ],
              "ui_text": {
                "ssa_action": "Use the source row for the actual follow-up stage, requester, recipient, day kind and stated anchor. Discuss dates and communicate delays under A.",
                "customer_action": "These are interoffice staff schedules, not actions or deadlines assigned to the customer."
              },
              "entity_ids": [
                "APP_M2M"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                },
                {
                  "id": "GN01070.440-D.3",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 2951,
                  "end": 3492,
                  "exact_text": "3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request. Query PCACS or Evidence Portal (EP) for an active REQ/EMFO TOEL that shows the PC is working on the request. REQ/EMFO TOEL that shows the PC is working on the request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM, MM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM,MM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAD, DAD, SM\n\n\t\n\nOM\n\n\t\n\n2 business days after 2nd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "7cee096fbb1000733a0d2d949796fb36211fe7ff90a13a891ada9b18322fe38f",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
                "No-communication gate is stated specifically in C.3/D.3; it is not silently imposed on every routine/high-priority request. Automated acknowledgement, interim reply or status entry must not be automatically classified as qualifying communication without source/application context."
              ],
              "status": "source_qualified_research_only_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "prescribed_followup_table": {
              "locator": "D.3",
              "direction": "FO/TSC to PC",
              "request_class": "Manager to Manager",
              "rows": [
                {
                  "followup": "First",
                  "requester_as_published": "DM, ADM, US",
                  "recipient_as_published": "AMM, MM",
                  "when_as_published": "5 business days after initial request",
                  "interval": {
                    "value": 5,
                    "day_kind": "business",
                    "anchor_as_published": "initial request",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13144,
                  "DOM_row_end": 13515,
                  "DOM_row_sha256": "a4626f233c2add08f5f4259e39b04d5f75653fc659f331b5245f888fc23c4fb6"
                },
                {
                  "followup": "Second",
                  "requester_as_published": "DM, ADM, US",
                  "recipient_as_published": "AMM,MM",
                  "when_as_published": "3 business days after 1st F/U",
                  "interval": {
                    "value": 3,
                    "day_kind": "business",
                    "anchor_as_published": "1st F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13515,
                  "DOM_row_end": 13862,
                  "DOM_row_sha256": "3c81c79d0e383bebd1a82666527e88eb88e3e5e49dedc87e5cb50695502782f4"
                },
                {
                  "followup": "Third",
                  "requester_as_published": "AD, DAD, SM",
                  "recipient_as_published": "OM",
                  "when_as_published": "2 business days after 2nd F/U",
                  "interval": {
                    "value": 2,
                    "day_kind": "business",
                    "anchor_as_published": "2nd F/U",
                    "kind": "published_followup_schedule_not_casecompletion_SLA"
                  },
                  "DOM_row_start": 13862,
                  "DOM_row_end": 14194,
                  "DOM_row_sha256": "8b79b8c97c206eb66c455c569e1e69d245571015efd1e931cea2cd6ccabba531"
                }
              ],
              "source_context_id": "GN01070.440-D.3"
            }
          },
          "interoffice-assistance-followup/followup-d3-active-req-emfo-query": {
            "id": "followup-d3-active-req-emfo-query",
            "title": "FO/TSC-to-PC M2M follow-up: query the active work-control indicator",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "D.3 directs a PCACS OR Evidence Portal query for an active REQ/EMFO TOEL showing that the PC is working on the request. Keep this status query distinct from creation of a PCACS assistance request. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged. Active REQ/EMFO indicates PC working under this paragraph; it does not prove completion/payment or explicitly prescribe suppressing, restarting or resetting a follow-up clock. PCACS OR EP is an alternative query, not a requirement to use both. The source does not provide an endpoint, actual permission or field-level procedure here. GN01070.228 PSC-only PCACS assistance-request method and .440D.3 query operation have different stated actions. This does not create a default FO PCACS request-creation path or imply date-based supersession. DATA_TOEL is an existing generic metadata concept. REQ/EMFO is retained verbatim; no expansion of its code levels or new artifact/system identity is invented.",
            "source": "assist_GN01070_440",
            "section": "D.3",
            "source_provenance": [
              {
                "id": "GN01070.440-D.3",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 2951,
                "end": 3492,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "7cee096fbb1000733a0d2d949796fb36211fe7ff90a13a891ada9b18322fe38f",
                "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP",
                "locator": "D.3",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "PCACS",
              "EP",
              "TOEL (generic recorded metadata family)"
            ],
            "entity_ids": [
              "APP_PCACS",
              "APP_EP"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Published follow-up references only; no measured duration or calculated customer deadline.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
              "Active REQ/EMFO indicates PC working under this paragraph; it does not prove completion/payment or explicitly prescribe suppressing, restarting or resetting a follow-up clock.",
              "PCACS OR EP is an alternative query, not a requirement to use both. The source does not provide an endpoint, actual permission or field-level procedure here.",
              "GN01070.228 PSC-only PCACS assistance-request method and .440D.3 query operation have different stated actions. This does not create a default FO PCACS request-creation path or imply date-based supersession.",
              "DATA_TOEL is an existing generic metadata concept. REQ/EMFO is retained verbatim; no expansion of its code levels or new artifact/system identity is invented."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "FO/TSC-to-PC Manager-to-Manager D.3 context applies.",
              "The source no-communication condition and applicable row/staff prerequisites are established."
            ],
            "condition_logic": "all",
            "when": "FO/TSC-to-PC Manager-to-Manager D.3 context applies.; The source no-communication condition and applicable row/staff prerequisites are established.",
            "source_qualified_branch": {
              "id": "followup-d3-active-req-emfo-query",
              "title": "FO/TSC-to-PC M2M follow-up: query the active work-control indicator",
              "conditions": [
                "FO/TSC-to-PC Manager-to-Manager D.3 context applies.",
                "The source no-communication condition and applicable row/staff prerequisites are established."
              ],
              "condition_logic": "all",
              "ui_text": {
                "ssa_action": "D.3 directs a PCACS OR Evidence Portal query for an active REQ/EMFO TOEL showing that the PC is working on the request. Keep this status query distinct from creation of a PCACS assistance request.",
                "customer_action": "No customer access to staff systems or personally verified request status is established."
              },
              "entity_ids": [
                "APP_PCACS",
                "APP_EP"
              ],
              "contextual_existing_metadata_id": "DATA_TOEL",
              "policy_refs": [
                {
                  "id": "GN01070.440-D.3",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 2951,
                  "end": 3492,
                  "exact_text": "3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request. Query PCACS or Evidence Portal (EP) for an active REQ/EMFO TOEL that shows the PC is working on the request. REQ/EMFO TOEL that shows the PC is working on the request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM, MM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM,MM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAD, DAD, SM\n\n\t\n\nOM\n\n\t\n\n2 business days after 2nd F/U\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "7cee096fbb1000733a0d2d949796fb36211fe7ff90a13a891ada9b18322fe38f",
                  "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
                "Active REQ/EMFO indicates PC working under this paragraph; it does not prove completion/payment or explicitly prescribe suppressing, restarting or resetting a follow-up clock.",
                "PCACS OR EP is an alternative query, not a requirement to use both. The source does not provide an endpoint, actual permission or field-level procedure here.",
                "GN01070.228 PSC-only PCACS assistance-request method and .440D.3 query operation have different stated actions. This does not create a default FO PCACS request-creation path or imply date-based supersession.",
                "DATA_TOEL is an existing generic metadata concept. REQ/EMFO is retained verbatim; no expansion of its code levels or new artifact/system identity is invented."
              ],
              "status": "separate_scoped_research_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ],
            "contextual_metadata_entity_ids": [
              "DATA_TOEL"
            ]
          },
          "interoffice-assistance-followup/followup-delay-two-way-communication": {
            "id": "followup-delay-two-way-communication",
            "title": "The receiving office anticipates delay beyond the follow-up timeframe",
            "you": "These are internal SSA coordination steps. Retain your correspondence and follow case-specific SSA instructions; this page assigns no staff-system action to you.",
            "ssa": "Advise the requester so alternative development sources can be discussed if necessary. A says notify FO/PC by telephone or email when the request cannot be answered within the prescribed timeframe. Scope and qualifications: Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA. Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories. Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date. A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here. No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged. This is delay notification, not evidence that telephone/email is an initial SBC assistance-submission mode or a defined M2M mailbox address.",
            "source": "assist_GN01070_440",
            "section": "A",
            "source_provenance": [
              {
                "id": "GN01070.440-A",
                "source_code": "GN01070.440",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                "start": 104,
                "end": 686,
                "offset_unit": "Unicode codepoints in captured rendered maintext",
                "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP",
                "locator": "A",
                "source_download_url": "/service/sources/GN01070.440-current-browser.txt"
              }
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
              "snapshot_path": "/service/sources/GN01070.440-current-browser.txt",
              "report": "/service/assistance-followup-source-provenance.json"
            },
            "owner": "SSA staff in the source-defined requesting and receiving offices; exact row roles shown for selected schedules.",
            "systems": [
              "Intercomponent Assistance Request Process"
            ],
            "entity_ids": [
              "PROC_INTERCOMP_ASSIST"
            ],
            "route": "Source-qualified staff coordination; no automatic transition or completed case outcome established.",
            "next": "Use only the established source predicates. Actual request, response, status update and completed rejoin are not demonstrated.",
            "timing": "Published follow-up references only; no measured duration or calculated customer deadline.",
            "verification": "Selected current browser-captured source scope reviewed; internal execution not tested.",
            "qualifications": [
              "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
              "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
              "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
              "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
              "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
              "This is delay notification, not evidence that telephone/email is an initial SBC assistance-submission mode or a defined M2M mailbox address."
            ],
            "review_status": "Selected source claims linked; operational execution, target cross-references and native acceptance remain unverified.",
            "conditions": [
              "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe."
            ],
            "condition_logic": "all",
            "when": "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe.",
            "source_qualified_branch": {
              "id": "followup-delay-two-way-communication",
              "title": "The receiving office anticipates delay beyond the follow-up timeframe",
              "conditions": [
                "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe."
              ],
              "condition_logic": "all",
              "ui_text": {
                "ssa_action": "Advise the requester so alternative development sources can be discussed if necessary. A says notify FO/PC by telephone or email when the request cannot be answered within the prescribed timeframe.",
                "customer_action": "No new customer processing duty, direct endpoint or case result is established."
              },
              "entity_ids": [
                "PROC_INTERCOMP_ASSIST"
              ],
              "policy_refs": [
                {
                  "id": "GN01070.440-A",
                  "source_code": "GN01070.440",
                  "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
                  "start": 104,
                  "end": 686,
                  "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
                  "offset_unit": "Unicode codepoints in captured rendered maintext",
                  "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
                  "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
                  "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
                  "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
                }
              ],
              "qualifications": [
                "Directed staff follow-up schedule only; not a customer filing deadline, payment/reinstatement guarantee, measured processing latency or broad Service SLA.",
                "Preserve each row requester/recipient and direction; do not reverse FO-to-PC versus PC-to-FO or collapse routine/high-priority/M2M categories.",
                "Intervals anchor to the stated initial request or actual prior follow-up, not the benefit application or a computed cumulative automatic escalation date.",
                "A says discuss follow-up dates; if the date falls on weekend/other non-workday use next workday. No real holiday calendar or day-zero convention supplied here.",
                "No source/native acceptance, real request, verified response, alias, source-priority-by-date or new native graph edge established. Generic MDW/AI identity hold and older evidence-source holds unchanged.",
                "This is delay notification, not evidence that telephone/email is an initial SBC assistance-submission mode or a defined M2M mailbox address."
              ],
              "status": "separate_scoped_research_no_integration"
            },
            "source_qualified_branch_history": {
              "scope": "Original pre-integration source-research snapshot; status text refers to that snapshot, not deployment or source acceptance.",
              "source_research_sha256": "75c2c5fbe33651a451c2dd745bcc210adf657758690a0799be38dbba3211bc07"
            },
            "status": "source_qualified_navigation_research",
            "rejoin_unknowns": [
              {
                "detail": "Actual request, response/status and completed downstream state are not demonstrated."
              }
            ]
          }
        },
        "source_contexts": [
          {
            "id": "GN01070.440-A",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 104,
            "end": 686,
            "exact_text": "A. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "e490a958caca723a127f4a896dcf2dcca46f4bb0ffdf928c5b38ddb5f6b413a5",
            "capture_type": "Actual coordinator IAB rendered maintext and DOM/accessibility snapshot, not parsedHTML or rawHTTP"
          },
          {
            "id": "GN01070.440-C.1",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 1245,
            "end": 1578,
            "exact_text": "1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\nCR/SR\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAMM, MM\n\n\t\n\nDM, ADM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM\n\n\t\n\n30 calendar days after 3rd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "6fd1280bc1765cf7847c86f87fe605699f79a82f8d414b54c84d2693af1108cf",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-C.2",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 1578,
            "end": 1902,
            "exact_text": "2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM\n\n\t\n\nOS\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nMM\n\n\t\n\nDM, ADM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM, AD\n\n\t\n\n15 calendar days after 3rd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "8c4b68c5300743471aae4b98a32b7f11c9e19743bc2f47cbd2938ca034fed371",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-C.3",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 1902,
            "end": 2276,
            "exact_text": "3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nOM, SM\n\n\t\n\nAD, DAD\n\n\t\n\n2 business days after 2nd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "1d2872dd4cf6fa4b2d09d99720cf0b75aea4632423c54e88f762c89bd547ff62",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-D.1",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 2293,
            "end": 2626,
            "exact_text": "1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nAMM, MM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM\n\n\t\n\nOM\n\n\t\n\n30 calendar days after 3rd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "d1f4ad95e0ca3a4e2f2704e565479687df9082e2fe6539b4fe7e38ecd0532b50",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-D.2",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 2626,
            "end": 2951,
            "exact_text": "2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR, SR\n\n\t\n\nCA/CTE\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nOS\n\n\t\n\nAMM\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nMM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM, AD\n\n\t\n\nOM\n\n\t\n\n15 calendar days after 3rd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "255f3061dd00282bd48c096857f267a54c1f10b1c04b1b3500400d343b9eba08",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-D.3",
            "source_code": "GN01070.440",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070440",
            "start": 2951,
            "end": 3492,
            "exact_text": "3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request. Query PCACS or Evidence Portal (EP) for an active REQ/EMFO TOEL that shows the PC is working on the request. REQ/EMFO TOEL that shows the PC is working on the request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM, MM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM,MM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAD, DAD, SM\n\n\t\n\nOM\n\n\t\n\n2 business days after 2nd F/U\n\n",
            "offset_unit": "Unicode codepoints in captured rendered maintext",
            "text_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
            "browser_DOM_accessibility_snapshot_sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
            "span_sha256": "7cee096fbb1000733a0d2d949796fb36211fe7ff90a13a891ada9b18322fe38f",
            "capture_type": "rendered maintext plus browser DOM/accessibility snapshot; not rawHTTP"
          },
          {
            "id": "GN01070.440-B",
            "source_code": "GN01070.440",
            "locator": "B glossary, literal published abbreviations retained",
            "start": 686,
            "end": 1228,
            "exact_text": "B. \nGlossary of Terms\n\n \n\nAcronym\tJob Position\n\n\nAD/DAD\n\n\t\n\nArea Director/Deputy Area Director\n\n\n\n\nSM\n\n\t\n\nTSC Section Manager\n\n\n\n\nDM/AD\n\n\t\n\nDistrict Manager/Assistant District Manager\n\n\n\n\nOS\n\n\t\n\nOperations Supervisor\n\n\n\n\nUS\n\n\t\n\nTSC Unit Supervisor\n\n\n\n\nCR/SR\n\n\t\n\nClaims Representative/Service Representative\n\n\n\n\nOM/DD\n\n\t\n\nOperations Manager/Division Director\n\n\n\n\nMM\n\n\t\n\nModule Manager\n\n\n\n\nAMM\n\n\t\n\nAssistant Module Manager\n\n\n\n\nCA/CTE\n\n\t\n\nClaims Authorizer/Claims Technical Examiner\n\n\n\n\nBA/BTE\n\n\t\n\nBenefit Authorizer/Benefit Technical Examiner\n\n",
            "span_sha256": "db212eb596f60d78bc33584f0d2e3294df5da2dcf0d087250990a8326e770507"
          },
          {
            "id": "GN01070.440-whole",
            "source_code": "GN01070.440",
            "start": 0,
            "end": 3898,
            "exact_text": "Effective Dates: 08/26/2021 - Present\nPrevious | Next\n\nTN 34 (08-21)\n\nGN 01070.440 Follow-Up Timeframes\nA. \nOverview of follow-up guidelines\n•\n\nReceiving field offices (FO) and processing centers (PC) should advise the requester when there would be delays so that alternative development sources can be discussed, if necessary.\n\n•\n\nDiscuss follow-up dates with the FO or PC to avoid any future misunderstanding. If the follow-up date falls on a weekend or other non-work day, use the next workday.\n\n•\n\nIf a request cannot be answered within the prescribed follow-up timeframe, notify the FO or PC via telephone or email. This two-way communication will help prevent multiple requests.\n\nB. \nGlossary of Terms\n\n \n\nAcronym\tJob Position\n\n\nAD/DAD\n\n\t\n\nArea Director/Deputy Area Director\n\n\n\n\nSM\n\n\t\n\nTSC Section Manager\n\n\n\n\nDM/AD\n\n\t\n\nDistrict Manager/Assistant District Manager\n\n\n\n\nOS\n\n\t\n\nOperations Supervisor\n\n\n\n\nUS\n\n\t\n\nTSC Unit Supervisor\n\n\n\n\nCR/SR\n\n\t\n\nClaims Representative/Service Representative\n\n\n\n\nOM/DD\n\n\t\n\nOperations Manager/Division Director\n\n\n\n\nMM\n\n\t\n\nModule Manager\n\n\n\n\nAMM\n\n\t\n\nAssistant Module Manager\n\n\n\n\nCA/CTE\n\n\t\n\nClaims Authorizer/Claims Technical Examiner\n\n\n\n\nBA/BTE\n\n\t\n\nBenefit Authorizer/Benefit Technical Examiner\n\nC. \nPC/TSC to FO\n1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\nCR/SR\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAMM, MM\n\n\t\n\nDM, ADM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM\n\n\t\n\n30 calendar days after 3rd F/U\n\n2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCA/CTE\n\n\t\n\nCR/SR\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM\n\n\t\n\nOS\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nMM\n\n\t\n\nDM, ADM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nOM\n\n\t\n\nDM, AD\n\n\t\n\n15 calendar days after 3rd F/U\n\n3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nAMM, MM, US\n\n\t\n\nDM, ADM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nOM, SM\n\n\t\n\nAD, DAD\n\n\t\n\n2 business days after 2nd F/U\n\nD. \nFO/TSC to PC\n1. \nRoutine requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE, BA/BTE\n\n\t\n\n60 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nCR/SR\n\n\t\n\nCA/CTE\n\n\t\n\n30 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nAMM, MM\n\n\t\n\n30 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM\n\n\t\n\nOM\n\n\t\n\n30 calendar days after 3rd F/U\n\n2. \nHigh priority requests\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nCR, SR\n\n\t\n\nCA/CTE\n\n\t\n\n20 calendar days after initial request\n\n\n\n\nSecond\n\n\t\n\nOS\n\n\t\n\nAMM\n\n\t\n\n10 calendar days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nDM, ADM\n\n\t\n\nMM\n\n\t\n\n15 calendar days after 2nd F/U\n\n\n\n\nFourth\n\n\t\n\nDM, AD\n\n\t\n\nOM\n\n\t\n\n15 calendar days after 3rd F/U\n\n3. \nManager to Manager\n\nNOTE: Only send follow-up requests if there has been no communication after the first request. Query PCACS or Evidence Portal (EP) for an active REQ/EMFO TOEL that shows the PC is working on the request. REQ/EMFO TOEL that shows the PC is working on the request.\n\nFollow-up\tRequester\tRecipient\tWhen\n\n\nFirst\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM, MM\n\n\t\n\n5 business days after initial request\n\n\n\n\nSecond\n\n\t\n\nDM, ADM, US\n\n\t\n\nAMM,MM\n\n\t\n\n3 business days after 1st F/U\n\n\n\n\nThird\n\n\t\n\nAD, DAD, SM\n\n\t\n\nOM\n\n\t\n\n2 business days after 2nd F/U\n\nE. \nReference\n\nGN 01070.228 Modes of Requesting Assistance\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0201070440\n\t\nGN 01070.440 - Follow-Up Timeframes - 08/26/2021\nBatch run: 08/20/2025\nRev:08/26/2021\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10"
          },
          {
            "id": "GN01070.228-whole",
            "source_code": "GN01070.228",
            "start": 0,
            "end": 8180,
            "exact_text": "Effective Dates: 10/15/2018 - Present\nPrevious | Next\n\nTN 30 (09-19)\n\nGN 01070.228 Modes of Requesting Assistance\nA. \nMethods to request assistance\n\nThere are five ways that an office can request assistance from another office. Listed in the order of preference, they are:\n\n1. \n\nDistrict Office Telephone Procedure (DOTEL)—All offices may use this process.\n\n2. \n\nProcessing Center Action Control System (PCACS)—This method is only for PSCs use.\n\n3. \n\nModernized Development Worksheet (MDW)--All components may use this method.\n\n4. \n\nElectronic E562 –All offices may use this method, if the program is available within the region.\n\n5. \n\nManager -to-Manager (M2M) web application –Managers in Field Offices, Processing Centers, and National 800 Number Network (N8NN) sites may use this method.\n\nRegardless of the means you use for a request, always provide priority handling to high priority requests.\n\nNote: Request assistance after the requesting office attempts to obtain the information by direct contact. (For instructions on use of DIRCON, see GN 01070.305).\n\n1. \nDOTEL\n\nDOTEL provides intercomponent telephone contact in initial entitlement and certain post-entitlement situations. DOTEL is the most expedient means of requesting help from another office. The basic feature of DOTEL is the use of the telephone to request assistance and the priority handling provided by the responding office. For this reason, we restrict the use of DOTEL. (For FO procedure on DOTEL, see GN 01070.200 and for PC procedure on DOTEL, see GN 01070.400).\n\nNOTE: If you do not receive the information requested, during the initial DOTEL call, always determine the mode of response before terminating the DOTEL call.\n\n2. \nPCACS\n\nFor instructions on completion and use of PCACS, see MSOM PCACS 001.001.\n\n3. \nMDW\n\nAfter completing the initial call or making the initial request, establish the issue on the MDW screen, if it is not in use by another office. In addition to the instructions below, refer to the MDW guidelines found in TC 29001.030.\n\na. \n\nEstablish the type of action in the last three positions of the “UNIT” field. (Use the first three positions as the unit identifier for the person responsible for the action). For a list of MDW codes, see GN 01070.228A.3.e. in this section.\n\nb. \n\nIn the “MISC” field, establish the type of request, the name, job position, PC MOD, or FO name and telephone number of the assisting claims authorizer (CA). Use the following format:\n\nMISC:\n\n\t\n\n“DOTEL”, ASST CA JOHN GEORGE,PC2,MOD 8,215-555-1122\n\n \n\n“ROUTINE”, ASST CR M JENKINS, A96 WESTMINSTER MD,410-555-3322\n\nc. \n\nDescribe the required evidence or the issue to resolve in the “Issue” field. Show any additional data about the issue in the “Remarks” field (see MS 03901.003). Use the following format:\n\nISSUE\n\n\t\n\nREMARKS\n\n\n\n\nPOA\n\n\t\n\nBaptismal\n\nd. \n\nShow the “TICKLE” date based on the follow-up schedule in GN 01070.440 or on the mutually agreed upon date.\n\ne. \n\nThe following list shows MDW unit field codes:\n\n Code\n\n\t\n\nExplanation\n\n\n\n\n001\n\n\t\n\nRSI APPLICATIONS\n\n\n\n\n002\n\n\t\n\nRSI NONDISABILITY DEPENDENT APPLICATIONS\n\n\n\n\n003\n\n\t\n\nDIB APPLICATIONS\n\n\n\n\n004\n\n\t\n\nDI NONDISABILITY DEPENDENT APPLICATIONS\n\n\n\n\n005\n\n\t\n\nRSDI MEDICAL CDR\n\n\n\n\n006\n\n\t\n\nRSDI WORK CDR\n\n\n\n\n007\n\n\t\n\nSSI AGED APPLICATIONS\n\n\n\n\n008\n\n\t\n\nSSI B/D APPLICATIONS\n\n\n\n\n009\n\n\t\n\nSSI REDETERMINATION (LOW & MIDDLE)\n\n\n\n\n010\n\n\t\n\nSSI REDETERMINATIONS (HIGH)\n\n\n\n\n011\n\n\t\n\nBL CLAIMS (SSA)\n\n\n\n\n012\n\n\t\n\nBL CLAIMS (DOL)\n\n\n\n\n013\n\n\t\n\nRSDHI RECONSIDERATION\n\n\n\n\n014\n\n\t\n\nSSI RECONSIDERATION\n\n\n\n\n015\n\n\t\n\nRSDHI HEARINGS\n\n\n\n\n016\n\n\t\n\nSSI HEARINGS AND APPEALS\n\n\n\n\n017\n\n\t\n\nRSDHI CLASS ACTIONS\n\n\n\n\n018\n\n\t\n\nSSI CLASS ACTIONS\n\n\n\n\n019\n\n\t\n\nSSI APPEAL EFFECTUATION\n\n\n\n\n020\n\n\t\n\nSSI ZEBLEY B/D APPLICATIONS\n\n\n\n\n021\n\n\t\n\nSSI ZEBLEY REDETERMINATION (HIGH)\n\n\n\n\n022\n\n\t\n\nSSI ZEBLEY RECONSIDERATION\n\n\n\n\n023\n\n\t\n\nSSI ZEBLEY HEARINGS & APPEALS\n\n\n\n\n024\n\n\t\n\nSSI ZEBLEY CDR\n\n\n\n\n025\n\n\t\n\nRSDI CHANGE OF PAYEE\n\n\n\n\n026\n\n\t\n\nSSI CHANGE OF PAYEE\n\n\n\n\n027\n\n\t\n\nRSDI R/P ACCOUNTING\n\n\n\n\n028\n\n\t\n\nSSI R/P ACCOUNTING\n\n\n\n\n029\n\n\t\n\nHI\n\n\n\n\n030\n\n\t\n\nSMI\n\n\n\n\n031\n\n\t\n\nRSDI PAYMENT AND CHECKS\n\n\n\n\n032\n\n\t\n\nSSI PAYMENT AND CHECKS\n\n\n\n\n033\n\n\t\n\nRSDI O/P ACTIONS/DECISIONS/COLLECTIONS\n\n\n\n\n034\n\n\t\n\nSSI O/P ACTIONS/DECISIONS/COLLECTIONS\n\n\n\n\n035\n\n\t\n\nEARNINGS DISCREPANCY\n\n\n\n\n036\n\n\t\n\nRSDI EARNINGS EFFECTUATION\n\n\n\n\n037\n\n\t\n\nSTUDENT ACTIONS\n\n\n\n\n038\n\n\t\n\nSSI CHANGE OF ADDRESS\n\n\n\n\n039\n\n\t\n\nASSISTANCE REQUEST\n\n\n\n\n040\n\n\t\n\nCLAIMS LEADS\n\n\n\n\n041\n\n\t\n\nCONGRESSIONAL INQUIRIES\n\n\n\n\n042\n\n\t\n\nATTORNEY WORKLOADS\n\n\n\n\n098\n\n\t\n\nOTHER RSDI CHANGES\n\n\n\n\n099\n\n\t\n\nOTHER SSI CHANGES\n\n4. \nElectronic 562\n\nThe electronic 562 is available in regions I through X and the Foreign Service Posts. Instructions for the completion and use of the electronic E562 are available here.\n\n5. \nManager-to-Manager (M2M) web application\n\nThe Manager-to-Manager web application is a two-way communication tool designed to provide a systematic process to address inquiries that require priority attention.  Managers in Field Offices, Processing Centers, and National 800 Number Network (N8NN) sites may initiate inquiries. Address all inquiries within five (5) business days. If you cannot complete a request within that time, provide an interim reply.\n\nUsing Manager-to-Manager to request PC assistance\n\nThe manager accesses the Manager-to-Manager application, located on the Management Resource Kit, based on PC jurisdiction. Within the application, each PC has its own webpage, with links set up according to that PC’s component protocol.\n\nThe manager follows the directions on the appropriate webpage and completes the web form. Click “SEND” to forward the request directly to a mailbox monitored by the appropriate PC component. The manager receives an acknowledgement of receipt from this mailbox.\n\na. \nLimiting requests from FOs to PCs\n\nYou should limit request from FOs to PCs to high priority requests, including:\n\n•\n\nTerminal illness (TERI cases) including any allegation of diagnosis of AIDS\n\n•\n\nHomicidal, suicide, or potentially violent behavior threats\n\n•\n\nDire need situations including eviction or homeless situations\n\n•\n\nCases with potential adverse public relations\n\n•\n\nThe third or subsequent follow-up development requests between managers as required by GN 01070.440\n\n•\n\nOther cases as required by POMS (e.g., Martinez cases, per GN 02613.865A.)\n\nb. \nLimiting requests from PCs to FOs\n\nYou should limit request from PCs to FOs to priority requests, including:\n\n•\n\nTerminal illness (TERI cases) including any allegation of diagnosis of AIDS\n\n•\n\nHomicidal, suicidal, or potentially violent behavior threats\n\n•\n\nDire need situations including eviction or homeless situations\n\n•\n\nCases with potential adverse public relations\n\n•\n\nHigh priority requests, as defined in GN 01070.400B.\n\n•\n\nThe third or subsequent follow-up development requests between managers, as required by GN 01070.440\n\nc. \nLimiting requests from N8NN sites to PCs or FOs\n\nYou should limit request from N8NN sites to PCs or FOs to priority requests, including:\n\n•\n\nTerminal illness (TERI cases), including any allegation of diagnosis of AIDS\n\n•\n\nHomicidal, suicidal, or potentially violent behavior threats\n\n•\n\nDire need situations including eviction or homeless situations\n\n•\n\nCases with potential adverse public relations\n\nNote: Limiting use to the situations listed in GN 01070.228A.5.a. through GN 01070.228A.5.c. ensures that we give proper attention to these critical cases.\n\nd. \nExamples of inappropriate manager-to-manager inquiries\n\nInappropriate manager-to-manger inquiries include:\n\n•\n\nRoutine contacts to fix coding on the MBR, (i.e., with no critical or dire need implications) including Death Information Processing System (DIPS) alerts\n\n•\n\nTo change address or bank data\n\n•\n\nTo release retro funds on Windfall offset cases unless they involve Dire Need or Public Relations issues \n\n•\n\nTo inquire about the status on previously submitted MDWs\n\n•\n\nTo inquire about the status of inquires on pending actions\n\n•\n\nTo request overpayment explanations or correction of overpayment amounts\n\n•\n\nTo request technical advice\n\n•\n\nTo process claims that have a future Month of Entitlement\n\nB. \nReferences\n\nRS 02801.000 - For a discussion of critical case criteria and exclusions",
            "span_sha256": "c0d3926884807efb8ec02655ecf877f76bb443fb90f2b63598c5f12e70c3e922"
          }
        ],
        "holds": [
          "Generic MDW versus APP_MDW_AI identity unresolved; no alias, edge or operational-state adoption.",
          "PCACS PSC-only request creation in GN228 and PCACS OR EP query in GN440 have separately stated actions; no date-based reconciliation or invented endpoint/permission.",
          "M2M priority/manager restrictions and no-communication gate remain; source228 five-business-day address-or-interim reply is not a completion SLA or substitute for440 stage intervals.",
          "Glossary DM/AD versus tables DM, ADM or DM, AD retained literally, no undocumented acronym repair.",
          "Calendar/business day units and original-request/prior-follow-up anchors remain; no actual workday/holiday calendar or day-zero convention supplied.",
          "No new source/native acceptance, source-version precedence, actual request/response/payment/case finding or successful rejoin."
        ],
        "negative_QA": [
          {
            "id": "N01",
            "case": "PC/TSC to FO versus FO/TSC to PC",
            "required_boundary": "Do not reverse requester and recipient by inferring symmetry."
          },
          {
            "id": "N02",
            "case": "C.2 fourth row",
            "required_boundary": "OM is requester and DM, AD recipient; preserve literal AD."
          },
          {
            "id": "N03",
            "case": "D.2 fourth row",
            "required_boundary": "DM, AD is requester and OM recipient; do not copy C.2 direction."
          },
          {
            "id": "N04",
            "case": "Glossary AD versus table ADM",
            "required_boundary": "Keep published codes; do not silently repair or infer exact role identity."
          },
          {
            "id": "N05",
            "case": "Routine/high-priority table",
            "required_boundary": "Do not import the Manager-to-Manager no-communication-only condition."
          },
          {
            "id": "N06",
            "case": "Manager-to-Manager communication after initial request",
            "required_boundary": "No automatic follow-up under the no-communication note."
          },
          {
            "id": "N07",
            "case": "Prior follow-up never occurred",
            "required_boundary": "No next-stage clock is established by reading a card."
          },
          {
            "id": "N08",
            "case": "Unknown initial date/work calendar",
            "required_boundary": "No due-date calculator, automatic Monday or holiday assumption."
          },
          {
            "id": "N09",
            "case": "60/30 or20/10/15 schedule",
            "required_boundary": "Calendar-day rules are not business-day rules or cumulative completion estimates."
          },
          {
            "id": "N10",
            "case": "5/3/2 Manager-to-Manager schedule",
            "required_boundary": "Business-day intervals remain stage-anchored; not a uniform five-day case SLA."
          },
          {
            "id": "N11",
            "case": "GN228 five-business-day address/interim reply",
            "required_boundary": "Do not equate the method-level address-or-interim rule with GN440 follow-up intervals or actual case completion."
          },
          {
            "id": "N12",
            "case": "Active REQ/EMFO found",
            "required_boundary": "Do not infer completion or a prescribed reset/suppression of follow-up."
          },
          {
            "id": "N13",
            "case": "PCACS OR EP",
            "required_boundary": "Do not require both or infer FO permission to create a PCACS assistance request."
          },
          {
            "id": "N14",
            "case": "MDW status inquiry",
            "required_boundary": "Do not equate generic MDW with MDW AI or automatically qualify an ordinary status inquiry for M2M."
          },
          {
            "id": "N15",
            "case": "Delay phone/email notification",
            "required_boundary": "Do not invent a new customer filing method, M2M mailbox address or completed delivery."
          },
          {
            "id": "N16",
            "case": "Unknown actual staff role or priority",
            "required_boundary": "Do not select the table or infer manager authority from a dropdown."
          },
          {
            "id": "N17",
            "case": "Source paragraph duplicated REQ/EMFO sentence",
            "required_boundary": "Preserve source observation; do not invent a second system or duplicate work-control action."
          },
          {
            "id": "N18",
            "case": "Changed parent/source/raw record/flow/card role",
            "required_boundary": "Future whole-chain/source/flow guard must reject without a generic metadata-ignore waiver."
          }
        ],
        "directed_source_rows": [
          {
            "full_route": "interoffice-assistance-followup/followup-c-1",
            "step_id": "followup-c-1-source-row-1",
            "table": "C.1",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "CA/CTE, BA/BTE",
              "recipient_as_published": "CR/SR",
              "when_as_published": "60 calendar days after initial request",
              "interval": {
                "value": 60,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 4628,
              "DOM_row_end": 5005,
              "DOM_row_sha256": "bc09783f3d5769f111e76eda0c730ba3fe8ae640ed780d317537295bd9524fc3"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CA/CTE, BA/BTE to CR/SR; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-1",
            "step_id": "followup-c-1-source-row-2",
            "table": "C.1",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "CA/CTE",
              "recipient_as_published": "CR/SR",
              "when_as_published": "30 calendar days after 1st F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 5005,
              "DOM_row_end": 5337,
              "DOM_row_sha256": "8bce3ec68b57c915235cfb269bfa6f0a3b496c07e866e9e2f776dcb5767b0184"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CA/CTE to CR/SR; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-1",
            "step_id": "followup-c-1-source-row-3",
            "table": "C.1",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "AMM, MM",
              "recipient_as_published": "DM, ADM",
              "when_as_published": "30 calendar days after 2nd F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 5337,
              "DOM_row_end": 5675,
              "DOM_row_sha256": "3bf7bc0d39e6f9d69e3168b17a07f93f70e61c31e82c8383e27b15aa6f25efbc"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s AMM, MM to DM, ADM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-1",
            "step_id": "followup-c-1-source-row-4",
            "table": "C.1",
            "source_row_exact": {
              "followup": "Fourth",
              "requester_as_published": "OM",
              "recipient_as_published": "DM",
              "when_as_published": "30 calendar days after 3rd F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 5675,
              "DOM_row_end": 5986,
              "DOM_row_sha256": "87a1e133c3528bb1c66ff8dd273b2759f332e6c2c8d06d90c3ed5e05b8020a7c"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s OM to DM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-2",
            "step_id": "followup-c-2-source-row-1",
            "table": "C.2",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "CA/CTE",
              "recipient_as_published": "CR/SR",
              "when_as_published": "20 calendar days after initial request",
              "interval": {
                "value": 20,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 6320,
              "DOM_row_end": 6673,
              "DOM_row_sha256": "a9b0e0212db9c83954b43fa0f720d79bf159c41ffe61d38b5688aa593d576b46"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CA/CTE to CR/SR; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-2",
            "step_id": "followup-c-2-source-row-2",
            "table": "C.2",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "AMM",
              "recipient_as_published": "OS",
              "when_as_published": "10 calendar days after 1st F/U",
              "interval": {
                "value": 10,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 6673,
              "DOM_row_end": 6987,
              "DOM_row_sha256": "a8d5390ef933864f070c623b5fd0187bf004ab638cd4a2d83695d2a3d459842f"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s AMM to OS; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-2",
            "step_id": "followup-c-2-source-row-3",
            "table": "C.2",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "MM",
              "recipient_as_published": "DM, ADM",
              "when_as_published": "15 calendar days after 2nd F/U",
              "interval": {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 6987,
              "DOM_row_end": 7310,
              "DOM_row_sha256": "d6aeeac66f5eb51c6edaf0c2f6b5180fc3596637356949a7248647ffebfb9941"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s MM to DM, ADM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-2",
            "step_id": "followup-c-2-source-row-4",
            "table": "C.2",
            "source_row_exact": {
              "followup": "Fourth",
              "requester_as_published": "OM",
              "recipient_as_published": "DM, AD",
              "when_as_published": "15 calendar days after 3rd F/U",
              "interval": {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 7310,
              "DOM_row_end": 7633,
              "DOM_row_sha256": "6074a5277fbdc7bfa06eef123de3f548890980c9c8311c7819842805eab49cdc"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s OM to DM, AD; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-3",
            "step_id": "followup-c-3-source-row-1",
            "table": "C.3",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "AMM, MM, US",
              "recipient_as_published": "DM, ADM",
              "when_as_published": "5 business days after initial request",
              "interval": {
                "value": 5,
                "day_kind": "business",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 8071,
              "DOM_row_end": 8442,
              "DOM_row_sha256": "56a5cea7c91a62c7e40181ef56b985a09e82afb194149d9708c51e77399f5f32"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-3",
            "step_id": "followup-c-3-source-row-2",
            "table": "C.3",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "AMM, MM, US",
              "recipient_as_published": "DM, ADM",
              "when_as_published": "3 business days after 1st F/U",
              "interval": {
                "value": 3,
                "day_kind": "business",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 8442,
              "DOM_row_end": 8792,
              "DOM_row_sha256": "b854f4789f35d4c8a7e0e704c905d747bb6650317a559b90999581f437ac4c8b"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-c-3",
            "step_id": "followup-c-3-source-row-3",
            "table": "C.3",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "OM, SM",
              "recipient_as_published": "AD, DAD",
              "when_as_published": "2 business days after 2nd F/U",
              "interval": {
                "value": 2,
                "day_kind": "business",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 8792,
              "DOM_row_end": 9124,
              "DOM_row_sha256": "a9709420f3ac520f7c44a692337cbaa072939e1afac7ff7efa42c9264f195b89"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-1",
            "step_id": "followup-d-1-source-row-1",
            "table": "D.1",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "CR/SR",
              "recipient_as_published": "CA/CTE, BA/BTE",
              "when_as_published": "60 calendar days after initial request",
              "interval": {
                "value": 60,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 9530,
              "DOM_row_end": 9907,
              "DOM_row_sha256": "966b2a72ffe21e1621b39ea92a2400da3e3946408113dcf67a6ca0a8631f3eb8"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CR/SR to CA/CTE, BA/BTE; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-1",
            "step_id": "followup-d-1-source-row-2",
            "table": "D.1",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "CR/SR",
              "recipient_as_published": "CA/CTE",
              "when_as_published": "30 calendar days after 1st F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 9907,
              "DOM_row_end": 10239,
              "DOM_row_sha256": "c8767462ffa13702bcbe1bfb19735b28c2a5597ed4cb0e9f6b648a816abe67e7"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CR/SR to CA/CTE; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-1",
            "step_id": "followup-d-1-source-row-3",
            "table": "D.1",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "DM, ADM",
              "recipient_as_published": "AMM, MM",
              "when_as_published": "30 calendar days after 2nd F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 10239,
              "DOM_row_end": 10577,
              "DOM_row_sha256": "6338f0720d4271183d6409c05cab27c5209666bc49439fc150351a3479fe8f41"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s DM, ADM to AMM, MM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-1",
            "step_id": "followup-d-1-source-row-4",
            "table": "D.1",
            "source_row_exact": {
              "followup": "Fourth",
              "requester_as_published": "DM",
              "recipient_as_published": "OM",
              "when_as_published": "30 calendar days after 3rd F/U",
              "interval": {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 10577,
              "DOM_row_end": 10888,
              "DOM_row_sha256": "469cf0d4fe6dd96b4a66be21fc09f5c2972c2fa024c43c31052119b97137cbfc"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s DM to OM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-2",
            "step_id": "followup-d-2-source-row-1",
            "table": "D.2",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "CR, SR",
              "recipient_as_published": "CA/CTE",
              "when_as_published": "20 calendar days after initial request",
              "interval": {
                "value": 20,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 11222,
              "DOM_row_end": 11578,
              "DOM_row_sha256": "ca8b58ded703cf16847fb45ebfec46531bee866640b1c091a15a700496ada2d6"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s CR, SR to CA/CTE; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-2",
            "step_id": "followup-d-2-source-row-2",
            "table": "D.2",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "OS",
              "recipient_as_published": "AMM",
              "when_as_published": "10 calendar days after 1st F/U",
              "interval": {
                "value": 10,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 11578,
              "DOM_row_end": 11892,
              "DOM_row_sha256": "57b0e4c0dfa2e0d724eb46ce30e1932bdb1d3a4e7743e60fa30759ccdfaa6274"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s OS to AMM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-2",
            "step_id": "followup-d-2-source-row-3",
            "table": "D.2",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "DM, ADM",
              "recipient_as_published": "MM",
              "when_as_published": "15 calendar days after 2nd F/U",
              "interval": {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 11892,
              "DOM_row_end": 12215,
              "DOM_row_sha256": "b14a0ae68216c07fc7abb2b51d5c969af69b6345155e687e73ab2a5f0d53a990"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s DM, ADM to MM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-2",
            "step_id": "followup-d-2-source-row-4",
            "table": "D.2",
            "source_row_exact": {
              "followup": "Fourth",
              "requester_as_published": "DM, AD",
              "recipient_as_published": "OM",
              "when_as_published": "15 calendar days after 3rd F/U",
              "interval": {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 12215,
              "DOM_row_end": 12538,
              "DOM_row_sha256": "63632eab4887b28076822e921131db1b774b11292fd2c473a0b2299685259c39"
            },
            "actual_stage_condition": "The applicable requester and recipient roles are the source row’s DM, AD to OM; their actual role context must be established."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-3",
            "step_id": "followup-d-3-source-row-1",
            "table": "D.3",
            "source_row_exact": {
              "followup": "First",
              "requester_as_published": "DM, ADM, US",
              "recipient_as_published": "AMM, MM",
              "when_as_published": "5 business days after initial request",
              "interval": {
                "value": 5,
                "day_kind": "business",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 13144,
              "DOM_row_end": 13515,
              "DOM_row_sha256": "a4626f233c2add08f5f4259e39b04d5f75653fc659f331b5245f888fc23c4fb6"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-3",
            "step_id": "followup-d-3-source-row-2",
            "table": "D.3",
            "source_row_exact": {
              "followup": "Second",
              "requester_as_published": "DM, ADM, US",
              "recipient_as_published": "AMM,MM",
              "when_as_published": "3 business days after 1st F/U",
              "interval": {
                "value": 3,
                "day_kind": "business",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 13515,
              "DOM_row_end": 13862,
              "DOM_row_sha256": "3c81c79d0e383bebd1a82666527e88eb88e3e5e49dedc87e5cb50695502782f4"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          },
          {
            "full_route": "interoffice-assistance-followup/followup-d-3",
            "step_id": "followup-d-3-source-row-3",
            "table": "D.3",
            "source_row_exact": {
              "followup": "Third",
              "requester_as_published": "AD, DAD, SM",
              "recipient_as_published": "OM",
              "when_as_published": "2 business days after 2nd F/U",
              "interval": {
                "value": 2,
                "day_kind": "business",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              "DOM_row_start": 13862,
              "DOM_row_end": 14194,
              "DOM_row_sha256": "8b79b8c97c206eb66c455c569e1e69d245571015efd1e931cea2cd6ccabba531"
            },
            "actual_stage_condition": "There has been no communication after the first request, as required by this Manager-to-Manager note."
          }
        ],
        "route_preparation_timing_actor_profiles": {
          "interoffice-assistance-followup/followup-c-1": {
            "preparation": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Routine requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "source_numeric_intervals": [
              {
                "value": 60,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "PC/TSC to FO",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed Routine requests follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-c-2": {
            "preparation": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the High priority requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "source_numeric_intervals": [
              {
                "value": 20,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 10,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "PC/TSC to FO",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed High priority requests follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-c-3": {
            "preparation": [
              "Established assistance direction is PC/TSC to FO.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
              "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility."
            ],
            "source_numeric_intervals": [
              {
                "value": 5,
                "day_kind": "business",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 3,
                "day_kind": "business",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 2,
                "day_kind": "business",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "PC/TSC to FO",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed Manager to Manager follow-up references for PC/TSC to FO; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-1": {
            "preparation": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Routine requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "source_numeric_intervals": [
              {
                "value": 60,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 30,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "FO/TSC to PC",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed Routine requests follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-2": {
            "preparation": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the High priority requests table and applicable staff-role context.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up."
            ],
            "source_numeric_intervals": [
              {
                "value": 20,
                "day_kind": "calendar",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 10,
                "day_kind": "calendar",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 15,
                "day_kind": "calendar",
                "anchor_as_published": "3rd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "FO/TSC to PC",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed High priority requests follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d-3": {
            "preparation": [
              "Established assistance direction is FO/TSC to PC.",
              "The request is within the Manager to Manager table and applicable staff-role context.",
              "The source no-communication-after-first-request condition is established; applicable M2M authorization/priority context must also be established.",
              "The actual request, applicable follow-up stage, source requester/recipient roles and stated time anchor must be established. Selecting this table does not establish an initial request or earlier follow-up.",
              "Manager authority and the applicable source method/priority restrictions must be established separately. An ordinary status inquiry alone does not establish Manager-to-Manager eligibility."
            ],
            "source_numeric_intervals": [
              {
                "value": 5,
                "day_kind": "business",
                "anchor_as_published": "initial request",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 3,
                "day_kind": "business",
                "anchor_as_published": "1st F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              },
              {
                "value": 2,
                "day_kind": "business",
                "anchor_as_published": "2nd F/U",
                "kind": "published_followup_schedule_not_casecompletion_SLA"
              }
            ],
            "published_direction": "FO/TSC to PC",
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Prescribed Manager to Manager follow-up references for FO/TSC to PC; source rows are not measured completion times.",
            "ordered_actor_labels": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-d3-active-req-emfo-query": {
            "preparation": [
              "FO/TSC-to-PC Manager-to-Manager D.3 context applies.",
              "The source no-communication condition and applicable row/staff prerequisites are established.",
              "The actual Manager-to-Manager method/priority and staff-authority prerequisites are established; this example grants no access or permissions."
            ],
            "source_numeric_intervals": [],
            "published_direction": null,
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Published follow-up references only; no measured duration or calculated customer deadline.",
            "ordered_actor_labels": [
              "SSA staff"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          },
          "interoffice-assistance-followup/followup-delay-two-way-communication": {
            "preparation": [
              "A receiving FO or PC anticipates delay, or the request cannot be answered within the prescribed follow-up timeframe."
            ],
            "source_numeric_intervals": [],
            "published_direction": null,
            "source_rows_not_automatic_clock_or_actual_completion": true,
            "original_timing_exact": "Published follow-up references only; no measured duration or calculated customer deadline.",
            "ordered_actor_labels": [
              "Receiving FO or PC",
              "SSA staff",
              "Receiving FO or PC"
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual staff authority, request/follow-up dates, communication, query status, response and successful return remain unverified."
              ]
            }
          }
        },
        "revision": {
          "prior_package_sha256": "465035e9aaa45dc640809b3fbf437f9f94b993f0ae21ed8a9781a28037a6ca26",
          "source_role_preservation": "The actual engine safe-label schema rejects comma-containing role lists. Use generic SSA staff actor badge, retain exact requester/recipient codes in each visible action and explicit source-role condition. All22 exact source rows/actions/intervals/directions/raw records/source objects unchanged; no actor-code alias or shared schema change."
        }
      }
    },
    "source_reviews": {
      "wage10": {
        "source_package_sha256": "f2efad3511c554ff5b39f758b2f2e99246d562c5606759f02c18906710cb76ca",
        "independent_source_review_sha256": "0ef95bf2bac35aa33a21aaefd5aaa71fb8d43a860a4d2009fa8e241ddbe6427b"
      },
      "followup8": {
        "source_package_sha256": "eb383de569e24ca060caec143bebe75216ba02204b809013726154c5140b5b22",
        "independent_source_review_sha256": "9ac4ac4cbf9593e20eb3c884a3623196575fd239f43211a97a19112fead6e524"
      }
    },
    "public_capture_provenance": [
      {
        "url": "/service/sources/wage10-SI00820.135-AX.txt",
        "sha256": "845b38c93b2efc3bd4bbeca49eb2d0b6df779b792608d03c5615b9b6a40faed3",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.135-DOM.json",
        "sha256": "cf775d8945eec6b7472148dfb5c3f567a3bae1d9a271355bf863581319851794",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.135-main.txt",
        "sha256": "8e1f21256f41cc91db051a6d1b7d173895a67e82735d3893ed535a1905c7a2ce",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.147-AX.txt",
        "sha256": "552afc8372eca97ae5e3294352cd1c5c66ae09b62c8a0ba11e452a97eba66365",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.147-DOM.json",
        "sha256": "ff428e0943b60785ca3bb041883293b61548333f2201a8d80bf36c9eda33e8e3",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.147-main.txt",
        "sha256": "cb85962f69b7a64e9648855f6a89b5ca0e16da5b7308e5fbe61cd3562803fc62",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.148-AX.txt",
        "sha256": "0be215a98244d3703aab491c83d93ec28e5b4bbb8f3160a277679424b9d2fef3",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.148-DOM.json",
        "sha256": "d4f4d1c21a9194e4cacf564656bbddd937d4b9567890b0f586b714737ad4c5cb",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/wage10-SI00820.148-main.txt",
        "sha256": "5bae78f69af7672dd235f696591064cf92597242f268af7f3bd45d6e37f14977",
        "capture_type": "Root actual IAB whole DIV#content role=main innerText and parsed DOM outerHTML/links/tables, AX and metadata. Not raw HTTP response bytes."
      },
      {
        "url": "/service/sources/followup8-dom.txt",
        "sha256": "c0f2290d53785266489d9b2e3f453f3a19f01f9bf6634dc6cd6175eb656420d2",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot for GN440; GN228 rendered main plus serialized parsed DOM. Neither is asserted raw HTTP."
      },
      {
        "url": "/service/sources/followup8-main.txt",
        "sha256": "b8a97eb8640994848a9da7966e93e2d77ed4e0f9017a87db82571747e30c4d10",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot for GN440; GN228 rendered main plus serialized parsed DOM. Neither is asserted raw HTTP."
      },
      {
        "url": "/service/sources/followup8-GN01070.228-main.txt",
        "sha256": "c0d3926884807efb8ec02655ecf877f76bb443fb90f2b63598c5f12e70c3e922",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot for GN440; GN228 rendered main plus serialized parsed DOM. Neither is asserted raw HTTP."
      },
      {
        "url": "/service/sources/followup8-GN01070.228-parsed-dom.html.txt",
        "sha256": "0598d5fcad3d1e66d630cc86bcf99d3a279816ef24243b95d27116f0369835cc",
        "capture_type": "Actual IAB rendered main text and DOM/accessibility snapshot for GN440; GN228 rendered main plus serialized parsed DOM. Neither is asserted raw HTTP."
      }
    ],
    "limits": [
      "Source follow-up intervals are prescribed staff references, not measured processing times or service guarantees.",
      "Actual facts, permission, completed actions and return to the usual path are not established by selecting an example.",
      "All inherited source histories, comparison holds and unmatched states remain unchanged."
    ],
    "no_new_native_links_or_acceptance": true
  },
  "r30_next21": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "TWENTY_ONE_SELECTED_EXISTING_SEQUENCES_SOURCE_REVIEWED_NOT_WHOLE_POLICY_OR_CASE_FINDING",
    "selected_flow_count": 21,
    "checked_on": "2026-11-01",
    "packages": {
      "CDB9": {
        "flows": {
          "childhood-disability-intake/cdb-own-record-insured": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-own-record-insured",
            "full_route": "childhood-disability-intake/cdb-own-record-insured",
            "entry_conditions": [
              "The CDB claimant has worked; possible entitlement on the claimant’s own SSN must be considered."
            ],
            "steps": [
              {
                "id": "cdb-own-record-insured-source-1",
                "title": "Consider the claimant’s own work record",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Consider possible entitlement on the claimant’s own SSN. Use DISCO or ICERS to check possible insured status.",
                "conditions": [
                  "The CDB claimant has worked; possible entitlement on the claimant’s own SSN must be considered."
                ],
                "source": "cdbdevelopment",
                "section": "A.3",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "Possible insured status is being examined; this is not a finding that insured status or entitlement is met.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-own-record-insured-source-2",
                "title": "Use a certified record for noninsured documentation",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Do not use DISCO to document noninsured status on any SSN. A certified earnings record, such as one from ICERS, is required under the linked instruction.",
                "conditions": [
                  "The CDB claimant has worked; possible entitlement on the claimant’s own SSN must be considered."
                ],
                "source": "cdbdevelopment",
                "section": "A.3",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "Only the negative-status documentation restriction is established here; the detailed GN 01010.440 procedure remains separately scoped.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-intake/cdb-erroneous-age18-termination": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-erroneous-age18-termination",
            "full_route": "childhood-disability-intake/cdb-erroneous-age18-termination",
            "entry_conditions": [
              "The child’s benefits were erroneously terminated while a childhood disability determination is pending under B.5.",
              "Student entitlement is separately governed; this example does not determine entitlement or a disability outcome."
            ],
            "steps": [
              {
                "id": "cdb-erroneous-age18-termination-source-1",
                "title": "Notify the processing center",
                "kind": "action",
                "actor": "FO",
                "action": "Notify the processing center and instruct its BA/BTE to place the child in suspense effective with the month of attaining age 18, pending the disability determination.",
                "conditions": [
                  "The child’s benefits were erroneously terminated while a childhood disability determination is pending under B.5.",
                  "Student entitlement is separately governed; this example does not determine entitlement or a disability outcome."
                ],
                "source": "cdbdevelopment",
                "section": "B.5.a",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The source assigns notification to the field office and the suspension input to the processing center.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-erroneous-age18-termination-source-2",
                "title": "Record the pending suspension",
                "kind": "action",
                "actor": "PC BA/BTE",
                "action": "Input the suspension action, the appropriate reason for suspension or termination, and any necessary diary.",
                "conditions": [
                  "The child’s benefits were erroneously terminated while a childhood disability determination is pending under B.5.",
                  "Student entitlement is separately governed; this example does not determine entitlement or a disability outcome."
                ],
                "source": "cdbdevelopment",
                "section": "B.5.b",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "A pending-status correction does not establish disability or that the input has occurred.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-erroneous-age18-termination-source-3",
                "title": "Keep related benefits conditional",
                "kind": "action",
                "actor": "PC BA/BTE",
                "action": "If other beneficiaries are involved, do not adjust their benefits upward pending the disability determination. Do not notify the payee if the suspension does not affect the amount paid because of the number of beneficiaries in the household.",
                "conditions": [
                  "The child’s benefits were erroneously terminated while a childhood disability determination is pending under B.5.",
                  "Student entitlement is separately governed; this example does not determine entitlement or a disability outcome."
                ],
                "source": "cdbdevelopment",
                "section": "B.5.b",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The amount-unaffected condition qualifies the payee-notification instruction; it is not a blanket no-notice rule.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-intake/cdb-pending-partial-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-pending-partial-notice",
            "full_route": "childhood-disability-intake/cdb-pending-partial-notice",
            "entry_conditions": [
              "The initial child award concerns entitlement before age 18 and a CDB determination remains pending under B.2.a.",
              "An existing student-entitlement case has the separate B.1 suspension restriction; the partial award does not establish disability."
            ],
            "steps": [
              {
                "id": "cdb-pending-partial-notice-source-1",
                "title": "Distinguish the partial award from the pending issue",
                "kind": "action",
                "actor": "FO",
                "action": "The claim can be processed as a partial award in the field office under the linked award procedures. Advise in the award notice that the CDB claim is pending.",
                "conditions": [
                  "The initial child award concerns entitlement before age 18 and a CDB determination remains pending under B.2.a.",
                  "An existing student-entitlement case has the separate B.1 suspension restriction; the partial award does not establish disability."
                ],
                "source": "cdbdevelopment",
                "section": "B.2.a; B.1 separately scoped qualification",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "Detailed award and notice-text instructions are linked procedures, not fully supplied by this page.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established.",
                  "Separate B.1 post-entitlement qualification: a child already entitled as a student is not subject to that pending-disability suspension instruction. This restriction is not a second sequential action in the B.2.a initial partial-award procedure."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-intake/cdb-ddib-diary-fallback": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-ddib-diary-fallback",
            "full_route": "childhood-disability-intake/cdb-ddib-diary-fallback",
            "entry_conditions": [
              "The B.2 pending CDB initial-award situation applies before age 18.",
              "The DDIB process cannot be used; that failure condition is required for the processing-center diary fallback."
            ],
            "steps": [
              {
                "id": "cdb-ddib-diary-fallback-source-1",
                "title": "Use the specified diary fallback",
                "kind": "action",
                "actor": "PC",
                "action": "When DDIB cannot be used, establish a diary for the first day of the month before the month the child attains age 18, for possible CDB payment.",
                "conditions": [
                  "The B.2 pending CDB initial-award situation applies before age 18.",
                  "The DDIB process cannot be used; that failure condition is required for the processing-center diary fallback."
                ],
                "source": "cdbdevelopment",
                "section": "B.2.b exception",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The source also permits DDIB entry as early as age 17; this fallback is conditional on DDIB being unusable and is not a customer filing deadline.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-ddib-diary-fallback-source-2",
                "title": "Describe what remains pending",
                "kind": "action",
                "actor": "PC",
                "action": "Annotate the diary: CDB determination pending (month, year), age 18 attainment.",
                "conditions": [
                  "The B.2 pending CDB initial-award situation applies before age 18.",
                  "The DDIB process cannot be used; that failure condition is required for the processing-center diary fallback."
                ],
                "source": "cdbdevelopment",
                "section": "B.2.b exception",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The annotation is an internal control; it does not establish entitlement, successful input or a payment date. Linked full-time-student exceptions remain separately scoped.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-intake/cdb-reapplication-pc-pending": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-reapplication-pc-pending",
            "full_route": "childhood-disability-intake/cdb-reapplication-pc-pending",
            "entry_conditions": [
              "The child reapplies within four years of termination and alleges disability before termination."
            ],
            "steps": [
              {
                "id": "cdb-reapplication-pc-pending-source-1",
                "title": "Tell the processing center the determination is pending",
                "kind": "action",
                "actor": "FO",
                "action": "Notify the processing center using the appropriate method: a Modernized Development Worksheet or fax into its paperless queue, stating that the disability determination is pending.",
                "conditions": [
                  "The child reapplies within four years of termination and alleges disability before termination."
                ],
                "source": "cdbdevelopment",
                "section": "B.3",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The four-year condition identifies this instruction; it does not decide entitlement or establish a processing duration. Generic MDW is not an adopted identity for an AI application.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-after-dds/cdb-denial-pc-related-notices": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-denial-pc-related-notices",
            "full_route": "childhood-disability-after-dds/cdb-denial-pc-related-notices",
            "entry_conditions": [
              "The processing center is handling a childhood disability denial under E.1; current benefit and student-entitlement status must be established."
            ],
            "steps": [
              {
                "id": "cdb-denial-pc-related-notices-source-1",
                "title": "Apply the conditional benefit actions",
                "kind": "action",
                "actor": "PC",
                "action": "Terminate benefits if they have not already been terminated, unless student entitlement applies, and adjust other benefits affected by the termination.",
                "conditions": [
                  "The processing center is handling a childhood disability denial under E.1; current benefit and student-entitlement status must be established."
                ],
                "source": "cdbdevelopment",
                "section": "E.1",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The instruction is conditional staff handling after a denial, not an actual determination or proof that payments have changed.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-denial-pc-related-notices-source-2",
                "title": "Send the applicable notices",
                "kind": "action",
                "actor": "PC",
                "action": "Send an adjustment notice to affected auxiliaries and a termination notice to the CDB beneficiary if the beneficiary is in suspense.",
                "conditions": [
                  "The processing center is handling a childhood disability denial under E.1; current benefit and student-entitlement status must be established."
                ],
                "source": "cdbdevelopment",
                "section": "E.1",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The suspense condition qualifies the CDB termination notice; other notice requirements are not waived.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-after-dds/cdb-age18-automatic-conversion-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-age18-automatic-conversion-notice",
            "full_route": "childhood-disability-after-dds/cdb-age18-automatic-conversion-notice",
            "entry_conditions": [
              "At least one source E.2.b purpose applies: the disability determination was made to entitle a mother, father or young spouse, OR to continue the child’s benefits past age 18 as CDB.",
              "Disability is indicated in the MBR BENE ENT line; choosing this example does not establish that record fact."
            ],
            "steps": [
              {
                "id": "cdb-age18-automatic-conversion-notice-source-1",
                "title": "Record the disability determination for continuation",
                "kind": "action",
                "actor": "PC",
                "action": "Make the appropriate record inputs, including posting the disability determination in the MBR BENE ENT line to enable conversion. Apply the separately conditional resumption, reinstatement and diary-cancellation actions only where their source conditions apply.",
                "conditions": [
                  "At least one source E.2.b purpose applies: the disability determination was made to entitle a mother, father or young spouse, OR to continue the child’s benefits past age 18 as CDB.",
                  "Disability is indicated in the MBR BENE ENT line; choosing this example does not establish that record fact."
                ],
                "source": "cdbdevelopment",
                "section": "E.2.a",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The selected page describes conditions and inputs; it does not prove that a record was updated or payment continued.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-age18-automatic-conversion-notice-source-2",
                "title": "Keep the notice distinction",
                "kind": "action",
                "actor": "PC",
                "action": "With disability indicated in the BENE ENT line, benefits automatically continue at age 18 in the specified case. No special notice is required solely upon attaining age 18; the source also directs staff to send the appropriate notice under NL 00703.000.",
                "conditions": [
                  "At least one source E.2.b purpose applies: the disability determination was made to entitle a mother, father or young spouse, OR to continue the child’s benefits past age 18 as CDB.",
                  "Disability is indicated in the MBR BENE ENT line; choosing this example does not establish that record fact."
                ],
                "source": "cdbdevelopment",
                "section": "E.2.b",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "Do not read the no-special-age-18-notice statement as waiving other determination or payment notices. Detailed notice text and system inputs remain linked scope.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "childhood-disability-after-dds/cdb-manual-initial-award-all-requirements": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cdb-manual-initial-award-all-requirements",
            "full_route": "childhood-disability-after-dds/cdb-manual-initial-award-all-requirements",
            "entry_conditions": [
              "All entitlement requirements are satisfied, the child was not previously entitled, and automated processing is not possible.",
              "A favorable disability finding alone does not establish these other conditions."
            ],
            "steps": [
              {
                "id": "cdb-manual-initial-award-all-requirements-source-1",
                "title": "Prepare the conditional manual initial award",
                "kind": "action",
                "actor": "PC",
                "action": "Prepare and review the EF-101 under existing procedures if necessary for this initial-award situation.",
                "conditions": [
                  "All entitlement requirements are satisfied, the child was not previously entitled, and automated processing is not possible.",
                  "A favorable disability finding alone does not establish these other conditions."
                ],
                "source": "cdbdevelopment",
                "section": "F.2",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "The linked detailed EF-101 procedure is not supplied here. This does not establish that an award was processed or paid.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              },
              {
                "id": "cdb-manual-initial-award-all-requirements-source-2",
                "title": "Keep capability and payment arrangements separate",
                "kind": "action",
                "actor": "PC",
                "action": "Direct payment applies to a CDB beneficiary capable of managing payments in their own interest. If medical or other evidence raises capability, follow the linked capability-development instructions.",
                "conditions": [
                  "All entitlement requirements are satisfied, the child was not previously entitled, and automated processing is not possible.",
                  "A favorable disability finding alone does not establish these other conditions."
                ],
                "source": "cdbdevelopment",
                "section": "F.2",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "F.2 separately directs conversion for a previously entitled child; that is not an action in this never-previously-entitled initial-award example. Do not decide capability or appoint a payee from this illustration.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          },
          "disabled-child-in-care-review/cic-physical-mental-remarks": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "cic-physical-mental-remarks",
            "full_route": "disabled-child-in-care-review/cic-physical-mental-remarks",
            "entry_conditions": [
              "A disability determination is necessary for a child age 15 or older to entitle or continue benefits to a mother, father or young spouse.",
              "Both physical and mental impairments are alleged."
            ],
            "steps": [
              {
                "id": "cic-physical-mental-remarks-source-1",
                "title": "Flag the child-in-care question for DDS",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Enter child-in-care in the remarks section of EDCS 3367. This alerts DDS to identify in remarks a documented mental impairment that is not shown as the primary or secondary impairment.",
                "conditions": [
                  "A disability determination is necessary for a child age 15 or older to entitle or continue benefits to a mother, father or young spouse.",
                  "Both physical and mental impairments are alleged."
                ],
                "source": "cdbdevelopment",
                "section": "A.5",
                "source_context_refs": [
                  "RS00203.085:whole"
                ],
                "qualifications": [
                  "This is a conditional information handoff, not a child-in-care entitlement finding or certification of a current system interface. Linked DI 11020.060 and DI 23505.001 remain separately scoped.",
                  "Prescribed staff instruction only; no actual case action, permission, payment or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected record does not establish actual completion or a successful return to the usual case path. Linked entitlement, system, notice and capability procedures remain separately scoped."
              ]
            }
          }
        },
        "original_records": {
          "childhood-disability-intake/cdb-own-record-insured": {
            "id": "cdb-own-record-insured",
            "title": "The CDB claimant worked on their own record",
            "when": "A CDB applicant has work history.",
            "you": "Identify prior work.",
            "ssa": "Consider own-record entitlement; check possible insured status with DISCO or ICERS. Noninsured status requires a certified earnings record, not DISCO alone.",
            "route": "FO own-record insured-status review",
            "next": "Staff obtains the required record; this is not a customer-created certificate or an eligibility result.",
            "source": "cdbdevelopment",
            "section": "A.3",
            "timing": "No end-to-end processing duration specified",
            "review_status": "Selected conditional staff procedure checked; full linked policy remains"
          },
          "childhood-disability-intake/cdb-erroneous-age18-termination": {
            "id": "cdb-erroneous-age18-termination",
            "title": "Benefits ended erroneously while the CDB decision is pending",
            "when": "The B.5 pending-disability correction situation applies.",
            "you": "Identify the termination and pending claim.",
            "ssa": "FO notifies PC; BA/BTE places the child in suspense effective with the month of attaining age 18, inputs the suspension reason and any needed diary. Do not increase other beneficiaries pending the determination.",
            "route": "FO → PC BA/BTE",
            "next": "This corrects pending status, not the disability outcome. Student entitlement has separate continuation rules.",
            "source": "cdbdevelopment",
            "section": "B.5",
            "timing": "No end-to-end processing duration specified",
            "review_status": "Selected conditional staff procedure checked; full linked policy remains"
          },
          "childhood-disability-intake/cdb-pending-partial-notice": {
            "id": "cdb-pending-partial-notice",
            "title": "An initial child award precedes the disability decision",
            "when": "Initial entitlement before18; CDB determination pending.",
            "you": "Keep the award notice.",
            "ssa": "FO may process a partial award; the award notice identifies CDB as pending. Existing student entitlement is not suspended under B.1.",
            "route": "FO award processing",
            "next": "Read the notice for the decided and pending issues. A partial award does not establish disability.",
            "source": "cdbdevelopment",
            "section": "B.1; B.2.a",
            "timing": "No decision duration specified",
            "review_status": "Selected official subsection checked; linked eligibility and detailed systems instructions remain separately scoped"
          },
          "childhood-disability-intake/cdb-ddib-diary-fallback": {
            "id": "cdb-ddib-diary-fallback",
            "title": "Staff cannot use the DDIB process before age18",
            "when": "CDB determination pending as age18 approaches.",
            "you": "Ask SSA about the pending disability issue.",
            "ssa": "DDIB input can begin at17 to prevent age18 termination. If unavailable, PC sets a diary for the first day of the preceding month, noting pending determination and age18 attainment.",
            "route": "FO → PC diary fallback",
            "next": "The diary is an internal control, not your filing deadline or a payment promise.",
            "source": "cdbdevelopment",
            "section": "B.2.b",
            "timing": "First day of month before age18 attainment month; student exception separately applies",
            "review_status": "Selected official subsection checked; linked eligibility and detailed systems instructions remain separately scoped"
          },
          "childhood-disability-intake/cdb-reapplication-pc-pending": {
            "id": "cdb-reapplication-pc-pending",
            "title": "A prior child beneficiary reapplies and disability is pending",
            "when": "Reapplication within four years of termination; disability alleged before termination.",
            "you": "Give SSA the prior termination date and alleged disability onset.",
            "ssa": "FO informs PC that the disability determination is pending, using MDW or fax to the PC paperless queue.",
            "route": "FO → PC pending-issue notification",
            "next": "Ask SSA which issue remains. This staff notification is separate from a customer decision notice.",
            "source": "cdbdevelopment",
            "section": "B.3",
            "timing": "Four years identifies this procedure; no processing duration specified",
            "review_status": "Official subsection checked; entitlement and application-scope rules remain separate"
          },
          "childhood-disability-after-dds/cdb-denial-pc-related-notices": {
            "id": "cdb-denial-pc-related-notices",
            "title": "A CDB denial also affects other beneficiaries",
            "when": "PC receives a disability denial; current entitlement status matters.",
            "you": "Read each affected beneficiary notice.",
            "ssa": "PC terminates benefits if needed unless student entitlement applies, adjusts affected benefits, and sends adjustment notices to auxiliaries plus a termination notice to the CDB beneficiary if in suspense.",
            "route": "PC benefit adjustment and notices",
            "next": "Different affected beneficiaries may receive different notices.",
            "source": "cdbdevelopment",
            "section": "E.1",
            "timing": "No notice-delivery duration specified",
            "review_status": "Selected conditional notice procedure checked; individual entitlement not determined"
          },
          "childhood-disability-after-dds/cdb-age18-automatic-conversion-notice": {
            "id": "cdb-age18-automatic-conversion-notice",
            "title": "The disability record supports automatic continuation at 18",
            "when": "A child’s disability determination supports the specified continuation case, including a determination made for a mother, father or young spouse’s entitlement, and disability is recorded in the MBR BENE ENT line.",
            "you": "Keep SSA’s determination and payment notices. Ask SSA to check the recorded disability determination if continuation is unclear.",
            "ssa": "The processing center makes the appropriate record inputs to enable conversion. RS 00203.085 E.2.b provides for automatic continuation at age 18 when disability is indicated on the BENE ENT line. It says no special notice is required solely upon attaining age 18, while also directing staff to send the appropriate notice under NL 00703.000. This does not waive other determination or payment notices.",
            "route": "Processing center disability-record input and supported age-18 continuation",
            "next": "The recorded determination can support continuation without a separate special age-18 notice. Unresolved eligibility, payee or manual-payment actions still require their own review.",
            "source": "cdbdevelopment",
            "section": "E.2.a–b",
            "timing": "Age 18 is the conversion event in this conditional instruction; no processing or notice-delivery duration is specified.",
            "review_status": "Selected record/notice distinction independently checked; detailed SM inputs and notice text not independently reviewed."
          },
          "childhood-disability-after-dds/cdb-manual-initial-award-all-requirements": {
            "id": "cdb-manual-initial-award-all-requirements",
            "title": "An initial CDB award cannot be processed automatically",
            "when": "All entitlement requirements are satisfied, the child was not previously entitled, and automated processing is unavailable.",
            "you": "Respond to any outstanding SSA requests and ask which component owns the remaining award action.",
            "ssa": "Under RS 00203.085 F.2, the processing center prepares and reviews the EF-101 under existing procedures if necessary for this initial-award situation. The same subsection distinguishes a previously entitled child, whose benefits are converted to CDB. It provides for direct payment to a capable beneficiary and separate capability development if medical or other evidence raises that issue.",
            "route": "Processing center manual initial-award preparation/review or prior-entitlement conversion",
            "next": "A favorable disability finding alone does not establish that every entitlement requirement is met or that payment has been effectuated. Capability and payment arrangement remain separate questions.",
            "source": "cdbdevelopment",
            "section": "F.2",
            "timing": "No manual-award completion duration or payment date is specified.",
            "review_status": "Selected all-requirements and manual-processing gates independently checked; detailed EF-101 preparation and entitlement requirements remain outside this branch."
          },
          "disabled-child-in-care-review/cic-physical-mental-remarks": {
            "id": "cic-physical-mental-remarks",
            "title": "Both physical and mental impairments are alleged",
            "when": "A child age 15 or older needs the cited disability determination for a mother/father or young-spouse benefit.",
            "you": "Describe both kinds of impairment.",
            "ssa": "Enter child-in-care in EDCS-3367 remarks to alert DDS to identify a documented mental impairment not shown as primary or secondary.",
            "route": "FO EDCS remarks → DDS",
            "next": "The handoff supports the medical question; it does not itself establish child-in-care entitlement.",
            "source": "cdbdevelopment",
            "section": "A.5",
            "timing": "No end-to-end processing duration specified",
            "review_status": "Selected conditional staff procedure checked; full linked policy remains"
          }
        },
        "source_contexts": [
          {
            "id": "RS00203.085:whole",
            "start": 0,
            "end": 13849,
            "exact_text": "Effective Dates: 01/31/2023 - Present\nPrevious | Next\n\nTN 46 (01-26)\n\nRS 00203.085 Childhood Disability Development and Determination\nA. \nProcedure - general\n1. \nDisability development\n\nComplete development instructions for childhood disability benefit (CDB) cases are located in DI 11020.000.\n\nConsider re-entitlement via expedited reinstatement (DI 13050.000) if the childs previous CDB entitlement ended due to their own work activity.\n\nCAUTION: Disability development does not have to be undertaken if the dependency or relationship requirements are not met or the number holder (NH) was not insured. Follow DI 11020.050, Field Office (FO) Authorization of Childhood Disability Benefits (CDB) Involving Substantial Gainful Activity (SGA), and Technical Denials, when the CDB claim does not require a disability determination.\n\nREMINDER: Follow GN 00204.022 on when to explore entitlement on another earnings record and DI 13010.500 on when to use the Disability Control File (DCF).\n\n2. \nElectronic Disability Collect System (EDCS) Processing\n\nThe FO will complete the case in EDCS unless an exclusion exists and will transfer the claim to the Disability Determination Services (DDS). See DI 81010.030A. The claim will be accessible in eView or the Evidence Portal (EP), which allows the user to check the status of the claim. Messages and case updates can be added through the EDCS program and will be posted in eView or the EP. For example, claimant can only be reached after 5 p.m.\n\n3. \nInsured status\n\nAlways consider the possibility of entitlement on the CDBs own SSN if they worked. Use the Disability Insured Status Calculator Online (DISCO) or the Informational Certified Earnings Record System (ICERS) to verify possible insured status.\n\nNOTE: Remarks can be entered in EDCS so they are readily available to the DDS in eView or the EP.\n\nIMPORTANT: DISCO cannot be used to document non-insured status on any SSN since a certified earnings record (CER), such as a CER from ICERS, is required per GN 01010.440.\n\n4. \nFO routing\na. \nGeneral\n\nAll CDB cases which need a determination of disability will be transferred to the appropriate DDS or other adjudicating component. Follow instructions in:\n\n•\n\nDI 11020.000 on jurisdiction, routing and transmitting cases to DDS or the Program Center (PC); and\n\n•\n\nDI 81010.085B regarding the transfer of the Certified Electronic Folder (CEF).\n\nNOTE: GLPSC Disability Process Branch (DCR) has jurisdiction of Title II disability determinations for career annuitant and career railroad dependent survivor claims. (See DI 11010.262 and DI 20101.040A.1. for additional instructions.)\n\nb. \nExceptions\n\nSee DI 11020.060 for exceptions to the general routing procedures.\n\n5. \nDisability determination for child to entitle or to continue benefits to a mother/father or young spouse\n\nIf a disability determination is necessary for a child age 15 or older in order to entitle or continue benefits to a mother/father or young spouse, follow DI 11020.060 and DI 23505.001.\n\nIf both a physical and mental impairment are alleged, enter child-in-care in the remarks section of the EDCS 3367. This will alert the DDS to identify in remarks a documented mental impairment which is not shown as the primary or secondary impairment.\n\n6. \nDisability determination for disabled minor child to enable continuation of child's benefits at age 18\n\nCDB payments cannot begin prior to age 18. While the disability determination is being developed, ensure that the appropriate system input is made to enable automatic conversion when the child attains age 18.\n\nB. \nProcedure pending childhood disability action\n\nIf other claimants are simultaneously filing, process the disability claim as a delayed claim (see GN 01010.140). If the child is also claiming benefits as a full-time student, see RS 00203.090.\n\n1. \nChild already entitled (post-entitlement action)\n\nSuspension actions for developing childhood disability determinations are processed by Title II Redesign (T2RD).\n\nIMPORTANT: If the child is entitled as a student, a suspension action is not appropriate.\n\n2. \nChild entitled prior to age 18 (initial award)\na. \nPartial award\n\nThe claim can be processed as a partial award in the FO (see GN 01010.110 - GN 01010.120). Advise in the award notice that the claim for CDB benefits is pending. See NL 00725.005 for the appropriate Universal Text Identifiers (UTI).\n\nb. \nDevelop for Child Disability Determination (DDIB) Process\n\nThe DDIB screen can be entered for the child beneficiary as early as age 17 to prevent termination at age 18. Follow RS 00203.090 Exception and DI 11020.005 if the child could be found entitled as a full-time student.\n\nEXCEPTION: When the DDIB process cannot be used, the Program Center (PC) diaries for the first day of the month prior to the month of attainment of age 18, for possible payment of CDB benefits. Annotate the diary screen: CDB determination pending (month, year), age 18 attainment.\n\n3. \nChild reapplying within 4 years of termination and alleges disability prior to termination\n\nThe FO will notify the PC via the appropriate method, i.e., Modernized Development Worksheet (MDW) or faxing into the PC paperless queue, that a disability determination is pending. See also RS 00203.080B.\n\n4. \nChild entitled age 18 or later as full-time student (initial award)\n\nEntitle the child to student benefits pending a CDB determination. See SM 03020.320E for detailed instructions regarding T2RD processing.\n\nIf there are other beneficiaries, do not adjust benefits upward pending the disability determination. (Do not notify the payee if the amount of the benefits paid will not be affected by the suspension because of the number of beneficiaries in the household.)\n\nIf the case is a Modernized Claims System (MCS) exclusion, instruct the benefit authorizer (BA)/benefit technical examiner (BTE) to:\n\n•\n\nplace the child in suspense status rather than terminated pending the disability determination; and\n\n•\n\ninput the appropriate reason for suspension/termination (RFST) (see procedure in SM 00848.425).\n\nREMINDER: See DI 11020.085 for a list of claims excluded from District Office Final Authorization (DOFA) processing.\n\n5. \nChilds benefits erroneously terminated\na. \nFO action\n\nNotify the PC and instruct the BA/BTE to place the child in suspense status effective with the age 18 attainment month pending the disability determination.\n\nb. \nPC action\n\nThe BA/BTE will input the suspension action, appropriate RFST and prepare any necessary diary.\n\nIf there are other beneficiaries, do not adjust benefits upward pending the disability determination. (Do not notify the payee if the amount of the benefits paid will not be affected by the suspension because of the number of beneficiaries in the household.)\n\n6. \nPayee development\n\nFollow GN 00502.075 for determining when payee development is required.\n\nC. \nProcedure status check on DDS or DCR determination\n\nUse the DDS Service Query (DDSQ), eView, or EP to check the progress of DDS case or DCR processing.\n\nD. \nProcedure FO action following disability determination\n1. \nGeneral\n\nAfter the DDS or DCR makes a disability determination and the case is transferred to the FO, follow:\n\n•\n\nDI 11020.135 through DI 11020.140;\n\n•\n\nDI 11010.265 regarding case control inputs.\n\nThis reference list is for claims that cannot be processed for non-DOFA reasons.\n\nSee DI 11020.085 for claims excluded from DOFA processing.\n\n2. \nDisability established\n\nThe following chart provides case scenarios and processing instructions. The chart is not all inclusive:\n\nIf the child is:\n\n\t\n\nAction:\n\n\n\n\nAge 16 and entitled to childs benefits (CDB claim to continue benefits to child-in-care (CIC) beneficiary)\n\n\t\n\nUse the CLAIM INT CDB barcode to fax actionable material into the PCs paperless queue. Annotate Remarks CDB claim to continue mother/fathers or spouses benefits if CIC beneficiary entitled. Provide the disability onset date and other coding if necessary, i.e., rep payee. In EDCS, the claims material is faxed to the EF.\n\nIf the official folder is CEF, fax all claims material to the EF.\n\n\n\n\nAge 17 to age 18\n\n\t\n\nUpdate DDIB screen and make appropriate systems input to update the Master Beneficiary Record (MBR) for the child and any CIC beneficiary.\n\n\n\n\nOver 18 (and not receiving student benefits)\n\n\t\n\nIf Supplemental Security Income (SSI) is involved, use the CLAIM INT CDB barcode to fax the actionable material into the PCs paperless queue. Provide the disability onset date and other coding if necessary, i.e., rep payee. In EDCS, the claims material is faxed to the EF.\n\nIf the official folder is the CEF, fax all claims material to the EF.\n\nIf SSI is not involved, update DDIB screen and make appropriate systems input to update the MBR and resume benefits.\n\n\n\n\nOver 18 (receiving student benefits)\n\n\t\n\nUse the CLAIM INT CDB barcode to fax the actionable material into the PCs paperless queue. Provide the disability onset date and other coding if necessary, i.e., rep payee. In EDCS, the claims material is faxed to the EF.\n\nIf the official folder is the CEF, fax all claims material to the EF.\n\n\n\n\nOver age 18 and benefits are terminated\n\n\t\n\nUse the CLAIM INT CDB barcode to fax the actionable material into the PCs paperless queue. Provide the disability onset date and other coding if necessary, i.e., rep payee.\n\nRefer to:\n\n•\n\nGN 01010.140C if claimant was in delayed status;\n\n•\n\nDI 26535.036 if capability or payee is in question and an interim notice is required.\n\n3. \nDisability not established\n\nTake the following actions:\n\n•\n\nProcess the disallowance/denial through the MACADE Disallowance Function if the disallowance cannot be processed through MCS EC.\n\n•\n\nMake appropriate systems input to update the MBR.\n\n•\n\nPrepare an MDW or appropriate paperless directive for the PC to inform them that the CDB claim is denied.\n\n•\n\nRelease the disability denial notice, if not released by the DDS.\n\nFollow DI 11020.135 if DDS denied based on res judicata.\n\nIMPORTANT: If the childs benefit termination event has a collateral effect on the entitlement of a child-in-care beneficiary, refer to SM 03020.100.\n\nE. \nProcedure PC action following disability determination\n1. \nDisability denied\n\nTake the following actions:\n\n•\n\nTerminate benefits if benefits have not already been terminated (unless student entitlement is applicable),\n\n•\n\nAdjust other benefits affected by such termination, and\n\n•\n\nSend a notice of adjustment to the auxiliaries and a termination notice to the CDB if in suspense status.\n\n2. \nDisability established\n\nThe following is a brief overview and is not all inclusive.\n\na. \nGeneral\n\nWhen a disability determination for a child is received:\n\n•\n\nResume the payment of benefits (including mothers, fathers and spouses benefits if CDB is in their care) if they had been suspended;\n\n•\n\nMake appropriate systems inputs (i.e., post the disability determination in the BENE ENT line on the MBR to enable automatic conversion);\n\n•\n\nReinstate benefits to the CDB if they had been terminated at age 18;\n\n•\n\nCancel any diary established according to RS 00203.085B.2.\n\nb. \nDisability determination made to entitle mother/father, young spouse or to continue child's benefits past age 18 as CDB\n\nBenefits will automatically be continued to the child upon attainment of age 18 if disability is indicated in the BENE ENT line on the MBR. No special notices are required when the child attains age 18. Send the appropriate notice in NL 00703.000. See SM 03020.100 and SM 00883.125 regarding any systems input required.\n\nc. \nDirect payment\n\nDirect payment will be made to a CDB beneficiary who is capable of managing payments in their own interest.\n\nIf capability is raised by medical or other evidence, follow development instructions in GN 00502.001 through GN 00502.075.\n\nF. \nProcedure PC action child not previously entitled or prior entitlement terminated\n1. \nDisability denied\n\nTake the following actions:\n\n•\n\nProcess the disallowance using the MACADE Disallowance function (see SM 00380.500) if MCS EC cannot be used.\n\n•\n\nTake any necessary action to adjust benefits to any other beneficiaries affected by the denial of the CDB claim.\n\n•\n\nEnsure that the denial is posted to the MBR.\n\n•\n\nIf the case was returned to the PC from ODO, or if the DDS did not prepare and release the denial notice, send a disallowance letter (see NL 00701.000).\n\n2. \nDisability and other requirements established\n\nIf all requirements for entitlement are satisfied, the child was not previously entitled, and automated processing is not possible, prepare and review the EF-101 in accordance with existing procedures if necessary. If the child was previously entitled, convert benefits to CDB benefits.\n\nDirect payment will be made to a CDB beneficiary who is capable of managing payments in their own interest. If capability is raised by medical or other evidence, follow the development instructions in GN 00502.001 through GN 00502.075.\n\nG. \nReferences\n•\n\nFO-DDS Exchange of Information and Coordination of Actions (DI 10005.010)\n\n•\n\nCompletion of Item 34 (Remarks) (DI 26510.095)\n\n•\n\neView (DI 81005.000)\n\n•\n\nCreating an EDCS Case (DI 81010.020)\n\n•\n\nCertified Electronic Folder (CEF) Exclusions and Limitations (DI 81010.030)\n\n•\n\nDevelopment for Disabled Child Prior to Age 16 Procedure (RS 00208.070)\n\n•\n\nConditions for Entitlement and Definitions (RS 01310.001)\n\n•\n\nICER Background/Introduction (SM 00349.001)\n\n•\n\nDevelop for Child Disability (DDIB) (SM 03020.120)\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203085\n\t\nRS 00203.085 - Childhood Disability Development and Determination - 01/31/2023\nBatch run: 08/31/2026\nRev:01/31/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "whole_sha256": "fce4c40ebacd80a8dfbee985ad8767ce9ad39fc2f2b6bbe1489ee212538225af"
          }
        ],
        "holds": [
          "Full DI 11020 development, routing/DOFA, student exceptions and technical-denial procedures remain linked scope; this page does not decide eligibility.",
          "A.3 DISCO/ICERS named query roles do not create native identity or accepted system relationships; a certified earnings record is required to document noninsured status.",
          "Generic MDW is not equated with APP_MDW_AI. EDCS/eView/EP references are source descriptions, not runtime telemetry.",
          "F.2 all-requirements, never-entitled and automation-unavailable conjunction is not inferred from a favorable disability finding. Prior entitlement and capability routes remain conditional.",
          "E.2.b no special notice solely at age 18 coexists with appropriate NL notice instruction; no blanket notice waiver."
        ],
        "negative_QA": [
          {
            "id": "N01",
            "case": "Worked but insured status not established",
            "expected": "Do not decide insured status or benefits."
          },
          {
            "id": "N02",
            "case": "DISCO says noninsured",
            "expected": "Do not use DISCO alone to document noninsured status."
          },
          {
            "id": "N03",
            "case": "Claimant has no work history",
            "expected": "Do not infer the A.3 work-history premise."
          },
          {
            "id": "N04",
            "case": "Benefits terminated but error not established",
            "expected": "Do not select the B.5 correction as an established case fact."
          },
          {
            "id": "N05",
            "case": "Another beneficiary exists",
            "expected": "Do not automatically increase their benefit pending the determination."
          },
          {
            "id": "N06",
            "case": "Payee amount affected",
            "expected": "Do not import the conditional no-notification instruction."
          },
          {
            "id": "N07",
            "case": "Student entitlement applies",
            "expected": "Do not apply B.1 pending-disability suspension."
          },
          {
            "id": "N08",
            "case": "DDIB remains usable",
            "expected": "Do not select its diary fallback."
          },
          {
            "id": "N09",
            "case": "Reapplication after four years",
            "expected": "Do not infer B.3 within-four-years scope."
          },
          {
            "id": "N10",
            "case": "Disability denial not issued",
            "expected": "Do not infer E.1 denial actions."
          },
          {
            "id": "N11",
            "case": "CDB not in suspense",
            "expected": "Do not silently import suspense-only notice condition."
          },
          {
            "id": "N12",
            "case": "No disability indicated on BENE ENT",
            "expected": "Do not assert automatic age-18 continuation."
          },
          {
            "id": "N13",
            "case": "No special age-18 notice",
            "expected": "Do not waive other determination/payment notices."
          },
          {
            "id": "N14",
            "case": "Favorable medical finding only",
            "expected": "Do not infer all F.2 entitlement requirements."
          },
          {
            "id": "N15",
            "case": "Previously entitled child",
            "expected": "Keep prior-entitlement conversion separate from initial-award EF-101 conditions."
          },
          {
            "id": "N16",
            "case": "Capability evidence raises a question",
            "expected": "Do not determine capability or appoint a payee."
          },
          {
            "id": "N17",
            "case": "Only one impairment type alleged",
            "expected": "Do not establish A.5 both-physical-and-mental premise."
          },
          {
            "id": "N18",
            "case": "Child under age 15",
            "expected": "Do not silently extend the A.5 age-15-or-older instruction."
          }
        ]
      },
      "IAR8": {
        "flows": {
          "apply-ssi/iar-manual-accounting-state-nonresponse": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-manual-accounting-state-nonresponse",
            "full_route": "apply-ssi/iar-manual-accounting-state-nonresponse",
            "entry_conditions": [
              "The underpayment cannot be computed on the SSR and the manual IAR payment-pending procedure applies."
            ],
            "steps": [
              {
                "id": "iar-manual-accounting-state-nonresponse-source-1",
                "title": "Request the State’s accounting",
                "kind": "action",
                "actor": "FO",
                "action": "Prepare SSA-L8125 with the required identifying, payee and retroactive-amount summary information. Mail or fax it to the State or local agency to obtain the IAR amount due; the form requests return within 10 working days.",
                "conditions": [
                  "The underpayment cannot be computed on the SSR and the manual IAR payment-pending procedure applies."
                ],
                "source": "iarmanualpayment",
                "section": "B.2.c",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "Detailed form completion is linked SI 02003.024 scope, not a newly reproduced form or actual accounting result.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-manual-accounting-state-nonresponse-source-2",
                "title": "Set the return control",
                "kind": "action",
                "actor": "FO",
                "action": "Use the Development Worksheet to control return for 15 working days from the date SSA-L8125 is sent. If a systems limitation prevents an MSSICS issue, the note instead says to use MDW with a 15-day tickle.",
                "conditions": [
                  "The underpayment cannot be computed on the SSR and the manual IAR payment-pending procedure applies."
                ],
                "source": "iarmanualpayment",
                "section": "B.2.d",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The fallback says 15 days without specifying working days. Do not equate it with the 15-working-day control or turn either into a payment promise; generic MDW identity remains held.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-manual-accounting-state-nonresponse-source-3",
                "title": "Follow up only after the stated nonresponse condition",
                "kind": "action",
                "actor": "FO",
                "action": "If the form is not received within 15 working days of the diary control, send SSA-L8125 marked SECOND REQUEST or contact the State about its status.",
                "conditions": [
                  "The underpayment cannot be computed on the SSR and the manual IAR payment-pending procedure applies.",
                  "The first specified nonresponse condition has been reached."
                ],
                "source": "iarmanualpayment",
                "section": "B.2.e",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The second-request and State-contact methods are alternatives, not two mandatory actions or a new date calculator.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-manual-accounting-state-nonresponse-source-4",
                "title": "Keep the second-request clocks separate",
                "kind": "action",
                "actor": "FO",
                "action": "If the State does not respond within 10 working days after the second request was forwarded, send a copy to the regional office for handling or follow supplemental regional instructions. If the form remains unreturned 15 working days after the second request, release the retroactive amount to the SSI individual to protect against hardship.",
                "conditions": [
                  "The underpayment cannot be computed on the SSR and the manual IAR payment-pending procedure applies.",
                  "The applicable second-request nonresponse condition has been reached."
                ],
                "source": "iarmanualpayment",
                "section": "B.2.f",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The 10- and 15-working-day conditions have a second-request anchor. The source does not add a separate customer hardship-proof requirement or establish a universal IAR payment schedule.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-state-accounting-none-due": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-state-accounting-none-due",
            "full_route": "apply-ssi/iar-state-accounting-none-due",
            "entry_conditions": [
              "A completed SSA-L8125 indicates that the State is not due IAR."
            ],
            "steps": [
              {
                "id": "iar-state-accounting-none-due-source-2",
                "title": "Retain the code prerequisite and authority hold",
                "kind": "action",
                "actor": "FO",
                "action": "The B.4 note requires deletion of the GR code before release. The original record also preserves the separately scoped SI 02003.020 coordinator instruction; this walkthrough does not assign deletion authority or resolve that staff-procedure question.",
                "conditions": [
                  "A completed SSA-L8125 indicates that the State is not due IAR."
                ],
                "source": "iarmanualpayment",
                "section": "B.4 note",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "Only the prerequisite stated in this page is supplied. SI 02003.020 detailed authority is not provided by this whole capture and remains a distinct dependency.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-state-accounting-none-due-source-1",
                "title": "Apply the remaining-payment exceptions",
                "kind": "action",
                "actor": "FO",
                "action": "Release the past-due benefits to the individual, representative payee or legal guardian unless dedicated-account, installment or representative-fee instructions apply; those instructions require their own handling.",
                "conditions": [
                  "A completed SSA-L8125 indicates that the State is not due IAR."
                ],
                "source": "iarmanualpayment",
                "section": "B.4",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "No IAR due does not establish an unrestricted immediate lump sum or that linked payment conditions have been met.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-erroneous-state-check-return": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-erroneous-state-check-return",
            "full_route": "apply-ssi/iar-erroneous-state-check-return",
            "entry_conditions": [
              "The State IAR office returns a check because it was erroneously sent to that State."
            ],
            "steps": [
              {
                "id": "iar-erroneous-state-check-return-source-1",
                "title": "Reissue to the proper individual-side recipient",
                "kind": "action",
                "actor": "FO",
                "action": "Reissue the returned check to the recipient, representative payee or legal guardian under current SSI payment procedures. Do not reissue this check to another State for any reason.",
                "conditions": [
                  "The State IAR office returns a check because it was erroneously sent to that State."
                ],
                "source": "iarmanualpayment",
                "section": "C.1 erroneous State payment",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "Other returned IAR checks intended for reissue to a State have separate refund instructions. Detailed reissue transactions and amounts are not established here.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-agency-payment-nonreceipt": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-agency-payment-nonreceipt",
            "full_route": "apply-ssi/iar-agency-payment-nonreceipt",
            "entry_conditions": [
              "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment."
            ],
            "steps": [
              {
                "id": "iar-agency-payment-nonreceipt-source-1",
                "title": "Verify the payment and report nonreceipt",
                "kind": "action",
                "actor": "FO",
                "action": "Review SSR payment history: payflag 1 identifies type 2 underpayment or type 4 A-OTP, and payflag 3 is 1 for an IAR payment. Transmit nonreceipt on the Missing Check UPMC screen in MSSICS Direct SSR Update.",
                "conditions": [
                  "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment."
                ],
                "source": "iarmanualpayment",
                "section": "E steps 1–2",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "Detailed MS transaction instructions remain linked scope; this does not establish an actual report or authorization to change an unrelated payment.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-agency-payment-nonreceipt-source-2",
                "title": "Check an uncertain mailing address",
                "kind": "action",
                "actor": "FO",
                "action": "If it is uncertain whether the payment went to the correct IAR address, the field office Management Support Specialist or Operations Supervisor can check Treasury’s Check Information System for the mailed address.",
                "conditions": [
                  "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment.",
                  "The IAR mailing address is uncertain."
                ],
                "source": "iarmanualpayment",
                "section": "E step 2 note",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The named check is assigned to MSS or OS; no new system identity or automatic address result is inferred.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-agency-payment-nonreceipt-source-3",
                "title": "Preserve the type-2 replacement controls",
                "kind": "action",
                "actor": "FO",
                "action": "For a type-2 payment, use the same months for its A-OTP replacement. Reissue by A-OTP before a returned check posts to the SSR to avoid an incorrect type-2 payment to the claimant. If more development is needed before A-OTP, post a U TAC through UOUP; may remove it once the A-OTP is issued.",
                "conditions": [
                  "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment.",
                  "Payflag 1 identifies the missing payment as type 2."
                ],
                "source": "iarmanualpayment",
                "section": "E Type 2 paragraph",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The further-development condition qualifies the U TAC instruction. This does not authorize release before evidence or linked transaction requirements are satisfied.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ],
                "alternative_group": "payment-type"
              },
              {
                "id": "iar-agency-payment-nonreceipt-source-4",
                "title": "Preserve the type-4 replacement controls",
                "kind": "action",
                "actor": "FO",
                "action": "For a type-4 A-OTP, reissue to the IAR agency for the same months as the original. If replacement will be delayed, post a U TAC through Underpayment Processing in Direct SSR Update to prevent unintended automated release to the claimant.",
                "conditions": [
                  "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment.",
                  "Payflag 1 identifies the missing payment as type 4."
                ],
                "source": "iarmanualpayment",
                "section": "E Type 4 paragraph",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The delay condition qualifies the U TAC instruction. Type 2 and type 4 are source-conditioned alternatives, not sequential classifications.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ],
                "alternative_group": "payment-type"
              },
              {
                "id": "iar-agency-payment-nonreceipt-source-5",
                "title": "Address the replacement to the agency",
                "kind": "action",
                "actor": "FO",
                "action": "Reissue by A-OTP to the IAR agency as soon as possible, using the complete agency address on UPOA and retaining the applicable original payment months and conditional controls.",
                "conditions": [
                  "The reported missing payment is an IAR reimbursement payment issued to an IAR agency, not the individual’s residual SSI payment."
                ],
                "source": "iarmanualpayment",
                "section": "E step 3; Type 2/Type 4 paragraphs",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "As soon as possible is not a fixed delivery deadline. This is an agency reimbursement route, not an automatic individual-payment replacement.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            },
            "alternative_groups": [
              {
                "id": "payment-type",
                "label": "Different controls for the established payment type",
                "logic": "source_conditions_determine_branch",
                "note": "Apply only the type supported by payment history. These two branches are alternatives; neither is selected merely by viewing this example."
              }
            ]
          },
          "apply-ssi/iar-returned-code-routing-limitation": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-returned-code-routing-limitation",
            "full_route": "apply-ssi/iar-returned-code-routing-limitation",
            "entry_conditions": [
              "A returned IAR check is reflected by GRC code C in the SSR MPMT segment."
            ],
            "steps": [
              {
                "id": "iar-returned-code-routing-limitation-source-1",
                "title": "Do not treat the return indicator as payment routing",
                "kind": "action",
                "actor": "FO",
                "action": "The note says P or G changes to C when the check is returned. C is informational only and does not send the next retroactive payment to the IAR agency. Only R for pending initial-claim IAR or F for pending posteligibility IAR causes routing to the IAR address.",
                "conditions": [
                  "A returned IAR check is reflected by GRC code C in the SSR MPMT segment."
                ],
                "source": "iarmanualpayment",
                "section": "E final note",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "These are the source’s routing distinctions, not authority to edit codes or a finding of who is owed a payment. Detailed SM 01005.625 remains linked scope.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-death-state-accounting-handoff": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-death-state-accounting-handoff",
            "full_route": "apply-ssi/iar-death-state-accounting-handoff",
            "entry_conditions": [
              "The recipient dies while State IAR accounting/payment handling remains pending."
            ],
            "steps": [
              {
                "id": "iar-death-state-accounting-handoff-source-1",
                "title": "Carry the death date into State accounting",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Record the date of death on the manual SSA-L8125 and send the form to the State under SI 02003.040.",
                "conditions": [
                  "The recipient dies while State IAR accounting/payment handling remains pending."
                ],
                "source": "iarmanualpayment",
                "section": "D",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The linked form instructions are not supplied by this page; this is not a determination of survivor or residual-underpayment eligibility.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-death-state-accounting-handoff-source-2",
                "title": "Keep the death-case payment limits conditional",
                "kind": "action",
                "actor": "SSA staff",
                "action": "The page directs State payment by A-OTP and says the system generally accepts one A-OTP in a death case; an additional amount uses manual OTP. Its stated exception permits up to two A-OTPs on a deceased record with both a surviving ineligible spouse and a valid unpaid GR code.",
                "conditions": [
                  "The recipient dies while State IAR accounting/payment handling remains pending."
                ],
                "source": "iarmanualpayment",
                "section": "D note",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The surviving-spouse and valid-unpaid-GR predicates are conjunctive. Detailed SM 01901.154 payment handling remains separately scoped; no actual payment action is established.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-state-paid-residual-notice-processing": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-state-paid-residual-notice-processing",
            "full_route": "apply-ssi/iar-state-paid-residual-notice-processing",
            "entry_conditions": [
              "The field office receives a completed SSA-L8125 and the B.3 State-payment/remainder procedure applies."
            ],
            "steps": [
              {
                "id": "iar-state-paid-residual-notice-processing-source-1",
                "title": "Pay the State’s specified claimed amount",
                "kind": "action",
                "actor": "FO",
                "action": "Send an A-OTP to the State for the amount in item 2 of the State’s Account of Reimbursement Claimed section.",
                "conditions": [
                  "The field office receives a completed SSA-L8125 and the B.3 State-payment/remainder procedure applies."
                ],
                "source": "iarmanualpayment",
                "section": "B.3.a",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "A completed accounting and actual amount must be established; this example does not compute or certify them.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-state-paid-residual-notice-processing-source-2",
                "title": "Apply remaining-benefit payment provisions",
                "kind": "action",
                "actor": "FO",
                "action": "If the remaining benefits are covered by dedicated-account, installment or representative-fee provisions, issue an A-OTP and process under the linked SI 02101.010–SI 02101.020 instructions.",
                "conditions": [
                  "The field office receives a completed SSA-L8125 and the B.3 State-payment/remainder procedure applies.",
                  "A remaining-benefit payment provision applies."
                ],
                "source": "iarmanualpayment",
                "section": "B.3.b",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "Do not infer a single unrestricted lump sum or treat these linked procedures as fully supplied.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              },
              {
                "id": "iar-state-paid-residual-notice-processing-source-3",
                "title": "Document the form and use the applicable notice",
                "kind": "action",
                "actor": "FO",
                "action": "Complete the bottom of page 3 of SSA-L8125 and fax a copy of the paper form to the appropriate electronic folder. Prepare a manual notice if applicable; the system can produce an automated notice in most situations.",
                "conditions": [
                  "The field office receives a completed SSA-L8125 and the B.3 State-payment/remainder procedure applies."
                ],
                "source": "iarmanualpayment",
                "section": "B.3.c–d",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "The source does not mandate a manual notice in every case or name a specific electronic-folder identity in this instruction.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          },
          "apply-ssi/iar-recipient-mistaken-residual-check-return": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "iar-recipient-mistaken-residual-check-return",
            "full_route": "apply-ssi/iar-recipient-mistaken-residual-check-return",
            "entry_conditions": [
              "The recipient mistakenly returns the residual IAR check to SSA."
            ],
            "steps": [
              {
                "id": "iar-recipient-mistaken-residual-check-return-source-1",
                "title": "Use the separate recipient-return procedure",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Follow the returned-check procedures referenced in SM 01315.020 and SM 01315.042. Keep this recipient return distinct from a State refund or an agency nonreceipt payment.",
                "conditions": [
                  "The recipient mistakenly returns the residual IAR check to SSA."
                ],
                "source": "iarmanualpayment",
                "section": "C.2",
                "source_context_refs": [
                  "SI02003.025:whole"
                ],
                "qualifications": [
                  "This page supplies the referral only. The detailed linked reissue transactions, evidence and any delivery timing are unreviewed here; no filler action or successful replacement is inferred.",
                  "Prescribed staff handling only; selecting the example does not establish a case fact, completed payment or successful return."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The selected instruction does not demonstrate actual completion, successful release or return to the usual case path. Linked authority and transaction rules remain separately scoped."
              ]
            }
          }
        },
        "original_records": {
          "apply-ssi/iar-manual-accounting-state-nonresponse": {
            "id": "iar-manual-accounting-state-nonresponse",
            "title": "The State does not return manual IAR accounting",
            "when": "SSA is using the manual payment-pending procedure because the underpayment cannot be computed on the SSI record.",
            "you": "Ask SSA about the accounting request and any follow-up; keep related notices.",
            "ssa": "The field office sends SSA-L8125 to the State, requesting return within 10 working days, and sets a 15-working-day control from sending. Nonresponse prompts a second request or State contact. If the second request has no response after 10 working days, staff forward a copy to the regional office or follow supplemental regional instructions. If the form remains unreturned 15 working days after the second request, B.2.f directs release of the retroactive amount to the individual to protect against hardship.",
            "route": "Field office → State accounting request/follow-up → regional office when specified → conditional release",
            "next": "This release rule applies to the specified manual nonresponse case. It does not establish a universal IAR payment schedule.",
            "source": "iarmanualpayment",
            "section": "B.2.c–f",
            "timing": "Keep the original-request control and second-request clocks separate. The fallback control note says 15 days without specifying working days; do not silently equate them.",
            "review_status": "Manual scope and distinct follow-up clocks checked; no additional hardship proof condition inferred."
          },
          "apply-ssi/iar-state-accounting-none-due": {
            "id": "iar-state-accounting-none-due",
            "title": "The State accounting shows no IAR reimbursement is due",
            "when": "A completed SSA-L8125 reports that the State is not owed IAR.",
            "you": "Keep the accounting and SSI notices. Ask SSA whether any remaining payment is subject to separate fee, installment or dedicated-account rules.",
            "ssa": "SI 02003.025 B.4 directs release to the individual, payee or legal guardian unless dedicated-account, installment or representative-fee instructions apply. Those exceptions require their own processing. Its code-deletion prerequisite must be read with SI 02003.020 B IMPORTANT, which directs coordinator contact for justified deletion. This branch preserves that referral without assigning unverified deletion authority.",
            "route": "Field office completed-accounting review → applicable payment-exception processing; code question → regional coordinator",
            "next": "No State reimbursement is due under this accounting, but that does not guarantee an immediate unrestricted lump sum.",
            "source": "iarmanualpayment",
            "section": "B.4",
            "additional_sources": [
              {
                "source": "iarforeturn",
                "section": "B IMPORTANT"
              }
            ],
            "timing": "No customer payment duration is specified here.",
            "review_status": "No-IAR outcome and release exceptions verified; exact code-deletion authority remains an explicit unresolved staff-procedure issue."
          },
          "apply-ssi/iar-erroneous-state-check-return": {
            "id": "iar-erroneous-state-check-return",
            "title": "A State returns an IAR check that was sent to it in error",
            "when": "The State IAR office returns a check because it was erroneously sent to that State.",
            "you": "Keep any related payment correspondence and ask SSA to review the returned payment’s proper recipient.",
            "ssa": "SI 02003.025 C.1 directs the field office to reissue the returned check to the recipient, representative payee or legal guardian under current SSI payment procedures. It expressly prohibits reissuing this check to another State. Other returned checks intended for reissue to a State follow the separate refund procedures, not this erroneous-payment branch.",
            "route": "State IAR office return → field office recipient/payee payment review → proper recipient under SSI procedures",
            "next": "SSA handles reissue under the applicable payment rules. This branch does not establish an individual amount or guaranteed delivery date.",
            "source": "iarmanualpayment",
            "section": "C.1 erroneous State payment",
            "timing": "No reissue turnaround is specified in this subsection.",
            "review_status": "Erroneous-payment trigger and recipient destination checked; separate refund transaction details remain for linked SM sources."
          },
          "apply-ssi/iar-agency-payment-nonreceipt": {
            "id": "iar-agency-payment-nonreceipt",
            "title": "The IAR agency reports that its reimbursement payment is missing",
            "when": "An IAR agency reports nonreceipt of its reimbursement payment.",
            "you": "Keep related SSI notices and distinguish an agency reimbursement issue from a missing payment owed directly to you. Ask SSA which payment is being traced.",
            "ssa": "SI 02003.025 E directs the field office to verify issuance to the agency using payment history, transmit nonreceipt and reissue to the agency with its complete address. If the mailing address is uncertain, the Management Support Specialist or Operations Supervisor can check Treasury’s Check Information System. The listed type-2 and type-4 replacements retain the original payment months. Separate transaction instructions address preventing unintended automated release during development.",
            "route": "Field office agency-payment verification → address check when needed → nonreceipt/reissue to IAR agency",
            "next": "This resolves an agency reimbursement payment, not an automatic replacement of the individual’s residual SSI payment.",
            "source": "iarmanualpayment",
            "section": "E steps 1–3; type-2/type-4 paragraphs",
            "timing": "The source says reissue as soon as possible, without a fixed delivery or completion deadline.",
            "review_status": "Agency destination, address owner and original-month checks verified; exact transaction controls remain for linked technical-source review."
          },
          "apply-ssi/iar-returned-code-routing-limitation": {
            "id": "iar-returned-code-routing-limitation",
            "title": "A returned IAR check code does not route the next payment",
            "when": "A returned IAR check is reflected by reimbursement code C on the SSI record.",
            "you": "Ask SSA which payment is being reviewed and who should receive it; keep return and payment correspondence.",
            "ssa": "SI 02003.025 E’s final note says the returned-check code changes from P or G to C. C is informational and does not route the next retroactive payment to the IAR agency. The note identifies pending codes R for an initial claim and F for posteligibility as the routing conditions. Staff must review the actual payment destination rather than treating the returned-check indicator as a new agency-payment instruction.",
            "route": "Field office returned-payment and destination review → applicable agency nonreceipt or recipient-payment procedure",
            "next": "A return indicator alone does not settle who is owed the next payment. Exact code-update actions require their separate instructions.",
            "source": "iarmanualpayment",
            "section": "E final note",
            "timing": "This is a routing limitation, not a payment deadline.",
            "review_status": "Informational-versus-pending code distinction verified; no code-edit authority inferred. SM01005.625 details remain separately unverified."
          },
          "apply-ssi/iar-death-state-accounting-handoff": {
            "id": "iar-death-state-accounting-handoff",
            "title": "A death occurs while State IAR accounting is pending",
            "when": "The SSI recipient dies before the IAR payment/accounting process is complete.",
            "you": "Report the death to SSA and keep relevant payment and State-assistance correspondence. Any survivor or residual-underpayment question needs separate review.",
            "ssa": "SI 02003.025 D directs staff to record the death date on the manual SSA-L8125 and send it to the State under SI 02003.040. The latter’s B instructions require the deceased date when death occurs before payment. Staff handle State reimbursement under the applicable payment rules; detailed one-time-payment limits and exceptions require their linked instructions.",
            "route": "Field office death-date/accounting update → State IAR agency accounting handoff",
            "next": "Death documentation is carried into State reimbursement processing. This branch does not determine which survivor can receive any remaining SSI.",
            "source": "iarmanualpayment",
            "section": "D",
            "additional_sources": [
              {
                "source": "iarstateaccountingform",
                "section": "B Date of SSI Eligibility"
              }
            ],
            "timing": "Neither subsection gives a death-case accounting completion deadline.",
            "review_status": "Death-date entry and State handoff verified; SM01901.154 payment exception and separate survivor eligibility remain unverified here."
          },
          "apply-ssi/iar-state-paid-residual-notice-processing": {
            "id": "iar-state-paid-residual-notice-processing",
            "title": "State IAR reimbursement is paid and remaining SSI needs processing",
            "when": "The field office receives completed SSA-L8125 accounting and processes State reimbursement and any remaining past-due SSI.",
            "you": "Keep the State accounting and SSA notices. Ask how any fee, installment or dedicated-account rules affect the remainder.",
            "ssa": "SI 02003.025 B.3 directs payment of the State’s claimed amount from item 2. Remaining benefits covered by dedicated-account, installment or representative-fee provisions follow the linked instructions. Staff complete the bottom of page 3, document the form in the electronic folder and prepare a manual notice when applicable; automated notices are possible in most situations.",
            "route": "Field office completed-accounting review → State payment → applicable remainder-payment and notice processing",
            "next": "Any remaining benefit requires its applicable payment handling. The rule does not promise a single immediate lump sum or a universal manual notice.",
            "source": "iarmanualpayment",
            "section": "B.3.a–d",
            "timing": "No fixed remaining-benefit release duration is specified here.",
            "review_status": "Selected State-payment/documentation/notice sequence verified; exact linked dedicated-account/installment/fee requirements require their own subsection review."
          },
          "apply-ssi/iar-recipient-mistaken-residual-check-return": {
            "id": "iar-recipient-mistaken-residual-check-return",
            "title": "The recipient mistakenly returns the remaining SSI check",
            "when": "The recipient mistakenly sends the residual IAR check back to SSA.",
            "you": "Contact SSA about the mistaken return and keep the check or return correspondence and related notices.",
            "ssa": "SI 02003.025 C.2 directs the returned-check procedure in SM 01315.020 and SM 01315.042. Staff must distinguish this recipient return from a State refund or agency nonreceipt. Detailed reissue transactions and evidence requirements are not established by C.2 alone.",
            "route": "SSA returned-payment review for recipient residual check → linked returned-check procedure",
            "next": "SSA reviews the returned payment under the applicable procedure. No immediate replacement amount or delivery date is inferred.",
            "source": "iarmanualpayment",
            "section": "C.2",
            "timing": "C.2 gives no reissue deadline.",
            "review_status": "Separate recipient-return route verified in preserved live C.2 research; linked SM pages inaccessible this run, so detailed reissue steps remain deferred."
          }
        },
        "source_contexts": [
          {
            "id": "SI02003.025:whole",
            "start": 0,
            "end": 11811,
            "exact_text": "Effective Dates: 12/29/2023 - Present\nPrevious | Next\n\nTN 30 (10-24)\n\nSI 02003.025 IAR Payment Processing for Exception Cases and Proration Cases\nA. \nPolicy for underpayments that involve attorney or eligible non-attorney fee payment, dedicated account, or installment payment cases\n1. \nAttorney or eligible non-attorney fee payment cases\n\nSection 302 of P. L. 108-203, requires SSA to review the individual's file to determine if an attorney or non-attorney fee agreement or petition has been approved by the FO or the Office of Hearings Operations (OHO). If so, we pay the fee to the designated attorney or certified non-attorney if there is a U/P remaining after the FO paid the State the IAR amount claimed on the SSA-L8125 (Notice of Interim Assistance Reimbursement).\n\n2. \nDedicated account cases\n\nP.L. 104-193 requires SSA to deposit the residual amount of past-due SSI benefits (including any Federally administered State Supplement) due an eligible individual under age 18 into a dedicated account, if the past-due SSI benefits including any federally administered State Supplement exceed six times the FBR plus any Federally administered State supplement. The residual amount of past due SSI benefits is the amount remaining after IAR payments to a State, payment of attorney fees, and recovery of a prior overpayment.\n\nEffective May 22, 2006, all dedicated accounts are installment cases based on the change to the law explained in SI 02003.025B.3. and SI 02101.020.\n\n3. \nInstallment cases\n\nP.L. 104-193 requires that past-due SSI benefits (including any federally administered State supplement but minus any reimbursement for IAR) equal to or exceeding twelve (12) times the FBR including any federally administered State supplement be paid in installments under the conditions set forth in SI 02101.020.\n\nP.L. 109-171 changed the formula for determining whether SSI past due benefits must be paid in installments. Effective May 22, 2006, the new installment formula (after IAR reimbursement, payment of any representative fee, and recovery of a prior overpayment) is three times the FBR plus any federally administered Optional State Supplement (OSS) payment. For information about installment payments, see SI 02101.020.\n\nB. \nProcedures for paying retroactive SSI benefits when IAR is involved\n1. \nSummary of the rules that affect payment of retroactive SSI\n\nP.L. 108-203 requires SSA to withhold and make direct payment of all or part of the authorized fee to an attorney or non-attorney whom SSA has found eligible for direct payment. These requirements apply to fees authorized under the fee agreement or fee petition process. The law specifies that direct payment must occur after any IAR is paid to the State. It also specifies that the past-due benefits for dedicated account purposes and installment payment purposes are those remaining after any withholding for payment of the attorney or eligible non-attorney's fee. Therefore, SSA will pay all or part of the attorney or eligible non-attorney's fee when an underpayment remains after the FO has paid the State the amount claimed on the IAR Payment Pending accounting form. For more information about the fee process, see GN 03920.017, GN 03920.031, and GN 03920.033.\n\n2. \nFO prepayment steps for IAR payment pending cases\n\nFollow these instructions to prepare for issuing retroactive SSI benefits when the underpayment cannot be computed on the SSR:\n\na. \n\nManually compute the underpayment for the entire period.\n\nb. \n\nDetermine if the total U/P requires processing under the dedicated account, installment, attorney or eligible non-attorney procedures in GN 03930.030., SI 02101.010., and SI 02101.020.\n\nc. \n\nWhen the underpayment cannot be computed on the SSR, prepare an SSA-L8125 (IAR Payment Pending Case). Send it to the State or local agency by mail or fax to obtain the amount of IAR the State is due.\n\nNOTES:\n\n•\n\nFollowing the instructions in SI 02003.024, complete the claimant’s identifying information including payee and retroactive amount due summary data on the manual SSA-L8125. The SSA-L8125 form tells the State to complete the form and return it to the servicing FO within 10 working days.\n\n•\n\nFor Attorney or Eligible Non-attorney Fee Payment, Dedicated Account, or Installment Payment information, see GN 03920.017, SI 02101.010, or SI 02101.020.\n\nd. \n\nUse the Development Worksheet to establish an issue to control the return of the SSA-L8125 from the State. You should set the control period for 15 working days from the date that you send the SSA-L8125 to the State.\n\nNOTE: If a systems limitation precludes the use of MSSICS to establish an issue to control the return of the SSA-L8125 from the State, use the MDW to set a tickle date for 15 days for the return of the SSA-L8125.\n\ne. \n\nIf the SSA-L8125 is not received from the State within 15 working days of the diary control, follow up by either:\n\n•\n\nsending a Form SSA-L8125 to the State marked SECOND REQUEST; or\n\n•\n\ncontacting the State to discuss the status of the SSA-L8125.\n\nf. \n\nForward a copy of the second request to the RO for handling (or follow any supplemental RO instructions) if the State fails to respond to the second request within 10 working days of the date the second request was forwarded to the State. If the State fails to return the form within 15 working days of the second request, SSA will release the retroactive amount to the SSI individual to protect the individual from hardship that may arise from the State's failure to adhere to SSA IAR processing requirements.\n\n3. \nFO steps for releasing IAR payment to State\n\nUpon receipt of a completed SSA-L8125:\n\na. \n\nSend an A-OTP to the State for the amount shown in number 2 of the “State's Account of Reimbursement Claimed” section of the SSA-L8125;\n\nb. \n\nIf the remaining past due benefits are covered by the Dedicated Account, Installment, Attorney or Eligible Non-attorney Fee provisions, issue an A-OTP and process the case following the instructions in SI 02101.010 - SI 02101.020.\n\nc. \n\nComplete the bottom portion on page three of the SSA-L8125 and fax a copy of the paper form to the appropriate electronic folder.\n\nd. \n\nPrepare the manual notice, if applicable, following SI 02101.010 - SI 02101.020. The system is able to produce an automated notice in most situations.\n\nNOTE: Complete the claimant’s identifying information including payee and retroactive amount due summary data. The SSA-L8125 form tells the State to complete the form and return it to the servicing FO within 10 working days.\n\n4. \nNo IAR due State\n\nIf the completed SSA-L8125 indicates the State is not due IAR, release the past due benefits to the individual or the representative payee or legal guardian unless the dedicated account, installment, attorney or eligible non-attorney fee instructions in SI 02101.010 - SI 02101.020 apply. If so, follow those instructions.\n\nNOTE: The GR code must be deleted before releasing the past due payment to the individual.\n\nC. \nProcedure for returned IAR checks\n1. \nIAR Check Returned to SSA\n•\n\nThe State may return an IAR check to the FO for various reasons (e.g., the check was misdirected or is not negotiable).\n\n•\n\nThe returned IAR amount may be in the form of the SSI check or a check issued by the State agency.\n\n•\n\nTreat both types of returned IAR checks as a refund in accordance with SM 01315.075 and SM 01315.100 if it is reissued to a State agency.\n\n•\n\nIf the State IAR office returns an IAR check to the FO because it was erroneously sent to the State, reissue the returned check to the recipient or their representative payee or legal guardian in accordance with current SSI payment procedures. NOTE: Do not reissue the check to another State for any reason.\n\n2. \nReturned IAR check due the recipient\n\nIf the recipient mistakenly returns the residual IAR check to SSA, follow the returned check procedure in SM 01315.020 and SM 01315.042.\n\nD. \nProcedure for payment to State when recipient dies or disappears\n•\n\nPay the State via A-OTP; and\n\nNOTE: The system will generally accept only one A-OTP in death cases. If we issued an A-OTP and an additional payment is due, pay via manual OTP. However, a maximum of two A-OTPs can be issued on a deceased individual's record with surviving ineligible spouse and if a valid unpaid GR code is also on the record. For information about A-OTPs and surviving ineligible spouses, see SM 01901.154.\n\n•\n\nRecord the date of death on the manual SSA-L8125; and\n\n•\n\nSend the SSA-L8125 to the State per SI 02003.040.\n\nE. \nProcedure for non-receipt of IAR reimbursement payment\n\nTake the following steps to reissue the check to the IAR agency.\n\n1. Identify that we issued the payment to an IAR agency. Review the PMTH field of the SSR. Payflag 1 of PMTH will reflect either a type 2 (underpayment) or type 4 (A-OTP). Payflag 3 will reflect “1” for any IAR payment;\n\n2. Transmit the non-receipt on the Missing Check (UPMC) screen in MSSICS Direct SSR Update. For information on using the UPMC screen, see MS 00303.013; and\n\nNOTE: If you are unsure if the payment went to the correct IAR address, the FO Management Support Specialist (MSS) or Operations Supervisor (OS) can the check the Treasury's Check Information System to determine the address where the check was mailed.\n\n3. Reissue the check via A-OTP to the IAR agency as soon as possible. Include the complete IAR agency address on the One Time Payment Address (UPOA) screen. For information on using the UPOA screen, see MS 00303.023.\n\nType 2 - Underpayment\n\nIf the missing payment is type 2 (in payflag 1 of PMTH), the underpayment was calculated and generated by the system. A type 2 check must be replaced with an A-OTP using the same months as the original type 2 check. If a type 2 IAR check is returned and posts to the SSR, the system may incorrectly generate another type 2 payment to the claimant. The only way to issue a replacement check to the IAR agency is to reissue the funds by A-OTP before a returned check is posted to the SSR. If further development is needed prior to issuing an A-OTP, prevent automated release of the underpayment by posting a U TAC to the SSR via the Underpayment Processing (UOUP) screen in Direct SSR Update. Once an A-OTP is issued, you can remove the U TAC. For more information about using the UOUP screen, see MS 00304.018. For information about processing type 2 underpayments, see GN 02406.205.\n\nType 4 - A-OTP\n\nIf the missing payment is type 4 (in payflag 1 of PMTH), reissue it as an A-OTP addressed to the IAR agency for the same months as the original A-OTP. It is also possible for a returned A-OTP to result in a type 2 underpayment being issued to the claimant. Post a U TAC to the SSR via “Underpayment Processing” in Direct SSR Update to prevent the automated release of the underpayment if there will be a delay in issuing the replacement A-OTP.\n\nNOTE: The GRC code in the MPMT segment of the SSR will change from P (IAR check paid for initial claim) or G (IAR check paid for post-entitlement) to C (IAR check returned) if the IAR check is returned. However, GRC code C is informational only, it will not cause the next retroactive payment to be released to the IAR agency. Only GRC codes of R (pending IAR case for initial claim) or F (pending IAR case for posteligibility) will cause a retroactive check to be sent to the IAR address. For information about how the system updates the GR code, see SM 01005.625.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0502003025\n\t\nSI 02003.025 - IAR Payment Processing for Exception Cases and Proration Cases - 12/29/2023\nBatch run: 08/12/2026\nRev:12/29/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "whole_sha256": "f44d9b86723d0569a479056cdaf0032ca364a3041fb4ade374c697ef461bc774"
          }
        ],
        "holds": [
          "B.2.d Development Worksheet 15 working days versus MDW fallback 15 days remains distinct; no silent business/calendar conversion.",
          "SI02003.020 code-deletion authority and SI02003.040 detailed State form handling are linked dependencies, not fully supplied by this capture.",
          "SM transaction, notice, refund and replacement targets remain unreviewed; no general current system or native identity adoption.",
          "B.2.f 10-working-day RO escalation and 15-working-day release use the second-request anchor, distinct from original-request control.",
          "Generic MDW is not APP_MDW_AI; UPOA/UPMC/UOUP and SSR codes are source-named records/screens/transactions, not new IT entities."
        ],
        "negative_QA": [
          {
            "case": "SSR can compute the underpayment",
            "expected": "Do not infer the manual B.2 entry condition."
          },
          {
            "case": "First request not yet at stated control",
            "expected": "Do not infer second-request nonresponse."
          },
          {
            "case": "MDW fallback says 15 days",
            "expected": "Do not convert its unspecified day unit to working days."
          },
          {
            "case": "Second request less than 10 working days old",
            "expected": "Do not infer B.2.f regional escalation condition."
          },
          {
            "case": "State form returned",
            "expected": "Do not select unreturned-form hardship release."
          },
          {
            "case": "No IAR due but fee/installment provision applies",
            "expected": "Do not infer immediate unrestricted lump sum."
          },
          {
            "case": "GR code exists",
            "expected": "Do not assign deletion authority from this example."
          },
          {
            "case": "Check sent erroneously to a State",
            "expected": "Do not reissue to another State."
          },
          {
            "case": "Missing individual residual check",
            "expected": "Do not select IAR agency nonreceipt as an established agency case."
          },
          {
            "case": "Mailing address known",
            "expected": "Do not infer address uncertainty or unnecessary Treasury check."
          },
          {
            "case": "Type 2 not established",
            "expected": "Do not select its control branch."
          },
          {
            "case": "Type 4 not established",
            "expected": "Do not select its control branch."
          },
          {
            "case": "No replacement delay",
            "expected": "Do not infer type-4 delay-conditioned U TAC."
          },
          {
            "case": "Returned code C",
            "expected": "Do not infer that it routes the next agency payment."
          },
          {
            "case": "Death and spouse but no valid unpaid GR",
            "expected": "Do not infer the two-A-OTP conjunctive exception."
          },
          {
            "case": "Automated notice available",
            "expected": "Do not impose a universal manual notice."
          },
          {
            "case": "Recipient returned a residual check",
            "expected": "Do not substitute State refund instructions."
          },
          {
            "case": "Linked SM procedure absent",
            "expected": "Do not invent reissue evidence, date or completed return."
          }
        ]
      },
      "pendingPE4": {
        "flows": {
          "represented-pending-contact-request/represented-pending-PE-request": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "represented-pending-PE-request",
            "full_route": "represented-pending-contact-request/represented-pending-PE-request",
            "entry_conditions": [
              "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
              "The appointed representative requests direct claimant contact about that pending matter.",
              "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route."
            ],
            "steps": [
              {
                "id": "represented-pending-PE-request-source-step-1",
                "title": "Use the pending-case instruction",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Some post-entitlement or post-eligibility matters are pending cases. When that scope and the representative’s request are established, use the pending-case preparation instructions. Do not substitute the different non-pending PE record and Special Message procedure or assume all PE matters are pending.",
                "conditions": [
                  "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
                  "The appointed representative requests direct claimant contact about that pending matter.",
                  "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route."
                ],
                "source": "r18_represented_contact050",
                "section": "GN03910.050 B.2; B.1",
                "source_context_refs": [
                  "GN03910.050:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "GN050 expressly says DDS staff must defer to DI31001.010 where instructions conflict. This is not a blanket MCS/RASR rule for every DDS contact; the independently scoped DDS workflow remains separate.",
                  "GN03910.001B pending-case definition is a linked target, not a determination made by these cards. Non-pending PE handling and SNO notice-reading contacts remain distinct.",
                  "No five-business-day SNO notice clock or permission to ask unrelated evidence questions is transplanted into this pending-request route."
                ]
              },
              {
                "id": "represented-pending-PE-request-source-step-2",
                "title": "Make both required contact records",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Before contacting the claimant, document the request in MCS RPOC or CCE DROC, and also complete a report of contact in RASR. Manually document the request in the appropriate MCS or CCE screen: RASR does not automatically update either system. The OR choice is between MCS and CCE; RASR is an additional record.",
                "conditions": [
                  "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
                  "The appointed representative requests direct claimant contact about that pending matter.",
                  "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route."
                ],
                "source": "r18_represented_contact050",
                "section": "GN03910.050 B.1.a; B.2",
                "source_context_refs": [
                  "GN03910.050:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "GN050 expressly says DDS staff must defer to DI31001.010 where instructions conflict. This is not a blanket MCS/RASR rule for every DDS contact; the independently scoped DDS workflow remains separate.",
                  "GN03910.001B pending-case definition is a linked target, not a determination made by these cards. Non-pending PE handling and SNO notice-reading contacts remain distinct.",
                  "No five-business-day SNO notice clock or permission to ask unrelated evidence questions is transplanted into this pending-request route."
                ]
              },
              {
                "id": "represented-pending-PE-request-source-step-3",
                "title": "Alert the disability component through EDCS",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Complete an update after transfer in EDCS under Other Updates and provide details to alert DDS or Disability Adjudication to the representative’s request. This does not equate the agency actor with a new IT system or prove alert receipt.",
                "conditions": [
                  "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
                  "The appointed representative requests direct claimant contact about that pending matter.",
                  "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route."
                ],
                "source": "r18_represented_contact050",
                "section": "GN03910.050 B.1.b; B.2",
                "source_context_refs": [
                  "GN03910.050:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "GN050 expressly says DDS staff must defer to DI31001.010 where instructions conflict. This is not a blanket MCS/RASR rule for every DDS contact; the independently scoped DDS workflow remains separate.",
                  "GN03910.001B pending-case definition is a linked target, not a determination made by these cards. Non-pending PE handling and SNO notice-reading contacts remain distinct.",
                  "No five-business-day SNO notice clock or permission to ask unrelated evidence questions is transplanted into this pending-request route."
                ]
              },
              {
                "id": "represented-pending-PE-request-source-step-4",
                "title": "Put the report and Message in the electronic folder",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "For the electronic case, use EDCS to enter the report of contact in the CEF. Add the source Message: \"Representative Involved - prefers direct contact with the claimant.\" This Message and the EDCS update/alert instruction are separate source actions; no automatic propagation or completed record entry is inferred.",
                "conditions": [
                  "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
                  "The appointed representative requests direct claimant contact about that pending matter.",
                  "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route.",
                  "The case is electronic under this selected electronic disability scope."
                ],
                "source": "r18_represented_contact050",
                "section": "GN03910.050 B.1.c; B.2",
                "source_context_refs": [
                  "GN03910.050:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "GN050 expressly says DDS staff must defer to DI31001.010 where instructions conflict. This is not a blanket MCS/RASR rule for every DDS contact; the independently scoped DDS workflow remains separate.",
                  "GN03910.001B pending-case definition is a linked target, not a determination made by these cards. Non-pending PE handling and SNO notice-reading contacts remain distinct.",
                  "No five-business-day SNO notice clock or permission to ask unrelated evidence questions is transplanted into this pending-request route."
                ]
              },
              {
                "id": "represented-pending-PE-request-source-step-5",
                "title": "Contact only after the applicable preparation",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "After the applicable pending-case record and notification steps are complete, staff may contact the claimant directly about this pending matter. Document that contact and send a copy of the documentation to the principal representative. Choosing a card neither completes the prerequisites nor grants unrestricted contact about other issues.",
                "conditions": [
                  "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
                  "The appointed representative requests direct claimant contact about that pending matter.",
                  "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route.",
                  "The applicable pre-contact steps in B.1 have actually been completed."
                ],
                "source": "r18_represented_contact050",
                "section": "GN03910.050 B.1 final paragraph; B.2",
                "source_context_refs": [
                  "GN03910.050:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "GN050 expressly says DDS staff must defer to DI31001.010 where instructions conflict. This is not a blanket MCS/RASR rule for every DDS contact; the independently scoped DDS workflow remains separate.",
                  "GN03910.001B pending-case definition is a linked target, not a determination made by these cards. Non-pending PE handling and SNO notice-reading contacts remain distinct.",
                  "No five-business-day SNO notice clock or permission to ask unrelated evidence questions is transplanted into this pending-request route."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-PC-action-required": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "nonmedical-PC-action-required",
            "full_route": "nonmedical-evidence-PC-action/nonmedical-PC-action-required",
            "entry_conditions": [
              "The non-medical EDCS PE document requires storage.",
              "PC action is required."
            ],
            "steps": [
              {
                "id": "nonmedical-PC-action-required-source-step-1",
                "title": "Fax the document to the designated evidence section",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Create the appropriate barcoded cover sheet and document type, using the source’s section-specific generic type only if the form is not listed. Fax the document using the appropriate Regional DMA fax number. These are staff storage instructions, not a public upload endpoint or proof the image arrived.",
                "conditions": [
                  "The non-medical EDCS PE document requires storage.",
                  "PC action is required."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.2; C.3 final document bullet",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "These are non-medical EDCS post-entitlement documents that require storage and PC action. They do not resolve medical/HIT original-document or blue/yellow disposition holds.",
                  "Evidence storage, image verification and the additional SSA-409 notification retain their separate conditions. Card order is explanatory, not evidence that earlier actions occurred or an added rule withholding notification pending image availability.",
                  "Barcode routing and generic document types remain source-conditioned. Linked detailed routing procedures and local error-reporting steps are not invented or newly expanded."
                ]
              },
              {
                "id": "nonmedical-PC-action-required-source-step-2",
                "title": "Prepare the separate PC action notice",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Use SSA-409 to notify the processing center of the action needed and clearly identify the actionable material so the PC can assign an appropriate TOEL. Annotate the SSA-409 with the remark that the material has been faxed to the designated eView section only when that faxing fact is established.",
                "conditions": [
                  "The non-medical EDCS PE document requires storage.",
                  "PC action is required.",
                  "The material has actually been faxed to the designated eView section before that fact is stated in the SSA-409 remark."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.3",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "These are non-medical EDCS post-entitlement documents that require storage and PC action. They do not resolve medical/HIT original-document or blue/yellow disposition holds.",
                  "Evidence storage, image verification and the additional SSA-409 notification retain their separate conditions. Card order is explanatory, not evidence that earlier actions occurred or an added rule withholding notification pending image availability.",
                  "Barcode routing and generic document types remain source-conditioned. Linked detailed routing procedures and local error-reporting steps are not invented or newly expanded."
                ]
              },
              {
                "id": "nonmedical-PC-action-required-source-step-3",
                "title": "Send SSA-409 to the PC Paperless route",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Fax SSA-409 using the processing center’s Paperless fax number, separately from the document’s Regional DMA evidence-fax route. eView does not alert the PC to take action on the document; storing the document alone does not replace this notification. No number, endpoint, actual delivery or PC completion is supplied or inferred.",
                "conditions": [
                  "The non-medical EDCS PE document requires storage.",
                  "PC action is required."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.3",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "These are non-medical EDCS post-entitlement documents that require storage and PC action. They do not resolve medical/HIT original-document or blue/yellow disposition holds.",
                  "Evidence storage, image verification and the additional SSA-409 notification retain their separate conditions. Card order is explanatory, not evidence that earlier actions occurred or an added rule withholding notification pending image availability.",
                  "Barcode routing and generic document types remain source-conditioned. Linked detailed routing procedures and local error-reporting steps are not invented or newly expanded."
                ]
              },
              {
                "id": "nonmedical-PC-action-required-source-step-4",
                "title": "Verify the evidence image and handle an unavailable image",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Access eView and open the document to verify that all its pages were successfully faxed. If the image does not appear, use the local problem-reporting procedures rather than inventing a retry interval or confirmation. The source does not make successful image display an added prerequisite for the separately required PC notification.",
                "conditions": [
                  "The non-medical EDCS PE document requires storage.",
                  "PC action is required.",
                  "The document has been faxed under the selected storage instruction."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.2",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "These are non-medical EDCS post-entitlement documents that require storage and PC action. They do not resolve medical/HIT original-document or blue/yellow disposition holds.",
                  "Evidence storage, image verification and the additional SSA-409 notification retain their separate conditions. Card order is explanatory, not evidence that earlier actions occurred or an added rule withholding notification pending image availability.",
                  "Barcode routing and generic document types remain source-conditioned. Linked detailed routing procedures and local error-reporting steps are not invented or newly expanded."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-image-not-available": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "nonmedical-image-not-available",
            "full_route": "nonmedical-evidence-PC-action/nonmedical-image-not-available",
            "entry_conditions": [
              "The document was faxed under the selected C2 handling.",
              "The image does not appear in eView."
            ],
            "steps": [
              {
                "id": "nonmedical-image-not-available-source-step-1",
                "title": "Use the local fax-image problem procedure",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "If the image does not appear in eView after the selected fax handling, follow local procedures for reporting problems with faxed documents that are not immediately available. This page supplies no local procedure, automatic retry, retry delay, successful upload confirmation or permission to treat faxing as proven receipt.",
                "conditions": [
                  "The document was faxed under the selected C2 handling.",
                  "The image does not appear in eView."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.2",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "Non-medical EDCS PE scope only. The local error-handling target is not supplied; successful image availability and any later actions remain unverified."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-original-return": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "nonmedical-original-return",
            "full_route": "nonmedical-evidence-PC-action/nonmedical-original-return",
            "entry_conditions": [
              "The document falls within this selected non-medical C2 handling.",
              "It is an original document that should be returned to the claimant or beneficiary."
            ],
            "steps": [
              {
                "id": "nonmedical-original-return-source-step-1",
                "title": "Preserve the original-document return instruction",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "Within this selected non-medical C.2 handling, return original documents to the claimant or beneficiary as required. Successful addition of an image to eView does not remove that original-return instruction or establish that an original was returned. Do not extend the ordinary paper-destruction instruction into an authorization to destroy an original that should be returned.",
                "conditions": [
                  "The document falls within this selected non-medical C2 handling.",
                  "It is an original document that should be returned to the claimant or beneficiary."
                ],
                "source": "r18_nonmedical135",
                "section": "DI81010.135 C.2 final bullet",
                "source_context_refs": [
                  "DI81010.135:whole"
                ],
                "qualifications": [
                  "Source-defined staff instructions only; selecting a scenario establishes no case facts, permission, transmitted record, image, office receipt, accepted evidence or completed outcome.",
                  "Existing source objects, historical native record observations/context registries and source flags remain unchanged; no new link, alias, edge or current runtime certification.",
                  "The selected source conditions are not a public portal or new upload/email feature; staff source actions are not an invented customer access duty.",
                  "The paper-copy disposal and original-return instructions retain their distinct scopes. No rule for medical originals, HIT material or conflicting source disposition is derived here."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          }
        },
        "original_records": {
          "represented-pending-contact-request/represented-pending-PE-request": {
            "id": "represented-pending-PE-request",
            "title": "The issue is post-entitlement but still pending",
            "you": "Ask SSA or your representative which issue the request covers.",
            "ssa": "If the PE matter is part of a pending case and the representative requests direct contact, B2 sends staff to B1.",
            "next": "Do not use this scenario for a non-pending PE matter; it has separate documentation rules.",
            "source_context_refs": [
              "GN050-B1",
              "GN050-B2"
            ],
            "qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "outcome_routes": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false
            },
            "condition_logic": "all",
            "conditions": [
              "The matter is post-entitlement or post-eligibility.",
              "SSA has established that this issue is part of a pending case. The definition is a separate linked source.",
              "The representative requests direct contact about that pending matter.",
              "The electronic disability EDCS scope of this proposed journey applies."
            ],
            "source": "r18_represented_contact050",
            "section": "B1; B2",
            "owner": "SSA staff in the source-defined component; individual assignment not established",
            "systems": [],
            "entity_ids": [],
            "timing": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "route": "Selected staff-handling scenario; no automatic transition or completed rejoin",
            "review_status": "Selected source-linked research; actual facts, internal execution and completed outcomes unverified.",
            "source_case_conditions": [
              "The matter is post-entitlement or post-eligibility.",
              "It meets the pending-case definition; GN03910.001B remains an observed unreviewed definition target.",
              "The representative requests direct contact about that pending matter.",
              "The electronic disability EDCS scope of this proposed journey applies."
            ],
            "source_case_qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "6bbfef491f245edddad72f8b1bc8b76d4222d49490b0671f7f104f43105d8037",
              "snapshot_path": "/service/sources/GN03910.050-r18-main.txt",
              "report": "/service/r18-selected-claim-ledger.json"
            },
            "source_provenance": [
              {
                "source_code": "GN03910.050",
                "start": 2473,
                "end": 4051,
                "span_sha256": "f00d9d39ea02ff109e496ea69c87b4ca8db49a5f1558d4216a4cd05f6655a29b",
                "id": "GN050-B1",
                "exact_text": "1. \nDocumenting the record when contacting a represented claimant directly about a pending case\n\nIf the representative requests that we contact the claimant about a pending case (i.e., claim, matter, or issue), take the following actions before contacting the claimant:\n\na. \n\nDocument the request in a Report of Contact (RPOC) in the Modernized Claims System (MCS) or a Report of Contact (DROC) in the Consolidated Claims Experience (CCE).\n\nNOTE: Technicians must also complete a report of contact in the Registration, Appointment, and Services for Representatives (RASR) application. Manually document the representative's request using the appropriate screens in the MCS or CCE, because RASR does not automatically update information in those systems.\n\nb. \n\nComplete an update after transfer (UAT) in the Electronic Data Collection System (EDCS) under Other Updates and provide details to alert the DDS or Disability Adjudication (DA) to the representative's request.\n\nc. \n\nFor electronic cases:\n\n1. \n\nUse EDCS to enter the report of contact in the certified electronic folder (CEF).\n\n2. \n\nAdd the following Message: \"Representative Involved - prefers direct contact with the claimant.\" For information on Alerts and Messages, see DI 81005.040.\n\nd. \n\nFor paper cases, forward the report of contact to the appropriate component.\n\nAfter completing a. through d., you may contact the claimant directly in this pending case. Document your contact with the claimant accordingly (e.g., with a report of contact) and send a copy of that documentation to the principal representative.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203910050",
                "maintext_sha256": "6bbfef491f245edddad72f8b1bc8b76d4222d49490b0671f7f104f43105d8037",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              },
              {
                "source_code": "GN03910.050",
                "start": 4053,
                "end": 5646,
                "span_sha256": "0031e2e01e4f65c692df638a56225637657d564b4027501b19030904c98cb15c",
                "id": "GN050-B2",
                "exact_text": "2. \nDocumenting the record when contacting a represented claimant directly about post-entitlement or post-eligibility matters\n\nSome post-entitlement or post-eligibility (PE) matters fall within this chapter's definition of a pending case (see GN 03910.001B). If the representative requests we contact the claimant directly in a PE matter that is part of a pending case, take the actions described in GN 03910.050B.1.\n\nIf the representative requests we contact the claimant directly in a PE matter that is part of a non-pending case, take the following actions before contacting the claimant:\n\na. \n\nComplete Form SSA-5002 (Report of Contact) or document the report of contact screen in CCE cases, indicating that the representative has requested we contact the claimant directly and specifying the PE issue the representative is handling.\n\nb. \n\nDocument the Special Message field of the Master Beneficiary Record (MBR) or Supplemental Security Income Record Display (SSIRD), indicating that the representative has requested we contact the claimant directly and specifying the PE issue the representative is handling.\n\nc. \n\nFor electronic disability cases, use EDCS to enter the report of contact in the CEF.\n\nd. \n\nFor electronic non-disability and paper cases, fax a copy of the report of contact into the Evidence Portal (EP), as appropriate.\n\nAfter completing steps a. through d., you may contact the claimant directly in the PE matter. Document your contact with the claimant accordingly (e.g., with a report of contact) and send a copy of that documentation to the principal representative.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203910050",
                "maintext_sha256": "6bbfef491f245edddad72f8b1bc8b76d4222d49490b0671f7f104f43105d8037",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              }
            ],
            "when": "The issue is post-entitlement but still pending. The matter is post-entitlement or post-eligibility.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_staff_scenario",
              "case_applicability_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "record_context_registry_ref": {
              "kind": "source_qualified_existing_record_context_not_native_edge",
              "registry_url": "/service/r18-existing-record-context.json",
              "registry_sha256": "01d890b23cfd901814de24e9c1952546e555fed8c6b04d7905237a2e337b0e94",
              "operational_or_source_acceptance": false,
              "record_id": "represented-pending-PE-request"
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-PC-action-required": {
            "id": "nonmedical-PC-action-required",
            "title": "The processing center needs to act",
            "you": "Ask SSA what action is needed; this page does not confirm a request was received.",
            "ssa": "Use the separate SSA-409 notification as well as the document-storage steps. Identify actionable material so the PC can assign an appropriate TOEL.",
            "next": "No assignment or completed PC action is inferred.",
            "source_context_refs": [
              "DI135-C2",
              "DI135-C3"
            ],
            "qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "outcome_routes": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false
            },
            "condition_logic": "all",
            "conditions": [
              "The non-medical EDCS PE document requires storage.",
              "PC action is required."
            ],
            "source": "r18_nonmedical135",
            "section": "C2; C3",
            "owner": "SSA staff in the source-defined component; individual assignment not established",
            "systems": [],
            "entity_ids": [],
            "timing": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "route": "Selected staff-handling scenario; no automatic transition or completed rejoin",
            "review_status": "Selected source-linked research; actual facts, internal execution and completed outcomes unverified.",
            "source_case_conditions": [
              "The non-medical EDCS PE document requires storage.",
              "PC action is required."
            ],
            "source_case_qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
              "snapshot_path": "/service/sources/DI81010.135-r18-main.txt",
              "report": "/service/r18-selected-claim-ledger.json"
            },
            "source_provenance": [
              {
                "source_code": "DI81010.135",
                "start": 5258,
                "end": 6776,
                "span_sha256": "52cf2dc7661374ddd5e185f76a880bea0f415057b72d67f648cdabef9deae674",
                "id": "DI135-C2",
                "exact_text": "2. \nTo store a document for an EDCS case in eView:\n•\n\nCreate a barcoded cover sheet, in EDCS or eView, for the document per Faxing Documents into the CEF - DI 81010.090.\n\n•\n\nSelect the appropriate document type for the form/document that is being added to eView. If the document is not on the list, use the generic document type for the section:\n\nIf the document should be filed in:\tUse Document Type:\n\n\nA section -- Yellow Front\n\n\t\n\n7010 - Misc Payment Documents\n\n\n\n\nB section -- Red\n\n\t\n\n7011- Misc Jurisdictional Documents/Notices\n\n\n\n\nC section -- Green\n\n\t\n\n7012 - Misc Current Development/Temporary\n\n\n\n\nD section -- Orange\n\n\t\n\n7013 - Misc Non Disability Development\n\n\n\n\nE section -- Blue\n\n\t\n\n7014 - Misc Disability Development\n\n\n\n\nF section – Yellow Back\n\n\t\n\n7015 - Misc Medical Records\n\n•\n\nFax the document to the appropriate Regional DMA fax number per Faxing Documents into the CEF Using Barcodes - DI81010.090. (See Storing Non-Medical Evidence in the EF - DI 81010.135C.3., for important information about documents that require Program Center action.)\n\n•\n\nAccess eView, and open the document to verify that all pages of the document were successfully faxed into eView.\n\n•\n\nIf the image does not appear, follow local procedures for reporting problems when faxed documents are not immediately available in eView.\n\n•\n\nWhen the document has been successfully added to eView, destroy the paper document, even if it is signed. Keep in mind that any original documents should be returned to the claimant/beneficiary.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010135",
                "maintext_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              },
              {
                "source_code": "DI81010.135",
                "start": 6778,
                "end": 7660,
                "span_sha256": "8610edd53c22e32b35c167ffe41eb29961e6e31ff96af015197691241cec0ee5",
                "id": "DI135-C3",
                "exact_text": "3. \nIf action is required in the PC the following is needed in addition to faxing into eView:\n•\n\nUse the SSA-409 (Post Adjudicative Routing) to notify the PC of the action to be taken. Clearly identify the actionable material so it can be assigned an appropriate TOEL.\n\n•\n\nAnnotate the SSA-409 with a remark indicating the material has been faxed to the designated section in eView.\n\n•\n\nFax the SSA-409 to the PC’s Paperless Processing Center System (PPC) using the Paperless fax number.\n\nPC fax numbers are available here.\n\n•\n\nFax the document into the appropriate section using the appropriate Regional DMA fax number. (See Faxing Documents into the CEF Using Barcodes - DI 81010.090 for a list of Regional DMA fax numbers).\n\nIMPORTANT NOTE: eView will not alert the PC to take an action on the document. This is why you must also fax the SSA-409 to the PC’s Paperless fax number.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010135",
                "maintext_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              }
            ],
            "when": "The processing center needs to act. The non-medical EDCS PE document requires storage.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_staff_scenario",
              "case_applicability_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "record_context_registry_ref": {
              "kind": "source_qualified_existing_record_context_not_native_edge",
              "registry_url": "/service/r18-existing-record-context.json",
              "registry_sha256": "01d890b23cfd901814de24e9c1952546e555fed8c6b04d7905237a2e337b0e94",
              "operational_or_source_acceptance": false,
              "record_id": "nonmedical-PC-action-required"
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-image-not-available": {
            "id": "nonmedical-image-not-available",
            "title": "The image is not yet available",
            "you": "Keep your records while SSA checks the document.",
            "ssa": "Follow local procedures for reporting problems when a faxed document is not immediately available in eView.",
            "next": "The selected source does not supply a retry count, resolution deadline or completed rejoin.",
            "source_context_refs": [
              "DI135-C2"
            ],
            "qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "outcome_routes": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false
            },
            "condition_logic": "all",
            "conditions": [
              "The document was faxed under the selected C2 handling.",
              "The image does not appear in eView."
            ],
            "source": "r18_nonmedical135",
            "section": "C2",
            "owner": "SSA staff in the source-defined component; individual assignment not established",
            "systems": [],
            "entity_ids": [],
            "timing": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "route": "Selected staff-handling scenario; no automatic transition or completed rejoin",
            "review_status": "Selected source-linked research; actual facts, internal execution and completed outcomes unverified.",
            "source_case_conditions": [
              "The document was faxed under the selected C2 handling.",
              "The image does not appear in eView."
            ],
            "source_case_qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
              "snapshot_path": "/service/sources/DI81010.135-r18-main.txt",
              "report": "/service/r18-selected-claim-ledger.json"
            },
            "source_provenance": [
              {
                "source_code": "DI81010.135",
                "start": 5258,
                "end": 6776,
                "span_sha256": "52cf2dc7661374ddd5e185f76a880bea0f415057b72d67f648cdabef9deae674",
                "id": "DI135-C2",
                "exact_text": "2. \nTo store a document for an EDCS case in eView:\n•\n\nCreate a barcoded cover sheet, in EDCS or eView, for the document per Faxing Documents into the CEF - DI 81010.090.\n\n•\n\nSelect the appropriate document type for the form/document that is being added to eView. If the document is not on the list, use the generic document type for the section:\n\nIf the document should be filed in:\tUse Document Type:\n\n\nA section -- Yellow Front\n\n\t\n\n7010 - Misc Payment Documents\n\n\n\n\nB section -- Red\n\n\t\n\n7011- Misc Jurisdictional Documents/Notices\n\n\n\n\nC section -- Green\n\n\t\n\n7012 - Misc Current Development/Temporary\n\n\n\n\nD section -- Orange\n\n\t\n\n7013 - Misc Non Disability Development\n\n\n\n\nE section -- Blue\n\n\t\n\n7014 - Misc Disability Development\n\n\n\n\nF section – Yellow Back\n\n\t\n\n7015 - Misc Medical Records\n\n•\n\nFax the document to the appropriate Regional DMA fax number per Faxing Documents into the CEF Using Barcodes - DI81010.090. (See Storing Non-Medical Evidence in the EF - DI 81010.135C.3., for important information about documents that require Program Center action.)\n\n•\n\nAccess eView, and open the document to verify that all pages of the document were successfully faxed into eView.\n\n•\n\nIf the image does not appear, follow local procedures for reporting problems when faxed documents are not immediately available in eView.\n\n•\n\nWhen the document has been successfully added to eView, destroy the paper document, even if it is signed. Keep in mind that any original documents should be returned to the claimant/beneficiary.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010135",
                "maintext_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              }
            ],
            "when": "The image is not yet available. The document was faxed under the selected C2 handling.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_staff_scenario",
              "case_applicability_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "record_context_registry_ref": {
              "kind": "source_qualified_existing_record_context_not_native_edge",
              "registry_url": "/service/r18-existing-record-context.json",
              "registry_sha256": "01d890b23cfd901814de24e9c1952546e555fed8c6b04d7905237a2e337b0e94",
              "operational_or_source_acceptance": false,
              "record_id": "nonmedical-image-not-available"
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-original-return": {
            "id": "nonmedical-original-return",
            "title": "An original must be returned",
            "you": "Ask SSA about return of your original document.",
            "ssa": "Successful electronic storage does not remove the source instruction to return original documents to the claimant or beneficiary.",
            "next": "This scenario does not show the original was returned or classify a medical original under other procedures.",
            "source_context_refs": [
              "DI135-C2"
            ],
            "qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "outcome_routes": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false
            },
            "condition_logic": "all",
            "conditions": [
              "The document falls within this selected non-medical C2 handling.",
              "It is an original document that should be returned to the claimant or beneficiary."
            ],
            "source": "r18_nonmedical135",
            "section": "C2",
            "owner": "SSA staff in the source-defined component; individual assignment not established",
            "systems": [],
            "entity_ids": [],
            "timing": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "route": "Selected staff-handling scenario; no automatic transition or completed rejoin",
            "review_status": "Selected source-linked research; actual facts, internal execution and completed outcomes unverified.",
            "source_case_conditions": [
              "The document falls within this selected non-medical C2 handling.",
              "It is an original document that should be returned to the claimant or beneficiary."
            ],
            "source_case_qualifications": [
              "These are source-qualified staff handling scenarios, not a customer filing channel or access to staff systems.",
              "Selecting a scenario establishes no individual case facts, permission, actual record entry, transmitted message, receipt, completed action or successful rejoin.",
              "Native records and relationships retain their own historical observations; source review is not current runtime telemetry or acceptance."
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
              "snapshot_path": "/service/sources/DI81010.135-r18-main.txt",
              "report": "/service/r18-selected-claim-ledger.json"
            },
            "source_provenance": [
              {
                "source_code": "DI81010.135",
                "start": 5258,
                "end": 6776,
                "span_sha256": "52cf2dc7661374ddd5e185f76a880bea0f415057b72d67f648cdabef9deae674",
                "id": "DI135-C2",
                "exact_text": "2. \nTo store a document for an EDCS case in eView:\n•\n\nCreate a barcoded cover sheet, in EDCS or eView, for the document per Faxing Documents into the CEF - DI 81010.090.\n\n•\n\nSelect the appropriate document type for the form/document that is being added to eView. If the document is not on the list, use the generic document type for the section:\n\nIf the document should be filed in:\tUse Document Type:\n\n\nA section -- Yellow Front\n\n\t\n\n7010 - Misc Payment Documents\n\n\n\n\nB section -- Red\n\n\t\n\n7011- Misc Jurisdictional Documents/Notices\n\n\n\n\nC section -- Green\n\n\t\n\n7012 - Misc Current Development/Temporary\n\n\n\n\nD section -- Orange\n\n\t\n\n7013 - Misc Non Disability Development\n\n\n\n\nE section -- Blue\n\n\t\n\n7014 - Misc Disability Development\n\n\n\n\nF section – Yellow Back\n\n\t\n\n7015 - Misc Medical Records\n\n•\n\nFax the document to the appropriate Regional DMA fax number per Faxing Documents into the CEF Using Barcodes - DI81010.090. (See Storing Non-Medical Evidence in the EF - DI 81010.135C.3., for important information about documents that require Program Center action.)\n\n•\n\nAccess eView, and open the document to verify that all pages of the document were successfully faxed into eView.\n\n•\n\nIf the image does not appear, follow local procedures for reporting problems when faxed documents are not immediately available in eView.\n\n•\n\nWhen the document has been successfully added to eView, destroy the paper document, even if it is signed. Keep in mind that any original documents should be returned to the claimant/beneficiary.",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010135",
                "maintext_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
                "capture_type": "Actual IAB rendered main innerText and DOM/accessibility snapshot; not raw HTTP"
              }
            ],
            "when": "An original must be returned. The document falls within this selected non-medical C2 handling.",
            "source_qualified_branch": {
              "kind": "selected_source_qualified_staff_scenario",
              "case_applicability_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "record_context_registry_ref": {
              "kind": "source_qualified_existing_record_context_not_native_edge",
              "registry_url": "/service/r18-existing-record-context.json",
              "registry_sha256": "01d890b23cfd901814de24e9c1952546e555fed8c6b04d7905237a2e337b0e94",
              "operational_or_source_acceptance": false,
              "record_id": "nonmedical-original-return"
            }
          }
        },
        "source_contexts": [
          {
            "id": "GN03910.050:whole",
            "source_code": "GN03910.050",
            "start": 0,
            "end": 8669,
            "exact_text": "Effective Dates: 03/24/2026 - Present\nPrevious | Next\n\nTN 50 (04-26)\n\nGN 03910.050 Contacting a Represented Claimant\n\nNOTE: Disability Determination Services (DDS) employees must defer to DI 31001.010 Disability Determination Services (DDS) Responsibilities When an Appointed Representative is Involved when its instructions conflict with the instructions in this section.\n\nA. \nWhen we may contact a represented claimant directly\n\nGenerally, when a claimant has an appointed representative, we communicate directly with the representative and not the claimant. This rule applies to written and verbal communications. It does not apply to notices.\n\nWe may contact a represented claimant directly under the following circumstances:\n\n•\n\nThe representative asks us to deal directly with the claimant. For more information, see GN 03910.050B of this section;\n\n•\n\nThe claimant, who is alleging blindness or a visual impairment, elects to receive notices by first class mail with a follow-up telephone call from us to read the notices to him or her. For more information about this special notice option (SNO), see NL 01001.110 and GN 03910.050B of this section;\n\n•\n\nThe contact relates to a possible violation of the Rules of Conduct and Standards of Responsibility for Representatives. For more information about those rules, see GN 03970.010;\n\n•\n\nThere is an indication that a representative's appointment may have ended, but the information in our records is not updated or is insufficient. For more information about events that end a representative's appointment, see GN 03910.060B;\n\n•\n\nThere is ambiguity about the scope of representation. For more information about the scope of the appointment of a representative, see GN 03910.040A.3;\n\n•\n\nThe representative has not responded to multiple contact attempts. For more information on guidelines for contacting appointed representatives by telephone, see GN 01070.330; or\n\n•\n\nThe claimant has appointed multiple representatives, and it is not clear in our records who is currently appointed or who is the principal representative. For more information on multiple appointed representatives, and principal representatives, see GN 03910.040C.\n\nEXAMPLE: The claimant appointed two representatives at different times, and did not indicate which one is the principal representative. In this instance, we will contact the claimant directly to clarify who is the principal representative.\n\nB. \nHow we contact a represented claimant\n1. \nDocumenting the record when contacting a represented claimant directly about a pending case\n\nIf the representative requests that we contact the claimant about a pending case (i.e., claim, matter, or issue), take the following actions before contacting the claimant:\n\na. \n\nDocument the request in a Report of Contact (RPOC) in the Modernized Claims System (MCS) or a Report of Contact (DROC) in the Consolidated Claims Experience (CCE).\n\nNOTE: Technicians must also complete a report of contact in the Registration, Appointment, and Services for Representatives (RASR) application. Manually document the representative's request using the appropriate screens in the MCS or CCE, because RASR does not automatically update information in those systems.\n\nb. \n\nComplete an update after transfer (UAT) in the Electronic Data Collection System (EDCS) under Other Updates and provide details to alert the DDS or Disability Adjudication (DA) to the representative's request.\n\nc. \n\nFor electronic cases:\n\n1. \n\nUse EDCS to enter the report of contact in the certified electronic folder (CEF).\n\n2. \n\nAdd the following Message: \"Representative Involved - prefers direct contact with the claimant.\" For information on Alerts and Messages, see DI 81005.040.\n\nd. \n\nFor paper cases, forward the report of contact to the appropriate component.\n\nAfter completing a. through d., you may contact the claimant directly in this pending case. Document your contact with the claimant accordingly (e.g., with a report of contact) and send a copy of that documentation to the principal representative.\n\n2. \nDocumenting the record when contacting a represented claimant directly about post-entitlement or post-eligibility matters\n\nSome post-entitlement or post-eligibility (PE) matters fall within this chapter's definition of a pending case (see GN 03910.001B). If the representative requests we contact the claimant directly in a PE matter that is part of a pending case, take the actions described in GN 03910.050B.1.\n\nIf the representative requests we contact the claimant directly in a PE matter that is part of a non-pending case, take the following actions before contacting the claimant:\n\na. \n\nComplete Form SSA-5002 (Report of Contact) or document the report of contact screen in CCE cases, indicating that the representative has requested we contact the claimant directly and specifying the PE issue the representative is handling.\n\nb. \n\nDocument the Special Message field of the Master Beneficiary Record (MBR) or Supplemental Security Income Record Display (SSIRD), indicating that the representative has requested we contact the claimant directly and specifying the PE issue the representative is handling.\n\nc. \n\nFor electronic disability cases, use EDCS to enter the report of contact in the CEF.\n\nd. \n\nFor electronic non-disability and paper cases, fax a copy of the report of contact into the Evidence Portal (EP), as appropriate.\n\nAfter completing steps a. through d., you may contact the claimant directly in the PE matter. Document your contact with the claimant accordingly (e.g., with a report of contact) and send a copy of that documentation to the principal representative.\n\n3. \nContacting a represented claimant to read a notice when the claimant elects the SNO to receive notices by first class mail with a follow-up telephone call\n\nIf a represented claimant elects to receive notices by first class mail with a follow-up telephone call from us to read the notices to him or her, call the claimant directly within five (5) business days of the date of the notice and assist them with any notice-related questions they may have.\n\nNOTE: Do not initiate requests for information (e.g., invite or ask additional questions) unless the representative gives us permission to communicate directly with the claimant. Advise the claimant that additional questions unrelated to SNO and the notice must be related to us through his or her appointed representative.\n\nEXAMPLE: The field office (FO) technician calls to read a notice to a claimant because he or she elected this SNO. The technician discovers the claimant also needs to submit additional evidence such as proof of wages. The technician must not ask for this additional information during this contact. Instead, the technician must contact the representative to obtain the information or permission to contact the claimant directly.\n\nFor more information on cases involving SNO, see NL 01001.000.\n\nC. \nNotices sent to claimants and representatives\n1. \nClaim Notices\n\nWe send all notices relating to a case to the claimant and the principal representative, as appropriate. For information about the principal representative’s responsibility to keep other representatives informed, refer to GN 03910.040C.\n\n2. \nOther Notices\n\nWhile we send all claim notices to both the claimant and the principal representative, there are notices that we will also send to each appointed representative or to a representative and the representative’s affiliated entity.\n\nEXAMPLE: We send notices related to a fee agreement to the principal representative and the claimant, but we send notices relating to a fee authorization under the fee petition process to each representative who submitted a fee petition, copying the claimant on each notice.\n\nThere are also notices that we send only to the representative or the representative’s affiliated entity. These include notices to recover unauthorized fees or to correct erroneous direct payments.\n\nFor more information on:\n\n•\n\nFee petition processing notices and model notices, refer to GN 03905.075 - GN 03905.085 and GN 03930.055 - GN 03930.075.\n\n•\n\nFee agreement notices, refer to GN 03940.055 - GN 03940.085.\n\n•\n\nAssignment of direct payment, refer to GN 03910.040A and GN 03920.021.\n\n•\n\nExcess fee payment to entities notices refer to GN 03905.095.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0203910050\n\t\nGN 03910.050 - Contacting a Represented Claimant - 03/24/2026\nBatch run: 10/02/2026\nRev:03/24/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "6bbfef491f245edddad72f8b1bc8b76d4222d49490b0671f7f104f43105d8037"
          },
          {
            "id": "DI81010.135:whole",
            "source_code": "DI81010.135",
            "start": 0,
            "end": 8046,
            "exact_text": "Effective Dates: 10/17/2023 - Present\nPrevious | Next\n\nTN 63 (10-23)\n\nDI 81010.135 Storing Non-Medical Evidence in the Electronic Folder (EF)\n\nWhenever possible, annotate new non-medical evidence electronically via Modernized Claims System (MCS), Modernized Supplemental Security Income Claims System (MSSICS), Consolidated Claims Experience (CCE), Interactive Computation Facility (ICF), Shared Process, or Post-Entitlement Online System (POS) per instructions:\n\n•\n\nElectronic Evidence Documentation and Retention - GN 00301.286;\n\n•\n\nMaterial Essential to Claims Folder Documentation - GN 00301.290; and\n\n•\n\nNonessential Material to be Omitted from Title II and Title XVI Claims Folders - GN 00301.295.\n\nA. \nEvidence for pending claims or appeals\n\nWhen a copy of a document must be stored in the file for pending claims or appeals:\n\n•\n\nFax the documents into the EF per Faxing Documents into the Certified Electronic Folder (CEF) Using Barcodes - DI 81010.090.\n\n•\n\nShred the document after successful faxing, unless other procedures require the return of the evidence to the claimant.\n\nB. \nReceiving paper disability reports\n1. \nReceiving a paper disability report in the field office (FO) for Electronic Disability Collect System (EDCS) claims\n\nThe EDCS version of the disability report is deemed the official record. When processing a paper disability report take the following action:\n\n•\n\nEnter all disability report responses in conjunction with any information provided by the claimant during a disability interview into EDCS, and destroy the paper form.\n\n•\n\nWhen something is unusual about the appearance of the paper report (e.g., there are unusual drawings, extensive writing in the margins, or unusual language) and that information could be relevant to the disability determination annotate the “Remarks” section of the EDCS 3367 with a description of the relevant information included on the paper report.\n\n•\n\nWhen a paper disability report is received after the claim has been transferred to the Disability Determination Services (DDS) or Hearings Office (HO), compare it to what is already on EDCS, record any new or changed information using the EDCS Update-After-Transfer function, and destroy the paper form.\n\nNOTE: Do not collect or store worksheets from the Disability Starter Kits in the EF.\n\n2. \nReceiving a Paper Disability Report for EDCS Exclusion and Paper Cases\n\nIf a case is excluded from EDCS processing:\n\n•\n\nRetain the paper version of the disability report as the official record;\n\n•\n\nReview and complete the paper report;\n\n•\n\nObtain any incomplete or missing information or clarify as necessary; and\n\n•\n\nFile the paper report in the applicable section of the Modular Disability Folder (MDF).\n\nNOTE: For more information on exclusion cases, see Certified Electronic Folder (CEF) Exclusions - DI 81010.030.\n\n3. \nOther non-medical evidence\n\nWhen the claimant, representative, or third-party submits non-medical evidence take the following action:\n\n•\n\nAnnotate non-medical evidence on the SSA Mainframe system whenever possible (See Electronic Evidence Documentation and Retention - GN 00301.286A.2.).\n\n•\n\nWhen non-medical evidence must be stored in the disability folder, create a barcode and fax the document into the EF.\n\nREMINDER: As a general rule, if a document is signed, a signature is required, and it cannot be recorded using attestation, the original document should be faxed into eView. Also fax all Workers’ Compensation/Public Disability Benefits (WC/PDB) proofs for EDCS claims into eView.\n\nC. \nPost-entitlement (PE) material\n1. \nDetermine whether the documents need to be stored in the claims file\n•\n\nIf possible, record the evidence in MCS, RPOC or CCE Report of Contact page. Refer to What Information is Needed on EVID screen and CCE Report of Contact page in PE Situations to Identify the Type of Evidence Submitted - GN 00301.288.\n\n•\n\nMost folder documentation can be summarized on the EVID screen or CCE Report of Contact page.\n\nSome documents cannot be summarized and must be faxed into eView. To determine whether the document needs to be stored in the claims folder follow Electronic Evidence Documentation and Retention - GN 00301.286. As a general rule, if a document is signed, a signature is required, and it cannot be recorded using attestation, the original document should be faxed into eView. Also fax all WC/PDB (Workers Compensation/Public Disability Benefits) proofs for EDCS claims into eView.\n\nExamples include:\n\n–\n\nSigned Employer Report of Monthly Earnings (SSA-725s),\n\n–\n\nRepresentative appointment and fee documents,\n\n–\n\nSubsidy questionnaires,\n\n–\n\nCourt decisions,\n\n–\n\nCessation or Continuance of Disability or Blindness Determination and Transmittal for work CDRs (SSA 832/833s) and SSA-725.\n\n•\n\nPost entitlement material pertaining to non-disabled auxiliary beneficiaries entitled on the disabled Number Holder’s (NH) claim should also be stored in eView under the NH’s SSN. If the auxiliary is disabled i.e., CDB, DWB all post entitlement material will be stored in eView using the beneficiary’s BOAN.\n\n•\n\nTrailer Mail – follow Processing Trailer Material for CEF Cases - DI 81020.140. Trailer material must not be routed to the PC as was done in the former paper folder environment.\n\n2. \nTo store a document for an EDCS case in eView:\n•\n\nCreate a barcoded cover sheet, in EDCS or eView, for the document per Faxing Documents into the CEF - DI 81010.090.\n\n•\n\nSelect the appropriate document type for the form/document that is being added to eView. If the document is not on the list, use the generic document type for the section:\n\nIf the document should be filed in:\tUse Document Type:\n\n\nA section -- Yellow Front\n\n\t\n\n7010 - Misc Payment Documents\n\n\n\n\nB section -- Red\n\n\t\n\n7011- Misc Jurisdictional Documents/Notices\n\n\n\n\nC section -- Green\n\n\t\n\n7012 - Misc Current Development/Temporary\n\n\n\n\nD section -- Orange\n\n\t\n\n7013 - Misc Non Disability Development\n\n\n\n\nE section -- Blue\n\n\t\n\n7014 - Misc Disability Development\n\n\n\n\nF section – Yellow Back\n\n\t\n\n7015 - Misc Medical Records\n\n•\n\nFax the document to the appropriate Regional DMA fax number per Faxing Documents into the CEF Using Barcodes - DI81010.090. (See Storing Non-Medical Evidence in the EF - DI 81010.135C.3., for important information about documents that require Program Center action.)\n\n•\n\nAccess eView, and open the document to verify that all pages of the document were successfully faxed into eView.\n\n•\n\nIf the image does not appear, follow local procedures for reporting problems when faxed documents are not immediately available in eView.\n\n•\n\nWhen the document has been successfully added to eView, destroy the paper document, even if it is signed. Keep in mind that any original documents should be returned to the claimant/beneficiary.\n\n3. \nIf action is required in the PC the following is needed in addition to faxing into eView:\n•\n\nUse the SSA-409 (Post Adjudicative Routing) to notify the PC of the action to be taken. Clearly identify the actionable material so it can be assigned an appropriate TOEL.\n\n•\n\nAnnotate the SSA-409 with a remark indicating the material has been faxed to the designated section in eView.\n\n•\n\nFax the SSA-409 to the PC’s Paperless Processing Center System (PPC) using the Paperless fax number.\n\nPC fax numbers are available here.\n\n•\n\nFax the document into the appropriate section using the appropriate Regional DMA fax number. (See Faxing Documents into the CEF Using Barcodes - DI 81010.090 for a list of Regional DMA fax numbers).\n\nIMPORTANT NOTE: eView will not alert the PC to take an action on the document. This is why you must also fax the SSA-409 to the PC’s Paperless fax number.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0481010135\n\t\nDI 81010.135 - Storing Non-Medical Evidence in the Electronic Folder (EF) - 10/17/2023\nBatch run: 09/18/2025\nRev:10/17/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df"
          }
        ],
        "holds": [
          "GN050 pending/nonpending PE definition and actual representative request remain case predicates, not choice-induced facts. DDS conflict precedence retained.",
          "No sourceflag/native refresh: GN050 DDS010 target and local/barcode routing targets are not silently adopted beyond selected existing scope.",
          "NonmedicalC2 only; no resolution of medical/HIT originals, SSA827 consent validity or other evidence-disposition holds.",
          "Image storage/verification, PC action notification and original return remain separate source duties, not a generic upload-confirmation or retry flow.",
          "Existing12 native-context observations and registry metadata remain exact; no new API/native links, aliases or edges."
        ],
        "negative_QA": [
          {
            "id": "N01",
            "case": "PE matter not established pending",
            "required_boundary": "Do not use B1/RASR workflow for every PE matter."
          },
          {
            "id": "N02",
            "case": "Representative never requested direct contact",
            "required_boundary": "Route choice does not create a request or permission."
          },
          {
            "id": "N03",
            "case": "RASR record exists",
            "required_boundary": "Manual MCS/CCE documentation remains additional; no automatic propagation."
          },
          {
            "id": "N04",
            "case": "MCS versus CCE",
            "required_boundary": "RPOC OR DROC, plus RASR; do not require both claim-system records."
          },
          {
            "id": "N05",
            "case": "Electronic case EDCS update",
            "required_boundary": "UAT alert and CEF ROC/Message remain separate; no DA IT-entity alias."
          },
          {
            "id": "N06",
            "case": "Pre-contact steps unverified",
            "required_boundary": "No direct contact merely because cards were read."
          },
          {
            "id": "N07",
            "case": "DDS conflicting instruction",
            "required_boundary": "Retain GN050DDSprecedence and separate DDS010 workflow."
          },
          {
            "id": "N08",
            "case": "SNO contact",
            "required_boundary": "No transplanted5business clock or new wage-evidence-question permission."
          },
          {
            "id": "N09",
            "case": "Document stored in eView only",
            "required_boundary": "Not a substitute for SSA409PCPaperless notification when PC action required."
          },
          {
            "id": "N10",
            "case": "Image unavailable",
            "required_boundary": "Local procedure unspecified; no automatic retry/time or successful upload receipt."
          },
          {
            "id": "N11",
            "case": "SSA409 remark claims fax complete",
            "required_boundary": "Actual faxing fact must be established, not inferred from route choice."
          },
          {
            "id": "N12",
            "case": "PC Paperless versus Regional DMA",
            "required_boundary": "Keep notification and document fax destinations distinct."
          },
          {
            "id": "N13",
            "case": "Document type not on list",
            "required_boundary": "Use appropriate section generic type; no invented code/automatic categorization."
          },
          {
            "id": "N14",
            "case": "Original should be returned",
            "required_boundary": "No destruction solely because image was added."
          },
          {
            "id": "N15",
            "case": "Medical/HIT original",
            "required_boundary": "NonmedicalC2 does not resolve separate originaldispositionholds."
          },
          {
            "id": "N16",
            "case": "Image verification pending",
            "required_boundary": "Do not invent successfuldisplay as a new prerequisite to PCnotification."
          },
          {
            "id": "N17",
            "case": "Source or fullchain/record/flow changed",
            "required_boundary": "Future exactguard must reject; no blindflow projection."
          },
          {
            "id": "N18",
            "case": "Request sent or record visible",
            "required_boundary": "No case outcome, permission, receipt, benefit action or completed rejoin."
          }
        ],
        "preparation_timing_actor_rejoin_profiles": {
          "represented-pending-contact-request/represented-pending-PE-request": {
            "preparation_and_case_conditions": [
              "The matter is post-entitlement or post-eligibility, and SSA has established that it is part of a pending case under the separately linked definition.",
              "The appointed representative requests direct claimant contact about that pending matter.",
              "This selected walkthrough’s electronic disability/EDCS scope applies. The pending-case classification and the representative’s request are actual facts to establish, not consequences of choosing the route."
            ],
            "ordered_source_card_ids": [
              "represented-pending-PE-request-source-step-1",
              "represented-pending-PE-request-source-step-2",
              "represented-pending-PE-request-source-step-3",
              "represented-pending-PE-request-source-step-4",
              "represented-pending-PE-request-source-step-5"
            ],
            "source_actors": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "original_timing_exact": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "selected_numeric_interval": null,
            "timing_limit": "Source conditional order only. No overall processing duration, upload confirmation, retry timer, contact deadline or PC completion estimate.",
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-PC-action-required": {
            "preparation_and_case_conditions": [
              "The non-medical EDCS PE document requires storage.",
              "PC action is required."
            ],
            "ordered_source_card_ids": [
              "nonmedical-PC-action-required-source-step-1",
              "nonmedical-PC-action-required-source-step-2",
              "nonmedical-PC-action-required-source-step-3",
              "nonmedical-PC-action-required-source-step-4"
            ],
            "source_actors": [
              "SSA staff",
              "SSA staff",
              "SSA staff",
              "SSA staff"
            ],
            "original_timing_exact": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "selected_numeric_interval": null,
            "timing_limit": "Source conditional order only. No overall processing duration, upload confirmation, retry timer, contact deadline or PC completion estimate.",
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-image-not-available": {
            "preparation_and_case_conditions": [
              "The document was faxed under the selected C2 handling.",
              "The image does not appear in eView."
            ],
            "ordered_source_card_ids": [
              "nonmedical-image-not-available-source-step-1"
            ],
            "source_actors": [
              "SSA staff"
            ],
            "original_timing_exact": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "selected_numeric_interval": null,
            "timing_limit": "Source conditional order only. No overall processing duration, upload confirmation, retry timer, contact deadline or PC completion estimate.",
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          },
          "nonmedical-evidence-PC-action/nonmedical-original-return": {
            "preparation_and_case_conditions": [
              "The document falls within this selected non-medical C2 handling.",
              "It is an original document that should be returned to the claimant or beneficiary."
            ],
            "ordered_source_card_ids": [
              "nonmedical-original-return-source-step-1"
            ],
            "source_actors": [
              "SSA staff"
            ],
            "original_timing_exact": "Source instructions do not establish a case-completion estimate or measured processing time.",
            "selected_numeric_interval": null,
            "timing_limit": "Source conditional order only. No overall processing duration, upload confirmation, retry timer, contact deadline or PC completion estimate.",
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual applicability, staff actions, communication, records, images, receipt and successful continuation remain unverified."
              ]
            }
          }
        }
      }
    },
    "source_reviews": {
      "CDB9": {
        "source_package_sha256": "e472c6fca85409d2203bf600d31bdf003535c9590fa931bfce50db3ee12a6041",
        "independent_primary_source_review_sha256": "b69cf2f3cd95a1d421cfe641ad26f15861017fb60bd304ef5292493a3ce5e805"
      },
      "IAR8": {
        "source_package_sha256": "bc76b2315e505d55f6795f6b74e980a8fe6cd91014b61f9a4dbb388e8e2439fb",
        "independent_primary_source_review_sha256": "664dda73335f228d04d60238c2195c1a0b575bf2ffb0ea2e9ded672c00330f94"
      },
      "pendingPE4": {
        "source_package_sha256": "b50e74667edec17ee0859dfd3a3af4249c942a524de030febd7538af146fb006",
        "independent_primary_source_review_sha256": "ced1c8240eeedc05ad16bfd45670a21e57657bcdd9a2a16507dd95bde928ce02"
      }
    },
    "public_capture_provenance": [
      {
        "url": "/service/sources/r30-CDB9-RS00203.085-main.txt",
        "sha256": "fce4c40ebacd80a8dfbee985ad8767ce9ad39fc2f2b6bbe1489ee212538225af",
        "capture_type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r30-CDB9-RS00203.085-body-rendered.html.txt",
        "sha256": "e42e1ecc0733ba8c7e1198dfa785f6fa242a361de0a000e047ae87f3f9d5f4c7",
        "capture_type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r30-IAR8-SI02003.025-main.txt",
        "sha256": "f44d9b86723d0569a479056cdaf0032ca364a3041fb4ade374c697ef461bc774",
        "capture_type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r30-IAR8-SI02003.025-body-rendered.html.txt",
        "sha256": "a01e1529939452ff39c7d05604ce6ec1fbb89cd00508da9a03176673696ac2d6",
        "capture_type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r30-pendingPE4-GN03910.050-main.txt",
        "sha256": "6bbfef491f245edddad72f8b1bc8b76d4222d49490b0671f7f104f43105d8037",
        "capture_type": "Actual rootIAB whole rendered main and DOM/accessibility snapshot/capture metadata; not rawHTTP bytes."
      },
      {
        "url": "/service/sources/r30-pendingPE4-GN03910.050-dom.txt",
        "sha256": "665555e7ed8e3cd25d4f44841849bfaf7ca8802c3949eb693c04a4b614f5ab2f",
        "capture_type": "Actual rootIAB whole rendered main and DOM/accessibility snapshot/capture metadata; not rawHTTP bytes."
      },
      {
        "url": "/service/sources/r30-pendingPE4-DI81010.135-main.txt",
        "sha256": "0fbbf08994c830df58c0f98beeabb692882e3c29d1e99600f982f9f1eec1b8df",
        "capture_type": "Actual rootIAB whole rendered main and DOM/accessibility snapshot/capture metadata; not rawHTTP bytes."
      },
      {
        "url": "/service/sources/r30-pendingPE4-DI81010.135-dom.txt",
        "sha256": "e79f0da4b6fd9f633b4980538a8838f92838ce1fd7eb911d908dabbaabb3ea60",
        "capture_type": "Actual rootIAB whole rendered main and DOM/accessibility snapshot/capture metadata; not rawHTTP bytes."
      }
    ],
    "limits": [
      "The source cards are conditional published staff instructions, not observations of completed case actions or customer deadlines.",
      "Earlier records, source dates, status/history and linked-target holds remain unchanged. No deletion authority, eligibility, capability, permission or successful rejoin is established.",
      "IAR020 is a separate later dependency capture; this package retains the approved IAR025 authority hold and does not adopt an inferred coordinator transaction power."
    ],
    "no_new_native_links_or_acceptance": true
  },
  "r32_ALJ_disclosure19": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "NINETEEN_SELECTED_ALJ_AND_DISCLOSURE_SEQUENCES_SOURCE_REVIEWED_NOT_POLICY_OR_CASE_ACCEPTANCE",
    "selected_flow_count": 19,
    "checked_on": "2026-11-01",
    "packages": {
      "ALJ12": {
        "flows": {
          "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-notice-copy-present-reported-nonreceipt",
            "full_route": "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt",
            "entry_conditions": [
              "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
              "A copy of the reconsideration notice is in the file.",
              "The claimant alleges not receiving the original notice."
            ],
            "steps": [
              {
                "id": "alj-notice-copy-present-reported-nonreceipt-source-step-1",
                "title": "Provide the notice copy and take the request",
                "kind": "ssa",
                "actor": "FO",
                "action": "Make a copy of the reconsideration notice for the claimant and accept the hearing request as instructed. The claimant’s allegation that the original was not received remains separate from the copy being present in the file.",
                "conditions": [
                  "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
                  "A copy of the reconsideration notice is in the file.",
                  "The claimant alleges not receiving the original notice."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.3.b",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-notice-copy-present-reported-nonreceipt-source-step-2",
                "title": "Record the reported nonreceipt",
                "kind": "ssa",
                "actor": "FO",
                "action": "Document that the claimant did not receive the original reconsideration notice. Accepting a request or documenting an allegation does not decide timeliness, good cause or the appeal outcome.",
                "conditions": [
                  "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
                  "A copy of the reconsideration notice is in the file.",
                  "The claimant alleges not receiving the original notice."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.3.b",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-notice-copy-absent-reconsideration-indicated",
            "full_route": "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated",
            "entry_conditions": [
              "No copy of the reconsideration notice is in the file.",
              "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
            ],
            "steps": [
              {
                "id": "alj-notice-copy-absent-reconsideration-indicated-source-step-1",
                "title": "Accept the request and contact DDS",
                "kind": "ssa",
                "actor": "FO",
                "action": "When the notice copy is absent but the file indicates a reconsideration determination, accept the hearing request and contact DDS by email or phone. The source gives SSA-831 Remarks and DDSQ as evidence examples; no current system result is presumed.",
                "conditions": [
                  "No copy of the reconsideration notice is in the file.",
                  "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.3.c",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-notice-copy-absent-reconsideration-indicated-source-step-2",
                "title": "Arrange the specified duplicate copies",
                "kind": "ssa",
                "actor": "SSA staff",
                "action": "The source calls for an immediate duplicate reconsideration notice to the claimant and FO, and a copy to the attorney or non-attorney representative when applicable. If SSA-831 is also missing, ask DDS for its copy. Do not infer that the copies arrived or establish an actual notice-receipt date.",
                "conditions": [
                  "No copy of the reconsideration notice is in the file.",
                  "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.3.c",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-no-notice-no-reconsideration-indication",
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication",
            "entry_conditions": [
              "No reconsideration notice copy is found.",
              "No indication that a reconsideration determination was made is found after the source-defined checks.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "steps": [
              {
                "id": "alj-no-notice-no-reconsideration-indication-source-step-1",
                "title": "Use the separate appeal-stage instruction",
                "kind": "ssa",
                "actor": "FO",
                "action": "If the prescribed file checks show neither a notice copy nor evidence of a reconsideration determination, follow the hearing-before-reconsideration instruction. That absence alone does not determine the real appeal stage. The conditional choices require the actual next appeal level and the claimant’s decision; no automatic conversion or dismissal occurs here.",
                "conditions": [
                  "No reconsideration notice copy is found.",
                  "No indication that a reconsideration determination was made is found after the source-defined checks.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.3.c; GN03103.120 A-B",
                "source_context_refs": [
                  "DI12010.001:whole",
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-missing-3441-or-827-no-transfer-delay",
            "full_route": "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay",
            "entry_conditions": [
              "This is the ALJ-hearing request handling covered by DI12010.001.",
              "The file lacks an SSA3441 or SSA827 with the appeal."
            ],
            "steps": [
              {
                "id": "alj-missing-3441-or-827-no-transfer-delay-source-step-1",
                "title": "Keep the national transfer and no-follow-up limits",
                "kind": "ssa",
                "actor": "FO",
                "action": "Under the selected national instruction, do not delay transfer because the file lacks SSA-3441 or SSA-827 with the appeal; transfer without the missing form and do not make follow-up attempts to obtain one. Follow differing regional instructions. This is not a waiver for every missing document or a finding of valid consent or disclosure authority.",
                "conditions": [
                  "This is the ALJ-hearing request handling covered by DI12010.001.",
                  "The file lacks an SSA3441 or SSA827 with the appeal."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.4",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-concurrent-medical-appeal-scope",
            "full_route": "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope",
            "entry_conditions": [
              "The application claims Title II and Title XVI benefits OR more than one Title II disability benefit.",
              "The claimant appeals a medical issue for any of those benefits."
            ],
            "steps": [
              {
                "id": "alj-concurrent-medical-appeal-scope-source-step-1",
                "title": "Keep the medical issues together for ALJ review",
                "kind": "ssa",
                "actor": "FO",
                "action": "When the application includes Title II and Title XVI benefits or more than one Title II disability benefit and any medical issue is appealed, the source places the entire medical claim under review, including favorable disability findings. Transfer the medical case as concurrent; this does not decide the merits or a payment outcome.",
                "conditions": [
                  "The application claims Title II and Title XVI benefits OR more than one Title II disability benefit.",
                  "The claimant appeals a medical issue for any of those benefits."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.5",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-concurrent-medical-appeal-scope-source-step-2",
                "title": "Exclude the separately unappealed technical denial",
                "kind": "ssa",
                "actor": "FO",
                "action": "Do not forward another claim that was technically denied and is not under appeal, because its issues differ. Both the technical-denial and not-under-appeal conditions matter; do not exclude a medical issue merely because another claim was denied.",
                "conditions": [
                  "The application claims Title II and Title XVI benefits OR more than one Title II disability benefit.",
                  "The claimant appeals a medical issue for any of those benefits.",
                  "The other claim was technically denied AND that technical denial is not under appeal."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.5",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-concurrent-medical-appeal-scope-source-step-3",
                "title": "Preserve the limited favorable-action qualification",
                "kind": "ssa",
                "actor": "FO",
                "action": "The FO may still effectuate the favorable determination, but the claimant should know that the medical determination under review is not final. This conditional permission does not order an award or establish eligibility, actual effectuation or payment.",
                "conditions": [
                  "The application claims Title II and Title XVI benefits OR more than one Title II disability benefit.",
                  "The claimant appeals a medical issue for any of those benefits.",
                  "A favorable determination exists and its separately applicable effectuation requirements are established."
                ],
                "source": "r20_ALJ_request001",
                "section": "DI12010.001 B.5",
                "source_context_refs": [
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-reconsideration-next-claimant-chooses",
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses",
            "entry_conditions": [
              "The parent file/no-indication scenario applies.",
              "Reconsideration is in fact the next appeal level due.",
              "The claimant chooses reconsideration and has not previously filed it.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "steps": [
              {
                "id": "alj-reconsideration-next-claimant-chooses-source-step-1",
                "title": "Explain the actual next appeal step",
                "kind": "ssa",
                "actor": "FO",
                "action": "Explain reconsideration as the next appeal step and the source’s ordinary dismissal warning for a premature hearing, while retaining the separately stated dual-determination exception. No dismissal or stage decision is made by this walkthrough.",
                "conditions": [
                  "The parent file/no-indication scenario applies.",
                  "Reconsideration is in fact the next appeal level due.",
                  "The claimant chooses reconsideration and has not previously filed it.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 A-B; C exception",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-reconsideration-next-claimant-chooses-source-step-2",
                "title": "Assist with the chosen reconsideration request",
                "kind": "ssa",
                "actor": "FO",
                "action": "Assist the claimant in requesting reconsideration when that is the claimant’s decision and reconsideration has not already been filed. A written appeal can be interpreted as reconsideration only when it is in fact the next level due, unless the claimant insists otherwise. This card does not establish filing or completion.",
                "conditions": [
                  "The parent file/no-indication scenario applies.",
                  "Reconsideration is in fact the next appeal level due.",
                  "The claimant chooses reconsideration and has not previously filed it.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 A-B",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-claimant-insists-before-reconsideration",
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration",
            "entry_conditions": [
              "The parent file/no-indication scenario applies.",
              "The source’s explanation that reconsideration is next/before completion has been given.",
              "The claimant still insists on filing for a hearing.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "steps": [
              {
                "id": "alj-claimant-insists-before-reconsideration-source-step-1",
                "title": "Complete the hearing-request form under the stated choice",
                "kind": "ssa",
                "actor": "FO",
                "action": "If the claimant still insists on a hearing after the explanation, complete HA-501-U5. Do not automatically convert the request into reconsideration or decide what the ALJ will do.",
                "conditions": [
                  "The parent file/no-indication scenario applies.",
                  "The source’s explanation that reconsideration is next/before completion has been given.",
                  "The claimant still insists on filing for a hearing.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 B",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-claimant-insists-before-reconsideration-source-step-2",
                "title": "Attach the specified contact record to the right copies",
                "kind": "ssa",
                "actor": "FO",
                "action": "Attach a Report of Contact with the brief explanation given and why the claimant still insists to all form copies except the claimant’s. Use the separately linked processing instructions; they are not expanded here. No actual dismissal or hearing decision is inferred.",
                "conditions": [
                  "The parent file/no-indication scenario applies.",
                  "The source’s explanation that reconsideration is next/before completion has been given.",
                  "The claimant still insists on filing for a hearing.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 B",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-dual-determination-proper-hearing-exception",
            "full_route": "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception",
            "entry_conditions": [
              "SSA made a reconsideration determination and an initial determination on the same case.",
              "A hearing is proper with respect to the reconsideration determination.",
              "The initial determination has not been reconsidered."
            ],
            "steps": [
              {
                "id": "alj-dual-determination-proper-hearing-exception-source-step-1",
                "title": "Preserve the proper-hearing exception",
                "kind": "ssa",
                "actor": "FO",
                "action": "For the same-case reconsideration and initial determinations, when a hearing is proper for the reconsideration determination, the source says the ALJ will not dismiss merely because the initial determination was not reconsidered. Send the entire claims file to the ALJ. This exception does not rule out other dismissal grounds or establish the actual ALJ action.",
                "conditions": [
                  "SSA made a reconsideration determination and an initial determination on the same case.",
                  "A hearing is proper with respect to the reconsideration determination.",
                  "The initial determination has not been reconsidered."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 C EXCEPTION",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-premature-request-PC-handling": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-premature-request-PC-handling",
            "full_route": "hearing-after-medical-reconsideration/alj-premature-request-PC-handling",
            "entry_conditions": [
              "PC is handling the selected hearing-request-before-reconsideration procedure.",
              "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "steps": [
              {
                "id": "alj-premature-request-PC-handling-source-step-1",
                "title": "Prepare the folder when PC is told a hearing was filed",
                "kind": "ssa",
                "actor": "PC",
                "action": "When advised that a hearing has been filed, immediately prepare the folder for transmittal to the servicing FO under the separately linked forwarding instruction. This conditional instruction does not establish that a hearing was actually filed or the folder transferred.",
                "conditions": [
                  "PC is handling the selected hearing-request-before-reconsideration procedure.",
                  "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established.",
                  "PC is advised that a hearing has been filed."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 C",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-premature-request-PC-handling-source-step-2",
                "title": "Handle a direct claimant letter under the source stage rules",
                "kind": "ssa",
                "actor": "PC",
                "action": "If PC receives the claimant’s hearing-request letter directly, contact the claimant and explain the source’s appeal-stage points. Prepare a Report of Contact and the appropriate reconsideration or hearing form if necessary. The actual stage and claimant choice remain material; this is not automatic conversion.",
                "conditions": [
                  "PC is handling the selected hearing-request-before-reconsideration procedure.",
                  "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established.",
                  "PC receives the claimant’s letter directly requesting a hearing."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 C; B",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-premature-request-PC-handling-source-step-3",
                "title": "Keep final related action pending the ALJ action",
                "kind": "ssa",
                "actor": "PC",
                "action": "Do not take final related action pending ALJ action on the hearing request. On actual notice of the ALJ action, PC may complete pending action or consider additional evidence. This is not an automatic post-dismissal rejoin or actual benefit determination.",
                "conditions": [
                  "PC is handling the selected hearing-request-before-reconsideration procedure.",
                  "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing.",
                  "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
                ],
                "source": "r20_ALJ_stage120",
                "section": "GN03103.120 C",
                "source_context_refs": [
                  "GN03103.120:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-late-paper-explanation-routing",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing",
            "entry_conditions": [
              "The existing late-filing parent scenario and the selected source late-hearing procedure apply; actual timeliness remains to be established.",
              "The case is paper.",
              "A written explanation is already available for routing; this flow does not decide when to obtain it."
            ],
            "steps": [
              {
                "id": "alj-late-paper-explanation-routing-source-step-1",
                "title": "Route the existing original explanation",
                "kind": "ssa",
                "actor": "FO",
                "action": "For the paper late-hearing case, attach the original available written explanation to the Hearing Office File copy of HA-501-U5. This routing instruction does not add a universal duty to solicit a new statement through every contact channel.",
                "conditions": [
                  "The existing late-filing parent scenario and the selected source late-hearing procedure apply; actual timeliness remains to be established.",
                  "The case is paper.",
                  "A written explanation is already available for routing; this flow does not decide when to obtain it."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 steps1-2",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-late-paper-explanation-routing-source-step-2",
                "title": "Keep the Claims Folder copy",
                "kind": "ssa",
                "actor": "FO",
                "action": "Attach a copy of the explanation to the Claims Folder Copy. Do not treat routing copies as proof that the hearing office received them.",
                "conditions": [
                  "The existing late-filing parent scenario and the selected source late-hearing procedure apply; actual timeliness remains to be established.",
                  "The case is paper.",
                  "A written explanation is already available for routing; this flow does not decide when to obtain it."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 step3",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-late-paper-explanation-routing-source-step-3",
                "title": "Explain who decides an extension",
                "kind": "ssa",
                "actor": "FO",
                "action": "Advise that the ALJ decides whether to extend the hearing-filing time. The source’s 60-day receipt rule and rebuttable 5-day receipt presumption are not a deadline calculator or a good-cause ruling here.",
                "conditions": [
                  "The existing late-filing parent scenario and the selected source late-hearing procedure apply; actual timeliness remains to be established.",
                  "The case is paper.",
                  "A written explanation is already available for routing; this flow does not decide when to obtain it."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 opening; step4",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-late-electronic-explanation-recording",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording",
            "entry_conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is electronic and good-cause information is being handled."
            ],
            "steps": [
              {
                "id": "alj-late-electronic-explanation-recording-source-step-1",
                "title": "Record the appeal and good-cause material",
                "kind": "ssa",
                "actor": "FO",
                "action": "For the electronic case, load the appeal in MCS or MSSICS using the appeals program and scan the good-cause information into the electronic folder under the linked processing instructions. Recording does not establish good cause, accepted filing or successful scanning.",
                "conditions": [
                  "The existing late-filing parent scenario applies.",
                  "The case is electronic and good-cause information is being handled."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 step3",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-late-electronic-explanation-recording-source-step-2",
                "title": "Keep the extension decision with the ALJ",
                "kind": "ssa",
                "actor": "FO",
                "action": "Advise that the ALJ decides whether to extend the hearing-filing time. No determination of actual receipt, the rebuttable receipt presumption, late filing or good cause is made by selecting this card.",
                "conditions": [
                  "The existing late-filing parent scenario applies.",
                  "The case is electronic and good-cause information is being handled."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 opening; step4",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "alj-late-paper-worsening-new-application",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application",
            "entry_conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is paper.",
              "The claimant alleges worsening condition OR additional impairment."
            ],
            "steps": [
              {
                "id": "alj-late-paper-worsening-new-application-source-step-1",
                "title": "Keep the new-paper-application instruction narrowly conditioned",
                "kind": "ssa",
                "actor": "FO",
                "action": "The published paper-case step calls for a new paper application only when the claimant alleges a worsening condition or an additional impairment, and forwarding it to the ALJ with HA-501-U5. The separate subsequent-application policy referenced by DI12010.001 remains a linked limit; this card does not decide that an actual new application is permitted or complete one.",
                "conditions": [
                  "The existing late-filing parent scenario applies.",
                  "The case is paper.",
                  "The claimant alleges worsening condition OR additional impairment."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 step5; DI12010.001 opening NOTE",
                "source_context_refs": [
                  "DI12010.002:whole",
                  "DI12010.001:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-late-paper-worsening-new-application-source-step-2",
                "title": "Record the source’s pending-claim context",
                "kind": "ssa",
                "actor": "FO",
                "action": "The source calls for entering the new claim on the generic Modernized Development Worksheet to show it pending at OHO. Generic MDW is not identified with MDW AI, and this instruction does not establish that a new claim was entered.",
                "conditions": [
                  "The existing late-filing parent scenario applies.",
                  "The case is paper.",
                  "The claimant alleges worsening condition OR additional impairment.",
                  "The source-conditioned new paper application is actually being processed under the applicable instructions."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 step5",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              },
              {
                "id": "alj-late-paper-worsening-new-application-source-step-3",
                "title": "Give the conditional return instruction",
                "kind": "ssa",
                "actor": "FO",
                "action": "Advise OHO to return the new claim to the FO if the ALJ dismisses the hearing request so it can be pursued. The actual dismissal and return remain unknown; there is no automatic rejoin or general new-application rule for every late hearing.",
                "conditions": [
                  "The existing late-filing parent scenario applies.",
                  "The case is paper.",
                  "The claimant alleges worsening condition OR additional impairment."
                ],
                "source": "r20_ALJ_late002",
                "section": "DI12010.002 step5",
                "source_context_refs": [
                  "DI12010.002:whole"
                ],
                "qualifications": [
                  "Selected ALJ-hearing source instructions only. This is distinct from a DHO medical-cessation reconsideration hearing, not an actual case filing, deadline calculation, good-cause ruling, dismissal or payment result.",
                  "The usual after-reconsideration story does not establish the conditions for a before-completed-reconsideration exception. Missing records do not themselves establish the actual appeal stage.",
                  "Source initial-prototype wording is retained as captured history; no current 2026 prototype deployment or new initial-stage bypass is asserted. Source MISSICS spelling is not silently aliased to MSSICS or CCE.",
                  "Linked forms, appeal-stage, good-cause, electronic-processing and subsequent-claim procedures retain their own scope. No source/native status promotion, new alias/edge or operational system acceptance.",
                  "No request, copy, record, notice delivery, office receipt, benefit action or successful continuation is established by choosing a card."
                ]
              }
            ],
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          }
        },
        "original_records": {
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing": {
            "id": "alj-late-paper-explanation-routing",
            "title": "A written late-filing explanation is routed with a paper case",
            "when": "Staff are handling an existing written explanation in a paper late-hearing case.",
            "you": "Keep your explanation and any submission record.",
            "ssa": "The source puts the original explanation with the Hearing Office File copy of the hearing request and a copy with the Claims Folder Copy.",
            "next": "This routing example does not add a universal requirement for FO to solicit a new statement through every contact channel.",
            "condition_logic": "all",
            "conditions": [
              "The existing late-filing parent scenario applies and staff are handling the source’s late-hearing procedure.",
              "The case is paper.",
              "A written explanation is available for routing; this draft does not decide when to obtain it."
            ],
            "source_case_conditions": [
              "The existing late-filing parent scenario applies and staff are handling the source’s late-hearing procedure.",
              "The case is paper.",
              "A written explanation is available for routing; this draft does not decide when to obtain it."
            ],
            "source_context_refs": [
              "002-clock",
              "002-steps1-4"
            ],
            "source_provenance": [
              {
                "id": "002-clock",
                "source_code": "DI12010.002",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010002",
                "start": 145,
                "end": 505,
                "exact_text": "The time limit for requesting an appeal is 60 days after the date the claimant receives notice of the determination or decision. The date that the individual receives the notice is presumed to be 5 days after the date on the notice unless the individual can show us that he or she did not receive it within the 5 days. If the request for hearing is filed late:",
                "span_sha256": "dd861d48654d405d6a8e620de3fc005f5db407cd5d8c7247b83ac98a84d77f92",
                "maintext_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72"
              },
              {
                "id": "002-steps1-4",
                "source_code": "DI12010.002",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010002",
                "start": 507,
                "end": 1336,
                "exact_text": "1. \n\nFollow procedures in GN 03101.020B, (Good Cause for Extending Time Limit). For additional information on a late request for hearing see GN 03103.010C.7.\n\n2. \n\nFor paper cases, attach original statement which explains reason for filing late to the “Hearing Office File” copy of the HA 501-U5 (Request for Hearing).\n\n3. \n\nAttach a copy of explanation to the “Claims Folder Copy.” For electronic cases, load the appeal into the Modernized Claim System (MCS) or the Modernized Supplemental Security Income Claims System (MSSICS) using the appeals program and scan the good cause information into the electronic folder. For additional information see DI 81010.150B.3. and DI 81010.150C.5.\n\n4. \n\nAdvise the claimant that the ALJ will decide whether to grant an extension for filing the hearing request. (See HALLEX I-2-4-15).\n\n5. ",
                "span_sha256": "a7eefd704de45f52f137f51b68083ae7793251fa5f18b4d75ad66b5f141fe866",
                "maintext_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72"
              }
            ],
            "source_instruction_summary": "Paper originalstatement→HOFilecopyHA501; copy→ClaimsFolderCopy. Collection/channelrules020B/03103.010C7/D2 scopes remain separate. ALJdecidesextension; no FOgoodcausefinding or calculateddeadline.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "FORM_R96_HA501U5"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "parent_full_route": "hearing-after-medical-reconsideration/late-filing",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing",
            "source": "r20_ALJ_late002",
            "section": "002-clock; 002-steps1-4",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "HA-501-U5 Request for Hearing by Administrative Law Judge"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72",
              "snapshot_path": "/service/sources/DI12010.002-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording": {
            "id": "alj-late-electronic-explanation-recording",
            "title": "The late-hearing material is recorded electronically",
            "when": "Staff handle the appeal and good-cause material in an electronic case.",
            "you": "Keep the explanation and confirmation you receive.",
            "ssa": "Staff load the appeal using MCS or MSSICS and scan the good-cause information into the electronic folder under the linked processing instructions.",
            "next": "The ALJ decides whether to extend time. Recording or scanning does not establish good cause or acceptance.",
            "condition_logic": "all",
            "conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is electronic and good-cause information is being handled."
            ],
            "source_case_conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is electronic and good-cause information is being handled."
            ],
            "source_context_refs": [
              "002-clock",
              "002-steps1-4"
            ],
            "source_provenance": [
              {
                "id": "002-clock",
                "source_code": "DI12010.002",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010002",
                "start": 145,
                "end": 505,
                "exact_text": "The time limit for requesting an appeal is 60 days after the date the claimant receives notice of the determination or decision. The date that the individual receives the notice is presumed to be 5 days after the date on the notice unless the individual can show us that he or she did not receive it within the 5 days. If the request for hearing is filed late:",
                "span_sha256": "dd861d48654d405d6a8e620de3fc005f5db407cd5d8c7247b83ac98a84d77f92",
                "maintext_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72"
              },
              {
                "id": "002-steps1-4",
                "source_code": "DI12010.002",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010002",
                "start": 507,
                "end": 1336,
                "exact_text": "1. \n\nFollow procedures in GN 03101.020B, (Good Cause for Extending Time Limit). For additional information on a late request for hearing see GN 03103.010C.7.\n\n2. \n\nFor paper cases, attach original statement which explains reason for filing late to the “Hearing Office File” copy of the HA 501-U5 (Request for Hearing).\n\n3. \n\nAttach a copy of explanation to the “Claims Folder Copy.” For electronic cases, load the appeal into the Modernized Claim System (MCS) or the Modernized Supplemental Security Income Claims System (MSSICS) using the appeals program and scan the good cause information into the electronic folder. For additional information see DI 81010.150B.3. and DI 81010.150C.5.\n\n4. \n\nAdvise the claimant that the ALJ will decide whether to grant an extension for filing the hearing request. (See HALLEX I-2-4-15).\n\n5. ",
                "span_sha256": "a7eefd704de45f52f137f51b68083ae7793251fa5f18b4d75ad66b5f141fe866",
                "maintext_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72"
              }
            ],
            "source_instruction_summary": "ElectronicappealloadMCS ORproperMSSICS appealsprogram; scangoodcauseinfoelectronicfolder; ALJextensiondecision.150B3/C5targets unreviewed; no universalCEFidentityoroperationalstateinference.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "APP_MCS",
              "APP_MSSICS"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "parent_full_route": "hearing-after-medical-reconsideration/late-filing",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording",
            "source": "r20_ALJ_late002",
            "section": "002-clock; 002-steps1-4",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "Modernized Claims System",
              "Modernized Supplemental Security Income Claims System"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72",
              "snapshot_path": "/service/sources/DI12010.002-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application": {
            "id": "alj-late-paper-worsening-new-application",
            "title": "A paper late-hearing case includes a worsening or additional impairment allegation",
            "when": "The paper-case claimant alleges a worsening condition or an additional impairment.",
            "you": "Explain the allegation to staff. This page does not decide a new claim or the hearing result.",
            "ssa": "For this source-defined paper circumstance, staff obtain a new paper application and send it to the ALJ with the hearing request. The source calls for a development-worksheet record and an instruction to return the new claim to FO if the ALJ dismisses the hearing request.",
            "next": "Neither a new application nor return to FO is automatic for every late request; the ALJ’s actual action remains unknown.",
            "condition_logic": "all",
            "conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is paper.",
              "The claimant alleges worsening condition OR additional impairment."
            ],
            "source_case_conditions": [
              "The existing late-filing parent scenario applies.",
              "The case is paper.",
              "The claimant alleges worsening condition OR additional impairment."
            ],
            "source_context_refs": [
              "002-step5",
              "001-note-A"
            ],
            "source_provenance": [
              {
                "id": "002-step5",
                "source_code": "DI12010.002",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010002",
                "start": 1333,
                "end": 1902,
                "exact_text": "5. \n\nFor paper cases, obtain a new paper application only if the claimant alleges a worsening condition or an additional impairment. Forward the new application to the ALJ with the HA 501-U5. Input the new claim on the Modernized Development Worksheet (MDW) to show the new initial claim is pending at the Office of Hearings Operations (OHO). Advise OHO to return the new claim to the field office if the ALJ dismisses the hearing request so that the new claim can be pursued. See GN 03103.220 for more information on hearing dismissal.\n\nFor the electronic process see:",
                "span_sha256": "01c289e7a8c014fb28b800a555ff2dd13daf426158583284284d43e2be849cea",
                "maintext_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72"
              },
              {
                "id": "001-note-A",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 135,
                "end": 2274,
                "exact_text": "NOTE: If a claimant files a new disability application and has a prior disability claim for the same title and benefit type pending at any level of administrative review, see DI 51501.001 Procedural Change for Subsequent Disability Applications, Effective July 28, 2011.\n\nA. \nPolicy for requesting a hearing before an ALJ\n\nA claimant, who is dissatisfied either with a reconsideration or revised reconsideration determination, or with an initial determination in a prototype state, may request a hearing before an ALJ. A claimant may submit a request for a hearing by walk-in, mail, fax, email, or internet.\n\nIf the field office (FO) interviews a claimant who submits a request for a hearing, it explains the hearing process and explains that if he or she appeals, the Social Security Administration (SSA) can review all issues, including those decided favorably. This means that the claimant’s disability status may change from “disabled” to “not disabled”. SSA may also find that the established onset date (EOD) may be the same, earlier, or later than the EOD established in the reconsideration determination or in the initial determination if a prototype state handled the claim. See DI 25501.260 Establishing the Established Onset Date (EOD) in Reconsideration and Appeal Claims.\n\nThe FO obtains form HA 501-U5 (Request for Hearing By Administrative Law Judge) or completes the request on the Modernized Claim System (MCS) or the Modernized Supplemental Security Income Claims System (MISSICS) unless a hearing was requested informally by letter or other correspondence, or the request was made using the iAppeals process.\n\nSee also:\n\n \n\nGN 03103.010 The Hearing Process\n\nDI 20101.020 Social Security Administration (SSA) Jurisdiction for Hearing Cases\n\nDI 81010.150 Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS).\n\nDI 81010.155 Processing Subsequent Claims or Appeals Filed While a Prior Claim or Appeal is Pending at the Appeals Council (AC).\n\nGN 03101.125– iAppeals – General and Title II Instructions\n\nSI 04005.035 iAppeals - Title XVI\n\nB. \nProcedure when claimant requests a hearing",
                "span_sha256": "979371cab71f0e2a0cdaecad62214e570a607315e183e99410818f9b3b250710",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "Onlypaper+allegation triggernewpaperapp; forwardwithHA501; genericMDWnewinitialpendingOHO; adviseOHORETURNnewclaimFO IFALJdismisses. Do notaliasMDWtoAI, declareworseningproven/dismissalcompleted/newclaimallowed;51501pending-appdetails unreviewed.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "FORM_R96_HA501U5"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "parent_full_route": "hearing-after-medical-reconsideration/late-filing",
            "full_route": "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application",
            "source": "r20_ALJ_late002",
            "section": "002-step5; 001-note-A",
            "additional_sources": [
              {
                "source": "r20_ALJ_request001",
                "section": "001-note-A"
              }
            ],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "HA-501-U5 Request for Hearing by Administrative Law Judge"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72",
              "snapshot_path": "/service/sources/DI12010.002-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt": {
            "id": "alj-notice-copy-present-reported-nonreceipt",
            "title": "A notice copy is in the file, but you report not receiving it",
            "when": "The reconsideration notice is in the file and the claimant says the original was not received.",
            "you": "Tell staff about the missing notice and keep the copy they provide.",
            "ssa": "Staff give the claimant a copy, accept the hearing request and document the reported nonreceipt as instructed.",
            "next": "Accepting the request and recording nonreceipt do not decide timeliness, good cause or the appeal outcome.",
            "condition_logic": "all",
            "conditions": [
              "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
              "A copy of the reconsideration notice is in the file.",
              "The claimant alleges not receiving the original notice."
            ],
            "source_case_conditions": [
              "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
              "A copy of the reconsideration notice is in the file.",
              "The claimant alleges not receiving the original notice."
            ],
            "source_context_refs": [
              "001-B3"
            ],
            "source_provenance": [
              {
                "id": "001-B3",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 3171,
                "end": 5160,
                "exact_text": "3. \nCopy of reconsideration notice\n\nTake one of the following actions for verifying receipt or non-receipt of the notice.\n\na. \n\nCheck the file for a copy of the reconsideration notice. In electronic folders, check eView, Evidence Portal (EP),or the Online Retrieval System (ORS) for the notice.\n\nb. \n\nIf a copy of the reconsideration notice is in file but the claimant alleges not receiving a notice:\n\n•\n\nMake a copy of the reconsideration notice for the claimant and accept the request for hearing.\n\n•\n\nDocument the file that the claimant did not receive the original reconsideration notice.\n\nc. \n\nIf a copy of the reconsideration notice is not in file, check the claim folder(s) for an indication that a reconsideration determination was made, e.g., item 34 (Remarks) on the SSA 831 (Disability Determination and Transmittal) shows “Recon Affirmation.”\n\n•\n\nIf there is evidence that a reconsideration determination was made, i.e., disability determination services query (DDSQ), accept the request for a hearing and contact the disability determination services (DDS) by email or phone. Immediately send a duplicate reconsideration notice to the claimant, the FO, and a copy to his or her attorney or non-attorney representative, if applicable. If the SSA-831 is missing, ask the DDS to send a copy of SSA-831 as well.\n\n•\n\nIf there is no indication that a reconsideration determination has been made, follow the instructions in GN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\n•\n\nWhen the disability quality branch (DQB) selects a case for review, an undated copy of the DDS prepared notice is stored in the certified electronic folder (CEF). After the review is completed, DQB prints, dates, and mails the notice. The DQB does not add the date to the image of the notice in the CEF. Instead, the notice release date is recorded in the Office of Quality Performance (OQP) Routing Information in the Case Review link.\n\n4. \nMedical information and release forms",
                "span_sha256": "7193aa4733994956fc24953773b72ae3341dca903ca52d806fade64c1c6ebca0",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "B3a check notice in file; for electronic folders eView, EP OR ORS. B3b copy for claimant, accept request and document nonreceipt; no presumption that the allegation proves a filing-date exception.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "APP_EVIEW",
              "APP_EP",
              "APP_ORS"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt",
            "source": "r20_ALJ_request001",
            "section": "001-B3",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "eView",
              "Evidence Portal",
              "On-line Retrieval System"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated": {
            "id": "alj-notice-copy-absent-reconsideration-indicated",
            "title": "The notice copy is missing, but the file indicates a reconsideration decision",
            "when": "No notice copy is found, but there is evidence a reconsideration determination was made.",
            "you": "Ask staff about the missing notice and keep the replacement when provided.",
            "ssa": "Staff accept the hearing request, contact DDS and arrange the notice copies required by the instruction. If the determination form is also missing, staff ask DDS for its copy.",
            "next": "A request for copies does not show they were received or establish the notice’s actual receipt date.",
            "condition_logic": "all",
            "conditions": [
              "No copy of the reconsideration notice is in the file.",
              "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
            ],
            "source_case_conditions": [
              "No copy of the reconsideration notice is in the file.",
              "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
            ],
            "source_context_refs": [
              "001-B3"
            ],
            "source_provenance": [
              {
                "id": "001-B3",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 3171,
                "end": 5160,
                "exact_text": "3. \nCopy of reconsideration notice\n\nTake one of the following actions for verifying receipt or non-receipt of the notice.\n\na. \n\nCheck the file for a copy of the reconsideration notice. In electronic folders, check eView, Evidence Portal (EP),or the Online Retrieval System (ORS) for the notice.\n\nb. \n\nIf a copy of the reconsideration notice is in file but the claimant alleges not receiving a notice:\n\n•\n\nMake a copy of the reconsideration notice for the claimant and accept the request for hearing.\n\n•\n\nDocument the file that the claimant did not receive the original reconsideration notice.\n\nc. \n\nIf a copy of the reconsideration notice is not in file, check the claim folder(s) for an indication that a reconsideration determination was made, e.g., item 34 (Remarks) on the SSA 831 (Disability Determination and Transmittal) shows “Recon Affirmation.”\n\n•\n\nIf there is evidence that a reconsideration determination was made, i.e., disability determination services query (DDSQ), accept the request for a hearing and contact the disability determination services (DDS) by email or phone. Immediately send a duplicate reconsideration notice to the claimant, the FO, and a copy to his or her attorney or non-attorney representative, if applicable. If the SSA-831 is missing, ask the DDS to send a copy of SSA-831 as well.\n\n•\n\nIf there is no indication that a reconsideration determination has been made, follow the instructions in GN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\n•\n\nWhen the disability quality branch (DQB) selects a case for review, an undated copy of the DDS prepared notice is stored in the certified electronic folder (CEF). After the review is completed, DQB prints, dates, and mails the notice. The DQB does not add the date to the image of the notice in the CEF. Instead, the notice release date is recorded in the Office of Quality Performance (OQP) Routing Information in the Case Review link.\n\n4. \nMedical information and release forms",
                "span_sha256": "7193aa4733994956fc24953773b72ae3341dca903ca52d806fade64c1c6ebca0",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "B3c check folders for indication, e.g. SSA831 item34 Recon Affirmation; evidence such as DDSQ supports accepting request/contactingDDS byemailorphone. Source directs duplicate notice immediately to claimant andFO, repcopyifapplicable; askDDSfor831ifmissing. No automated query-to-case classification or promised delivery.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "APP_DDSQ",
              "R201_E027"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated",
            "source": "r20_ALJ_request001",
            "section": "001-B3",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "Disability Determination Services Query",
              "SSA-831 Disability Determination and Transmittal"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication": {
            "id": "alj-no-notice-no-reconsideration-indication",
            "title": "The file does not show a reconsideration decision",
            "when": "No notice copy or indication of a reconsideration determination is found.",
            "you": "Discuss the appeal stage with staff and explain whether you want reconsideration or still want to request a hearing.",
            "ssa": "Staff follow the separate instructions for a hearing request made before a reconsideration decision is established. A missing record alone does not decide which appeal stage is actually due.",
            "next": "The selected choices below require their own facts; this walkthrough does not convert the request or dismiss it.",
            "condition_logic": "all",
            "conditions": [
              "No reconsideration notice copy is found.",
              "No indication that a reconsideration determination was made is found after the source-defined checks."
            ],
            "source_case_conditions": [
              "No reconsideration notice copy is found.",
              "No indication that a reconsideration determination was made is found after the source-defined checks."
            ],
            "source_context_refs": [
              "001-B3",
              "120-A",
              "120-B"
            ],
            "source_provenance": [
              {
                "id": "001-B3",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 3171,
                "end": 5160,
                "exact_text": "3. \nCopy of reconsideration notice\n\nTake one of the following actions for verifying receipt or non-receipt of the notice.\n\na. \n\nCheck the file for a copy of the reconsideration notice. In electronic folders, check eView, Evidence Portal (EP),or the Online Retrieval System (ORS) for the notice.\n\nb. \n\nIf a copy of the reconsideration notice is in file but the claimant alleges not receiving a notice:\n\n•\n\nMake a copy of the reconsideration notice for the claimant and accept the request for hearing.\n\n•\n\nDocument the file that the claimant did not receive the original reconsideration notice.\n\nc. \n\nIf a copy of the reconsideration notice is not in file, check the claim folder(s) for an indication that a reconsideration determination was made, e.g., item 34 (Remarks) on the SSA 831 (Disability Determination and Transmittal) shows “Recon Affirmation.”\n\n•\n\nIf there is evidence that a reconsideration determination was made, i.e., disability determination services query (DDSQ), accept the request for a hearing and contact the disability determination services (DDS) by email or phone. Immediately send a duplicate reconsideration notice to the claimant, the FO, and a copy to his or her attorney or non-attorney representative, if applicable. If the SSA-831 is missing, ask the DDS to send a copy of SSA-831 as well.\n\n•\n\nIf there is no indication that a reconsideration determination has been made, follow the instructions in GN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\n•\n\nWhen the disability quality branch (DQB) selects a case for review, an undated copy of the DDS prepared notice is stored in the certified electronic folder (CEF). After the review is completed, DQB prints, dates, and mails the notice. The DQB does not add the date to the image of the notice in the CEF. Instead, the notice release date is recorded in the Office of Quality Performance (OQP) Routing Information in the Case Review link.\n\n4. \nMedical information and release forms",
                "span_sha256": "7193aa4733994956fc24953773b72ae3341dca903ca52d806fade64c1c6ebca0",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              },
              {
                "id": "120-A",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 145,
                "end": 659,
                "exact_text": "A. \nPolicy\n\nOnce a hearing is filed, the case is Office of Hearings Operations’ (OHO) jurisdiction and there is no regulatory authority for the FO or PC to take adjudicative action except at the direction of the ALJ; i.e., if ALJ remands case.\n\nHowever, a written request for appeal may be interpreted as a request for reconsideration, if, in fact, a reconsideration is the next level of appeal that is due, regardless of the form submitted to SSA, unless the claimant insists otherwise.\n\nB. \nProcedure — FO Action",
                "span_sha256": "61439381db96a63de09502e3162b9f40eec7c9dbdcd04b16c9ec636a0c5bbc30",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              },
              {
                "id": "120-B",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 634,
                "end": 1717,
                "exact_text": "B. \nProcedure — FO Action\n\nFO action:\n\n•\n\nIf a claimant wants to file a request for hearing without filing for a reconsideration or before the reconsideration determination has been completed, explain that reconsideration is the next step in the appeals process and that the hearing will be dismissed (see GN 03103.220 on dismissal).\n\n•\n\nAssist the claimant in requesting a reconsideration if that is the claimant's decision and the claimant has not previously filed a reconsideration. (See GN 03102.225.)\n\n•\n\nIf claimant still insists on filing for a hearing, complete an HA-501-U5 and attach to all copies (except the claimant's) an RC containing a brief statement of the explanation given the claimant and indicate why claimant insists on filing for a hearing before having a reconsideration. Follow\nGN 03103.080 for processing HA-501-U5.\n\n•\n\nIf FO receives a letter requesting a hearing, contact claimant and explain the above points. Prepare an RC and, if necessary, complete either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020 F.).\n\nC. \nProcedure — PC Action",
                "span_sha256": "fee83e759eff20c20cabe9d2b52487e3ce1ddfff78f77c69fe8102b85eb6d546",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              }
            ],
            "source_instruction_summary": "B3c referGN03103.120.120A writtenappeal mayberecon onlyIFreconinfactnextdue, unlessclaimantinsistsotherwise. Oncehearingfiled OHOjurisdiction/noFO-PCadjudicationexceptALJdirection. Absenceofindication isnotproofnoactualdetermination.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication",
            "entry_exception_scope": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "source": "r20_ALJ_request001",
            "section": "001-B3; 120-A; 120-B",
            "additional_sources": [
              {
                "source": "r20_ALJ_stage120",
                "section": "120-A; 120-B"
              }
            ],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses": {
            "id": "alj-reconsideration-next-claimant-chooses",
            "title": "You choose reconsideration when that is the next step",
            "when": "Staff establish reconsideration is the next appeal step and the claimant chooses it.",
            "you": "Tell staff whether you want help requesting reconsideration.",
            "ssa": "FO staff assist with reconsideration if it is the claimant’s choice and it has not already been filed.",
            "next": "The choice does not establish that reconsideration was filed or completed.",
            "condition_logic": "all",
            "conditions": [
              "The parent file/no-indication scenario applies.",
              "Reconsideration is in fact the next appeal level due.",
              "The claimant chooses reconsideration and has not previously filed it."
            ],
            "source_case_conditions": [
              "The parent file/no-indication scenario applies.",
              "Reconsideration is in fact the next appeal level due.",
              "The claimant chooses reconsideration and has not previously filed it."
            ],
            "source_context_refs": [
              "120-A",
              "120-B"
            ],
            "source_provenance": [
              {
                "id": "120-A",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 145,
                "end": 659,
                "exact_text": "A. \nPolicy\n\nOnce a hearing is filed, the case is Office of Hearings Operations’ (OHO) jurisdiction and there is no regulatory authority for the FO or PC to take adjudicative action except at the direction of the ALJ; i.e., if ALJ remands case.\n\nHowever, a written request for appeal may be interpreted as a request for reconsideration, if, in fact, a reconsideration is the next level of appeal that is due, regardless of the form submitted to SSA, unless the claimant insists otherwise.\n\nB. \nProcedure — FO Action",
                "span_sha256": "61439381db96a63de09502e3162b9f40eec7c9dbdcd04b16c9ec636a0c5bbc30",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              },
              {
                "id": "120-B",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 634,
                "end": 1717,
                "exact_text": "B. \nProcedure — FO Action\n\nFO action:\n\n•\n\nIf a claimant wants to file a request for hearing without filing for a reconsideration or before the reconsideration determination has been completed, explain that reconsideration is the next step in the appeals process and that the hearing will be dismissed (see GN 03103.220 on dismissal).\n\n•\n\nAssist the claimant in requesting a reconsideration if that is the claimant's decision and the claimant has not previously filed a reconsideration. (See GN 03102.225.)\n\n•\n\nIf claimant still insists on filing for a hearing, complete an HA-501-U5 and attach to all copies (except the claimant's) an RC containing a brief statement of the explanation given the claimant and indicate why claimant insists on filing for a hearing before having a reconsideration. Follow\nGN 03103.080 for processing HA-501-U5.\n\n•\n\nIf FO receives a letter requesting a hearing, contact claimant and explain the above points. Prepare an RC and, if necessary, complete either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020 F.).\n\nC. \nProcedure — PC Action",
                "span_sha256": "fee83e759eff20c20cabe9d2b52487e3ce1ddfff78f77c69fe8102b85eb6d546",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              }
            ],
            "source_instruction_summary": "WrittenrequestmayinterpretreconregardlessformONLYinfactnextdueUNLESSclaimantinsistsotherwise; FOassistifclaimantdecisionandnotpreviousfiled. Noauto-conversion;561targetunreviewed.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "parent_full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication",
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses",
            "entry_exception_scope": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "source": "r20_ALJ_stage120",
            "section": "120-A; 120-B",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
              "snapshot_path": "/service/sources/GN03103.120-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration": {
            "id": "alj-claimant-insists-before-reconsideration",
            "title": "You still want a hearing after the stage explanation",
            "when": "The claimant still insists on filing a hearing request after the explanation.",
            "you": "Tell staff your decision and why you still want to request a hearing.",
            "ssa": "FO staff complete the hearing-request form and attach the recorded explanation and reason to the copies specified by the source, except the claimant’s copy.",
            "next": "Staff explain the source’s dismissal warning, but this walkthrough does not dismiss the request or decide what the ALJ will do.",
            "condition_logic": "all",
            "conditions": [
              "The parent file/no-indication scenario applies.",
              "The source’s explanation that reconsideration is next/before completion has been given.",
              "The claimant still insists on filing for a hearing."
            ],
            "source_case_conditions": [
              "The parent file/no-indication scenario applies.",
              "The source’s explanation that reconsideration is next/before completion has been given.",
              "The claimant still insists on filing for a hearing."
            ],
            "source_context_refs": [
              "120-A",
              "120-B"
            ],
            "source_provenance": [
              {
                "id": "120-A",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 145,
                "end": 659,
                "exact_text": "A. \nPolicy\n\nOnce a hearing is filed, the case is Office of Hearings Operations’ (OHO) jurisdiction and there is no regulatory authority for the FO or PC to take adjudicative action except at the direction of the ALJ; i.e., if ALJ remands case.\n\nHowever, a written request for appeal may be interpreted as a request for reconsideration, if, in fact, a reconsideration is the next level of appeal that is due, regardless of the form submitted to SSA, unless the claimant insists otherwise.\n\nB. \nProcedure — FO Action",
                "span_sha256": "61439381db96a63de09502e3162b9f40eec7c9dbdcd04b16c9ec636a0c5bbc30",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              },
              {
                "id": "120-B",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 634,
                "end": 1717,
                "exact_text": "B. \nProcedure — FO Action\n\nFO action:\n\n•\n\nIf a claimant wants to file a request for hearing without filing for a reconsideration or before the reconsideration determination has been completed, explain that reconsideration is the next step in the appeals process and that the hearing will be dismissed (see GN 03103.220 on dismissal).\n\n•\n\nAssist the claimant in requesting a reconsideration if that is the claimant's decision and the claimant has not previously filed a reconsideration. (See GN 03102.225.)\n\n•\n\nIf claimant still insists on filing for a hearing, complete an HA-501-U5 and attach to all copies (except the claimant's) an RC containing a brief statement of the explanation given the claimant and indicate why claimant insists on filing for a hearing before having a reconsideration. Follow\nGN 03103.080 for processing HA-501-U5.\n\n•\n\nIf FO receives a letter requesting a hearing, contact claimant and explain the above points. Prepare an RC and, if necessary, complete either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020 F.).\n\nC. \nProcedure — PC Action",
                "span_sha256": "fee83e759eff20c20cabe9d2b52487e3ce1ddfff78f77c69fe8102b85eb6d546",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              }
            ],
            "source_instruction_summary": "FOcompleteHA501; RCbriefexplanation+whyclaimantinsists attachedallcopiesEXCEPTclaimantcopy; follow080. A oncefiledOHOjurisdiction; noautomateddismissal.120Cdualexceptionseparate, notcompatiblewithblanketno-reconoutcome.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "FORM_R96_HA501U5"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "parent_full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication",
            "full_route": "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration",
            "entry_exception_scope": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "source": "r20_ALJ_stage120",
            "section": "120-A; 120-B",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "HA-501-U5 Request for Hearing by Administrative Law Judge"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
              "snapshot_path": "/service/sources/GN03103.120-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay": {
            "id": "alj-missing-3441-or-827-no-transfer-delay",
            "title": "The appeal packet lacks an SSA-3441 or SSA-827",
            "when": "The ALJ appeal file does not contain one of these named forms.",
            "you": "Keep any forms and instructions you receive. This page does not decide whether a release is valid.",
            "ssa": "The national instruction says to transfer the appeal without waiting for the missing SSA-3441 or SSA-827 and not make follow-up attempts to obtain one. Differing regional instructions must be followed.",
            "next": "This is not a waiver for every missing document or permission to disclose information without valid authority.",
            "condition_logic": "all",
            "conditions": [
              "This is the ALJ-hearing request handling covered by DI12010.001.",
              "The file lacks an SSA3441 or SSA827 with the appeal."
            ],
            "source_case_conditions": [
              "This is the ALJ-hearing request handling covered by DI12010.001.",
              "The file lacks an SSA3441 or SSA827 with the appeal."
            ],
            "source_context_refs": [
              "001-B4"
            ],
            "source_provenance": [
              {
                "id": "001-B4",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 5119,
                "end": 5865,
                "exact_text": "4. \nMedical information and release forms\n\nObtain new Form SSA-3441 (Disability Report – Appeal) and Form SSA-827 (Authorization to Disclose Information to the Social Security Administration). Obtain one SSA-827 for in-person interviews. If the file does not contain an SSA-3441 or SSA-827 with an appeal, do not delay transferring the appeal request. Transfer it without the SSA-3441 or SSA-827. Do not make any follow up attempts to obtain one. See DI 12010.005 Development of Administrative Law Judge (ALJ) Hearing Cases and DI 11005.055 Completing Form SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)). Follow regional instructions when they differ from national instructions.\n\n5. \nConcurrent claims",
                "span_sha256": "341a665f356b5b0576316364fbbbdbfafd8f727a737173848e527287017e3348",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "Obtainnew3441and827; one827forinpersoninterview. Ifeitherformabsent doNOTdelaytransfer, transferwithout, doNOTfollowupobtainone. Followregionalinstructionswhendifferfromnational. Linked12010.005/11005.055 details unexpanded. Do notimporteCDRchildhood3881conditionorconsent-validityfinding.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "FORM_SSA827"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay",
            "source": "r20_ALJ_request001",
            "section": "001-B4",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "SSA-827 Authorization to Disclose Information to the Social Security Administration"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope": {
            "id": "alj-concurrent-medical-appeal-scope",
            "title": "A medical appeal involves concurrent benefit claims",
            "when": "The application involves the source’s multiple-benefit situation and a medical issue is appealed.",
            "you": "Ask staff which medical issues and claims are included, including any favorable medical finding.",
            "ssa": "Staff transfer the medical case as concurrent for ALJ review. An unappealed technical denial on another claim is excluded under the source condition.",
            "next": "A favorable determination may still be effectuated, but the source says the medical determination under review is not final. No payment outcome is shown.",
            "condition_logic": "all",
            "conditions": [
              "The application claims TitleII andTitleXVI benefits OR morethanoneTitleII disability benefit.",
              "The claimant appeals a medical issue for any of those benefits."
            ],
            "source_case_conditions": [
              "The application claims TitleII andTitleXVI benefits OR morethanoneTitleII disability benefit.",
              "The claimant appeals a medical issue for any of those benefits."
            ],
            "source_context_refs": [
              "001-B5"
            ],
            "source_provenance": [
              {
                "id": "001-B5",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 5844,
                "end": 6601,
                "exact_text": "5. \nConcurrent claims\n\nIf an application involves claiming Title II and Title XVI benefits, or claiming more than one Title II disability benefit, and the claimant appeals any medical issue for any of the benefits, the entire claim is under review, including any favorable determination regarding disability status. Therefore, transfer the case as a concurrent claim for a hearing before an ALJ.\n\nThe FO may still effectuate the favorable determination, but the claimant should be aware that our determination regarding the medical issue is not final.\n\nIf the other claim was a technical denial that is not under appeal, do not forward the technically denied claim for a hearing before an ALJ as the issues under appeal are not the same.\n\n6. \nFolder request",
                "span_sha256": "84eb5fa5b77d4de98d568e4ebf899ce5b376d968368e39d225667524808becab",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "Entiremedicalclaimunderreviewincludingfavorablemedicaldisabilitydeterminations; transferconcurrent. FOmaystill effectuatefavorable butmedicalissuenotfinal. IFotherclaimtechnicaldenial ANDnotunderappeal, doNOTforwardit becauseissuesarenotsame. Notalltechnicaldenials excludeduniversally; not synonymouswith120dual-determinationexception.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope",
            "source": "r20_ALJ_request001",
            "section": "001-B5",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception": {
            "id": "alj-dual-determination-proper-hearing-exception",
            "title": "One case includes both a reconsideration and an initial determination",
            "when": "A hearing is proper for the reconsideration part, while the initial determination has not been reconsidered.",
            "you": "Ask staff to explain which determinations are in the case.",
            "ssa": "The source says the ALJ will not dismiss merely because the initial determination has not been reconsidered when a hearing is proper for the reconsideration determination. The entire file goes to the ALJ.",
            "next": "This exception does not rule out other dismissal grounds or establish the ALJ’s actual action.",
            "condition_logic": "all",
            "conditions": [
              "SSA made a reconsideration determination and an initial determination on the same case.",
              "A hearing is proper with respect to the reconsideration determination.",
              "The initial determination has not been reconsidered."
            ],
            "source_case_conditions": [
              "SSA made a reconsideration determination and an initial determination on the same case.",
              "A hearing is proper with respect to the reconsideration determination.",
              "The initial determination has not been reconsidered."
            ],
            "source_context_refs": [
              "120-C"
            ],
            "source_provenance": [
              {
                "id": "120-C",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 1692,
                "end": 2888,
                "exact_text": "C. \nProcedure — PC Action\n\nPC action:\n\n•\n\nWhen PC is advised a hearing has been filed, the PC immediately prepares the folder for transmittal to the servicing FO per GN 03103.080K .\n\n•\n\nIf PC receives a letter directly from claimant requesting a hearing, contact claimant and explain the points in B. above. PC prepares an RC and, if necessary, completes either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020F.).\n\n•\n\nDo not take any final related action pending the ALJ action on the hearing request. Upon receipt of notice of the ALJ action, the PC may complete any pending action and/or consider any additional evidence or information submitted.\n\nEXCEPTION: In a dual determination situation, where SSA makes a reconsideration determination and an initial determination on the same case, the ALJ will not dismiss the case merely because the initial determination has not been reconsidered, since a hearing is proper with respect to the reconsideration determination. Therefore, the entire claims file is sent to the ALJ. (See GN 03101.001 and GN 03103.140 concerning multiple levels of appeal on one case and GN 03103.220 on dismissal.)\n\nTo Link to this section - Use this URL:",
                "span_sha256": "058634f0c5293260b7d695a96a92675ca7eadedb7d9d5a5ab708ad8052bfff41",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              }
            ],
            "source_instruction_summary": "Explicitdual-determinationexception: ALJnotdismissMERELYinitialnotreconsidered; entireclaimsfileALJ. Notmerelyconcurrenttitles, notgenericno-reconbypass;03101.001/03103.140/03103.220 targets unreviewed.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception",
            "source": "r20_ALJ_stage120",
            "section": "120-C",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
              "snapshot_path": "/service/sources/GN03103.120-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "hearing-after-medical-reconsideration/alj-premature-request-PC-handling": {
            "id": "alj-premature-request-PC-handling",
            "title": "A hearing-request issue reaches the processing center",
            "when": "The processing center receives the source’s hearing notification or a direct claimant letter.",
            "you": "Respond to staff contact about the appeal stage and keep the correspondence.",
            "ssa": "When advised a hearing has been filed, PC prepares the folder for the servicing field office. If a claimant’s letter comes directly to PC, staff explain the source’s stage points, document the contact and prepare the appropriate form if needed.",
            "next": "PC takes no final related action pending ALJ action; the instruction does not establish that the hearing was filed or dismissed in your case.",
            "condition_logic": "all",
            "conditions": [
              "PC is handling the selected hearing-request-before-reconsideration procedure.",
              "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing."
            ],
            "source_case_conditions": [
              "PC is handling the selected hearing-request-before-reconsideration procedure.",
              "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing."
            ],
            "source_context_refs": [
              "120-A",
              "120-B",
              "120-C"
            ],
            "source_provenance": [
              {
                "id": "120-A",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 145,
                "end": 659,
                "exact_text": "A. \nPolicy\n\nOnce a hearing is filed, the case is Office of Hearings Operations’ (OHO) jurisdiction and there is no regulatory authority for the FO or PC to take adjudicative action except at the direction of the ALJ; i.e., if ALJ remands case.\n\nHowever, a written request for appeal may be interpreted as a request for reconsideration, if, in fact, a reconsideration is the next level of appeal that is due, regardless of the form submitted to SSA, unless the claimant insists otherwise.\n\nB. \nProcedure — FO Action",
                "span_sha256": "61439381db96a63de09502e3162b9f40eec7c9dbdcd04b16c9ec636a0c5bbc30",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              },
              {
                "id": "120-B",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 634,
                "end": 1717,
                "exact_text": "B. \nProcedure — FO Action\n\nFO action:\n\n•\n\nIf a claimant wants to file a request for hearing without filing for a reconsideration or before the reconsideration determination has been completed, explain that reconsideration is the next step in the appeals process and that the hearing will be dismissed (see GN 03103.220 on dismissal).\n\n•\n\nAssist the claimant in requesting a reconsideration if that is the claimant's decision and the claimant has not previously filed a reconsideration. (See GN 03102.225.)\n\n•\n\nIf claimant still insists on filing for a hearing, complete an HA-501-U5 and attach to all copies (except the claimant's) an RC containing a brief statement of the explanation given the claimant and indicate why claimant insists on filing for a hearing before having a reconsideration. Follow\nGN 03103.080 for processing HA-501-U5.\n\n•\n\nIf FO receives a letter requesting a hearing, contact claimant and explain the above points. Prepare an RC and, if necessary, complete either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020 F.).\n\nC. \nProcedure — PC Action",
                "span_sha256": "fee83e759eff20c20cabe9d2b52487e3ce1ddfff78f77c69fe8102b85eb6d546",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              },
              {
                "id": "120-C",
                "source_code": "GN03103.120",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0203103120",
                "start": 1692,
                "end": 2888,
                "exact_text": "C. \nProcedure — PC Action\n\nPC action:\n\n•\n\nWhen PC is advised a hearing has been filed, the PC immediately prepares the folder for transmittal to the servicing FO per GN 03103.080K .\n\n•\n\nIf PC receives a letter directly from claimant requesting a hearing, contact claimant and explain the points in B. above. PC prepares an RC and, if necessary, completes either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020F.).\n\n•\n\nDo not take any final related action pending the ALJ action on the hearing request. Upon receipt of notice of the ALJ action, the PC may complete any pending action and/or consider any additional evidence or information submitted.\n\nEXCEPTION: In a dual determination situation, where SSA makes a reconsideration determination and an initial determination on the same case, the ALJ will not dismiss the case merely because the initial determination has not been reconsidered, since a hearing is proper with respect to the reconsideration determination. Therefore, the entire claims file is sent to the ALJ. (See GN 03101.001 and GN 03103.140 concerning multiple levels of appeal on one case and GN 03103.220 on dismissal.)\n\nTo Link to this section - Use this URL:",
                "span_sha256": "058634f0c5293260b7d695a96a92675ca7eadedb7d9d5a5ab708ad8052bfff41",
                "maintext_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e"
              }
            ],
            "source_instruction_summary": "C: notifiedhearingfiled→immediatelypreparefolderforsvcFOvia080K; directclaimantletter→contact/explainB/RC/ifnecessary561or501. No finalrelatedactionpendingALJaction; afterALJnotice PCmaycompletependingaction/consideradditionalinfo. Conditionscanoverlap, notmutuallyexclusive. Knownfilingstatusisnotinferredfromintention.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Processing-center staff; servicing FO and ALJ only in the source-defined roles",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "FORM_R96_HA501U5"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-premature-request-PC-handling",
            "entry_exception_scope": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "source": "r20_ALJ_stage120",
            "section": "120-A; 120-B; 120-C",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "HA-501-U5 Request for Hearing by Administrative Law Judge"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
              "snapshot_path": "/service/sources/GN03103.120-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          }
        },
        "source_contexts": [
          {
            "id": "DI12010.001:whole",
            "source_code": "DI12010.001",
            "start": 0,
            "end": 8539,
            "exact_text": "Effective Dates: 12/14/2021 - Present\nPrevious | Next\n\nTN 15 (01-25)\n\nDI 12010.001 Request for Administrative Law Judge (ALJ) Hearing\n\nNOTE: If a claimant files a new disability application and has a prior disability claim for the same title and benefit type pending at any level of administrative review, see DI 51501.001 Procedural Change for Subsequent Disability Applications, Effective July 28, 2011.\n\nA. \nPolicy for requesting a hearing before an ALJ\n\nA claimant, who is dissatisfied either with a reconsideration or revised reconsideration determination, or with an initial determination in a prototype state, may request a hearing before an ALJ. A claimant may submit a request for a hearing by walk-in, mail, fax, email, or internet.\n\nIf the field office (FO) interviews a claimant who submits a request for a hearing, it explains the hearing process and explains that if he or she appeals, the Social Security Administration (SSA) can review all issues, including those decided favorably. This means that the claimant’s disability status may change from “disabled” to “not disabled”. SSA may also find that the established onset date (EOD) may be the same, earlier, or later than the EOD established in the reconsideration determination or in the initial determination if a prototype state handled the claim. See DI 25501.260 Establishing the Established Onset Date (EOD) in Reconsideration and Appeal Claims.\n\nThe FO obtains form HA 501-U5 (Request for Hearing By Administrative Law Judge) or completes the request on the Modernized Claim System (MCS) or the Modernized Supplemental Security Income Claims System (MISSICS) unless a hearing was requested informally by letter or other correspondence, or the request was made using the iAppeals process.\n\nSee also:\n\n \n\nGN 03103.010 The Hearing Process\n\nDI 20101.020 Social Security Administration (SSA) Jurisdiction for Hearing Cases\n\nDI 81010.150 Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS).\n\nDI 81010.155 Processing Subsequent Claims or Appeals Filed While a Prior Claim or Appeal is Pending at the Appeals Council (AC).\n\nGN 03101.125– iAppeals – General and Title II Instructions\n\nSI 04005.035 iAppeals - Title XVI\n\nB. \nProcedure when claimant requests a hearing before an ALJ\n1. \nConduct the interview, if necessary\n\nExplain the hearing process and the claimant's rights and responsibilities. Refer to GN 03103.010C for FO instructions on interviewing the claimant.\n\n2. \nForm HA 501-U5\n\nAssist the claimant in completing the HA 501-U5. See GN 03103.020 HA-501-U5 (Request for Hearing by Administrative Law Judge) for instructions on the use and completion of the HA 501-U5. For electronic files, see DI 81010.020 Creating Electronic Disability Collect System (EDCS) Cases and DI 81010.150 Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS).\n\nSee also:\n\nGN 03103.020.F Procedure on when to use and how to complete the Spanish Language HA-501-U5-SP\n\nNOTE: If the claimant files a late request for hearing see DI 12010.002 Request for Administrative Law Judge (ALJ) Hearing Filed Late for FO processing instructions.\n\n3. \nCopy of reconsideration notice\n\nTake one of the following actions for verifying receipt or non-receipt of the notice.\n\na. \n\nCheck the file for a copy of the reconsideration notice. In electronic folders, check eView, Evidence Portal (EP),or the Online Retrieval System (ORS) for the notice.\n\nb. \n\nIf a copy of the reconsideration notice is in file but the claimant alleges not receiving a notice:\n\n•\n\nMake a copy of the reconsideration notice for the claimant and accept the request for hearing.\n\n•\n\nDocument the file that the claimant did not receive the original reconsideration notice.\n\nc. \n\nIf a copy of the reconsideration notice is not in file, check the claim folder(s) for an indication that a reconsideration determination was made, e.g., item 34 (Remarks) on the SSA 831 (Disability Determination and Transmittal) shows “Recon Affirmation.”\n\n•\n\nIf there is evidence that a reconsideration determination was made, i.e., disability determination services query (DDSQ), accept the request for a hearing and contact the disability determination services (DDS) by email or phone. Immediately send a duplicate reconsideration notice to the claimant, the FO, and a copy to his or her attorney or non-attorney representative, if applicable. If the SSA-831 is missing, ask the DDS to send a copy of SSA-831 as well.\n\n•\n\nIf there is no indication that a reconsideration determination has been made, follow the instructions in GN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\n•\n\nWhen the disability quality branch (DQB) selects a case for review, an undated copy of the DDS prepared notice is stored in the certified electronic folder (CEF). After the review is completed, DQB prints, dates, and mails the notice. The DQB does not add the date to the image of the notice in the CEF. Instead, the notice release date is recorded in the Office of Quality Performance (OQP) Routing Information in the Case Review link.\n\n4. \nMedical information and release forms\n\nObtain new Form SSA-3441 (Disability Report – Appeal) and Form SSA-827 (Authorization to Disclose Information to the Social Security Administration). Obtain one SSA-827 for in-person interviews. If the file does not contain an SSA-3441 or SSA-827 with an appeal, do not delay transferring the appeal request. Transfer it without the SSA-3441 or SSA-827. Do not make any follow up attempts to obtain one. See DI 12010.005 Development of Administrative Law Judge (ALJ) Hearing Cases and DI 11005.055 Completing Form SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)). Follow regional instructions when they differ from national instructions.\n\n5. \nConcurrent claims\n\nIf an application involves claiming Title II and Title XVI benefits, or claiming more than one Title II disability benefit, and the claimant appeals any medical issue for any of the benefits, the entire claim is under review, including any favorable determination regarding disability status. Therefore, transfer the case as a concurrent claim for a hearing before an ALJ.\n\nThe FO may still effectuate the favorable determination, but the claimant should be aware that our determination regarding the medical issue is not final.\n\nIf the other claim was a technical denial that is not under appeal, do not forward the technically denied claim for a hearing before an ALJ as the issues under appeal are not the same.\n\n6. \nFolder request\n\nIf the case is paper and if the claim folder(s) is not in the servicing FO when the claimant files the request for hearing, follow GN 03103.080 Forwarding the Form HA-501-U5 (Request for Hearing by Administrative Law Judge) to obtain the claim folder(s).\n\n7. \nInformal remand\n\nReview the claim folder(s) to determine if an informal remand or reopening applies. Refer to DI 12010.015 Informal Remand of Medical/Vocational Determinations and DI 12010.020 Informal Remand Requested By The Review Component.\n\nFor the Electronic Process see:\n\nDI 81010.085 Transferring Cases in Electronic Disability Collect System (EDCS).\n\nDI 81010.150 Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS).\n\nDI 81010.141 Processing Electronic Informal Remands\n\nDI 81010.155 Processing Subsequent Claims or Appeals Filed While a Prior Claim or Appeal is Pending at the Appeals Council (AC)\n\nDI 81020.119 Processing Electronic Informal Remands\n\nSee also:\n\nGN 03103.000 Hearings (Title II and Entitlement Under Title XVIII) - Table of Contents\n\nSI 04030.000 Administrative Law Judge (ALJ) Hearings – SSI - Table of Contents\n\nGN 03103.020 HA 501-U5 (Request for Hearing by Administrative Law Judge).\n\nGN 03103.080 Forwarding the Form HA­ 501-U5 (Request for Hearing by Administrative Law Judge) and Folder to the Servicing Hearing Office (HO).\n\nDI 11005.055 Completing Form SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA))\n\nGN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0412010001\n\t\nDI 12010.001 - Request for Administrative Law Judge (ALJ) Hearing - 12/14/2021\nBatch run: 10/29/2026\nRev:12/14/2021\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
            "scope": "Whole captured primary source, complete prerequisites/notes and reference labels retained."
          },
          {
            "id": "DI12010.002:whole",
            "source_code": "DI12010.002",
            "start": 0,
            "end": 2617,
            "exact_text": "Effective Dates: 04/11/2018 - Present\nPrevious | Next\n\nTN 3 (07-10)\n\nDI 12010.002 Request for Administrative Law Judge (ALJ) Hearing Filed Late\n\nThe time limit for requesting an appeal is 60 days after the date the claimant receives notice of the determination or decision. The date that the individual receives the notice is presumed to be 5 days after the date on the notice unless the individual can show us that he or she did not receive it within the 5 days. If the request for hearing is filed late:\n\n1. \n\nFollow procedures in GN 03101.020B, (Good Cause for Extending Time Limit). For additional information on a late request for hearing see GN 03103.010C.7.\n\n2. \n\nFor paper cases, attach original statement which explains reason for filing late to the “Hearing Office File” copy of the HA 501-U5 (Request for Hearing).\n\n3. \n\nAttach a copy of explanation to the “Claims Folder Copy.” For electronic cases, load the appeal into the Modernized Claim System (MCS) or the Modernized Supplemental Security Income Claims System (MSSICS) using the appeals program and scan the good cause information into the electronic folder. For additional information see DI 81010.150B.3. and DI 81010.150C.5.\n\n4. \n\nAdvise the claimant that the ALJ will decide whether to grant an extension for filing the hearing request. (See HALLEX I-2-4-15).\n\n5. \n\nFor paper cases, obtain a new paper application only if the claimant alleges a worsening condition or an additional impairment. Forward the new application to the ALJ with the HA 501-U5. Input the new claim on the Modernized Development Worksheet (MDW) to show the new initial claim is pending at the Office of Hearings Operations (OHO). Advise OHO to return the new claim to the field office if the ALJ dismisses the hearing request so that the new claim can be pursued. See GN 03103.220 for more information on hearing dismissal.\n\nFor the electronic process see:\n\nDI 81010.085 – Transferring Cases in Electronic Disability Collect System (EDCS).\n\nDI 81010.150 – Processing Claims Appeals of Medical Decisions in Electronic Disability Collect System (EDCS).\n\nDI 81010.155 – Processing Subsequent Claims or Appeals Filed While a Prior Claim or Appeal is Pending at the Appeals Council (AC).\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0412010002\n\t\nDI 12010.002 - Request for Administrative Law Judge (ALJ) Hearing Filed Late - 04/11/2018\nBatch run: 02/25/2025\nRev:04/11/2018\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72",
            "scope": "Whole captured primary source, complete prerequisites/notes and reference labels retained."
          },
          {
            "id": "GN03103.120:whole",
            "source_code": "GN03103.120",
            "start": 0,
            "end": 3236,
            "exact_text": "Effective Dates: 01/28/2021 - Present\nPrevious | Next\n\nTN 42 (07-23)\n\nGN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination\nA. \nPolicy\n\nOnce a hearing is filed, the case is Office of Hearings Operations’ (OHO) jurisdiction and there is no regulatory authority for the FO or PC to take adjudicative action except at the direction of the ALJ; i.e., if ALJ remands case.\n\nHowever, a written request for appeal may be interpreted as a request for reconsideration, if, in fact, a reconsideration is the next level of appeal that is due, regardless of the form submitted to SSA, unless the claimant insists otherwise.\n\nB. \nProcedure — FO Action\n\nFO action:\n\n•\n\nIf a claimant wants to file a request for hearing without filing for a reconsideration or before the reconsideration determination has been completed, explain that reconsideration is the next step in the appeals process and that the hearing will be dismissed (see GN 03103.220 on dismissal).\n\n•\n\nAssist the claimant in requesting a reconsideration if that is the claimant's decision and the claimant has not previously filed a reconsideration. (See GN 03102.225.)\n\n•\n\nIf claimant still insists on filing for a hearing, complete an HA-501-U5 and attach to all copies (except the claimant's) an RC containing a brief statement of the explanation given the claimant and indicate why claimant insists on filing for a hearing before having a reconsideration. Follow\nGN 03103.080 for processing HA-501-U5.\n\n•\n\nIf FO receives a letter requesting a hearing, contact claimant and explain the above points. Prepare an RC and, if necessary, complete either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020 F.).\n\nC. \nProcedure — PC Action\n\nPC action:\n\n•\n\nWhen PC is advised a hearing has been filed, the PC immediately prepares the folder for transmittal to the servicing FO per GN 03103.080K .\n\n•\n\nIf PC receives a letter directly from claimant requesting a hearing, contact claimant and explain the points in B. above. PC prepares an RC and, if necessary, completes either an SSA-561-U2 (see GN 03102.225) or HA-501-U5 (see GN 03103.020F.).\n\n•\n\nDo not take any final related action pending the ALJ action on the hearing request. Upon receipt of notice of the ALJ action, the PC may complete any pending action and/or consider any additional evidence or information submitted.\n\nEXCEPTION: In a dual determination situation, where SSA makes a reconsideration determination and an initial determination on the same case, the ALJ will not dismiss the case merely because the initial determination has not been reconsidered, since a hearing is proper with respect to the reconsideration determination. Therefore, the entire claims file is sent to the ALJ. (See GN 03101.001 and GN 03103.140 concerning multiple levels of appeal on one case and GN 03103.220 on dismissal.)\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0203103120\n\t\nGN 03103.120 - Hearing Filed Before Receipt of Reconsideration Determination - 01/28/2021\nBatch run: 10/27/2026\nRev:01/28/2021\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
            "scope": "Whole captured primary source, complete prerequisites/notes and reference labels retained."
          },
          {
            "id": "DI26535.036:whole",
            "source_code": "DI26535.036",
            "start": 0,
            "end": 5154,
            "exact_text": "Effective Dates: 09/17/2021 - Present\nPrevious | Next\n\nTN 5 (08-22)\n\nDI 26535.036 Special Notice Situations\nA. \nNotices not covered by instructions\n\nOn rare occasions instructions may not provide a notice that exactly fits a unique or complex case situation. However, Disability Determination Services (DDS) examiners may use independent judgment to decide what information must be included in notices not covered by instructions, provided the decisions are consistent with the notice standards outlined in NL 00603.020, Preparing a Notice for Situations Not Fully Covered by Instructions.\n\nB. \nPre-effectuation Review (PER) and Quality Assurance (QA) sample cases\n\nWhen the DDS prepares a notice or personalized explanation and the case is selected for Pre-effectuation Review (PER) or Quality Assurance (QA) review, DDS prepares an undated notice or explanation, according to the procedures outlined in DI 81020.130, Electronic Case Closure and DI 81020.135, Federal Quality Review\n\nAfter review, the Disability Quality Branch (DQB) dates and releases notices to the claimant, and any authorized representative (e.g., attorney or non-attorney representative) at the conclusion of the review. The certified electronic folder (CEF) will include a dated image of the released notice, and the DQB does not need to annotate the CEF with the date the notice is released. The notice release date is entered in the OQR legacy system and can be viewed in eView on the Case Review screen under the Case Data tab.\n\nC. \nSpanish language notices\n\nThe field office (FO) identifies those individuals, including representative payees, who should receive a Spanish notice by inserting the remark “Spanish Notice Required” in the 3367. The DDS prepares the notice according to the instructions in NL 00603.110, Spanish Language Notices.\n\nREMINDER: If a Spanish notice is not available, include a Spanish cover letter and/or the multi language insert with the English notice. \n\nFor additional information on the multi-language insert, see NL 10601.225.\n\nFor a copy of the multi-language insert, see The Multilanguage Letter Insert\n\nD. \nPrisoner cases\n\nSpecific notices are prepared for prisoner cases. The DDS may use these notices only when the exclusion of felony-related or confinement impairments under Section 223(d) (6) of the Social Security Act affects the outcome of the disability determination.\n\nReferences:\n\n•\n\nDI 23501.020, Prisoner Case Notices\n\n•\n\nDI 23501.025, Prisoner Notice Finder Chart\n\nE. \nInterim notices for capability or payee in question\n\nThe DDS prepares the personalized rationale for total and partially unfavorable medical determinations on the SSA-4268 (Explanation of Determination) and uses interim notice SSA-L1157 (Social Security Notice of Disability) to send the rationale to the party who receives the award notice. The DDS is able to send the interim notice unless:\n\n•\n\nthe FO determines claimant is incapable; or\n\n•\n\ncapability is in question.\n\nIf DDS is unable to send the interim notice because a capability issue is raised, the DDS places the personalized rationale in the:\n\n•\n\n(red) Jurisdictional Documents or Notices section of the Certified Electronic Folder (CEF) for release by the FO (See DI 81020.130 for electronic folder instructions); or\n\n•\n\nModular Disability Folder (MDF) for release by the FO (EDCS exclusion cases only); and\n\n•\n\nAnnotate item 34 of the SSA-831 (Disability Determination and Transmittal) with special notice instructions to the FO.\n\nF. \nTitle II and Title XVI special notice options for the blind or visually impaired\n\nEffective June 30, 2008, special notice options are available to any applicant, beneficiary, claimant or recipient who applies for benefits under title II or title XVI if they are blind or tell us they need assistance because of a visual impairment. The policies and instructions on the preparation of special notification to the blind or visually impaired are located in NL 01000.000ff. Special Notice Options for the Blind or Visually Impaired.\n\nG. \nTitle II and Title XVI cases involving the death of a claimant\n\nIn cases involving death, (depending on the status of the case) the DDS may be required to make a determination on the claim and prepare a notice. To determine the required DDS actions in Title II or Title XVI cases involving death, please see the following:\n\n•\n\nDI 23510.020, Death after Filing – Title II (Chart)\n\n•\n\nDI 23510.025, Death Prior to Filing – Title II (Chart)\n\n•\n\nDI 23510.030, Determination Paragraph for a Disability Insurance Benefit (DIB) Claim filed after Death (Chart)\n\n•\n\nDI 23510.035, Death after Filing – Title XVI (Chart)\n\n•\n\nDI 23510.040, Determination Paragraph, Death after Filing – Title XVI (Chart)\n\n•\n\nDI 81020.130, Electronic Case Closure\n\n•\n\nDI 81020.135, Federal Quality Review\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0426535036\n\t\nDI 26535.036 - Special Notice Situations - 09/17/2021\nBatch run: 06/12/2025\nRev:09/17/2021\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "span_sha256": "6fc82ec8575712d86f2470c7a64f3e7407238977a9c58dca4f370e4438e39af9",
            "scope": "Held comparison context only; no workflow claim adopted."
          }
        ],
        "holds": [
          "One quality-review undated-image record remains explicitly unmapped under001B3-vs036B comparison, not automaticallyreconciled.",
          "No current prototypeinitial-program bypass; no MSSICS/MISSICS/CCE or MDW/MDWAI alias adoption.",
          "Regional difference, linked subsequentclaims DI51501.001 and other linked processing/dismissal/goodcause procedures retain their own scope, not actual individual decisions.",
          "Existing old3core/5oldbranches and all rawR20thirteen records/sourceobjects/sourcehistories retained; only12 selected futureflow appends proposed.",
          "No automatic filing, conversion, extension, dismissal, payment, receipt, office transition or successful rejoin."
        ],
        "negative_QA": [
          {
            "id": "N01",
            "case": "Copy in file but reported nonreceipt",
            "required_boundary": "Accept/copy/document are distinct from goodcause or receipt-date decision."
          },
          {
            "id": "N02",
            "case": "No copy but recon indicated",
            "required_boundary": "Keep actualevidence and DDS-copy requests, no receivedcopy/date inference."
          },
          {
            "id": "N03",
            "case": "No copy and no indication",
            "required_boundary": "Absence alone is not actualappealstage or automatic dismissal/conversion."
          },
          {
            "id": "N04",
            "case": "Before-completed-recon route",
            "required_boundary": "Do not inherit usual completed-recon premise; fullparent entryexception guard required."
          },
          {
            "id": "N05",
            "case": "Claimant chooses recon but alreadyfiled",
            "required_boundary": "Do not treat source assistance condition as met."
          },
          {
            "id": "N06",
            "case": "Claimant insists hearing",
            "required_boundary": "Do not override choice; RC copies exclude claimantcopy."
          },
          {
            "id": "N07",
            "case": "PC directlyreceivesletter versus noticehearingfiled",
            "required_boundary": "Separate conditional actions/FO-PC roles."
          },
          {
            "id": "N08",
            "case": "Dual determination properreconpart",
            "required_boundary": "No dismissal merelyinitialnotreconsidered, no guarantee against othergrounds."
          },
          {
            "id": "N09",
            "case": "Concurrent medicalappeal",
            "required_boundary": "Keep entiremedicalscope includingfavorable, excludeothertechnicaldenial ONLY ifunappealed."
          },
          {
            "id": "N10",
            "case": "SSA3441/827 missing",
            "required_boundary": "National no-delay/nofollowup namedforms only; differingregionalinstructions retained."
          },
          {
            "id": "N11",
            "case": "Late request bychannel",
            "required_boundary": "No universal newlysolicited statement requirement;existingroutingpaper/electronic distinction."
          },
          {
            "id": "N12",
            "case": "Paperlate newapp",
            "required_boundary": "Paper AND(worsening ORadditionalimpairment), linkedsubsequentclaimlimit/noeligibilitydecision."
          },
          {
            "id": "N13",
            "case": "MDW record",
            "required_boundary": "No MDWAI alias or proofnewclaim entered."
          },
          {
            "id": "N14",
            "case": "Conditionalreturn ifALJdismisses",
            "required_boundary": "No actualdismissal/automaticrejoin."
          },
          {
            "id": "N15",
            "case": "Undatedimage sourcecomparison",
            "required_boundary": "Held/unmapped, no datecalc or date-onlyreconciliation."
          },
          {
            "id": "N16",
            "case": "Prototypeinitial text",
            "required_boundary": "No currentprogramdeployment or new bypassproposed."
          },
          {
            "id": "N17",
            "case": "60fromreceipt/5presumption",
            "required_boundary": "Rebuttable sourcefilingrule, no deadlinecalculator/timelinessruling."
          },
          {
            "id": "N18",
            "case": "Record/source/ancestor/flow/entryscope changed",
            "required_boundary": "Future exactguard must reject, no genericprojectionwaiver."
          }
        ],
        "entry_exception_scopes_exact": {
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing": null,
          "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording": null,
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application": null,
          "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt": null,
          "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated": null,
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication": {
            "kind": "exception_to_usual_after_reconsideration_entry",
            "usual_path_completed_reconsideration_not_inherited": true,
            "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
            "render_before_main_route_steps": true,
            "full_parent_path_source_guard_required": true
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses": {
            "kind": "exception_to_usual_after_reconsideration_entry",
            "usual_path_completed_reconsideration_not_inherited": true,
            "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
            "render_before_main_route_steps": true,
            "full_parent_path_source_guard_required": true
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration": {
            "kind": "exception_to_usual_after_reconsideration_entry",
            "usual_path_completed_reconsideration_not_inherited": true,
            "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
            "render_before_main_route_steps": true,
            "full_parent_path_source_guard_required": true
          },
          "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay": null,
          "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope": null,
          "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception": null,
          "hearing-after-medical-reconsideration/alj-premature-request-PC-handling": {
            "kind": "exception_to_usual_after_reconsideration_entry",
            "usual_path_completed_reconsideration_not_inherited": true,
            "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
            "render_before_main_route_steps": true,
            "full_parent_path_source_guard_required": true
          }
        },
        "held_unmapped_record": {
          "full_route": "hearing-after-medical-reconsideration/alj-quality-review-undated-notice-image",
          "original_record_exact": {
            "id": "alj-quality-review-undated-notice-image",
            "title": "The notice image has no date during quality-review handling",
            "when": "A quality-selected case has an undated DDS notice image in the electronic folder.",
            "you": "Ask staff to check the source-specific notice-release information.",
            "ssa": "The instruction says the quality branch prints, dates and mails the notice after its review. The image can remain undated; the release date is recorded in the stated routing-information field.",
            "next": "An undated image alone does not establish whether the notice was mailed or when it was received.",
            "condition_logic": "all",
            "conditions": [
              "The case is selected for review by the source-named DQB.",
              "An undated DDS-prepared reconsideration notice copy is stored in the CEF."
            ],
            "source_case_conditions": [
              "The case is selected for review by the source-named DQB.",
              "An undated DDS-prepared reconsideration notice copy is stored in the CEF."
            ],
            "source_context_refs": [
              "001-B3"
            ],
            "source_provenance": [
              {
                "id": "001-B3",
                "source_code": "DI12010.001",
                "url": "https://secure.ssa.gov/poms.nsf/lnx/0412010001",
                "start": 3171,
                "end": 5160,
                "exact_text": "3. \nCopy of reconsideration notice\n\nTake one of the following actions for verifying receipt or non-receipt of the notice.\n\na. \n\nCheck the file for a copy of the reconsideration notice. In electronic folders, check eView, Evidence Portal (EP),or the Online Retrieval System (ORS) for the notice.\n\nb. \n\nIf a copy of the reconsideration notice is in file but the claimant alleges not receiving a notice:\n\n•\n\nMake a copy of the reconsideration notice for the claimant and accept the request for hearing.\n\n•\n\nDocument the file that the claimant did not receive the original reconsideration notice.\n\nc. \n\nIf a copy of the reconsideration notice is not in file, check the claim folder(s) for an indication that a reconsideration determination was made, e.g., item 34 (Remarks) on the SSA 831 (Disability Determination and Transmittal) shows “Recon Affirmation.”\n\n•\n\nIf there is evidence that a reconsideration determination was made, i.e., disability determination services query (DDSQ), accept the request for a hearing and contact the disability determination services (DDS) by email or phone. Immediately send a duplicate reconsideration notice to the claimant, the FO, and a copy to his or her attorney or non-attorney representative, if applicable. If the SSA-831 is missing, ask the DDS to send a copy of SSA-831 as well.\n\n•\n\nIf there is no indication that a reconsideration determination has been made, follow the instructions in GN 03103.120 Hearing Filed Before Receipt of Reconsideration Determination.\n\n•\n\nWhen the disability quality branch (DQB) selects a case for review, an undated copy of the DDS prepared notice is stored in the certified electronic folder (CEF). After the review is completed, DQB prints, dates, and mails the notice. The DQB does not add the date to the image of the notice in the CEF. Instead, the notice release date is recorded in the Office of Quality Performance (OQP) Routing Information in the Case Review link.\n\n4. \nMedical information and release forms",
                "span_sha256": "7193aa4733994956fc24953773b72ae3341dca903ca52d806fade64c1c6ebca0",
                "maintext_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6"
              }
            ],
            "source_instruction_summary": "B3c quality paragraph: afterreview DQBprints/dates/mails; doesnotadddateCEFimage; release date recorded OQP Routing Information inCaseReview. Actualreviewcompletion isneededbeforeinferring release. Not EFReceived, not automaticPDE/PDN or OQP/OQR identity.",
            "qualifications": [
              "Selected ALJ-hearing request handling only; not a DHO medical-CDR first-cessation hearing, a case eligibility decision or a completed filing/transfer.",
              "The usual after-reconsideration story does not establish the stage for an exception. Actual notice/reconsideration/filing facts and claimant choice must be established separately.",
              "No prototype-initial bypass is proposed as current practice. The published prototype wording is preserved as a source limitation, not verified current program deployment.",
              "Receipt and filing rules are not measured hearing wait times or an automatic deadline calculator; the five-day receipt presumption is rebuttable.",
              "Source-defined regional differences remain applicable where stated; no actual regional directive is supplied or chosen.",
              "Named staff systems/forms and historical Atlas observations do not prove current staff use, case data, valid release authority or successful office action.",
              "No actual ALJ dismissal, extension, payment outcome, new-claim allowance, remand or successful rejoin is established."
            ],
            "owner": "Field-office staff under the selected source scope",
            "timing": "Published staff instructions only; no measured completion time or date calculation.",
            "existing_record_context_candidate_ids": [
              "APP_EVIEW"
            ],
            "rejoin": {
              "status": "not_established_by_selected_source",
              "automatic_transition": false,
              "unknowns": [
                "Actual case facts, recipient receipt and final appeal action remain unverified."
              ]
            },
            "source_native_acceptance": false,
            "full_route": "hearing-after-medical-reconsideration/alj-quality-review-undated-notice-image",
            "source": "r20_ALJ_request001",
            "section": "001-B3",
            "additional_sources": [],
            "source_qualified_branch": {
              "kind": "selected_source_qualified_ALJ_exception",
              "case_facts_not_determined": true,
              "new_native_edges_or_aliases": false
            },
            "review_status": "Selected published ALJ exception; actual appeal stage, case facts, internal execution and outcome unverified.",
            "route": "Selected staff-handling instruction; return to the usual path not established",
            "entity_ids": [],
            "systems": [
              "eView"
            ],
            "source_receipt": {
              "checked_on": "2026-10-31",
              "snapshot_sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
              "snapshot_path": "/service/sources/DI12010.001-r20-main.txt",
              "report": "/service/r20-ALJ-selected-claim-ledger.json"
            }
          },
          "status": "UNMAPPED_SOURCE_APPLICABILITY_COMPARISON_HELD",
          "source_context_refs": [
            "DI12010.001:whole",
            "DI26535.036:whole"
          ],
          "source_observations": [
            "001B3 says DQB leaves the CEF notice image undated and records release date in OQP Routing Information under Case Review.",
            "036B says in PER/QA review DQB releases a notice and CEF includes a dated released-notice image; release date is entered in OQR legacy and viewed in CaseData/CaseReview."
          ],
          "limit": "The described review/document/copy stages overlap but exact identity/applicability is not established. Do not equate all images or field names, choose date precedence, repair the old record silently, assign a notice receipt/issue date, or call this a resolved uniform rule. This proposal leaves that original record and its bounded prior source claim unchanged; an uncertainty/field-repair proposal remains separate."
        },
        "preparation_timing_actor_rejoin_profiles": {
          "hearing-after-medical-reconsideration/alj-notice-copy-present-reported-nonreceipt": {
            "preparation_and_source_case_facts": [
              "Staff are verifying the notice for an ALJ hearing request under the selected medical-reconsideration context.",
              "A copy of the reconsideration notice is in the file.",
              "The claimant alleges not receiving the original notice."
            ],
            "actor_labels": [
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-notice-copy-present-reported-nonreceipt-source-step-1",
              "alj-notice-copy-present-reported-nonreceipt-source-step-2"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-notice-copy-absent-reconsideration-indicated": {
            "preparation_and_source_case_facts": [
              "No copy of the reconsideration notice is in the file.",
              "The file contains evidence that a reconsideration determination was made; the source gives SSA831 Remarks or DDSQ as examples."
            ],
            "actor_labels": [
              "FO",
              "SSA staff"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-notice-copy-absent-reconsideration-indicated-source-step-1",
              "alj-notice-copy-absent-reconsideration-indicated-source-step-2"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication": {
            "preparation_and_source_case_facts": [
              "No reconsideration notice copy is found.",
              "No indication that a reconsideration determination was made is found after the source-defined checks.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "actor_labels": [
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-no-notice-no-reconsideration-indication-source-step-1"
            ],
            "entry_exception_scope_exact": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-missing-3441-or-827-no-transfer-delay": {
            "preparation_and_source_case_facts": [
              "This is the ALJ-hearing request handling covered by DI12010.001.",
              "The file lacks an SSA3441 or SSA827 with the appeal."
            ],
            "actor_labels": [
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-missing-3441-or-827-no-transfer-delay-source-step-1"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-concurrent-medical-appeal-scope": {
            "preparation_and_source_case_facts": [
              "The application claims Title II and Title XVI benefits OR more than one Title II disability benefit.",
              "The claimant appeals a medical issue for any of those benefits."
            ],
            "actor_labels": [
              "FO",
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-concurrent-medical-appeal-scope-source-step-1",
              "alj-concurrent-medical-appeal-scope-source-step-2",
              "alj-concurrent-medical-appeal-scope-source-step-3"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-reconsideration-next-claimant-chooses": {
            "preparation_and_source_case_facts": [
              "The parent file/no-indication scenario applies.",
              "Reconsideration is in fact the next appeal level due.",
              "The claimant chooses reconsideration and has not previously filed it.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "actor_labels": [
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-reconsideration-next-claimant-chooses-source-step-1",
              "alj-reconsideration-next-claimant-chooses-source-step-2"
            ],
            "entry_exception_scope_exact": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-no-notice-no-reconsideration-indication/alj-claimant-insists-before-reconsideration": {
            "preparation_and_source_case_facts": [
              "The parent file/no-indication scenario applies.",
              "The source’s explanation that reconsideration is next/before completion has been given.",
              "The claimant still insists on filing for a hearing.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "actor_labels": [
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-claimant-insists-before-reconsideration-source-step-1",
              "alj-claimant-insists-before-reconsideration-source-step-2"
            ],
            "entry_exception_scope_exact": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-dual-determination-proper-hearing-exception": {
            "preparation_and_source_case_facts": [
              "SSA made a reconsideration determination and an initial determination on the same case.",
              "A hearing is proper with respect to the reconsideration determination.",
              "The initial determination has not been reconsidered."
            ],
            "actor_labels": [
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-dual-determination-proper-hearing-exception-source-step-1"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/alj-premature-request-PC-handling": {
            "preparation_and_source_case_facts": [
              "PC is handling the selected hearing-request-before-reconsideration procedure.",
              "PC is advised a hearing was filed OR receives a letter directly from the claimant requesting a hearing.",
              "This is the source’s entry exception: the usual-path completed-reconsideration premise is not inherited. The actual stage and selected exception predicates must be established."
            ],
            "actor_labels": [
              "PC",
              "PC",
              "PC"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": null,
            "ordered_step_ids": [
              "alj-premature-request-PC-handling-source-step-1",
              "alj-premature-request-PC-handling-source-step-2",
              "alj-premature-request-PC-handling-source-step-3"
            ],
            "entry_exception_scope_exact": {
              "kind": "exception_to_usual_after_reconsideration_entry",
              "usual_path_completed_reconsideration_not_inherited": true,
              "mandatory_visible_entry_scope": "This hearing-request question may arise before reconsideration is complete. The usual after-reconsideration story does not establish that stage for your case; only the conditions shown for this route apply.",
              "render_before_main_route_steps": true,
              "full_parent_path_source_guard_required": true
            },
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-explanation-routing": {
            "preparation_and_source_case_facts": [
              "The existing late-filing parent scenario and the selected source late-hearing procedure apply; actual timeliness remains to be established.",
              "The case is paper.",
              "A written explanation is already available for routing; this flow does not decide when to obtain it."
            ],
            "actor_labels": [
              "FO",
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": "60 days from notice receipt; 5-day receipt presumption can be rebutted; no actual timeliness finding.",
            "ordered_step_ids": [
              "alj-late-paper-explanation-routing-source-step-1",
              "alj-late-paper-explanation-routing-source-step-2",
              "alj-late-paper-explanation-routing-source-step-3"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-electronic-explanation-recording": {
            "preparation_and_source_case_facts": [
              "The existing late-filing parent scenario applies.",
              "The case is electronic and good-cause information is being handled."
            ],
            "actor_labels": [
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": "60 days from notice receipt; 5-day receipt presumption can be rebutted; no actual timeliness finding.",
            "ordered_step_ids": [
              "alj-late-electronic-explanation-recording-source-step-1",
              "alj-late-electronic-explanation-recording-source-step-2"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          },
          "hearing-after-medical-reconsideration/late-filing/alj-late-paper-worsening-new-application": {
            "preparation_and_source_case_facts": [
              "The existing late-filing parent scenario applies.",
              "The case is paper.",
              "The claimant alleges worsening condition OR additional impairment."
            ],
            "actor_labels": [
              "FO",
              "FO",
              "FO"
            ],
            "original_timing_exact": "Published staff instructions only; no measured completion time or date calculation.",
            "numeric_filing_rule_not_measured_time": "60 days from notice receipt; 5-day receipt presumption can be rebutted; no actual timeliness finding.",
            "ordered_step_ids": [
              "alj-late-paper-worsening-new-application-source-step-1",
              "alj-late-paper-worsening-new-application-source-step-2",
              "alj-late-paper-worsening-new-application-source-step-3"
            ],
            "entry_exception_scope_exact": null,
            "rejoin": {
              "status": "not_established",
              "automatic_transition": false,
              "unknowns": [
                "Actual appeal stage, request/receipt dates, claimant choice, ALJ action, receiving-office processing and successful continuation remain unverified."
              ]
            }
          }
        }
      },
      "GN7": {
        "flows": {
          "report-death/deceased-ss5-parent-names": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "deceased-ss5-parent-names",
            "full_route": "report-death/deceased-ss5-parent-names",
            "entry_conditions": [
              "A request concerns a deceased individual’s SS-5 and includes the parents’ first and last names.",
              "Applicable proof-of-death, living-person privacy and other disclosure restrictions still require review; this example does not authorize release."
            ],
            "steps": [
              {
                "id": "deceased-ss5-parent-names-source-1",
                "title": "Keep the parents’ death-proof condition",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Do not provide the parents’ first and last names without proof of their deaths.",
                "conditions": [
                  "A request concerns a deceased individual’s SS-5 and includes the parents’ first and last names.",
                  "Applicable proof-of-death, living-person privacy and other disclosure restrictions still require review; this example does not authorize release."
                ],
                "source": "deceaseddisclosure",
                "section": "C.4",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The deceased applicant’s death alone does not establish that the parents are deceased or that their names can be released.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              },
              {
                "id": "deceased-ss5-parent-names-source-2",
                "title": "Use the special request-handling route",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Send the SS-5 request to the OEIO FOIA Workgroup, the special unit identified by the source for these requests. The source lists Social Security Administration, OEIO FOIA Workgroup, 6100 Wabash Avenue, P.O. Box 33022, Baltimore MD 21290-3022.",
                "conditions": [
                  "A request concerns a deceased individual’s SS-5 and includes the parents’ first and last names.",
                  "Applicable proof-of-death, living-person privacy and other disclosure restrictions still require review; this example does not authorize release."
                ],
                "source": "deceaseddisclosure",
                "section": "C.4",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "This is the captured source’s routing address, not a tested current receipt, processing duration or guarantee of disclosure. The public FOIA page is also referenced in B.1.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          },
          "report-death/deceased-adap-consult": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "deceased-adap-consult",
            "full_route": "report-death/deceased-adap-consult",
            "entry_conditions": [
              "The requested deceased-person record includes alcoholism and drug abuse patient information covered by the source’s ADAP restriction."
            ],
            "steps": [
              {
                "id": "deceased-adap-consult-source-1",
                "title": "Obtain guidance for a vital-statistics disclosure",
                "kind": "action",
                "actor": "SSA staff",
                "action": "If Federal or State law requires ADAP disclosure for collecting death information or other vital statistics, consult the regional Privacy Act Coordinator. The coordinator contacts the Office of the General Counsel for guidance about the requested disclosure.",
                "conditions": [
                  "The requested deceased-person record includes alcoholism and drug abuse patient information covered by the source’s ADAP restriction.",
                  "Vital-statistics law requires this disclosure."
                ],
                "source": "deceaseddisclosure",
                "section": "C.2 first row",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "Whether a law requires this particular disclosure is not determined by selecting this example; 42 CFR 2.15 remains linked authority.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ],
                "alternative_group": "adap-law-scope"
              },
              {
                "id": "deceased-adap-consult-source-2",
                "title": "Obtain guidance for other ADAP disclosure",
                "kind": "action",
                "actor": "SSA staff",
                "action": "If the vital-statistics laws do not apply, other disclosure is subject to 42 CFR 2.15, which may require a personal representative’s consent. Consult the regional Privacy Act Coordinator for guidance.",
                "conditions": [
                  "The requested deceased-person record includes alcoholism and drug abuse patient information covered by the source’s ADAP restriction.",
                  "Vital-statistics laws do not apply to this disclosure."
                ],
                "source": "deceaseddisclosure",
                "section": "C.2 second row",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The source says consent may be required; this is not a finding that consent is given, sufficient or always required. GN 03301.040B remains separately scoped.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ],
                "alternative_group": "adap-law-scope"
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            },
            "alternative_groups": [
              {
                "id": "adap-law-scope",
                "label": "Different guidance routes depend on the applicable law",
                "logic": "source_conditions_determine_branch",
                "note": "These are conditional alternatives, not two disclosures that occur in sequence. This walkthrough does not decide whether a law applies."
              }
            ]
          },
          "report-death/funeral-director-ssn-disclosure": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "funeral-director-ssn-disclosure",
            "full_route": "report-death/funeral-director-ssn-disclosure",
            "entry_conditions": [
              "A funeral home director requests disclosure or verification of the deceased individual’s SSN."
            ],
            "steps": [
              {
                "id": "funeral-director-ssn-disclosure-source-1",
                "title": "Require the specified source of death proof",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Provide the requested SSN information only if proof that the individual is deceased comes from a source other than the State.",
                "conditions": [
                  "A funeral home director requests disclosure or verification of the deceased individual’s SSN."
                ],
                "source": "deceaseddisclosure",
                "section": "C.5",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "A funeral-home request or State death report alone does not establish the required proof or waive other applicable restrictions; this illustration makes no actual disclosure.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          },
          "replace-tax-form/deceased-statement-state-proof": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "deceased-statement-state-proof",
            "full_route": "replace-tax-form/deceased-statement-state-proof",
            "entry_conditions": [
              "The requested information has been independently classified as non-tax return information under its applicable instruction.",
              "The original statement-classification reference is separately scoped: GN 03315.010 does not itself classify every replacement tax statement.",
              "Review of a deceased person’s record must establish acceptable death proof and every applicable disclosure restriction."
            ],
            "steps": [
              {
                "id": "deceased-statement-state-proof-source-1",
                "title": "Do not rely only on restricted State data",
                "kind": "action",
                "actor": "SSA staff",
                "action": "When the State is the source of death information, do not tell an individual or entity that SSA has that State death information, disclose the fact of death, or use the State information alone as proof of death to disclose other information.",
                "conditions": [
                  "The requested information has been independently classified as non-tax return information under its applicable instruction.",
                  "The original statement-classification reference is separately scoped: GN 03315.010 does not itself classify every replacement tax statement.",
                  "Review of a deceased person’s record must establish acceptable death proof and every applicable disclosure restriction."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.a; C.1",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "Tax return information remains protected after death under A. This non-tax sequence does not decide the original record’s separately cited statement classification.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              },
              {
                "id": "deceased-statement-state-proof-source-2",
                "title": "Review independent acceptable death proof",
                "kind": "action",
                "actor": "SSA staff",
                "action": "If the record shows State death data but the requester presents acceptable independent death-proof documents, disclosure may be based on those documents unless Federal law or regulations prohibit it. Apply the source’s acceptable-proof criteria and other restrictions.",
                "conditions": [
                  "The requested information has been independently classified as non-tax return information under its applicable instruction.",
                  "The original statement-classification reference is separately scoped: GN 03315.010 does not itself classify every replacement tax statement.",
                  "Review of a deceased person’s record must establish acceptable death proof and every applicable disclosure restriction."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.a final note",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The source lists public death records, specified professional statements, coroner material, sufficiently identifying obituaries and other certified records acceptable in SSA’s discretion. No document is automatically accepted by this walkthrough; living-person privacy and ADAP restrictions remain.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          },
          "replace-tax-form/deceased-statement-living-privacy": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "deceased-statement-living-privacy",
            "full_route": "replace-tax-form/deceased-statement-living-privacy",
            "entry_conditions": [
              "The requested non-tax return information on a deceased person’s record pertains to or affects a living individual.",
              "Any separate statement classification and proof-of-death requirements must be established; they are not decided here."
            ],
            "steps": [
              {
                "id": "deceased-statement-living-privacy-source-1",
                "title": "Apply living-person privacy protections",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Apply the same FOIA and Privacy Act requirements that apply to the affected living person. In the source’s widow example, do not disclose the deceased person’s PIA or retirement benefit rate to others (except to the widow), because that would allow calculation of her benefit rate. If the two were living together at death, do not disclose their address to another party because it also pertains to the widow.",
                "conditions": [
                  "The requested non-tax return information on a deceased person’s record pertains to or affects a living individual.",
                  "Any separate statement classification and proof-of-death requirements must be established; they are not decided here."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.b; C.3",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The examples are not a universal entitlement finding or a waiver of the living person’s privacy.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              },
              {
                "id": "deceased-statement-living-privacy-source-2",
                "title": "Keep the specific release conditions",
                "kind": "action",
                "actor": "SSA staff",
                "action": "For the C.3 table, disclose only if the requester may be entitled to the affected living person’s information and a State is not its source. The note permits requester-provided consent from the living person if the requested deceased-person information is in that living person’s own record.",
                "conditions": [
                  "The requested non-tax return information on a deceased person’s record pertains to or affects a living individual.",
                  "Any separate statement classification and proof-of-death requirements must be established; they are not decided here."
                ],
                "source": "deceaseddisclosure",
                "section": "C.3",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The requester-entitlement, source and own-record consent conditions remain explicit; this does not grant permission or replace the separately linked disclosure framework.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          },
          "erroneous-death-record/own-state-death-report-access": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "own-state-death-report-access",
            "full_route": "erroneous-death-record/own-state-death-report-access",
            "entry_conditions": [
              "The Number Holder requests access to the State death report on their own record to resolve an erroneous report of death."
            ],
            "steps": [
              {
                "id": "own-state-death-report-access-source-1",
                "title": "Use the narrow own-record access exception",
                "kind": "action",
                "actor": "SSA staff",
                "action": "The source permits disclosure of the State report of death to the Number Holder who requests access to resolve the erroneous report.",
                "conditions": [
                  "The Number Holder requests access to the State death report on their own record to resolve an erroneous report of death."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.a",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "This exception is not general third-party access, a finding that the requester’s identity has been verified, or proof of a corrected record or reinstated payment. The separate proof-of-life/correction process remains separately scoped.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          },
          "erroneous-death-record/death-information-source-check": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "death-information-source-check",
            "full_route": "erroneous-death-record/death-information-source-check",
            "entry_conditions": [
              "The disclosure review requires identifying whether death information came from a State."
            ],
            "steps": [
              {
                "id": "death-information-source-check-source-1",
                "title": "Identify the recorded source",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Use Person Information through iMAIN to access the Numident query. SSD 01 through 65 indicates a State source; a record showing Electronic Death Report also indicates a State source.",
                "conditions": [
                  "The disclosure review requires identifying whether death information came from a State."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.a first note",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "The source describes query and field roles. It does not establish a new native identity, record schema equivalence or actual current system behavior; RM 10235.025 details remain linked scope.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              },
              {
                "id": "death-information-source-check-source-2",
                "title": "Apply only the relevant restriction or exception",
                "kind": "action",
                "actor": "SSA staff",
                "action": "Do not treat a State source as general permission to disclose or as sole proof for another deceased-record disclosure. Review the applicable narrow exception or acceptable independent death proof and the remaining restrictions.",
                "conditions": [
                  "The disclosure review requires identifying whether death information came from a State."
                ],
                "source": "deceaseddisclosure",
                "section": "B.2.a",
                "source_context_refs": [
                  "GN03315.010:whole"
                ],
                "qualifications": [
                  "A source check does not correct a death record, establish consent, prove entitlement or complete a return to another case process.",
                  "Source-conditioned staff review only; no actual information release, eligibility, case correction or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned review does not demonstrate actual disclosure, correction, successful continuation or return to the usual case path."
              ]
            }
          }
        },
        "original_records": {
          "report-death/deceased-ss5-parent-names": {
            "id": "deceased-ss5-parent-names",
            "title": "Requesting a deceased person’s SS-5",
            "when": "Request includes parent names.",
            "you": "Identify the requested SS-5 record.",
            "ssa": "Route to the OEIO FOIA Workgroup; parent names require proof of their deaths.",
            "route": "OEIO FOIA Workgroup",
            "next": "Provide requested death proof; no release or timing guarantee.",
            "source": "deceaseddisclosure",
            "section": "C.4",
            "timing": "No completion duration specified",
            "review_status": "Selected subsection checked; remaining disclosure exceptions require review"
          },
          "report-death/deceased-adap-consult": {
            "id": "deceased-adap-consult",
            "title": "The deceased record includes protected treatment information",
            "when": "A disclosure request involves ADAP records.",
            "you": "Explain the requested records and purpose to SSA.",
            "ssa": "Consult the regional Privacy Act Coordinator. For required vital-statistics disclosures, the coordinator contacts the Office of the General Counsel; other disclosures also require coordinator guidance.",
            "route": "Regional Privacy Act Coordinator; Office of the General Counsel for the cited vital-statistics case",
            "next": "SSA must obtain the prescribed guidance before resolving the disclosure request; release is not automatic.",
            "source": "deceaseddisclosure",
            "section": "B.2.c; C.2",
            "timing": "No consultation or completion duration specified",
            "review_status": "Consultation route checked; no independent interpretation of 42 CFR 2.15"
          },
          "report-death/funeral-director-ssn-disclosure": {
            "id": "funeral-director-ssn-disclosure",
            "title": "A funeral director asks SSA to verify the deceased person’s SSN",
            "when": "A funeral home director requests SSN disclosure or verification.",
            "you": "Provide the requested proof of death.",
            "ssa": "Check for proof of death from a source other than the State before providing the requested information.",
            "route": "SSA disclosure review; exact internal assignment not established",
            "next": "The request requires the specified death evidence; a State death report alone does not establish this release route.",
            "source": "deceaseddisclosure",
            "section": "C.5",
            "timing": "No processing duration specified",
            "review_status": "Selected disclosure condition checked; other applicable restrictions remain"
          },
          "replace-tax-form/deceased-statement-state-proof": {
            "id": "deceased-statement-state-proof",
            "title": "A deceased beneficiary statement needs disclosure review",
            "when": "Requesting a deceased beneficiary replacement statement.",
            "you": "Contact SSA about the request.",
            "ssa": "Treat the statement as non-tax return information; apply deceased-record disclosure rules. Restricted State death data alone cannot establish release; consider acceptable independent death proof.",
            "route": "SSA disclosure review",
            "next": "Provide requested death evidence; release is conditional.",
            "source": "deceaseddisclosure",
            "section": "B.2.a; C.1",
            "timing": "No completion duration specified",
            "review_status": "Selected subsection checked; remaining disclosure exceptions require review",
            "additional_sources": [
              {
                "source": "taxpoms",
                "section": "B.2"
              }
            ]
          },
          "replace-tax-form/deceased-statement-living-privacy": {
            "id": "deceased-statement-living-privacy",
            "title": "The requested information affects a living person",
            "when": "Deceased-record information reveals living-person information.",
            "you": "Explain whose information you seek.",
            "ssa": "Apply living-person privacy requirements; assess the requester’s entitlement and source restriction.",
            "route": "SSA disclosure review",
            "next": "Death does not make every record public.",
            "source": "deceaseddisclosure",
            "section": "B.2.b; C.3",
            "timing": "No completion duration specified",
            "review_status": "Selected subsection checked; remaining disclosure exceptions require review"
          },
          "erroneous-death-record/own-state-death-report-access": {
            "id": "own-state-death-report-access",
            "title": "You need access to the State death report on your own record",
            "when": "You seek your own record to resolve an erroneous death report.",
            "you": "Explain that the report incorrectly identifies you as deceased.",
            "ssa": "Apply the specific permission to disclose the State death report to the Number Holder for resolving the erroneous report.",
            "route": "SSA own-record access review; exact component not established by this subsection",
            "next": "This access exception does not itself correct records or reinstate payment. Continue the separate correction process.",
            "source": "deceaseddisclosure",
            "section": "B.2.a",
            "timing": "No access or correction duration specified",
            "review_status": "Specific access exception checked; full proof-of-life procedure remains outside this branch"
          },
          "erroneous-death-record/death-information-source-check": {
            "id": "death-information-source-check",
            "title": "SSA must identify the source before deciding disclosure",
            "when": "Disclosure review requires identifying restricted State death information.",
            "you": "Describe the record access request.",
            "ssa": "Use Person Information via iMAIN to inspect the Numident source: SSD 01–65 or Electronic Death Report indicates State data. Apply the relevant disclosure restriction or exception.",
            "route": "Numident source check → applicable disclosure review",
            "next": "A source check is not permission for general disclosure or a completed correction.",
            "source": "deceaseddisclosure",
            "section": "B.2.a notes",
            "timing": "No completion duration specified",
            "review_status": "GN03315.010 notes checked; linked RM10235.025 unavailable and not reconstructed"
          }
        },
        "source_contexts": [
          {
            "id": "GN03315.010:whole",
            "start": 0,
            "end": 9452,
            "exact_text": "Effective Dates: 02/28/2024 - Present\nPrevious | Next\n\nTN 9 (05-26)\n\nGN 03315.010 Disclosing a Deceased Individuals Information\nA. \nDisclosure of tax return information\n\nSection 6103 of the Internal Revenue Code (IRC), 26 U.S.C. 6103, prohibits disclosure of return information (any information taken from a Federal tax return), unless specifically authorized by that section. The IRC protects the confidentiality of tax return information after death. For more information about the disclosure of tax return information of deceased individuals, see GN 03320.020. For information about the definition of tax return information, see GN 03320.001D.1.\n\nB. \nDisclosure of non tax return information\n1. \nNon tax return information\n\nUnder both the Freedom of Information Act (FOIA) and the Privacy Act (PA), privacy rights end at death. Therefore, with the exceptions noted below in GN 03315.010B.2., we may disclose any non tax return information from our records about a deceased individual to any party. This includes the SSN as well as the date of death. For information about the definition of non-tax return information, see GN03320.001D.2.\n\nWe frequently receive requests for genealogical information related to a deceased individuals records, such as the place of birth and parents first and last names listed on the original Application for a Social Security Card (Form SS-5). Direct individuals who request SS-5 information to the FOIA webpage at www.ssa.gov/foia/.\n\nNOTE: We may require payment of a fee to process requests for information for non-program purposes. For more information about fees for non-program purposes, see GN 03311.005E.\n\n2. \nExceptions for disclosure of non tax return information\n\nCertain Federal laws prohibit us from disclosing the following non tax return information about a deceased individual.\n\na. \nState death information (including fact of death)\n\nSection 205(r) of the Social Security Act (Act) allows us to collect death information from the States. This section of the Act also prohibits disclosure of State death information, including the fact of an individuals death, if our source of that information is from a State. When a State is the source of death information for a deceased individual, we cannot tell an individual or entity we have such information about that deceased individual. Neither can we use the State death information solely as proof of death to disclose other information about the deceased individual. Section 205(r) of the Act prohibits disclosure of state death information and exempts state death information from the requirements of the FOIA and the PA.\n\nWe may disclose State death data under specific exceptions set forth at section 205(r) of the Act. When authorized by section 205(r) of the Act (e.g., to ensure proper payment of a federally-funded benefit or statistical or research activities), SSA can establish reimbursable data exchange agreements to provide a Federal or State agency state death data.\n\nWe may also disclose a State report of death to a Number Holder (NH) who requests access to their record to resolve an erroneous report of death.\n\nNOTE: The Numident is the agency's official source of death information. Use Person Information (via iMAIN) to access the Numident query. The Numident \"SSD\" indicates the source of the agency's death information. A SSD of \"01\" through \"65\" indicates that a State is the source of the death information. If the record shows that the death data was obtained via Electronic Death Report (EDR), the State is the source of death. Both the SSD and EDR fields indicate state death data. For more information about State death data on the Numident, see RM 10235.025.\n\nNOTE: \n\nIf the record indicates a State is the source of the death data, but the requester presents us with proof of death documents, then we may disclose the records based on the document provided to us. The agency will disclose records concerning a deceased individual when we have acceptable proof of death unless Federal law or regulations prohibits the disclosure. Acceptable proof of death includes a copy of a public record of death of the number holder; a statement of death by the funeral home director; a statement of death by the attending physician or the superintendent, physician, or intern of the institution where the person died; a copy of the coroner's report of death or the verdict of the coroner's jury; an obituary that we determine has sufficient identifying information; or other certified record of death that we determine within our discretion is acceptable.\n\nb. \nLiving individual affected\n\nThe FOIA and PA protect against invasion of a living individuals privacy resulting from the disclosure of someone else's information, including that of a deceased individual. Therefore, if disclosure of a deceased individuals information would affect a living individuals privacy, we apply the same FOIA and PA requirements as those that apply for disclosure of information about a living individual. This means we would not disclose the deceased individuals information.\n\nFor example, if a widow receives benefits on a deceased NHs record, we would not disclose the deceased NHs Primary Insurance Amount (PIA) because it would easily enable someone to calculate the widows PIA, thereby affecting her privacy. For more information about disclosing information that affects a living individual see GN 03315.010C.3.\n\nc. \nAlcoholism and Drug Abuse Patient (ADAP) records\n\nThe laws and regulations concerning ADAP programs greatly limit disclosure of records about living or deceased individuals treated under those programs. For more information about ADAP records, see GN 03301.040B and GN 03315.010C.2.\n\nC. \nProcedures for releasing non tax information about deceased individuals\n1. \nFacts about Death\n\nIf the source of the death (SSD) information in the Numident is...\n\n\t\n\nThen...\n\n\n\n\nA State (i.e., an SSD of \"01\" through \"65\"),\n\n\t\n\nDo not disclose the fact of death or any other information about the deceased individual.\n\n\n\n\nA death certificate; a funeral director's statement; or a source other than a State (e.g., VA),\n\n\t\n\nDisclose the fact of death, as well as other non tax return information, to any party unless the disclosure affects a living individual.\n\n \n\n2. \nADAP records\n\nIf...\n\n\t\n\nThen...\n\n\n\n\nDisclosure of ADAP records is required by a Federal or State law for the collection of death info or other vital statistics,\n\n \n\nNOTE: See the regulations at 42 CFR Section 2.15 for more information.\n\n\t\n\nConsult with the regional Privacy Act Coordinator (PAC). The PAC will contact the Office of the General Counsel for further guidance concerning the requested disclosure.\n\n\n\n\nVital statistics laws do not apply to the disclosure of ADAP records,\n\n\t\n\nAny other disclosure of an individuals ADAP record is subject to the regulations at 42 CFR Section 2.15, which may require a personal representatives consent. Consult with the regional PAC for guidance.\n\nNOTE:For more information about ADAP records, see GN 03301.040B.\n\n \n\n3. \nOther non tax return information that affects a living individual\n\nIf the information...\n\n\t\n\nThen disclose...\n\n\n\n\nOn the deceased individuals record pertains to or affects a living individual,\n\n\t\n\nOnly if the requester may be entitled to information about the affected living individual and a State is not the source of the information.\n\n \n\nEXAMPLE 1: X, a retirement beneficiary, dies, leaving no entitled survivors. The funeral home provides a statement of death. ADAP is not involved. We may disclose the fact, date of X's death, their benefit rate, their address, or any other non tax return information, to any party.\n\nEXAMPLE 2: The same facts as Example 1, except that X leaves a widow entitled on their record. Do not disclose X's PIA or retirement benefit rate (except to the widow), since that information would allow the requester to calculate the widow's benefit rate, thus invading her privacy. If the two were living together at X's death, do not disclose their address to another party, since that information also pertains to the widow.\n\nNOTE: The requester may provide consent from the living person to receive the deceaseds information if that information is in the living persons own record.\n\n4. \nSS-5 of deceased individual\n\nMembers of the public frequently request a copy of a deceased individuals application for an SSN (Form SS-5). We cannot provide the parents first and last names unless we have proof of their deaths. A special unit in the Division of Earnings & Business Services, Office of Earnings and International Operations, Office of Central Operations, processes these requests. Send requests to:\n\nSocial Security Administration\nOEIO FOIA Workgroup\n6100 Wabash Avenue\nP.O. Box 33022\nBaltimore MD 21290-3022\n5. \nDisclosure to funeral home directors\n\nFuneral home directors may request disclosure or verification of a deceased individuals SSN. We may only provide the funeral home director the requested information if we have proof that the individual is deceased from a source other than the State.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0203315010\n\t\nGN 03315.010 - Disclosing a Deceased Individuals Information - 02/28/2024\nBatch run: 08/20/2026\nRev:02/28/2024\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "whole_sha256": "04b3afbf8c7cbf593a0a14738126649e6ca278dc339f1c008ce8b1f737ce86de"
          }
        ],
        "holds": [
          "Tax-return information remains confidential after death; GN03320.020/001 classification/procedure targets not supplied by this whole capture.",
          "The original replacement-statement classification has a separately cited source; this sequence requires that classification to be established instead of claiming this page proves it.",
          "ADAP statutory/regulatory and GN03301.040B detail remain linked authority; no automatic consent, release or vital-statistics legal finding.",
          "State death data restrictions must be read with explicit independent-proof/own-Number-Holder exceptions; no blanket source-table precedence.",
          "Person Information/iMAIN/Numident/SSD/EDR named roles are not native identity or accepted relationship adoption.",
          "SS-5 routing and acceptable proof are captured publication instructions, not tested receipt/status or an adjudication of evidence."
        ],
        "negative_QA": [
          {
            "case": "Individual died",
            "expected": "Do not release all records automatically."
          },
          {
            "case": "Tax-return information requested",
            "expected": "Do not apply a blanket death-ends-confidentiality rule."
          },
          {
            "case": "State death data only",
            "expected": "Do not disclose its existence or use it as sole proof for other records."
          },
          {
            "case": "Requester provides an obituary",
            "expected": "Do not automatically accept it without sufficient identifying information and applicable review."
          },
          {
            "case": "Parents named on deceased applicant SS-5",
            "expected": "Require proof of parents’ deaths before releasing their names."
          },
          {
            "case": "Vital-statistics law not established",
            "expected": "Do not infer the mandatory-law ADAP branch."
          },
          {
            "case": "Other ADAP request",
            "expected": "Consult PAC; do not infer consent or permission."
          },
          {
            "case": "Widow benefit rate can be derived",
            "expected": "Apply living-person privacy limits."
          },
          {
            "case": "Shared address pertains to living widow",
            "expected": "Do not infer general public release."
          },
          {
            "case": "Own-record consent not established",
            "expected": "Do not assume C.3 note applies."
          },
          {
            "case": "Funeral director request without non-State proof",
            "expected": "Do not infer C.5 release condition."
          },
          {
            "case": "Third party seeks another person State report",
            "expected": "Do not use the Number Holder own-record exception."
          },
          {
            "case": "SSD65",
            "expected": "Treat the stated range endpoint as State data."
          },
          {
            "case": "EDR shown",
            "expected": "Do not infer a non-State source merely without an SSD check result."
          },
          {
            "case": "Numident source query completed",
            "expected": "Do not claim record correction or payment reinstatement."
          },
          {
            "case": "Replacement statement tax classification unknown",
            "expected": "Keep separate classification dependency; no global non-tax assertion."
          },
          {
            "case": "Linked RM record-schema detail absent",
            "expected": "Do not infer identity or new system interface."
          },
          {
            "case": "Disclosure source conditions remain uncertain",
            "expected": "Keep action/rejoin unknown; selection grants no permission."
          }
        ]
      }
    },
    "source_reviews": {
      "ALJ12": {
        "package_sha256": "2a3d2571fe4aa5f417f6ced5fa43756d69a7877ab726bf15c8de96b1269ea546",
        "full_primary_semantic_peer_sha256": "c9783dde18d19a40ec45fee9a2fcbf4232d46a873166511f69d6173e28af37f6"
      },
      "GN7": {
        "package_sha256": "84c78132c8893fc4698ee5397321a3c47de2b971ded8962db1924e9ff068f282",
        "full_primary_semantic_peer_sha256": "9a9045746a8ed044c6d081b3bcf21d54136af99fc079fdf97c8dc97ab775c627"
      }
    },
    "root_GN_correction_peer_sha256": "901954f9bbae3207ab97b6b9f12468881ed0d6f87b0432c9fd6fe1cc1a119554",
    "public_capture_provenance": [
      {
        "url": "/service/sources/r32-ALJ12-DI12010.001-main.txt",
        "sha256": "fdbbd04550c034e1da9a257d24433d877407d9d95288fd9a0f4dadb25b2bb7c6",
        "type": "Retained browser capture; not raw HTTP"
      },
      {
        "url": "/service/sources/r32-ALJ12-DI12010.002-main.txt",
        "sha256": "b2a2752f895541a6b8a832fcf5abbd5145d64448d8efee4cba3245cc0b37bd72",
        "type": "Retained browser capture; not raw HTTP"
      },
      {
        "url": "/service/sources/r32-ALJ12-GN03103.120-main.txt",
        "sha256": "b82af3ce64f22fad52b97b6dfabf9d8361faba774f5a89642b8b318d60501e4e",
        "type": "Retained browser capture; not raw HTTP"
      },
      {
        "url": "/service/sources/r32-ALJ12-DI26535.036-main.txt",
        "sha256": "6fc82ec8575712d86f2470c7a64f3e7407238977a9c58dca4f370e4438e39af9",
        "type": "Retained browser capture; not raw HTTP"
      },
      {
        "url": "/service/sources/r32-GN7-GN03315.010-main.txt",
        "sha256": "04b3afbf8c7cbf593a0a14738126649e6ca278dc339f1c008ce8b1f737ce86de",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r32-GN7-GN03315.010-body-rendered.html.txt",
        "sha256": "2899308d19dfa5430b2f64fe1cfa0bf47ad463e3e5aba8b31d6fef325d2dd6aa",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      }
    ],
    "limits": [
      "ALJ medical-reconsideration hearing scope is separate from initial medical CDR DHO handling. Entry exceptions do not establish completed reconsideration.",
      "Undated notice-image source comparison remains held and unmapped; linked procedures, actual facts and successful rejoins remain unestablished.",
      "Disclosure remains subject to tax classification, death-proof, State-data, living-person and ADAP restrictions. Selecting a scenario does not authorize release."
    ],
    "no_native_acceptance_or_new_links": true
  },
  "r33_SSI_interpreter14": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "FOURTEEN_SELECTED_SSI_AND_INTERPRETER_SEQUENCES_SOURCE_REVIEWED_NOT_CASE_ACCEPTANCE",
    "selected_flow_count": 14,
    "checked_on": "2026-11-01",
    "packages": {
      "SSI7": {
        "flows": {
          "apply-ssi/ssi-1996-residence-temporary-absence": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-1996-residence-temporary-absence",
            "full_route": "apply-ssi/ssi-1996-residence-temporary-absence",
            "entry_conditions": [
              "The historical lawful-residence condition for August 22, 1996 is being developed and the person was temporarily outside the United States around that date.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-1996-residence-temporary-absence-source-1",
                "title": "Review historical residence and intent",
                "kind": "action",
                "actor": "FO",
                "action": "Develop residence intent separately from immigration status. An absence of less than six months without intent to abandon does not interrupt historical residence. For more than six months, the source presumes abandonment unless evidence shows intent to resume residence.",
                "conditions": [
                  "The historical lawful-residence condition for August 22, 1996 is being developed and the person was temporarily outside the United States around that date.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "B.2.a",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The exact-six-month boundary is not resolved here. This historical test does not authorize a present-day six-month absence or establish current SSI residence.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-1996-residence-temporary-absence-source-2",
                "title": "Review lawful reentry for the historical date",
                "kind": "action",
                "actor": "FO",
                "action": "If the person was outside the United States on August 22, 1996, establish that DHS would or did allow lawful reentry.",
                "conditions": [
                  "The historical lawful-residence condition for August 22, 1996 is being developed and the person was temporarily outside the United States around that date.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here.",
                  "The individual was outside the United States on the historical date."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "B.2.b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "Residency intent and lawful presence are distinct requirements, and the linked residence/evidence procedures remain separately scoped.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-1996-residence-temporary-absence-source-3",
                "title": "Obtain and verify the historical status evidence",
                "kind": "action",
                "actor": "FO",
                "action": "Ask for relevant DHS immigration documents and verify them through SAVE while developing residence evidence. D.2 distinguishes current unexpired documents effective on or before the cutoff from later current status supported by qualifying earlier-status evidence.",
                "conditions": [
                  "The historical lawful-residence condition for August 22, 1996 is being developed and the person was temporarily outside the United States around that date.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "D.1–2",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "This does not authenticate a document, decide status, or reproduce all linked DHS/SAVE/evidence rules. Historical geographic coverage does not replace current SSI payment-residence requirements.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-aged-timelimited-medical-denial-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-aged-timelimited-medical-denial-notice",
            "full_route": "apply-ssi/ssi-aged-timelimited-medical-denial-notice",
            "entry_conditions": [
              "The recipient is aged and currently eligible under the applicable seven-year category, and DDS returns an unfavorable decision in the separate medical development.",
              "This is not a claimant who needs a medical allowance for any applicable noncitizen eligibility.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-aged-timelimited-medical-denial-notice-source-1",
                "title": "Record the medical decision under the applicable case instructions",
                "kind": "action",
                "actor": "FO",
                "action": "Use the F.8 MSSICS or non-MSSICS branch to record the date and denial code of the DDS decision and receipt the medical-decision control where specified.",
                "conditions": [
                  "The recipient is aged and currently eligible under the applicable seven-year category, and DDS returns an unfavorable decision in the separate medical development.",
                  "This is not a claimant who needs a medical allowance for any applicable noncitizen eligibility.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 8.a–b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The captured source’s system instructions are not tested current operation. A separate medical denial does not itself end the currently applicable time-limited eligibility.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-timelimited-medical-denial-notice-source-2",
                "title": "Send the explanation and scoped appeal notice",
                "kind": "action",
                "actor": "FO",
                "action": "Prepare the manual SSA-L8166-U-2 Important Information notice with the medical explanation and appeal information, and mail it with the DDS Information About the Disability Decision write-up. Explain that current eligibility can continue under the present status through the applicable seven-year period.",
                "conditions": [
                  "The recipient is aged and currently eligible under the applicable seven-year category, and DDS returns an unfavorable decision in the separate medical development.",
                  "This is not a claimant who needs a medical allowance for any applicable noncitizen eligibility.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 4.c; F step 8.c",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "Other eligibility conditions still apply. No new appeal deadline, mailing duration, actual continuation or permanent-payment guarantee is inferred.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-aged-medical-allowance-time-limit-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-aged-medical-allowance-time-limit-notice",
            "full_route": "apply-ssi/ssi-aged-medical-allowance-time-limit-notice",
            "entry_conditions": [
              "The aged recipient is currently eligible under the seven-year provision, receives a favorable DDS decision, and meets the historical lawful-residence exception.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-aged-medical-allowance-time-limit-notice-source-1",
                "title": "Update the applicable medical and eligibility data",
                "kind": "action",
                "actor": "FO",
                "action": "Follow the F.7 MSSICS or non-MSSICS branch for the disability decision and appropriate multi-category eligibility information.",
                "conditions": [
                  "The aged recipient is currently eligible under the seven-year provision, receives a favorable DDS decision, and meets the historical lawful-residence exception.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 7.a–b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "No actual system input, current implementation or completed payment is established by the source description.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-medical-allowance-time-limit-notice-source-2",
                "title": "Explain why this time limit no longer applies",
                "kind": "action",
                "actor": "FO",
                "action": "If appropriate, prepare the manual SSA-L8166 Important Information notice explaining that the earlier seven-year limit no longer applies because of blindness/disability and lawful residence on August 22, 1996, assuming every other eligibility factor continues to be met.",
                "conditions": [
                  "The aged recipient is currently eligible under the seven-year provision, receives a favorable DDS decision, and meets the historical lawful-residence exception.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 7.c; B.1–2",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The medical allowance alone does not establish the historical residence, qualified status or other eligibility conditions; this is not an unconditional permanent-payment promise.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-aged-medical-required-pending-development": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-aged-medical-required-pending-development",
            "full_route": "apply-ssi/ssi-aged-medical-required-pending-development",
            "entry_conditions": [
              "The aged claimant needs a medical allowance for this noncitizen exception, cannot use an applicable seven-year category for eligibility, and presumptive blindness/disability payments are not involved.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-aged-medical-required-pending-development-source-1",
                "title": "Request the required new medical decision",
                "kind": "action",
                "actor": "FO",
                "action": "Obtain a new DDS decision for this provision rather than adopting a prior Title II disability decision for someone age 65 or older. Include the source’s Aged Alien—Blindness/Disability Alleged—Systems Limitation annotation when sending the case.",
                "conditions": [
                  "The aged claimant needs a medical allowance for this noncitizen exception, cannot use an applicable seven-year category for eligibility, and presumptive blindness/disability payments are not involved.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 12.a",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "Detailed DDS form preparation remains linked scope. This does not decide disability, eligibility or a claimant’s actual case stage.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-medical-required-pending-development-source-2",
                "title": "Develop other factors at the same time",
                "kind": "action",
                "actor": "FO",
                "action": "Do not defer nonmedical development while the medical decision is pending. Obtain and verify the immigration evidence through SAVE; store legible copies of both sides, record an ARN if present, return the original document, after receiving the SAVE response update the status code as appropriate, retain the SAVE response, and develop the other eligibility factors.",
                "conditions": [
                  "The aged claimant needs a medical allowance for this noncitizen exception, cannot use an applicable seven-year category for eligibility, and presumptive blindness/disability payments are not involved.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 12.b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The published storage/return steps are source instructions, not proof of image legibility or successful upload. Detailed SAVE and acceptable-document rules remain separate.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-medical-required-pending-development-source-3",
                "title": "Keep the case pending for the decision",
                "kind": "action",
                "actor": "FO",
                "action": "Use the applicable F.12 systems branch to establish and hold the pending record. In the MSSICS branch, do not close the event before the medical decision; the source warns that premature closure can produce an erroneous denial.",
                "conditions": [
                  "The aged claimant needs a medical allowance for this noncitizen exception, cannot use an applicable seven-year category for eligibility, and presumptive blindness/disability payments are not involved.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 12.c–d",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The non-MSSICS input is a separately listed alternative. No current native system identity, field equivalence or operational outcome is adopted.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-aged-medical-required-denial-notice": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-aged-medical-required-denial-notice",
            "full_route": "apply-ssi/ssi-aged-medical-required-denial-notice",
            "entry_conditions": [
              "The aged claimant is medically denied and needed a medical allowance for this noncitizen eligibility provision.",
              "This is distinct from an already eligible seven-year recipient whose separate medical decision is unfavorable.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-aged-medical-required-denial-notice-source-1",
                "title": "Use the scoped denial and notice-suppression branch",
                "kind": "action",
                "actor": "FO",
                "action": "Process the F.15 denial through its applicable MSSICS or non-MSSICS branch and suppress the automated denial notice as specified.",
                "conditions": [
                  "The aged claimant is medically denied and needed a medical allowance for this noncitizen eligibility provision.",
                  "This is distinct from an already eligible seven-year recipient whose separate medical decision is unfavorable.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 15.a–b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The source’s legacy input details and linked technical manuals are not independently tested here; this example does not decide an actual claim.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-medical-required-denial-notice-source-2",
                "title": "Mail the manual denial and medical attachment",
                "kind": "action",
                "actor": "FO",
                "action": "Prepare the SSA-L8030-U2 ALIEN02 manual denial using the aged-person-not-disabled paragraph, attach the DDS Information About the Disability Decision write-up, and mail both to the claimant.",
                "conditions": [
                  "The aged claimant is medically denied and needed a medical allowance for this noncitizen eligibility provision.",
                  "This is distinct from an already eligible seven-year recipient whose separate medical decision is unfavorable.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "F step 15.c; F step 12.a",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "Do not substitute the different notice/payment consequences of F.8. No mailing deadline, actual receipt or new appeal-period calculation is established.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-noncitizen-couple-staggered-decisions": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-noncitizen-couple-staggered-decisions",
            "full_route": "apply-ssi/ssi-noncitizen-couple-staggered-decisions",
            "entry_conditions": [
              "The payable member is aged and eligible without a medical decision, while the spouse under age 65 awaits a needed medical decision.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-noncitizen-couple-staggered-decisions-source-1",
                "title": "Process the currently eligible aged member",
                "kind": "action",
                "actor": "FO",
                "action": "The source permits adjudicating the eligible aged member as an individual while the spouse’s medical decision remains pending.",
                "conditions": [
                  "The payable member is aged and eligible without a medical decision, while the spouse under age 65 awaits a needed medical decision.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "G.2",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The source’s other G.3/G.4 compositions—an under-65 disabled member approved first—remain separately scoped boundary references in the original record; they are not actions under this G.2 entry condition.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-noncitizen-couple-staggered-decisions-source-2",
                "title": "Update after the spouse’s decision arrives",
                "kind": "action",
                "actor": "FO",
                "action": "When the spouse’s decision is received, follow the G.2 record transition whether it is favorable or unfavorable. Any funds actually due the spouse for an earlier period use the specified A-OTP process after the record is start dated.",
                "conditions": [
                  "The payable member is aged and eligible without a medical decision, while the spouse under age 65 awaits a needed medical decision.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here.",
                  "The needed medical decision for the spouse has been received."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "G.2",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "No favorable spouse decision, amount due or current system/computation result is assumed. Detailed record transactions remain separately scoped.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            }
          },
          "apply-ssi/ssi-aged-posteligibility-disability-review": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "ssi-aged-posteligibility-disability-review",
            "full_route": "apply-ssi/ssi-aged-posteligibility-disability-review",
            "entry_conditions": [
              "The recipient is age 65 or older, alleges blindness/disability, was lawfully residing in the United States on August 22, 1996, and is eligible under an applicable time-limited category.",
              "No applicable grandfathered category governs, AND either no medical decision was previously obtained OR the appeal period for a prior medical denial has ended.",
              "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
            ],
            "steps": [
              {
                "id": "ssi-aged-posteligibility-disability-review-source-1",
                "title": "Review one of the source’s posteligibility triggers",
                "kind": "action",
                "actor": "FO",
                "action": "Develop the provision at a scheduled or unscheduled redetermination, after contact about the end-of-seven-year suspension notice, or when the recipient asks about the time limit before that notice is sent.",
                "conditions": [
                  "The recipient is age 65 or older, alleges blindness/disability, was lawfully residing in the United States on August 22, 1996, and is eligible under an applicable time-limited category.",
                  "No applicable grandfathered category governs, AND either no medical decision was previously obtained OR the appeal period for a prior medical denial has ended.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "H.1–2",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "These are alternative review triggers, not a new filing deadline. An appeal of a time-limit suspension has separately linked continuation requirements.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-posteligibility-disability-review-source-2",
                "title": "Obtain the medical development and control the decision",
                "kind": "action",
                "actor": "FO",
                "action": "If blindness or disability is alleged, obtain the required disability forms, forward them to DDS, and establish the specified medical-decision control and systems-limitation annotation.",
                "conditions": [
                  "The recipient is age 65 or older, alleges blindness/disability, was lawfully residing in the United States on August 22, 1996, and is eligible under an applicable time-limited category.",
                  "No applicable grandfathered category governs, AND either no medical decision was previously obtained OR the appeal period for a prior medical denial has ended.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "H.3 introductory development",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The source’s internal E.1/E.1.a cross-reference labels are preserved as unresolved locator issues; no missing target text or current implementation is invented.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ]
              },
              {
                "id": "ssi-aged-posteligibility-disability-review-source-3",
                "title": "When the medical decision is favorable",
                "kind": "action",
                "actor": "FO",
                "action": "Under H.3.a, prepare the manual Important Information notice explaining the removal of the time limit subject to all other factors, and make the applicable multi-category eligibility input.",
                "conditions": [
                  "The recipient is age 65 or older, alleges blindness/disability, was lawfully residing in the United States on August 22, 1996, and is eligible under an applicable time-limited category.",
                  "No applicable grandfathered category governs, AND either no medical decision was previously obtained OR the appeal period for a prior medical denial has ended.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here.",
                  "DDS has returned a favorable medical decision and the remaining source conditions apply."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "H.3.a",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "This is the source-conditioned favorable branch, not an actual allowance or guarantee of continued payment.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ],
                "alternative_group": "medical-outcome"
              },
              {
                "id": "ssi-aged-posteligibility-disability-review-source-4",
                "title": "When the medical decision is unfavorable",
                "kind": "action",
                "actor": "FO",
                "action": "Under H.3.b, follow the scoped denial recording and prepare the manual explanation/appeal notice with the DDS write-up. Explain that current eligibility can continue under its existing status through the applicable seven-year period.",
                "conditions": [
                  "The recipient is age 65 or older, alleges blindness/disability, was lawfully residing in the United States on August 22, 1996, and is eligible under an applicable time-limited category.",
                  "No applicable grandfathered category governs, AND either no medical decision was previously obtained OR the appeal period for a prior medical denial has ended.",
                  "This particular historical-residence exception is being developed; an independently established non-time-limited exception may make this development unnecessary. No individual eligibility or immigration finding is made here.",
                  "DDS has returned an unfavorable medical decision and the scoped time-limited eligibility situation applies."
                ],
                "source": "ssialienblinddisabled1996",
                "section": "H.3.b",
                "source_context_refs": [
                  "SI00502.142:whole"
                ],
                "qualifications": [
                  "The new medical decision and current time-limited basis remain distinct; no immediate termination, actual appeal or automatic continuation is inferred.",
                  "Source-conditioned staff procedure only; selecting this example does not establish immigration status, entitlement, permission, completed action or successful rejoin."
                ],
                "alternative_group": "medical-outcome"
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source sequence does not demonstrate completion, actual payment, an appeal outcome or a successful return to the usual case path. Linked procedure and case-applicability limits remain."
              ]
            },
            "alternative_groups": [
              {
                "id": "medical-outcome",
                "label": "Different instructions for the actual returned medical decision",
                "logic": "source_conditions_determine_branch",
                "note": "These are conditional alternatives, not consecutive decisions. No outcome is selected from the illustration."
              }
            ]
          }
        },
        "original_records": {
          "apply-ssi/ssi-1996-residence-temporary-absence": {
            "id": "ssi-1996-residence-temporary-absence",
            "title": "Review an absence around August 1996 separately from current residence",
            "when": "SSA develops the historical lawful-residence condition and the claimant was temporarily outside the United States around August22,1996.",
            "you": "Explain travel dates, intent to return, maintained home ties and available immigration documents.",
            "ssa": "The field office develops residence intent and lawful presence for that historical date. An absence under six months without intent to abandon does not interrupt historical residence; over six months raises a rebuttable abandonment presumption. If outside on August22,1996, establish that DHS would or did allow lawful reentry. Staff request relevant DHS documents and verify them through SAVE, while developing residence evidence separately.",
            "route": "Field office historical-residence and immigration-document review, with DHS verification.",
            "next": "Provide available home, rent, utility or other residence evidence and ask what remains needed. Current SSI residence and physical-presence conditions still require separate review.",
            "source": "ssialienblinddisabled1996",
            "section": "B.2.a-B.2.b; D.1-D.2",
            "additional_sources": [
              {
                "source": "usresidencyevidence",
                "section": "C; D.3"
              }
            ],
            "timing": "This historical test does not authorize a current six-month absence. The exact-six-month boundary is not resolved here; no individual residence finding is made.",
            "review_status": "Live linked evidence verified; historical intent and current payment-presence rules kept distinct."
          },
          "apply-ssi/ssi-aged-timelimited-medical-denial-notice": {
            "id": "ssi-aged-timelimited-medical-denial-notice",
            "title": "Read a medical denial while current time-limited eligibility continues",
            "when": "An aged recipient currently eligible under the seven-year provision receives an unfavorable medical decision in the separate blindness/disability development.",
            "you": "Review the medical explanation and appeal instructions; tell SSA if the notice or attachment is missing.",
            "ssa": "The field office records the DDS decision and prepares a manual SSI Important Information notice, SSA-L8166-U-2, with the DDS personalized medical explanation. The notice explains that the medical denial does not affect current eligibility under the applicable time-limited status and that the initial medical decision can be appealed. Staff mail the notice and medical write-up together.",
            "route": "DDS medical explanation returned to the field office for the scoped manual notice and appeal-rights mailing.",
            "next": "Use the notice appeal instructions if you disagree. Ask staff to distinguish the medical decision from any later action at the end of the time-limited period.",
            "source": "ssialienblinddisabled1996",
            "section": "F step4.c; F step8.a-F step8.c",
            "timing": "Current eligibility may continue through the applicable seven-year period subject to other conditions. No mailing turnaround or individual continuation decision is promised.",
            "review_status": "Live scoped notice verified; does not apply to a claimant who needs medical allowance for any noncitizen eligibility."
          },
          "apply-ssi/ssi-aged-medical-allowance-time-limit-notice": {
            "id": "ssi-aged-medical-allowance-time-limit-notice",
            "title": "Receive an explanation when the noncitizen time limit is removed",
            "when": "An aged recipient currently eligible under the seven-year provision receives a favorable DDS decision and meets the historical lawful-residence exception.",
            "you": "Review the new notice and report any facts that differ from SSA records.",
            "ssa": "The field office updates the medical determination and prepares a manual SSA-L8166 SSI Important Information notice. It explains that the earlier award time limit no longer applies because the recipient was found blind or disabled and lawfully residing in the United States on August22,1996. The explanation expressly depends on all other eligibility factors continuing to be met.",
            "route": "DDS favorable decision to field office medical-record update and manual notice.",
            "next": "Keep the notice and ask SSA to explain any remaining time-limit entry or missing explanation. A medical allowance by itself does not establish every condition.",
            "source": "ssialienblinddisabled1996",
            "section": "F step7.a-step7.c; B.1-B.2",
            "timing": "The manual notice follows the favorable medical determination and applicable findings; no notice-production or payment turnaround is specified.",
            "review_status": "Live scoped procedure verified; no permanent payment guarantee or individual eligibility conclusion."
          },
          "apply-ssi/ssi-aged-medical-required-pending-development": {
            "id": "ssi-aged-medical-required-pending-development",
            "title": "Develop other evidence while the required medical decision is pending",
            "when": "An aged claimant needs a medical allowance for the noncitizen exception and presumptive blindness or disability payments are not involved.",
            "you": "Respond to medical and nonmedical evidence requests and tell SSA about missing documents.",
            "ssa": "The field office requests a new DDS disability decision for this provision rather than adopting a prior Title II disability decision for someone age65 or older. Staff simultaneously develop immigration evidence, verify current qualified status through SAVE, and review other nonmedical conditions. They return original immigration documents after storing copies. The claim remains pending until the DDS decision; premature closure can create an erroneous denial.",
            "route": "Field office nonmedical development coordinated with DDS medical review.",
            "next": "Ask which evidence is outstanding and whether the medical decision has returned. A pending medical issue does not prevent staff from developing the other factors.",
            "source": "ssialienblinddisabled1996",
            "section": "F step12.a-step12.d",
            "timing": "Development proceeds together; no DDS completion time or payment entitlement is promised.",
            "review_status": "Live scoped workflow verified; unverified screen-by-screen operational details not reproduced."
          },
          "apply-ssi/ssi-aged-medical-required-denial-notice": {
            "id": "ssi-aged-medical-required-denial-notice",
            "title": "Receive the medical explanation with a required-allowance denial",
            "when": "An aged claimant is medically denied and a medical allowance was required for the noncitizen eligibility provision.",
            "you": "Read the decision and medical attachment; contact SSA if an enclosure is missing or the stated reason is unclear.",
            "ssa": "The field office processes this scoped denial, suppresses the automated notice and prepares the manual SSA-L8030-U2 ALIEN02 denial using the aged-person-not-disabled paragraph. Staff attach the DDS Information About the Disability Decision write-up and mail both documents to the claimant.",
            "route": "DDS medical explanation to the field office for the scoped manual denial and enclosure mailing.",
            "next": "Use the decision instructions to seek review if you disagree. Ask SSA which eligibility provision was decided; the separate notice for a person already eligible under the seven-year category has different payment consequences.",
            "source": "ssialienblinddisabled1996",
            "section": "F step15.a-step15.c; F step12.a explanatory note",
            "timing": "The manual notice follows the medical decision and scoped denial processing; no mailing deadline or individual eligibility conclusion is inferred.",
            "review_status": "Live selected notice procedure verified; old screen navigation and coding not reproduced."
          },
          "apply-ssi/ssi-noncitizen-couple-staggered-decisions": {
            "id": "ssi-noncitizen-couple-staggered-decisions",
            "title": "Process the eligible member while the spouse medical decision is pending",
            "when": "In a noncitizen couple case, an aged member is eligible without a medical decision while the under65 spouse awaits one.",
            "you": "Respond to each member evidence requests and identify which decision or payment question concerns which person.",
            "ssa": "The field office can adjudicate the eligible aged member as an individual while the spouse medical decision is pending. When that decision arrives, staff update the record whether it is favorable or unfavorable and address any earlier-period amount due the spouse through the specified one-time payment process. The source also directs individual-record processing when an under65 disabled member is approved first and the other member is still awaiting a decision.",
            "route": "Field office individual/couple record coordination with DDS medical decision follow-through.",
            "next": "Ask which member is currently eligible and how SSA will review earlier months after the second decision. No spouse allowance or payment amount is assumed.",
            "source": "ssialienblinddisabled1996",
            "section": "G.2-G.4",
            "timing": "The first eligible member can be processed while the second decision is pending; no guaranteed payment date is specified.",
            "review_status": "Live scoped coordination verified; legacy record codes and computation acronym not reproduced."
          },
          "apply-ssi/ssi-aged-posteligibility-disability-review": {
            "id": "ssi-aged-posteligibility-disability-review",
            "title": "Ask about the disability exception during a time-limit review",
            "when": "A recipient age65 or older alleges blindness/disability while SSA reviews the time-limited noncitizen provision.",
            "you": "Tell SSA about the medical condition, earlier medical decisions and lawful residence on August22,1996.",
            "ssa": "The field office checks the subsection gates: applicable time-limited category, historical lawful residence, no applicable grandfathered category, and no prior medical decision or an ended appeal period for a prior denial. Staff develop the issue at scheduled or unscheduled redetermination, after contact about the suspension notice, or during an inquiry before that notice. They obtain disability forms, send them to DDS and control receipt of the decision.",
            "route": "Field office posteligibility review coordinated with DDS; an appeal of time-limit suspension has separate continuation requirements.",
            "next": "Ask which exception is being developed and which decision remains pending. Review the resulting medical explanation and notice.",
            "source": "ssialienblinddisabled1996",
            "section": "H.1-H.3 introductory development; H.3.a-H.3.b notice outcomes",
            "timing": "The inquiry can occur before the suspension notice; no medical decision deadline is specified. Appeal-period and continuation questions require their separate rules.",
            "review_status": "Live trigger/development verified; favorable/adverse notice details mapped separately in research473."
          }
        },
        "source_contexts": [
          {
            "id": "SI00502.142:whole",
            "start": 0,
            "end": 40567,
            "exact_text": "Effective Dates: 04/12/2018 - Present\nPrevious | Next\n\nTN 73 (09-26)\n\nSI 00502.142 Qualified Aliens Who Are Blind Or Disabled And Were Lawfully Residing In The U.S. On 8/22/96\nA. \nIntroduction\n\nOn 8/22/96, P.L. 104-193, the Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA) allowed qualified aliens who were lawfully residing in the U.S. on 8/22/96, and who are blind or disabled, to be eligible for Supplemental Security Income (SSI) benefits, provided all other eligibility requirements are met. The alien's immigration status and document must be verified with DHS via an online Systematic Alien Verification for Entitlements (SAVE) request in all cases, including initial claims prior to approval, redeterminations, and immigration status changes. Follow SI 00502.110 for general alien development. For verification of status with DHS via SAVE, see SI 00502.115.\n\nIMPORTANT: If a qualified alien is eligible for SSI benefits based on another exception condition without a time limit (e.g., Lawful Permanent Resident (LPR) with 40 QQs or the military service conditions), then it is not necessary to develop eligibility under the provision described in this section.\n\nThe material in this section is organized as follows:\n\nTopic\tReference\n\n\nEligibility Under the Provision\n\n\t\n\nSee SI 00502.142B.1.\n\n\n\n\nLawfully Residing in the U.S.\n\n\t\n\nSee SI 00502.142B.2.\n\n\n\n•\n\nResident of the U.S.\n\n\t\n\nSee SI 00502.142B.2.a.\n\n\n\n•\n\nLawful Presence\n\n\t\n\nSee SI 00502.142B.2.b.\n\n\n\n\nPolicy - Who is a Lawfully Present Alien?\n\n\t\n\nSee SI 00502.142C.\n\n\n\n\nProcedure - Developing Lawfully Residing in the U.S.\n\n\t\n\nSee SI 00502.142D.\n\n\n\n\nProcedure - Processing Initial Claims-Claimant is Under Age 65\n\n\t\n\nSee SI 00502.142E.\n\n\n\n•\n\nObtain Medical Decision\n\n\t\n\nSee SI 00502.142E.1.\n\n\n\n•\n\nEstablish Systems Record\n\n\t\n\nSee SI 00502.142E.2.\n\n\n\n•\n\nCase is Medically Allowed\n\n\t\n\nSee SI 00502.142E.3.\n\n\n\n•\n\nCase is Medically Denied\n\n\t\n\nSee SI 00502.142E.4.\n\n\n\n\nProcedure - Initial Claims - Claimant is age 65 or older\n\n•\n\nClaimant is eligible under time-limited category\n\n•\n\nSpecial Systems Processing Instructions for Presumptive Disability Cases\n\n•\n\nNo Alien Eligibility Possible Without Disability Allowance\n\n\t\n\nSee SI 00502.142F.\n\nStep-Action Chart\n\n\n\n\nSpecial Systems Processing Instructions for Couples Cases\n\n\t\n\nSee SI 00502.142G.\n\n\n\n\nProcedure - Processing Posteligibility Cases\n\n\t\n\nSee SI 00502.142H.\n\n\n\n•\n\nAliens for Whom Eligibility Determinations Under This Provision May Be Necessary\n\n\t\n\nSee SI 00502.142H.1.\n\n\n\n•\n\nWhen to Determine Eligibility Under This Provision\n\n\t\n\nSee SI 00502.142H.2.\n\n\n\n•\n\nDeveloping Eligibility Under this Provision\n\n\t\n\nSee SI 00502.142H.3.\n\n\n\n\nReferences\n\n\t\n\nSee SI 00502.142I.\n\nB. \nPolicy—Rules for Eligibility Under This Provision\n1. \nGeneral\n\nQualified aliens who were lawfully residing in the U.S. on 8/22/96 and who are blind or disabled can be eligible for SSI (assuming all other factors of eligibility are met) regardless of--\n\n•\n\nthe alien's age; or\n\n•\n\nwhether onset of blindness or disability occurs before, on, or after 8/22/96; or\n\n•\n\nwhen the SSI application is filed.\n\nSee SI 00502.100A.2 for a list of qualified alien categories.\n\nNOTE: This provision applies to SSI aged and non-aged qualified aliens. Qualified aliens who meet this provision's criteria do not have to meet the 40 QQs or the veteran/active duty military exceptions or the other SSI alien eligibility requirements described in SI 00502.100A.3. Also, keep in mind that all SSI claimants who file as aged individuals (or aged spouses) must establish that they are age 65 or older in order to qualify for benefits.\n\n2. \nLawfully Residing in the U.S. on 8/22/96\n\nUnder this provision, an alien was lawfully residing in the U.S. if they were a resident of the U.S. and were \"lawfully present\" as defined by PRWORA.\n\na. \nResident of the U.S.\n\nA U.S. resident is an individual who establishes residency in the U.S. with the intent to continue living within the geographic limits of the U.S.\n\nNOTE: For purposes of the alien eligibility provision described in this section, \"resident of the U.S.\" includes a resident of the continental United States, Alaska, Hawaii, Puerto Rico, Guam, or the Virgin Islands of the United States. However, keep in mind that, unless there is an exception (for example, certain children of military parents stationed abroad (SI 00501.415)), to actually receive SSI benefits an individual must be a resident of the U.S., as defined in GN 00303.700B.4, during the month of eligibility.\n\nA U.S. resident is generally physically present during the period of residency. However, a temporary absence of less than six months from the U.S. with no intention of abandoning U.S. residency does not terminate or interrupt the individual's period of U.S. residency. If the resident is absent for more than six months, we presume that U.S. residency was abandoned unless the individual presents evidence of their intent to resume U.S. residency. The residency development instructions in GN 00303.740 apply in these cases. An alien who is residing in the U.S. must also be \"lawfully present\" as explained in SI 00502.142B.2.b to be eligible under the exception condition described in this section.\n\nb. \nLawful Presence\n\nIn order to be lawfully present under this provision, the individual must also establish their lawful presence in the U.S. on 8/22/96. If the alien was temporarily outside the U.S. on that date, they must establish that the Department of Homeland Security (DHS) would or did allow their lawful reentry into the U.S. See RS 00204.025 and SI 00502.142C for who is a lawfully present alien.\n\nC. \nPolicy—Who is a Lawfully Present Alien\n\nIn accordance with RS 00204.025, the following categories of aliens meet the definition of \"lawfully present\" for SSI purposes:\n\n1. \n\nQualified Alien (SI 00502.100A.2);\n\nNOTE: Aliens who have been subjected to battery or extreme cruelty as described in SI 00502.116 are not considered to be lawfully present in the U.S. based on that status alone. Instead, use the individual's immigration status on 8/22/96 (not SSA's finding that the battery/extreme cruelty criteria are met) to determine whether they were lawfully present in the U.S. on 8/22/96 for purposes of the provision described in this section.\n\nAliens paroled under section 212(d)(5) of the Immigration and Nationality Act (INA) for less than 1 year (except for aliens paroled for deferred inspection or exclusion proceedings under section 236(a) of the INA or prosecution in the U.S. under 8 CFR 212.5(a)(3));\n\n2. \n\nAliens inspected and admitted to the U.S. and who have not violated the applicable terms of their status;\n\n3. \n\nMost legal nonimmigrant aliens, including visitors, students, fiancées of citizens, and citizens of States in the Compact of Free Association (CFA);\n\n4. \n\nAliens with a pending application for political asylum under section 208(a) of the INA, or a pending application for withholding of deportation under section 243(h) of the INA or removal withheld under section 241(b)(3) of the INA, and employment authorization has been granted and such applicants under age 14 who have had an application pending for at least 180 days; and\n\n5. \n\nAliens in the following categories permitted to remain in the U.S. under U.S. law or policy, for humanitarian or other public policy reasons:\n\na. \n\nTemporary resident status under section 210 or 245A of the INA;\n\nb. \n\nTemporary Protected Status under section 244A of the INA;\n\nc. \n\nIndividuals from Cuba or Haiti who meet the requirements of P.L. 99-603, section 202(b) as amended (IRCA). These individuals may or may not be qualified alien “Cuban and Haitian entrants” as defined in the Refugee Education Assistance Act of 1980. See SI 00502.108F.2.\n\nd. \n\nFamily Unity beneficiary status under section 301 of P.L. 101-649, as amended;\n\ne. \n\nDeferred Enforced Departure status under a decision made by the President;\n\nf. \n\nDeferred action status under DHS Operations Instructions at OI 242.1(a)(22); and\n\ng. \n\nSpouses and children of U.S. citizens whose visa petitions have been approved and who have pending applications for adjustment of status.\n\nNOTE: \n\nAny alien who had qualified alien status on 8/22/96 and was residing in the U.S. meets the \"lawfully residing\" criteria.\n\nIMPORTANT: An alien who did not have qualified alien status on 8/22/96 but who was \"lawfully residing\" on 8/22/96 may be eligible under this provision if they are blind or disabled and is a qualified alien at the time of application for benefits.\n\nIMPORTANT: For purposes of this provision, a determination that an individual is ineligible for SSI benefits due to absence from the U.S. (N03) (as explained in SI 00501.410) does not preclude a finding of lawful presence in the U.S.\n\nEXAMPLE: An LPR alien leaves the U.S. in 8/96 and returns in 4/97. They are readmitted to the U.S. as LPR, and apply for SSI disability in 5/97 but does not have 40 QQs. They submit convincing evidence that they did not intend to abandon their U.S residence during the period of absence from the U.S.--rent receipts for their apartment for the period of absence. The field office (FO) confirms that the individual was lawfully present in the U.S. on 8/22/96 (that is, DHS did not revoke LPR status) based on an adjustment date before 8/22/96 on DHS Form I-551. The FO makes a determination of U.S. residency (per GN 00303.740C). If the FO determines that the individual did not abandon U.S. residency and was in lawful presence status on 8/22/96, the alien may be eligible for SSI if they are determined to be disabled.\n\nFor development of lawful presence in the U.S., follow the instructions in SI 00502.142D in this section.\n\nD. \nProcedure - Developing Lawfully Residing in the U.S.\n1. \nObtain Allegation of U.S. Residence\n\nAsk the individual if they were lawfully residing in the U.S. on 8/22/96. If so, request DHS documents showing the individual's immigration status for that date. Verify the DHS document via SAVE. Develop residence under SI 00502.142B.2.a.\n\nWe base the determination of whether an alien meets the lawful presence requirements on documents issued by DHS and verified by an online SAVE request. Follow the procedures in the next two subsections to verify lawful presence on or before 8/22/96.\n\n2. \nVerifying Lawful Presence Based on Individual's Immigration Documents\n\nIf a qualified alien was a U.S. resident on 8/22/96 and has current (unexpired) immigration documents that were effective on or before 8/22/96, the alien was lawfully present in the U.S. on 8/22/96 and meets the \"lawfully residing in the U.S. on 8/22/96\" requirement. Reverify the individual's immigration status via on online SAVE request.\n\nA qualified alien who was a U.S. resident on 8/22/96, and whose current alien status was granted after 8/22/96, may be able to provide a document (for example, a passport with an I-94 stamp) that shows that:\n\n•\n\nthe alien was in an earlier status in one of the categories listed in SI 00502.142B.2; and\n\n•\n\nthe earlier status was granted before 8/22/96.\n\nIf such a document conforms to the description in RS 00204.025B and appears authentic, it establishes lawful presence. Reverify the immigration document via an online SAVE request.\n\nSee RM 10214.100 through RM 10214.170 and SI 00502.115 for immigration information available through the SAVE program.\n\nE. \nProcedure - Processing Initial Claim for Claimant Under Age 65\n1. \nObtain Medical Decision\n\nComplete all necessary disability forms and forward them to the Disability Determination Services (DDS). If appropriate, make a presumptive disability determination (DI 11055.230 and DI 11055.240). Since the claimant is under age 65, SSI eligibility cannot be determined until a disability decision is made.\n\nNOTE: If the individual is under age 65 and receiving Title II benefits based on a (prior) determination that the individual is disabled, add the \"Potential Collateral Estoppel Apply\" flag in EDCS and request a disability determination from the DDS.\n\n2. \nEstablish Systems Record\n\nFollow current systems instructions pertaining to individuals under age 65 who are filing for SSI based on blindness or disability. Routine processing can be used for both MSSICS and non-MSSICS claims effective 5/11/98, with the following exception: Do not close the MSSICS event prior to receipt of the DDS decision.\n\nIMPORTANT: Leave the case in H80. Otherwise, MSSICS will build an erroneous N13 denial.\n\n3. \nCase is Medically Allowed\n\nFollow current update procedures if an allowance is returned. MSSICS will process these cases correctly once the Disability Clearance page is completed.\n\n4. \nCase is Medically Denied\n\nIf the case is medically denied, the DDS will release the medical denial notice and post the medical denial code to the Supplemental Security Record (SSR). If the denial is not posted by the DDS, the medical denial code can be keyed into the Denial Code option on the Adjudicative Decision (DADJ) screen (over-key the systems-generated N13 denial).\n\nIMPORTANT: An individual under age 65 must be blind or disabled in order to receive SSI. If the DDS determines the individual is neither blind nor disabled, the individual is ineligible for SSI-based on medical reasons and irrespective of alien status.\n\nF. \nProcedure - Processing Initial Claim for Claimant Age 65 or Older\n\nUse the following Step-Action chart to determine what development and adjudicative actions are necessary for aged aliens who are seeking eligibility under the condition for qualified aliens who are blind/disabled and were lawfully residing in the U.S. on 8/22/96. This chart includes procedures for aged aliens who--\n\n•\n\nCan be paid under the 7-year time-limited provision,\n\n•\n\nNeed a medical allowance to be eligible,\n\n•\n\nMeet the requirements for payments based on presumptive disability/blindness.\n\nSee SI 00502.142F for special procedures for handling aged couples cases under this provision. Refer to SI 00502.142G for the procedure for post-eligibility cases.\n\n \n\nStep\tAction\n\n\n1\n\n\t\n\nDoes the aged alien claimant allege that they were lawfully residing in the U.S. on 8/22/96 or that they entered the U.S. before 8/22/96?\n\n•\n\nIf yes, continue with Step 2.\n\n•\n\nIf, no, STOP. Eligibility is not possible under the exception condition for qualified aliens who are blind/disabled and were lawfully residing in the U.S. on 8/22/96.\n\n\n\n\n2\n\n\t\n\nIs the aged alien claimant potentially eligible under a time-limited category (e.g., refugee, asylee, etc.) in accordance with SI 00502.106B?\n\n•\n\nIf yes, continue with Step 3.\n\n•\n\nIf no, skip to Step 9.\n\n\n\n\n3\n\n\t\n\nDid the alien submit acceptable documentary evidence, verified via an online SAVE request, that proves they are now in time-limited alien category, or, if currently LPR, was previously in a time-limited category? (See SI 00502.130 for acceptable documentary evidence.)\n\n•\n\nIf yes, continue with Step 4.\n\n•\n\nIf no, obtain documentary evidence of immigration status in accordance with SI 00501.130. Scan legible copies of both sides of the immigration document into the electronic folder (e.g., Evidence Portal, eView). If the document includes an Alien Registration Number (ARN or A#), enter the ARN in Person Information. Return the immigration document to the claimant. After receiving the SAVE response, update the status code on the record as appropriate and store a copy of the SAVE response in the electronic folder. Once the immigration status has been verified via SAVE, continue developing other eligibility requirements, as appropriate.\n\nVerify the document via online SAVE request, per SI 00502.115.\n\nContinue with step 4.\n\n\n\n\n4\n\n\t\n\nIf the aged alien claimant is potentially eligible for SSI because they meet one of time limited categories based on documentary evidence and DHS verification via SAVE, take the following actions:\n\na. Adjudicate the application as an aged claim; and\n\nb. If the aged alien claimant alleges disability/blindness, establish the systems record as follows:\n\n•\n\nAnswer the appropriate disability/blindness questions on the Additional Client Data (ACLD) screen in MSSICS with “Y.”\n\n•\n\nMSSICS will build the type of claim as an Aged Individual (AI).\n\n•\n\nThe Development Worksheet page will control the receipt of the DDS decision.\n\n•\n\nSend to the SSR via BTS (DSSR) and close the event. Payments will begin under the applicable time-limited eligibility category.\n\nNOTE: \n\nThe SSR can reflect only one alien eligibility (AER) code at a time (SM 01005.642). The record of a refugee whose eligibility is limited to seven years (AR code = \"F”) will show an AER code “1.” The record of an alien whose deportation or removal is being withheld (AR = \"J”) will show an AER code “2.” For aged aliens with eligibility limited to seven years, the system will automatically build an AER code “8” (“aged alien requiring disability decision”) only for asylees (AR = \"L”), Amerasian immigrants (AR = \"3”), and Cuban/Haitian Entrants (AR = \"X”) who allege being blind or disabled.\n\nc. Obtain the medical determination on a post-adjudicative basis using the following guidelines:\n\n•\n\nNOTE: If the individual who is age 65 or older is receiving Title II benefits, do not adopt a prior Title II disability determination (if one was made in the case). Instead, obtain a new disability decision for purposes of establishing alien eligibility under the provision for blind/disabled qualified aliens who were lawfully residing in the U.S. on 8/22/96.\n\n•\n\nWhen sending the claim to the DDS for a medical decision, include the following notation in the “Remarks” portion of the “Title II/Title XVI Information” screen in MSDCT or SSA-831-U3: “Title XVI Aged Alien – Blindness/Disability Alleged – Systems Limitation.” Refer to instructions in DI 11055.130 for preparing Form SSA-831-U3 (Disability Determination and Transmittal).\n\nIMPORTANT: When the Aged Alien “System Limitation” annotation is included on the SSA-831-U3 and the DDS determines the individual is neither blind nor disabled, the DDS will prepare a write-up entitled “Information About the Disability Decision” that will provide the individual with a personalized explanation of the medical decision their case. The DDS will place the write-up in the medical folder and return the folder to the FO.\n\nd. Continue with Step 5\n\n\n\n\n5\n\n\t\n\nAfter the initial claim based on the 7-year provision has processed, has the medical determination for the aged alien been received?\n\n•\n\nIf yes, continue with step 6.\n\n•\n\nIf no, follow up on status of pending medical determination. When determination has been received, continue with step 6.\n\n\n\n\n6\n\n\t\n\nWas the aged alien medically allowed by DDS?\n\n•\n\nIf yes, continue with Step 7.\n\n•\n\nIf no, skip to Step 8.\n\n\n\n\n7\n\n\t\n\nProcess medical allowance for aged alien who is currently eligible based on 7-year provision as follows (post-entitlement):\n\na. If MSSICS case, input as follows:\n\n•\n\nUpdate by establishing a “STAND ALONE PE EVENT.”\n\n•\n\nComplete the Disability Clearance page, including the appropriate Multi-category Eligibility Code.\n\n•\n\nSend to the SSR via BTS (DSSR) and close the event. This will build the transaction that will establish the multi-category code, as well as other disability data, on the SSR.\n\nb. If non-MSSICS case, input as follows:\n\nTransmit an SSA-1719B with the appropriate disability data per SM 01301.605 (Multi-category, or “CM” field) and SM 01305.855 (Date of Onset field).\n\nc. Prepare Manual Notice for MSSICS and Non-MSSICS cases as follows:\n\nPrepare a manual SSA-L8166, “SSI Important Information,” using the Document Processing System (DPS) if appropriate. Explain in the notice that:\n\n•\n\nAlthough the prior notice (initial claim award) indicated that the individual’s eligibility was limited to seven years, the individual is now eligible to receive SSI benefits without a time limit; (assuming all other factors of eligibility continue to be met); and\n\n•\n\nThis is the case because the individual has been determined to be blind or disabled and was lawfully residing in the U.S. on 8/22/96.\n\nSTOP! No further action is necessary.\n\n\n\n\n8\n\n\t\n\nProcess medical denial for aged alien who is currently eligible based on 7-year provision as follows (post-entitlement):\n\na. If MSSICS case, input as follows:\n\n•\n\nUpdate MSSICS by establishing a “STAND ALONE PE EVENT.”\n\n•\n\nRecord in SSR Remarks (CRMK) the date and denial code of the DDS decision.\n\n•\n\nReceipt the Development Worksheet page for the medical decision.\n\nb. If non-MSSICS case, input as follows:\n\n•\n\nTransmit the date and denial code of the DDS decision via SSA-1719B in the Remarks field.\n\nNOTE: No other systems input is needed. The aged alien recipient’s SSI benefits will be suspended (N13) when the 7-year period expires, assuming the alien coding on the record shows no basis for eligibility past the 7-year period.\n\nc. Prepare a manual notice for both MSSICS and Non-MSSICS cases as follows:\n\n•\n\nUse an SSA-L8166-U-2, “SSI Important Information” from DPS.\n\n•\n\nInclude the following special language in the notice:\n\n“We looked at your claim to see if you were disabled under our rules. We have decided that you are not disabled under our rules. Detailed information about our decision is shown on the attachment called “Information About the Disability Decision.” If you disagree with the disability decision, please read the information later in this notice about filing an appeal.”\n\n•\n\nExplain in the SSA-L8166 that the recipient’s current eligibility is not affected by the medical denial and can continue based on their current alien status through the end of the applicable 7-year period.\n\n•\n\nMail the notice, along with the DDS write-up entitled “Information About the Disability Decision” (see “IMPORTANT” in Step 5c) to the aged alien recipient.\n\n•\n\nSince the medical decision is an initial determination, the decision is appealable. The DPS version of the SSA-L8166 has preprinted appeal rights.\n\nSTOP! No further action is necessary.\n\n\n\n\n9\n\n\t\n\nFor aged alien claimant where alien eligibility is not possible without disability allowance (i.e., alien cannot be eligible based on status in a 7-year category):\n\nIs the aged alien presumptively blind or disabled in accordance with the lists of impairment categories in DI 23535.010. (FO is authorized to make PD/PB decision) or DI 23535.010B. (DDS is authorized to make a PD/PB decision)?\n\n•\n\nIf yes, continue with Step 10.\n\n•\n\nIf no, skip to Step 12.\n\nNOTE: In general, an SSI claimant may receive six months of payments before the final determination of disability or blindness is made if\n\n•\n\nThey are determined to be presumptively disabled or blind; and\n\n•\n\nThey meet all other non-disability eligibility requirements.\n\n\n\n\n10\n\n\t\n\nFor aged alien who meets presumptive disability or blindness impairment from Step 9:\n\nDoes the aged alien meet all of the non-disability eligibility requirements?\n\n•\n\nIf yes, continue with Step 11.\n\n•\n\nIf no, skip to Step 12.\n\nIMPORTANT: For the purpose of determining whether an aged alien can get PD or PB payments, consider the aged alien to meet all of the non-disability eligibility requirements” if—\n\n•\n\nThey are currently a qualified alien based on appropriate documentary evidence of alien status (SI 00502.130) and DHS verification (if required in accordance with SI 00502.115); and\n\n•\n\nDHS verified that the aged alien was lawfully residing in the U.S. on 8/22/96; and\n\n•\n\nThe aged alien meets all of the other non-disability factors of eligibility (e.g., income, resources, residency, etc.).\n\nNOTE: Place the case in H80 until development for all factors is complete.\n\n\n\n\n11\n\n\t\n\nAged alien who needs medical allowance to be eligible meets the requirements for payment based on presumptive disability/blindness:\n\na. If MSSICS case:\n\n•\n\nAnswer the appropriate disability/blindness question on the Additional Client Data (ACLD) screen.\n\n•\n\nComplete the Disability page with the \"Presumptive disability or blindness checkbox\" selected for Presumptive Disability and the appropriate Presumptive Onset Date.\n\n•\n\nComplete the Adjudicative Decision (DADJ) screen, send to the SSR via BTS (DSSR), and close the event.\n\nb. If non-MSSICS case, code the SSA-450SI input as follows:\n\n•\n\nTP of “AI” for age 65 or older;\n\n•\n\nCM (if Aged);\n\n•\n\nThe appropriate AR (SM 01005.632), AQ (SM 01005.642), and ZX (SM 01005.645) fields;\n\n•\n\nInput a “DO” (Date of Onset) with “P” for presumptive disability;\n\n•\n\nOther necessary fields.\n\nSTOP! No further action is necessary.\n\n\n\n\n12\n\n\t\n\nTake the following actions if alien eligibility is not possible without a disability allowance and presumptive disability/blindness is not involved:\n\na. Obtain medical decision according to the following guidelines:\n\nNOTE: If the individual who is age 65 or older is receiving Title II benefits, do not adopt a prior Title II disability determination (if one was made in the case). Instead, obtain a new disability decision for purposes of the provision described in this section.\n\n•\n\nWhen sending the claim to the DDS for a medical decision, include the following notation in the “Remarks” portion of the “Title II/Title XVI Information” screen in MSDCT or SSA-831-U3: “Title XVI Aged Alien – Blindness/Disability Alleged – Systems Limitation.” Refer to instructions in DI 11055.130 for preparing Form SSA-831-U3.\n\nNOTE: When this annotation is included on the SSA-831-U3 and the DDS determines the individual is neither blind nor disabled, the DDS will prepare a write-up entitled “Information About the Disability Decision” that will provide the individual with a personalized explanation of the medical decision in their case. The DDS will place the write-up in the medical folder and return the folder to the FO.\n\nb. Undertake simultaneous development of non-disability factors of eligibility:\n\n•\n\nObtain documentary evidence of immigration status in accordance with SI 00501.130 and verify the immigration status via SAVE. Scan legible copies of both sides of the immigration document into the electronic folder (e.g., Evidence Portal, eView). If the document includes an Alien Registration Number (ARN or A#), enter the ARN in Person Information. Return the immigration document to the claimant. After receiving the SAVE response, update the status code on the record as appropriate and store a copy of the SAVE response in the electronic folder. Once the immigration status has been verified via SAVE, continue developing other eligibility requirements, as appropriate.\n\n•\n\nVerify current qualified alien status via an online SAVE request, per SI 00502.115.\n\n•\n\nDevelop whether the claimant meets all of the other non-disability factors of eligibility (e.g., income, resources, residency, etc.).\n\n•\n\nDo not defer development of the non-disability factors of eligibility in an aged alien’s case while the medical decision is pending.\n\nc. If MSSICS, establish the systems record as follows:\n\n•\n\nAnswer the appropriate DISABLED/BLIND question on the Additional Client Data (ACLD) screen with “Y.”\n\n•\n\nComplete the Disability page and other pages in the SSI system.\n\n•\n\nBuild the SSR but do not close the event. (If you close the event before a medical decision is posted, MSSICS will build an erroneous N13 denial.)\n\n•\n\nMSSICS will set up the case as an Aged Individual (AI) in H80 status.\n\n•\n\nMSSICS will automatically build the AER code of “8” (“aged alien requiring a disability determination”) on the SSR.\n\n•\n\nHold the case until the disability decision is returned from the DDS.\n\nd. If non-MSSICS case, establish the systems record as follows:\n\n•\n\nComplete the SSA-450SI as usual, including TP of “AI,” AQ with code “8,” and PS of “H80.”\n\n•\n\nDo not include the DO, SA, or CM fields\n\nContinue with Step 13.\n\n\n\n\n13\n\n\t\n\nUpon receipt of the medical decision from the DDS:\n\nWas the aged alien medically allowed by DDS?\n\n•\n\nIf yes, continue with Step 14.\n\n•\n\nIf no, skip to Step 15.\n\n\n\n\n14\n\n\t\n\nFor aged alien claimant who was medically allowed, and medical allowance is needed for eligibility, do systems input as follows:\n\na. If MSSICS case:\n\n•\n\nUpdate the existing MSSICS pending file with any new data.\n\n•\n\nComplete the Disability Clearance page if the DDS decision is not already recorded there, including the appropriate Multi-category Eligibility Code.\n\n•\n\nSend to the SSR via BTS (DSSR) and close the event.\n\nb. If non-MSSICS case, transmit an SSA-450SI with:\n\n•\n\nDLPS (to delete H80); and\n\n•\n\nDate of onset (SM 01305.855), medical data (SM 01305.900), and multi-category code (SM 01301.605).\n\nSTOP! No further action is necessary.\n\n\n\n\n15\n\n\t\n\nFor aged alien claimant who was medically denied, and a medical allowance was needed for eligibility, take the following actions to process the N13 denial:\n\na. If MSSICS case:\n\n•\n\nClose the open event on the Build SSR (DSSR) screen.\n\n•\n\nSuppress the automated denial notice via the Update Notice Suppression (UNSP) in Direct SSR Update. (See instructions in MS 00302.018 for completion of the UNSP screen).\n\n•\n\nSince no information was entered on the Disability Clearance page, MSSICS will build the N13 denial on the DADJ.\n\nb. If non-MSSICS case:\n\n•\n\nTransmit a PR9 with DS N13.\n\n•\n\nSuppress the automated denial notice (NP field).\n\nc. Prepare a manual (N13) denial notice for both MSSICS and non-MSSICS cases using DPS as follows:\n\n•\n\nComplete the client information, then click “Document Selection” in the left-hand navigation window.\n\n•\n\nSearch for the “SSA-L8030-U2 – ALIEN02 – MANUAL DENIAL – NOT ELIGIBLE ALIEN” or select “Initial Claims” and navigate to the notice.\n\n•\n\nWhen prompted, select the paragraph designated as “AGED PERSON DENIED – NOT DISABLED.”\n\n•\n\nFrom the “Group Selection” screen select “enclosure” and attach the DDS write-up entitled “Information About the Disability Decision” (see “IMPORTANT” under Step 5c of this table) to the notice.\n\n•\n\nMail the notice and the write-up to the claimant.\n\nSTOP! No further action is necessary.\n\n \n\nG. \nProcedure—Special Systems Processing Instructions for Couples Cases\n\nIf both members of the couple cannot be adjudicated on the same day, then the configuration of the claim dictates the processing path required:\n\n1. \nBoth Members Are Aged and Both Require Medical Decisions\na. \nAged Couple: Initial Application\n\nInput the case according to the following chart:\n\nMSSICS\tNon-MSSICS\n\n•\n\nComplete all screens as usual for aged alien couple.\n\n•\n\nSend to the SSR but do not close the event. (Closing the event will place the case in N13 as a denial) which is not appropriate.\n\n•\n\nThe system will establish the couple record with PSY of H80 (H80 means that an issue is pending).\n\n\t\n\nComplete the two SSA-450SI's with--\n\n•\n\nTP of AI for the aged individual and AS for the aged spouse,\n\n•\n\nAQ with code \"8\" for both, and\n\n•\n\nPS H80.\n\n•\n\nInclude the “DO,” “SA,” and “CM” fields.\n\nSee SM 01005.140 for the “DO” coding,\n\nSM 01005.220 for the “SA” coding, and SM 01005.330 for the “CM” coding.\n\nb. \nAged Couple: One Member of Couple is Determined to Be Blind/Disabled—Initial Allowance\n\nUpon receipt of the allowance for the payable spouse:\n\n•\n\nT50 the couple record, since the system cannot perform a Special Routine Eliminating Waiting (SREW) computation for an aged couple. One member of the couple would be in C01 status while the other is in H-80. See SM 01701.005 and SM 02101.035 for more information about the SREW computation.\n\n•\n\nManually clear the MSSICS claim per MS 04404.011, if needed.\n\n•\n\nEstablish an eligible AI with an ineligible spouse (XS) record via 450S input. DO NOT Start Date.\n\n•\n\nInclude AQ \"8\" (SM 01005.642) and the appropriate CM code for “AI” (SM 01005.330).\n\n•\n\nFollow subsection SI 00502.142G.1c or SI 00502.142G.1.d once the decision is received for the waiting spouse.\n\nc. \nAged Couple: Claimant in Current Pay - Favorable DDS Decision Received for “Ineligible Spouse” - Post Action\n\nTake the following actions if the ineligible aged spouse is later determined to be blind/disabled, and is thus eligible:\n\n​\t​\n\n\nMSSICS\n\n\t\n\nNon-MSSICS\n\n\n\n•\n\nSeed the record (AI/IS) into MSSICS.\n\n•\n\nAnswer all questions in MSSICS for the ineligible spouse.\n\n•\n\nComplete the Disability Clearance Page for the ineligible spouse.\n\n•\n\nMSSICS will set the record up and correctly pay as an eligible couple.\n\n\t\n•\n\nT33 the individual with ineligible spouse (AI/IS) record.\n\n•\n\nStart date a couple (AI/AS) record as an allowed couple.\n\n \n\nd. \nAged Couple: Unfavorable DDS Decision Received for Ineligible Spouse—Ineligible Spouse Not Blind/Disabled—Post Action\n\nIf the spouse is medically denied and is therefore an ineligible alien, take the following actions:\n\n•\n\nSeed the aged individual with ineligible spouse (AI/XS) record into MSSICS if not already in MSSICS.\n\n•\n\nProcess the denial for the ineligible spouse through MSSICS. MSSICS will correctly build the N13 denial.\n\n•\n\nRecord in \"Remarks\" on the SSR the date and denial code of the DDS decision for the ineligible spouse.\n\n•\n\nCAUTION: Do not overkey the N13 denial coding in this situation.\n\n•\n\nSDSP does not need to be in the first position. This entry must be present at the time the SD record is initially established to get workload credit.\n\n2. \nPayable Member is Aged and Eligible Without a Medical Decision, Needed Medical Decision for Spouse Under 65 is Pending\n\nAdjudicate the aged alien as an individual and T33/SD the record when the disability decision is received for the spouse, regardless of whether it is a denial or approval.  Once the record is start dated, any funds due the spouse for a prior period will need to be paid by A-OTP. The aged member can be adjudicated as an allowance while the disability decision is pending for the spouse. This will result in a SREW computation.\n\n3. \nDisabled Member (Under Age 65) Approved First and Aged Member Still Awaiting Medical Decision\n\nDue to systems limitations with alien cases, set up record as an individual to pay the person currently eligible and then start dated once a decision is received for the second party.\n\n4. \nBoth Members Disabled (and Under Age 65)\n\nDue to systems limitations with alien cases, set up record as an individual to pay the person currently eligible and then start dated once a decision is received for the second party.\n\nH. \nProcedure - Processing Posteligibility Cases\n1. \nAliens For Whom Eligibility Determinations Under This Provision May Be Necessary\n\nConsider eligibility under this provision if an alien age 65 or older alleges being blind or disabled and:\n\n•\n\nthe alien is not a \"grandfathered\" alien (SI 00502.150 and SI 00502.153);\n\n•\n\nthe alien was lawfully residing in the U.S. on 8/22/96 (SI 00502.142B);\n\n•\n\nthe alien is eligible under one of the time-limited categories described in SI 00502.106 (for example, is a refugee or asylee); and\n\n•\n\nno medical decision was previously obtained in the case, or the appeal period for a prior medical denial has ended.\n\n2. \nWhen to Determine Eligibility Under This Provision\n\nDetermine eligibility under this provision:\n\n•\n\nAt the time a scheduled or unscheduled redetermination is conducted; or\n\n•\n\nWhen the recipient contacts SSA after receiving the notice to suspend benefits at the end of the 7-year eligibility period. (See SI 00502.106C.3 for Goldberg-Kelly procedures for aged aliens who allege disability or blindness in connection with an appeal of the suspension of benefits under the 7-year rule); or\n\n•\n\nWhen the recipient contacts SSA inquiring about the 7-year time limit before the NPA for the time-limited suspension is sent.\n\n3. \nDeveloping Eligibility Under this Provision\n\nAsk the individual whether they are blind or disabled. If blindness or disability is alleged, obtain necessary disability forms and forward the forms to the DDS for a medical decision. Follow the applicable systems instructions in SI 00502.142E.1 to input the blindness/disability allegation and establish a systems control for the disability decision.\n\nNOTE: When the instructions in SI 00502.142E.1 are followed, the system will automatically post AER code \"8\" to the record. This will ensure that the FO gets workload credit for the disability portion of the claim.\n\nRefer to instructions in DI 11055.130 for preparing Form SSA-831-U3. Include the following notation in \"Remarks\" on the SSA-831-U3: \"Title XVI Alien -- Blindness/Disability Alleged -- Systems Limitation.\" (See \"IMPORTANT\" in SI 00502.142E.1.a. regarding DDS actions when the SSA-831-U3 is annotated in this way.)\n\na. \nCase is Medically Allowed\n•\n\nIssue the notice.\n\nManually prepare the notice, “SSI Important Information,\" using the DPS. Explain that—\n\nAlthough the prior (initial claim award) notice indicated that the individual's eligibility was limited to seven years, the individual is now eligible to receive SSI benefits without a time limit (assuming all other factors of eligibility continue to be met), and\n\nThis is the case because the individual is blind or disabled and was lawfully residing in the U.S. on 8/22/96.\n\n•\n\nMake Systems Input.\n\nIf the case is medically allowed, leave the record as an AI and add the multi-category code (SM 01005.330 or SM 01301.605) to the SSR. The presence of the multi-category code will result in continued eligibility beyond the \"7-year\" eligibility period.\n\nb. \nCase is Medically Denied\n•\n\nSystems Data\n\nDisability data will be built, as appropriate, on aged alien records in the DISB segment of the SSR. These cases must be denied N13 either through MSSICS or via manual input because the requirements in SI 00502.142B.1 are not met.\n\n•\n\nIssue the notice\n\nManually prepare the notice using the DPS. Include the following language in the notice:\n\n\"We looked at your claim to see if you were disabled under our rules. We have decided that you are not disabled under our rules. Detailed information about our decision is shown on the attachment called \"Information About the Disability Decision.\" If you disagree with the disability decision, please read the information later in this notice about filing an appeal.\"\n\nAlso explain in the notice that the recipient's eligibility can continue -- based on their current alien status -- through the end of the applicable 7-year period. Mail the notice, along with the DDS write-up entitled \"Information About the Disability Decision\" (see \"IMPORTANT\" in SI 00502.142E.1.a) to the individual.\n\nSince the medical decision is an initial determination, the decision is appealable. The DPS version of the notice has preprinted appeal rights.\n\nI. \nReferences\n•\n\nBasic SSI Alien Eligibility Requirements, SI 00502.100\n\n•\n\nExemption from Alien Provisions for Certain Noncitizen Indians, SI 00502.105\n\n•\n\nTime-Limited Eligibility for Certain Aliens, SI 00502.106\n\n•\n\nGoldberg-Kelly payments for aged aliens who allege disability/blindness in connection with an appeal of the suspension under the 7-year rule, SI 00502.106C.3.\n\n•\n\nGeneral Alien Development, SI 00502.110\n\n•\n\nVerification of Alien Eligibility with the Department of Homeland Security (DHS), SI 00502.115\n\n•\n\n\"Deemed Qualified Alien\" Status Based on Battery or Extreme Cruelty By A Family Member, SI 00502.116\n\n•\n\nEligibility on the Basis of Receiving SSI Benefits on an Application Filed Before January 1, 1979, SI 00502.120\n\n•\n\nDocumentary Evidence of Qualified Alien Status, SI 00502.130\n\n•\n\nLPR with 40 Qualifying Quarters of Earnings, SI 00502.135\n\n•\n\nVeteran or Active Duty Member of the Armed Forces, a Spouse, or a Dependent Child, SI 00502.140\n\n•\n\nDevelopment of Marital Relationships, SI 00502.145\n\n•\n\nQualified Aliens Receiving Benefits on 8/22/96 (Balanced Budget Act of 1997, P.L. 105-33), SI 00502.150\n\n•\n\nReadjudication of N13 Denials That Were Based on Alien Eligibility Law in Effect Prior To 8/5/97, SI 00502.152\n\n•\n\nSSI Eligibility for Nonqualified Aliens Who Were Receiving SSI on 8/22/96 - 1998 \"Grandfathering\" Legislation, SI 00502.153\n\n•\n\nIndividuals Who Received Informal Denials Based on Alien Eligibility Law in Effect Prior to 8/5/97, SI 00502.158\n\n•\n\nDue Process Rights under the Goldberg-Kelly ruling, SI 02301.300B.2\n\n•\n\nCitizenship/Alien Status, MS 08108.007 for instructions on completing the Alien Status page and SM 01005.630 for instructions on completing the AR field when an 450SI input is transmitted.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0500502142\n\t\nSI 00502.142 - Qualified Aliens Who Are Blind Or Disabled And Were Lawfully Residing In The U.S. On 8/22/96 - 04/12/2018\nBatch run: 10/29/2026\nRev:04/12/2018\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "whole_sha256": "7aff85a356bdf738661448a92fad1c7280493c92b02c1f374206215d93fb127b"
          }
        ],
        "holds": [
          "All qualified-status, lawful-presence/residence, blindness/disability and other eligibility findings require their source-specific evidence; no individual finding is made. Linked statutory, SAVE, document and residence targets remain separately scoped.",
          "Historical residence includes different geographic/absence considerations from current SSI payment residence; exactly six months is not resolved by the less-than/more-than wording.",
          "Publisher internal locators are not silently repaired: F introduction labels couples/posteligibility differently from actual G/H; F.8/F.15 write-up references point to Step5c while substantive annotation appears in F.4c/F.12a; H.3 cites E.1.a not present as a matching subsection.",
          "MSSICS/SSR/EDCS/DPS/AER and named screens/codes are captured publication descriptions, not current operational testing, aliases or adopted native identities.",
          "G.2 aged-payable/under-65-spouse composition is modeled; G.3/G.4 different compositions in the original record remain boundary references rather than actions under incompatible G.2 predicates.",
          "No current QQ rate, eligibility determination, time-limit payment guarantee, appeal deadline or successful case rejoin is supplied."
        ],
        "negative_QA": [
          {
            "case": "An independently established unlimited exception applies",
            "expected": "Do not force historical-residence/disability development merely for this example."
          },
          {
            "case": "Historical absence exactly six months",
            "expected": "Do not choose a presumption not stated by the source."
          },
          {
            "case": "Historical residence established",
            "expected": "Do not infer present SSI payment-residence requirements met."
          },
          {
            "case": "Outside United States on historical date",
            "expected": "Review lawful reentry separately from residence intent."
          },
          {
            "case": "Document not verified through SAVE",
            "expected": "Do not make a final status finding from the illustration."
          },
          {
            "case": "Current seven-year eligibility plus medical denial",
            "expected": "Do not substitute the required-medical-allowance denial/payment consequence."
          },
          {
            "case": "Medical allowance alone",
            "expected": "Do not infer historical residence or all other eligibility factors."
          },
          {
            "case": "Aged claimant with prior Title II disability decision",
            "expected": "Do not adopt it instead of the new decision required by the scoped source."
          },
          {
            "case": "Medical decision pending",
            "expected": "Do not defer other development or prematurely close the scoped event."
          },
          {
            "case": "Presumptive payments involved",
            "expected": "Do not apply the F.12 no-presumptive-payment entry."
          },
          {
            "case": "Medical allowance not needed for eligibility",
            "expected": "Do not select F.15 required-allowance denial as an established case."
          },
          {
            "case": "Spouse decision still pending",
            "expected": "Do not perform the after-receipt G.2 transition as if complete."
          },
          {
            "case": "Under-65 disabled member approved first",
            "expected": "Do not treat that G.3/G.4 composition as the G.2 aged-payable entry."
          },
          {
            "case": "Applicable grandfathered category",
            "expected": "Do not infer the H.1 gates."
          },
          {
            "case": "Earlier denial appeal period still open",
            "expected": "Do not infer H.1 no-prior-or-appeal-ended condition."
          },
          {
            "case": "Posteligibility outcome not received",
            "expected": "Do not select either H.3 outcome branch."
          },
          {
            "case": "Internal source locator mismatches",
            "expected": "Do not invent the linked content or choose date precedence."
          },
          {
            "case": "Source names an eligibility code or screen",
            "expected": "Do not create native identity or operational acceptance."
          }
        ]
      },
      "interpreter7": {
        "flows": {
          "apply-disability/dds-language-preference": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-language-preference",
            "full_route": "apply-disability/dds-language-preference",
            "entry_conditions": [
              "Language assistance is requested or is evidently needed in DDS claimant contact or a consultative examination."
            ],
            "steps": [
              {
                "id": "dds-language-preference-source-1",
                "title": "Identify and record the language need",
                "kind": "action",
                "actor": "DDS",
                "action": "Review the folder’s foreign-language indicator and relevant forms, contact reports or electronic/paper remarks. Determine and document the preferred spoken language, including sign language, rather than assuming further communication should be in English.",
                "conditions": [
                  "Language assistance is requested or is evidently needed in DDS claimant contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "C.1; C.5–6",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "Sign-language handling and foreign-language document translation have distinct linked instructions.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-language-preference-source-2",
                "title": "Arrange assistance before the specified contact",
                "kind": "action",
                "actor": "DDS",
                "action": "Explain free and equal interpreter service. Before further communication, a consultative examination or a telephone call, obtain State-contracted interpretation or SSA TIS if authorized; a person need not supply their own interpreter.",
                "conditions": [
                  "Language assistance is requested or is evidently needed in DDS claimant contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "C.2–6; C.8",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "TIS requires DDS/State authorization and the source’s contract conditions. Named service availability is a publication statement, not live runtime telemetry or an appointment-duration promise.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established.",
                  "B.6 requires State authorization before DDS uses SSA TIS and agreement adjustments when needed to prevent paying two providers for the same service. Third-party vendors and CE providers cannot request SSA-provided TIS. These are publication conditions, not tested service availability."
                ]
              },
              {
                "id": "dds-language-preference-source-3",
                "title": "Document the actions and required notice message",
                "kind": "action",
                "actor": "DDS",
                "action": "Record LEP actions in eCAT Claim communication, or on SSA-5002 for non-eCAT claims, except actions requiring SSA-795. A notice requiring contact with DDS must explain free interpreter service when a language indicator exists or DDS has reason to believe the person has LEP, and must never require the person to bring their own interpreter.",
                "conditions": [
                  "Language assistance is requested or is evidently needed in DDS claimant contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "C.7; E.1",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The source’s alternatives and SSA-795 exception are distinct; no form or system identity is silently substituted.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          },
          "apply-disability/dds-own-interpreter": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-own-interpreter",
            "full_route": "apply-disability/dds-own-interpreter",
            "entry_conditions": [
              "The individual elects to bring their own interpreter during further DDS contact or a consultative examination."
            ],
            "steps": [
              {
                "id": "dds-own-interpreter-source-1",
                "title": "Review prior approval before a new qualification inquiry",
                "kind": "action",
                "actor": "DDS",
                "action": "Review the claims folder for a qualified interpreter approved by the field office. Defer to the interpreter-signed SSA-795 already in the folder before determining whether the chosen interpreter meets the source’s qualified-interpreter criteria.",
                "conditions": [
                  "The individual elects to bring their own interpreter during further DDS contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "A; E.4",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "Prior documentation is relevant; selecting a family member does not by itself establish qualification or approval.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-own-interpreter-source-2",
                "title": "Keep participation distinct from official interpretation",
                "kind": "action",
                "actor": "DDS",
                "action": "The person may bring an interpreter approved by SSA or DDS as qualified. If not approved, the chosen helper may participate, but the SSA- or DDS-provided interpreter supplies the official interpretation.",
                "conditions": [
                  "The individual elects to bring their own interpreter during further DDS contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "B.3; C.6",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The qualified-interpreter criteria include accuracy, terminology, service protocols, confidentiality and no conflicting personal stake. Detailed H/I documentation and replacement conditions still apply.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established.",
                  "B.3 requires fluent reading and speaking in English and the individual’s language or dialect, accurate questions and responses without self-initiated follow-up questions or inferred facts/dates, relevant terminology, interpreter protocols, confidentiality and no personal stake creating a conflict. A potential or actual claimant or beneficiary on the same record may interpret if there is no other conflict of interest.",
                  "An interpreter facilitates communication. This does not certify an authorized translator of written evidence; B.4–5 and linked DI 23045.001/GN 00301.340 remain separate."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          },
          "apply-disability/dds-interpreter-mid-contact": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-interpreter-mid-contact",
            "full_route": "apply-disability/dds-interpreter-mid-contact",
            "entry_conditions": [
              "The need for language assistance is discovered during claimant contact or a consultative examination."
            ],
            "steps": [
              {
                "id": "dds-interpreter-mid-contact-source-1",
                "title": "Try to obtain authorized interpretation immediately",
                "kind": "action",
                "actor": "DDS",
                "action": "Contact TIS or the State-contracted interpreter service immediately so the contact or examination can continue with interpretation.",
                "conditions": [
                  "The need for language assistance is discovered during claimant contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "E.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "TIS authorization remains required; immediately describes the source instruction, not a guaranteed service response.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-mid-contact-source-2",
                "title": "Reschedule when qualified help is not readily available",
                "kind": "action",
                "actor": "DDS",
                "action": "If a qualified interpreter is not readily available, reschedule the contact or examination and tell the person that DDS will notify them when it will continue.",
                "conditions": [
                  "The need for language assistance is discovered during claimant contact or a consultative examination.",
                  "A qualified interpreter is not readily available."
                ],
                "source": "ddsinterpreter",
                "section": "E.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "No appointment date or elapsed rescheduling duration is established.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-mid-contact-source-3",
                "title": "Arrange the replacement appointment and flag the need",
                "kind": "action",
                "actor": "DDS",
                "action": "If a qualified interpreter is not readily available, take action to reschedule and arrange a qualified interpreter for the rescheduled appointment using the source’s qualified-interpreter list.",
                "conditions": [
                  "The need for language assistance is discovered during claimant contact or a consultative examination.",
                  "A qualified interpreter is not readily available."
                ],
                "source": "ddsinterpreter",
                "section": "E.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "A flag or arrangement does not prove a completed examination or successful return to another claim process.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-mid-contact-source-4",
                "title": "Add the language-assistance flag",
                "kind": "action",
                "actor": "DDS",
                "action": "Add an LEP flag to the claims folder.",
                "conditions": [
                  "The need for language assistance is discovered during claimant contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "E.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "E.3 lists this folder instruction after the interpreter-arrangement actions without expressly restricting it to interpreter unavailability. The flag does not prove an interpreter was obtained or a contact or examination completed.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          },
          "apply-disability/dds-minor-participation": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-minor-participation",
            "full_route": "apply-disability/dds-minor-participation",
            "entry_conditions": [
              "The person insists that a minor under age 18 participate as an interpreter during DDS contact or a consultative examination."
            ],
            "steps": [
              {
                "id": "dds-minor-participation-source-1",
                "title": "Provide the official qualified interpreter",
                "kind": "action",
                "actor": "DDS",
                "action": "A minor can never serve as the qualified interpreter. DDS must also provide a qualified interpreter whose rendition is official; explain the complex and sensitive issues in the person’s preferred language with qualified help.",
                "conditions": [
                  "The person insists that a minor under age 18 participate as an interpreter during DDS contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "A; E.5",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The person’s choice does not qualify the minor or make the child’s rendition official.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-minor-participation-source-2",
                "title": "Limit what the child may assist with",
                "kind": "action",
                "actor": "DDS",
                "action": "Use a minor only to identify the language, interpret the general purpose of the call or examination, or assist with rescheduling if business cannot be completed that day without qualified interpretation.",
                "conditions": [
                  "The person insists that a minor under age 18 participate as an interpreter during DDS contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "E.5",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "These limited assistance roles do not replace qualified medical or other substantive interpretation.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-minor-participation-source-3",
                "title": "Address the person and document the actions",
                "kind": "action",
                "actor": "DDS",
                "action": "Direct questions to the person needing language assistance and document the actions under C.7.",
                "conditions": [
                  "The person insists that a minor under age 18 participate as an interpreter during DDS contact or a consultative examination."
                ],
                "source": "ddsinterpreter",
                "section": "E.5; C.7",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "No interpreter approval, claimant response or substantive case outcome is established by the illustration.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          },
          "apply-disability/dds-own-interpreter-paperwork": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-own-interpreter-paperwork",
            "full_route": "apply-disability/dds-own-interpreter-paperwork",
            "entry_conditions": [
              "The individual chooses their own interpreter rather than relying only on an SSA- or DDS-provided interpreter."
            ],
            "steps": [
              {
                "id": "dds-own-interpreter-paperwork-source-1",
                "title": "Explain the free service and check qualifications",
                "kind": "action",
                "actor": "DDS",
                "action": "Review the claims folder for an FO-approved qualified interpreter and defer to an interpreter-signed SSA-795 already in the folder before determining qualifications. Explain that DDS provides qualified interpretation at no cost and pays only for services it provides. Identify the chosen interpreter and determine qualifications before contact or scheduling the examination.",
                "conditions": [
                  "The individual chooses their own interpreter rather than relying only on an SSA- or DDS-provided interpreter."
                ],
                "source": "ddsinterpreter",
                "section": "A; E.4; H.1–3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "Choosing an interpreter is not approval; the full B.3 criteria and existing-file documentation apply.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-own-interpreter-paperwork-source-2",
                "title": "Record the claimant’s choice and understanding",
                "kind": "you",
                "actor": "claimant",
                "action": "Sign the requested SSA-795 documenting the free-service offer, choice of a qualified interpreter, the preferred language used, and understanding of the statement read in that language.",
                "conditions": [
                  "The individual chooses their own interpreter rather than relying only on an SSA- or DDS-provided interpreter."
                ],
                "source": "ddsinterpreter",
                "section": "H.4",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "This is the source’s claimant statement, distinct from the interpreter’s statement and not proof of capacity, consent to unrelated disclosure or a completed contact.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-own-interpreter-paperwork-source-3",
                "title": "Check whether a new interpreter statement is required",
                "kind": "action",
                "actor": "DDS",
                "action": "Check for a prior field-office SSA-795 specifying this interpreter. If no statement was obtained at the FO or the interpreter is different, obtain the own interpreter’s SSA-795 before contact or scheduling the CE, subject to the separately conditional H.9 telephone procedure. Include accurate-communication role, ability to read/speak/understand English and the person’s language or dialect, the free-service offer and individual’s choice, interpreter name/address/telephone, any relationship, and relevant interpreter or DDS comments over the interpreter’s signature. SSA- or DDS-provided interpreters need not sign it.",
                "conditions": [
                  "The individual chooses their own interpreter rather than relying only on an SSA- or DDS-provided interpreter."
                ],
                "source": "ddsinterpreter",
                "section": "H.6",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "A second interpreter statement is required only for a different chosen interpreter; do not force duplicate same-interpreter documentation or confuse it with the claimant’s statement.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-own-interpreter-paperwork-source-4",
                "title": "Record language and confidentiality details",
                "kind": "action",
                "actor": "DDS",
                "action": "Annotate the preferred spoken and written language and foreign-language notices when available. Remind the interpreter that SSA policy prohibits disclosure of any SSN or other personal information obtained during agency proceedings without SSA’s permission; annotate SSA-795 to show the reminder was given.",
                "conditions": [
                  "The individual chooses their own interpreter rather than relying only on an SSA- or DDS-provided interpreter."
                ],
                "source": "ddsinterpreter",
                "section": "H.5; H.7",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The captured source’s English/Spanish systems-notice statement is not a tested current availability claim. Linked disclosure rules remain separately scoped.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          },
          "apply-disability/dds-interpreter-signature-pending": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-interpreter-signature-pending",
            "full_route": "apply-disability/dds-interpreter-signature-pending",
            "entry_conditions": [
              "Telephone contact uses the individual’s own interpreter and a qualified interpreter source is not readily available.",
              "Applicable earlier interpreter-qualification and claimant/documentation requirements remain; the signature-pending option does not approve an unqualified interpreter or a minor.",
              "The interpreter’s signed SSA-795 is required and remains outstanding; an already documented same interpreter is not automatically required to supply a duplicate statement."
            ],
            "steps": [
              {
                "id": "dds-interpreter-signature-pending-source-1",
                "title": "Explain the telephone-contact statement requirement",
                "kind": "action",
                "actor": "DDS",
                "action": "Explain the applicable LEP policy and procedures, including the need for the interpreter’s signed SSA-795.",
                "conditions": [
                  "Telephone contact uses the individual’s own interpreter and a qualified interpreter source is not readily available.",
                  "Applicable earlier interpreter-qualification and claimant/documentation requirements remain; the signature-pending option does not approve an unqualified interpreter or a minor.",
                  "The interpreter’s signed SSA-795 is required and remains outstanding; an already documented same interpreter is not automatically required to supply a duplicate statement."
                ],
                "source": "ddsinterpreter",
                "section": "H.9",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The interpreter’s statement is distinct from the claimant’s statement, and a pending signature is not a denial finding.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-signature-pending-source-2",
                "title": "If the interpreter refuses to sign",
                "kind": "action",
                "actor": "DDS",
                "action": "Terminate the contact if the interpreter says they will not sign, and follow the I.3 qualified-interpreter/rescheduling instruction.",
                "conditions": [
                  "Telephone contact uses the individual’s own interpreter and a qualified interpreter source is not readily available.",
                  "Applicable earlier interpreter-qualification and claimant/documentation requirements remain; the signature-pending option does not approve an unqualified interpreter or a minor.",
                  "The interpreter’s signed SSA-795 is required and remains outstanding; an already documented same interpreter is not automatically required to supply a duplicate statement.",
                  "The interpreter refuses to sign SSA-795."
                ],
                "source": "ddsinterpreter",
                "section": "H.9 refusal; I.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "This is not the agrees-to-sign branch and is not an automatic disability denial.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ],
                "alternative_group": "signature-response"
              },
              {
                "id": "dds-interpreter-signature-pending-source-3",
                "title": "If the interpreter agrees to sign",
                "kind": "action",
                "actor": "DDS",
                "action": "Continue the contact without the signed interpreter statement when the interpreter agrees to sign. Mail SSA-795 to the interpreter and the applicable disability material to the individual, or combine the mailing if their addresses are the same. Do not make a final determination until the signed interpreter statement is returned.",
                "conditions": [
                  "Telephone contact uses the individual’s own interpreter and a qualified interpreter source is not readily available.",
                  "Applicable earlier interpreter-qualification and claimant/documentation requirements remain; the signature-pending option does not approve an unqualified interpreter or a minor.",
                  "The interpreter’s signed SSA-795 is required and remains outstanding; an already documented same interpreter is not automatically required to supply a duplicate statement.",
                  "The interpreter agrees to sign SSA-795."
                ],
                "source": "ddsinterpreter",
                "section": "H.9 agreement",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "Agreement is not the returned signature; the final-determination restriction remains even though telephone contact may continue.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ],
                "alternative_group": "signature-response"
              },
              {
                "id": "dds-interpreter-signature-pending-source-4",
                "title": "If attempts to obtain the signature fail",
                "kind": "action",
                "actor": "DDS",
                "action": "Locate a second interpreter from the qualified-interpreter list, notify the field office when appropriate that contact or examination is being repeated, and reschedule with the second interpreter to verify the prior information.",
                "conditions": [
                  "Telephone contact uses the individual’s own interpreter and a qualified interpreter source is not readily available.",
                  "Applicable earlier interpreter-qualification and claimant/documentation requirements remain; the signature-pending option does not approve an unqualified interpreter or a minor.",
                  "The interpreter’s signed SSA-795 is required and remains outstanding; an already documented same interpreter is not automatically required to supply a duplicate statement.",
                  "Attempts to obtain the interpreter’s signed SSA-795 are unsuccessful."
                ],
                "source": "ddsinterpreter",
                "section": "H.10",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "This is a separately conditional verification response, not an automatic next step from every refusal or a prescribed return deadline.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            },
            "alternative_groups": [
              {
                "id": "signature-response",
                "label": "Different instructions for refusal and agreement",
                "logic": "source_conditions_determine_branch",
                "note": "These are conditional alternatives, not consecutive actions. Agreement to sign does not establish return of the signed statement."
              }
            ]
          },
          "apply-disability/dds-interpreter-replacement": {
            "schema": "securitystat.exception-flow/1",
            "record_id": "dds-interpreter-replacement",
            "full_route": "apply-disability/dds-interpreter-replacement",
            "entry_conditions": [
              "DDS finds qualified interpreter service necessary under I, including a refusal situation expressly referred by H.9.",
              "This walkthrough does not make a finding of misconduct, fraud or interpreter qualification."
            ],
            "steps": [
              {
                "id": "dds-interpreter-replacement-source-1",
                "title": "Explain free qualified service",
                "kind": "action",
                "actor": "DDS",
                "action": "Remind the person that DDS provides free qualified interpreter service to avoid disadvantage. The source’s I.1 concerns include inaccurate information, not acting in the person’s interests or suspected fraud.",
                "conditions": [
                  "DDS finds qualified interpreter service necessary under I, including a refusal situation expressly referred by H.9.",
                  "This walkthrough does not make a finding of misconduct, fraud or interpreter qualification."
                ],
                "source": "ddsinterpreter",
                "section": "I.1–2",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The concerns are source predicates, not findings about a person or an automated fraud referral.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-replacement-source-2",
                "title": "Stop and reschedule if the appropriate service is unavailable",
                "kind": "action",
                "actor": "DDS",
                "action": "After determining qualified service is necessary, terminate the contact or examination if that service is unavailable, explain that DDS will provide it at a rescheduled appointment, and document why communication or examination ended.",
                "conditions": [
                  "DDS finds qualified interpreter service necessary under I, including a refusal situation expressly referred by H.9.",
                  "This walkthrough does not make a finding of misconduct, fraud or interpreter qualification.",
                  "The appropriate interpreter service is unavailable after DDS determines qualified service is needed."
                ],
                "source": "ddsinterpreter",
                "section": "I.3",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "The lack of interpreter service does not itself establish a denial or customer failure to cooperate.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              },
              {
                "id": "dds-interpreter-replacement-source-3",
                "title": "Obtain appropriate service before continuing",
                "kind": "action",
                "actor": "DDS",
                "action": "Before contact or examination continues, explain that appropriate interpretation must be obtained. The person and chosen helper may remain on request; direct questions to the person, who provides responses in their preferred language.",
                "conditions": [
                  "DDS finds qualified interpreter service necessary under I, including a refusal situation expressly referred by H.9.",
                  "This walkthrough does not make a finding of misconduct, fraud or interpreter qualification."
                ],
                "source": "ddsinterpreter",
                "section": "I.4",
                "source_context_refs": [
                  "DI23040.001:whole"
                ],
                "qualifications": [
                  "This does not certify the helper as the official interpreter, establish that service was obtained, or demonstrate successful continuation.",
                  "Prescribed source instruction only; no actual interpreter approval, completed contact, claim outcome or successful rejoin is established."
                ]
              }
            ],
            "rejoin": {
              "status": "unknown",
              "automatic_transition": false,
              "unknowns": [
                "The source-conditioned arrangements do not prove that interpretation, contact, signature return or a successful return to the case path has occurred."
              ]
            }
          }
        },
        "original_records": {
          "apply-disability/dds-language-preference": {
            "id": "dds-language-preference",
            "title": "DDS needs your communication-language preference",
            "when": "Language assistance is requested or needed.",
            "you": "Tell DDS your preferred language.",
            "ssa": "Review folder indicators/reports; determine and document preference. Arrange authorized interpreter service before further contact or examination. Record actions in eCAT Claim communication, or SSA-5002 for non-eCAT cases, except required SSA-795 actions. Contact notices must describe free interpretation and never require your own interpreter.",
            "route": "DDS → interpreter arrangement / documentation",
            "next": "An evident need also triggers assistance without a request.",
            "source": "ddsinterpreter",
            "section": "C.1-8; E.1",
            "timing": "Before further contact as specified; no arrangement-duration promise",
            "review_status": "Selected official staff procedure checked; full qualification/documentation exceptions remain"
          },
          "apply-disability/dds-own-interpreter": {
            "id": "dds-own-interpreter",
            "title": "You want a family member or another interpreter to help",
            "when": "You choose your own interpreter for DDS contact or examination.",
            "you": "Identify your chosen interpreter and any prior approval.",
            "ssa": "Review prior FO approval first. Use an SSA/DDS-approved qualified interpreter. An unapproved interpreter may participate, but SSA/DDS-provided interpretation remains official.",
            "route": "DDS → interpreter qualification / contact",
            "next": "Participation is different from approval as the official interpreter.",
            "source": "ddsinterpreter",
            "section": "A; B.3; C.6",
            "timing": "Before further contact as specified; no arrangement-duration promise",
            "review_status": "Selected official staff procedure checked; full qualification/documentation exceptions remain"
          },
          "apply-disability/dds-interpreter-mid-contact": {
            "id": "dds-interpreter-mid-contact",
            "title": "The interpreter need becomes clear during a contact or examination",
            "when": "DDS discovers language assistance is needed during claimant contact or CE.",
            "you": "Explain the communication difficulty and keep the new appointment information.",
            "ssa": "Contact authorized interpreter service immediately. If a qualified interpreter is not readily available, arrange rescheduling, explain that continuation details will be sent, arrange an interpreter for the new appointment and add a language-assistance flag.",
            "route": "DDS → interpreter service / rescheduled contact or CE",
            "next": "DDS owns the continuation arrangements; no appointment date is promised here.",
            "source": "ddsinterpreter",
            "section": "E.3",
            "timing": "Immediate attempt to obtain interpretation; rescheduling duration not specified",
            "review_status": "Official conditional rescheduling steps checked"
          },
          "apply-disability/dds-minor-participation": {
            "id": "dds-minor-participation",
            "title": "You want a minor child to interpret",
            "when": "Individual insists on child participation during DDS contact or CE.",
            "you": "Discuss the need with DDS.",
            "ssa": "A minor cannot be the qualified interpreter. Provide a qualified interpreter whose rendition is official; explain in the preferred language. Limit child assistance to language identification, general purpose and rescheduling; direct questions to the individual and document.",
            "route": "DDS → qualified interpretation",
            "next": "Child participation does not replace official qualified interpretation.",
            "source": "ddsinterpreter",
            "section": "E.5",
            "timing": "No processing duration specified",
            "review_status": "Selected official conditions checked; no individual interpreter approval"
          },
          "apply-disability/dds-own-interpreter-paperwork": {
            "id": "dds-own-interpreter-paperwork",
            "title": "DDS needs statements for your chosen interpreter",
            "when": "Individual supplies an interpreter.",
            "you": "Review and sign the requested choice/understanding statement.",
            "ssa": "Explain free DDS service; identify qualifications before contact/CE. Obtain claimant SSA-795 and check prior FO interpreter SSA-795; obtain interpreter statement if absent or interpreter changed. SSA/DDS-provided interpreters need not sign it. Record confidentiality reminder.",
            "route": "DDS → SSA-795 evidence / interpreter review",
            "next": "Prior same-interpreter documentation can avoid a duplicate interpreter statement.",
            "source": "ddsinterpreter",
            "section": "H.1-7",
            "timing": "No processing duration specified",
            "review_status": "Selected official conditions checked; no individual interpreter approval"
          },
          "apply-disability/dds-interpreter-signature-pending": {
            "id": "dds-interpreter-signature-pending",
            "title": "Your interpreter statement is pending after a telephone contact",
            "when": "Own interpreter used by telephone and qualified service is not readily available.",
            "you": "Help your interpreter return the requested statement; follow rescheduling instructions.",
            "ssa": "If interpreter agrees to sign, continue contact and mail SSA-795 to interpreter, other materials to claimant; combine mail if same address. Do not make final determination until signed interpreter statement returns. If attempts fail, find a second qualified interpreter, notify FO when appropriate and repeat contact/CE to verify prior information.",
            "route": "DDS → interpreter SSA-795 return / second-interpreter verification",
            "next": "The interpreter signature is distinct from the claimant signature; missing interpreter form does not itself establish denial.",
            "source": "ddsinterpreter",
            "section": "H.9-10",
            "timing": "No form-return or rescheduling duration specified",
            "review_status": "Official signature/verification conditions checked; refusal route I.3 separately pending"
          },
          "apply-disability/dds-interpreter-replacement": {
            "id": "dds-interpreter-replacement",
            "title": "DDS cannot rely on the chosen interpreter",
            "when": "DDS finds a qualified replacement necessary, including the specified signature-refusal route.",
            "you": "Answer in your preferred language; ask if your chosen helper may remain.",
            "ssa": "Remind the individual of free qualified service. If unavailable, end the contact/CE, explain rescheduling with a qualified interpreter and document why. Obtain appropriate interpretation before continuation; the person and chosen interpreter may remain on request, with questions directed to the individual.",
            "route": "DDS → qualified replacement / documented rescheduling",
            "next": "Ending the contact is not itself a denial of the disability claim.",
            "source": "ddsinterpreter",
            "section": "I.1-4; H.9 refusal",
            "timing": "No replacement or rescheduling duration specified",
            "review_status": "Official conditional replacement procedure checked; no finding about an individual interpreter"
          }
        },
        "source_contexts": [
          {
            "id": "DI23040.001:whole",
            "start": 0,
            "end": 25388,
            "exact_text": "Effective Dates: 08/01/2023 - Present\nPrevious | Next\n\nTN 9 (03-26)\n\nDI 23040.001 DDS: Interpreters for Individuals with Limited English Proficiency (LEP) or Individuals Requiring Language Assistance\nA. \nPolicy for LEP individuals\n\nSocial Security Administration (SSA) is committed to providing fair and equitable service to the American public, regardless of an individual’s ability to communicate effectively in English.\n\nWe recognize that using qualified interpreters, including bilingual staff who can communicate directly with claimants in their primary language, efficiently facilitates our processes, deters fraud, and assures that we do not disadvantage individuals with limited English proficiency (LEP).\n\nDisability determination services (DDS) will provide an interpreter (free of charge) to any individual requesting language assistance, or when it is evident that such assistance is necessary to ensure that the individual is not disadvantaged.\n\nNOTE: DDS will not require individuals needing language assistance to provide their own interpreters.\n\nIndividuals have the option of using their own interpreter, such as a family member, friend, or third party, if the interpreter meets SSA criteria as a qualified interpreter. For more information regarding qualified interpreter, see DI 23040.001B.3.\n\nThe DDS must first review the claims folder for documentation of a qualified interpreter approved by the field office (FO) prior to obtaining information about the individual’s interpreter, see DI 23040.001C.1. For information on documentation requirements when using an interpreter, see DI 23040.001G and DI 23040.001H.\n\nA minor child (under age 18) cannot serve as a qualified interpreter due to the nature and complexities of the disability determination process. For more information regarding when a minor child may assist with interpretation, see DI 23040.001E.5.\n\nSpecial handling procedures apply to claims for LEP individuals, see DI 23007.005C, DI 22510.016A and DI 28075.005F.3.\n\nB. \nDefinitions of terms related to LEP\n1. \nIndividual with LEP\n\nAn individual with LEP is someone who has limited or no ability to read, write, speak or understand English.\n\n2. \nInterpreter\n\nAn interpreter is an individual who speaks English and another language fluently, including sign language, and facilitates communication between the individual needing language assistance and the DDS staff members who are not proficient in the individual’s preferred language.\n\n3. \nQualified Interpreter\n\nA qualified interpreter is an individual or vendor who is able to read and speak fluently in English and the language or dialect of the individual needing language assistance, and who meets the following criteria;\n\n•\n\nProvides an accurate interpretation of questions and responses by both the LEP individual and the DDS staff member (usually a disability examiner (DE)); i.e., does not self-initiate follow-up questions or infer facts or dates not provided by the individual or the DDS employee;\n\n•\n\nDemonstrates familiarity with basic terminology used in the disability determination process, including medical and social welfare terminology when necessary;\n\n•\n\nHas knowledge of and experience in applying the protocols and procedures for delivering interpreter services;\n\n•\n\nAgrees to comply with SSA's disclosure and confidentiality of information requirements, see GN 03301.004; and\n\n•\n\nHas no personal stake in the outcome of the case that would create a conflict of interest. An individual who is a potential or actual claimant or beneficiary on the same record as the individual needing language assistance can act as a qualified interpreter, providing that there is no other conflict of interest.\n\n4. \nTranslator\n\nA translator is an individual who can read and write English and another language and can accurately translate written material from one language to another.\n\nNOTE: For translation of foreign language documents, see DI 23045.001.\n\n5. \nAuthorized Translator\n\nAn authorized translator is a translator who SSA certifies through an official authorization process and accurately translates written documents and evidence from a non-English language into English. For additional information, see GN 00301.340.\n\nNOTE: This definition is not applicable to non-SSA translation services.\n\n6. \nTelephone Interpreter Service (TIS)\n\nSSA has a nationwide Blanket Purchase Agreement with a private company, Language Select, for TIS in more than 120 languages and dialects. TIS is accessible to all SSA and if authorized, DDS public contact employees. Interpreters are available immediately, 24 hours a day and 7 days a week. The instructions for this service are accessible on the intranet through the Multilanguage Resources page.\n\nThe DDSs may use the service provided they are not charged for the same service through a State contracted interpreter service or Indirect Cost Agreement. The DDS would need to adjust those agreements prior to participating in the SSA contract to ensure SSA does not pay both providers for the same service. DDS staff must ensure that they have authorization from their State prior to using SSA’s TIS. To obtain a Language Select telephone interpreter see instructions in GN 00203.011. Third-party vendors and Consultative Examination (CE) providers cannot request service from the SSA provided TIS.\n\nNOTE: Upon contacting TIS, you must provide your three-digit State Agency or Detailed Office/Organization Resource System (DOORS) code.\n\nC. \nProcedure – Identifying the need for an interpreter\n1. \n\nReview the claims folder for a foreign language indicator. If a foreign language indicator does not exist, determine if an interpreter or sign language interpreter is needed by reviewing the following documents in the claims folder:\n\n•\n\nDisability Report-Adult (SSA-3368-BK);\n\n•\n\nReport of Contact (SSA-5002);\n\n•\n\nStatement of Claimant or Other Person (SSA-795);\n\n•\n\nRemarks in eView for electronic cases or on the Disability Transmittal Sheet for paper folders; or\n\n•\n\nAny forms or documents that may indicate an interpreter is required.\n\nNOTE: If a sign language interpreter is necessary, follow the instructions in GN 00203.012.\n\n2. \n\nInform the individual that the DDS will provide interpreter services free of charge.\n\n3. \n\nAssure the individual that the DDS will provide him or her with service equal to that provided to individuals who are fluent in English.\n\n4. \n\nExplain to the individual that SSA may have materials (i.e., pamphlets, publications, or other materials) in his or her language by accessing the Multilanguage Gateway on the internet.\n\n5. \n\nBe alert to the language needs of any individual having difficulty understanding, hearing or speaking English, and be sensitive to the cultural differences that could adversely affect communication with the individual.\n\n6. \n\nDetermine whether the individual wants further communication in English, or another language, including sign language. If the individual does not want additional communication conducted in English, determine and document which language he or she prefers.\n\nPrior to scheduling additional communication, CE, or contacting the claimant by telephone, do the following:\n\n•\n\nObtain interpreter services through the State-contracted interpreter service, or SSA TIS if authorized.\n\n•\n\nExplain that the individual may bring his or her own interpreter during contact with the DDS, or during CEs, provided SSA or DDS has approved him or her as a qualified interpreter. For more information on qualified interpreters and the approval process, see DI 23040.001B.3 and DI 23040.001H in this section. If SSA or DDS has not approved the claimant’s interpreter, he or she may participate during the claimant contact or CE, but the official interpretation will be that of an SSA or DDS provided interpreter.\n\n7. \n\nDocument all LEP actions, except for actions requiring the use of a SSA Form 795, using the electronic claims analysis tool (eCAT) in the section titled “Claim communication.” For non-eCAT claims, use a SSA Form 5002 to document all LEP actions, except when a SSA-795 is required.\n\n8. \n\nProvide an interpreter whenever it is difficult to understand the individual, or when it is evident that language assistance is required to ensure that the individual is not disadvantaged, even if the individual does not request an interpreter.\n\n9. \n\nUse the following options when you do not know the language for which assistance is required:\n\n•\n\nThe TIS, which employs trained operators who can identify key words in foreign languages and effectively determine the language for which assistance is required, is accessible only if approved by your DDS, or\n\n•\n\nThe State-contracted interpreter service, if not authorized to use TIS, for assistance in identifying the language for which interpreter services is required.\n\n10. \n\nFor situations involving the use of an individual’s own interpreter, follow instructions in DI 23040.001E.4.\n\nD. \nQualified Interpreter Sources\n\nIn priority order, the DDS will accept the following list of qualified interpreters if they satisfy the requirements outlined in DI 23040.001B.3:\n\n1. \n\nDDS bilingual employees including bilingual CE providers, and\n\n•\n\nEmployees of the Veterans Administration Regional Office in Manila,\n\n•\n\nU.S. Military Consular Officers,\n\n•\n\nOfficials of foreign government liaison agencies, and\n\n•\n\nDesignated employees of the Federal Benefits Unit of a U.S. Foreign Service Post, who are fluent in the language that needs interpretation;\n\n2. \n\nOther bilingual State employees;\n\n3. \n\nSSA bilingual field office (FO) employees, see DI 23040.001E.2;\n\n4. \n\nNon-DDS interpreters in the community who have an agreement with the DDS to provide interpretations and who do not charge a fee for interpreter services, for example:\n\n•\n\nmembers of church groups,\n\n•\n\nuniversity employees or students,\n\n•\n\nemployees of other Federal, State or local agencies,\n\n•\n\nethnic social service agencies, or\n\n•\n\nmembers of advocacy groups.\n\n5. \n\nEmployees of vendors contracted by the DDS to provide interpreter services. This category also includes all interpreters working for the nationwide SSA TIS; and\n\n6. \n\nNon-DDS interpreters in the community who charge a fee for interpreter services; for example:\n\n•\n\nmembers of church groups,\n\n•\n\nuniversity employees or students,\n\n•\n\nemployees of other Federal, State or local agencies, ethnic social service agencies, or\n\n•\n\nmembers of advocacy groups\n\nE. \nProcedure - special situations involving interpreters\n1. \nNotices\n\nWhenever there is a foreign language indicator on a claim or the DDS has reason to believe an individual has LEP, any notice that requires the individual to contact the DDS regarding his or her claim (for example, additional claimant contact or a CE) must include the following statement:\n\n“We provide free interpreter services to conduct your Social Security business. However, if you prefer to have your own interpreter, you may do so, but with the understanding that our own interpreter may be present.”\n\nNOTE: Under no circumstances should any notice to individuals contain language requiring them to provide their own interpreter.\n\n2. \nProviding an interpreter\n\nWhen an interpreter is needed, DDS must provide one from the list of qualified interpreters, with bilingual DDS employees or CE providers being the preferred choice; for instructions see DI 23040.001D. The DE or other DDS staff must:\n\n•\n\nReview the file for prior interpreter contact(s) that the FO used.\n\n•\n\nDetermine whether an interpreter is qualified, and when there is a choice, which interpreter to use. For information on qualified interpreters, see DI 23040.001B.3. For documentation instructions, see DI 23040.001C.7.\n\n•\n\nKnow that the FO is not responsible for providing an interpreter to the DDS.\n\n•\n\nKnow that the DDS should only use bilingual FO employees as interpreters that have prior FO management agreement. However, the FO may be able to provide the DDS with a list of qualified interpreters and interpreter services in their areas. For FO instructions regarding interpreters see GN 00203.011.\n\n•\n\nDocument the interpreter source provided by the DDS, see DI 23040.001C.7.\n\n3. \nNeed for interpreter discovered during claimant contact or CE\n\nThe DDS will perform the following actions:\n\n•\n\nContact the TIS or State-contracted interpreter service immediately to continue the claimant contact or CE with the LEP individual.\n\n•\n\nReschedule the claimant contact or CE if a qualified interpreter is not readily available.\n\n•\n\nInform the claimant that we will notify him or her as to when we will continue the claimant contact or CE\n\n•\n\nTake action to have the claimant contact or CE rescheduled;\n\n•\n\nArrange to have a qualified interpreter present at the rescheduled appointment, see DI 23040.001D;\n\n•\n\nAdd a LEP flag to the claims folder.\n\n4. \nUse of individual’s own interpreter\n\nThough the individual is aware that the DDS will provide a qualified interpreter, he or she has the option of providing his or her own interpreter during additional contact with DDS or during a CE. However, the DE or other DDS staff member should defer to the interpreter signed SSA-795, if included in the disability claims folder, prior to determining whether the individual’s own interpreter is qualified per DI 23040.001B.3. The DDS staff must adhere to the SSA guidelines provided in DI 23040.001H and DI 23040.001I.\n\n5. \nUse of a minor child interpreter\n\nA minor child can never serve as a qualified interpreter. When an individual insists on having a minor child interpret for him or her during contact with DDS or during a CE, he or she may do so, but the DDS must also provide a qualified interpreter. In this situation, the qualified interpreter's rendition is the official interpretation of the contact or examination.\n\nIn the individual’s preferred language and with the assistance of a qualified interpreter, the DDS staff must take the following actions:\n\n•\n\nExplain that the disability process may involve complex and sensitive matters relating to medical and other issues discussed during the disability application process.\n\n•\n\nAdvise the individual that the DDS cannot use a minor child (under age 18) as a qualified interpreter and that we must obtain the services of either a State-contracted interpreter service or TIS.\n\n•\n\nExplain that we will use a minor child only to:\n\na. \n\nidentify the language the individual speaks;\n\nb. \n\ninterpret the general purpose of the telephone call or examination; and\n\nc. \n\nassist in rescheduling a future appointment if the business cannot be completed that day without the assistance of a qualified interpreter.\n\n•\n\nDirect all questions to the individual requiring language assistance.\n\n•\n\nDocument all actions in the file, see DI 23040.001C.7. for documentation instructions.\n\nF. \nAuthorization for Paid Interpreters\n1. \n\nWith prior approval or authorization, DDS hires third party interpreters for additional communication with the claimant. The State DDS should follow State reimbursement procedures. The Federal DDS should make payment from the imprest fund or complete an Order for Supplies or Services (OF-347). (See Administrative Instructions Manual System (AIMS): Financial Management Manual SSA. g: 03.05; and Small Purchase Procedure for Contracting Officers Handbook.)\n\n2. \n\nAfter the initial authorization of a qualified interpreter(s), no subsequent verification is necessary.\n\nNOTE: The cost of interpreter services may differ from State to State.\n\n3. \n\nIf you suspect fraud, follow the instructions in DI 23025.015 or other local instructions.\n\nG. \nProcedure - conducting claimant contact or CE with the assistance of an interpreter\n\nWhen using an interpreter, the DDS staff must:\n\n1. \n\nDirect all questions and comments to the claimant, not the interpreter. For example, ask, “What is your disability?” rather than “What is his or her disability?”\n\n2. \n\nAsk one question at a time and listen to the interpreted response(s) before asking the next question.\n\n3. \n\nUse short sentences to help the interpreter provide exact interpretations.\n\n4. \n\nAvoid jargon or words that have two or more meanings. If necessary, provide examples to clarify a question\n\n5. \n\nDocument the file with the individual’s language preference, see DI 23040.001C.7 for documentation instructions. Annotate the file with the following: “LEP [specify language] Interpreter required.”\n\nH. \nAdditional actions to take when the individual prefers to use his or her own interpreter\n\nThe DE or Other DDS staff member must:\n\n1. \n\nExplain that the DDS will provide a qualified interpreter at no cost to assist him or her in conducting business with the DDS, so he or she is not disadvantaged.\n\n2. \n\nIdentify the interpreter and determine his or her qualifications before conducting claimant contact or scheduling the CE.\n\n3. \n\nExplain that the DDS only pays for interpreter services it provides.\n\n4. \n\nWhen the claimant provides his or her own interpreter, the DDS must have the claimant sign a SSA-795 with the following statement included:\n\n“Social Security Administration has offered an interpreter free of charge to me. However, I have chosen to provide my own interpreter. I understand that the interpreter I provide must be a qualified interpreter as defined by SSA. However, if SSA does not deem my interpreter as qualified, SSA will provide an interpreter free of charge to me.”\n\n“The claimant contact or CE was conducted in (state language) which is my preferred language. This statement was read to me in (state language). I understand it.”\n\nThe statement should also include any additional actions taken to ensure his or her understanding of material covered during the claimant contact or CE.\n\n5. \n\nMake appropriate annotation(s) on the SSA-795 to identify the preferred spoken and written language of the individual and to issue foreign language notices, if available. Currently, only English and Spanish notices are systems generated for Title II and Title XVI claims.\n\n6. \n\nDetermine if the FO obtained a previous SSA-795 specifying use of the individual’s own interpreter. If an SSA-795 was not obtained at the FO, or if the interpreter is a different individual than was used previously, before conducting claimant contact or scheduling the CE, obtain an SSA-795 from the individual's own interpreter with the following statements and information:\n\n•\n\n“I am acting as an interpreter for (individual's name) to provide accurate communication between (individual's name) and DDS”;\n\n•\n\n“I can read, speak and understand English and (language), which is the language or dialect of (individual's name)”;\n\n•\n\n“Although Social Security Administration has offered (individual’s name) an interpreter free of charge to him or her, (individual’s name) chooses me to serve as his or her interpreter.”\n\n•\n\nInterpreter's name, address and telephone number;\n\n•\n\nRelationship, if any, of the interpreter to the individual (For example, son, mother, friend, minister);\n\n•\n\nAny relevant comments that the interpreter wishes to include; and\n\n•\n\nAny relevant comments the DDS staff deems necessary to document over the interpreter's signature.\n\nNOTE: Interpreters that SSA or DDS provides do not have to sign a SSA-795. In addition, a second SSA-795 is only necessary if the individual’s own interpreter is different from the interpreter previously used at the FO.\n\n7. \n\nRemind interpreters that SSA policy prohibits them from disclosing any Social Security Number or other personal information they have obtained during the agency proceedings without SSA's permission. Annotate the SSA-795 to show that the interpreter received this reminder. For additional information about disclosure, see GN 03301.004 and GN 03325.000.\n\n8. \n\nTake the following actions when the DDS conducts claimant contact by telephone with a qualified interpreter.\n\n•\n\nConduct the claimant contact with the TIS acting as the interpreter; or\n\n•\n\nIf the DDS is not authorized to use the TIS, obtain a qualified interpreter before calling the individual.\n\n9. \n\nTake the following actions when the DDS conducts claimant contact by telephone with the individual’s own interpreter and a qualified interpreter source is not readily available:\n\n•\n\nExplain the LEP policy and procedures as outlined in this subsection, including the need for a signed SSA-795;\n\n•\n\nTerminate the claimant contact if the interpreter states that he or she will not sign the SSA-795 and follow the procedures in DI 23040.001I.3; or\n\n•\n\nContinue the claimant contact and proceed without the signed SSA-795 if the interpreter agrees to sign the SSA-795;\n\n•\n\nMail the SSA-795 to the interpreter's address and the applicable disability forms or materials to the individual’s address; or\n\n•\n\nMail the SSA-795 with any applicable disability forms or materials if the interpreter and the individual have the same address.\n\n•\n\nDo not make a final determination until the interpreter returns the signed SSA-795.\n\n10. \n\nTake the following actions when attempts to obtain the interpreter's signed SSA-795 are unsuccessful:\n\n•\n\nLocate a second interpreter using the qualified interpreter listing found in DI 23040.001D;\n\n•\n\nNotify the FO, if appropriate, that the claimant contact or CE is being repeated with a second interpreter; and\n\n•\n\nReschedule the individual with a second interpreter to verify the information obtained at the prior contact or CE.\n\nI. \nActions to take when DDS is not satisfied with the claimant-provided interpreter\n1. \n\nThe DE or other DDS staff member must take the following actions when it appears the interpreter:\n\n•\n\nIs not acting in the individual’s best interest; or\n\n•\n\nIs not providing accurate information to the DDS staff; or\n\n•\n\nIs engaging in fraudulent activity.\n\n2. \n\nRemind the individual needing language assistance that the DDS will provide free interpreter service to ensure the individual is not disadvantaged.\n\n3. \n\nAfter determining that the services of a qualified interpreter are necessary:\n\n•\n\nTerminate the claimant contact or CE if the appropriate interpreter service is not available;\n\n•\n\nInform the individual that the DDS will provide a qualified interpreter at the time of his or her rescheduled appointment; and\n\n•\n\nDocument the file stating the reason DDS terminated the communication or examination. See DI 23040.001C.7 for documentation instructions.\n\n4. \n\nBefore conducting the claimant contact or CE, explain that the appropriate interpreter service must be obtained before the contact or examination can continue. The individual and his or her own interpreter can remain (upon request) during the claimant contact or exam; however, DDS will direct all questions to the individual and he or she must provide all responses in his or her own preferred language.\n\n5. \n\nIf DDS suspects fraud at any time during the contact, CE or development of the disability determination, follow the procedures in GN 04111.035.\n\nJ. \nProcedures to submit a complaint on a TIS interpreter\n\nTo submit a complaint about a TIS interpreter not performing completely or appropriately, follow local procedures and provide the following information:\n\n•\n\nDate of incident,\n\n•\n\nTime of incident,\n\n•\n\nDDS Office code – DDS office that has the complaint against Language Select (TIS),\n\n•\n\nInterpreter identification number,\n\n•\n\nLanguage requested,\n\n•\n\nDetails regarding nature of the complaint, and\n\n•\n\nDE or other DDS staff should call Language Select at 1-877-526-8438 or email to report the complaint and provide Language Select with detailed information.\n\nK. \nProcedures to submit a complaint on a State-contracted provided interpreter\n\nTo submit a complaint about a State-contracted interpreter not performing completely or appropriately, follow local procedures. Be sure to include the following information in all complaints:\n\n•\n\nDate of incident,\n\n•\n\nTime of incident,\n\n•\n\nInterpreter identifying information,\n\n•\n\nLanguage requested, and\n\n•\n\nDetails regarding the nature of the complaint.\n\nL. \nReferences for Good Cause, Language Preference and Other Interpreter Policy\n•\n\nDI 22510.016 - Consultative Examination (CE) Appointment Special Scheduling Procedures\n\n•\n\nDI 23007.005 - Failure to Cooperate With Requests to the Claimant for Evidence or Action\n\n•\n\nDI 23025.015 - Disability Determination Services (DDS) - Referring Potential Fraud or Similar Fault (FSF)\n\n•\n\nDI 23045.001 - Translation of Foreign-Language Documents\n\n•\n\nDI 28075.005 - Failure to Cooperate (FTC) and Whereabouts Unknown (WU) Cases\n\n•\n\nGN 00203.011 - Special Interviewing Situations, Limited English Proficiency (LEP) or Language Assistance Required\n\n•\n\nGN 00203.012 - Special Interviewing Situations (Deaf or Hard of Hearing Individual)\n\n•\n\nGN 00301.340 - Authorized Translators\n\n•\n\nGN 03301.004 - Development of Policy on Confidentiality and Disclosure\n\n•\n\nGN 03325.000 - Social Security Number-Disclosure and Verification\n\n•\n\nGN 04111.005 - Reporting Guidelines for Program Violations\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0423040001\n\t\nDI 23040.001 - DDS: Interpreters for Individuals with Limited English Proficiency (LEP) or Individuals Requiring Language Assistance - 08/01/2023\nBatch run: 10/19/2026\nRev:08/01/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          }
        ],
        "holds": [
          "Special good-cause/CE/noncooperation, sign-language, translation, disclosure, procurement and fraud-reference targets remain separately scoped; no automated referral or denial.",
          "TIS State authorization and no-double-charge contract conditions remain; CE providers/third-party vendors cannot request SSA TIS. No current uptime or native identity adoption.",
          "A child under 18 cannot be a qualified interpreter; participation and official interpretation are different.",
          "H.9 agreement-to-sign permits conditional contact but not a final determination before the signed interpreter statement returns; H.10 unsuccessful attempts has its own trigger.",
          "English/Spanish systems-notice and TIS availability statements describe the captured publication, not live system testing.",
          "Interpreting oral communication does not establish authorized translation of written evidence; B.4–5 and DI23045.001/GN00301.340 stay separate.",
          "E.3 final LEP flag is shown separately because its text has no express unavailable-interpreter condition; this is an instruction, not proof of a completed system action.",
          "H.6 already-documented same-interpreter rule and H.9 pending-signature telephone alternatives must remain separately conditional; no new duplicate-document rule."
        ],
        "negative_QA": [
          {
            "case": "No language-assistance request but evident need",
            "expected": "Do not make assistance depend solely on an explicit request."
          },
          {
            "case": "Individual needs interpretation",
            "expected": "Do not require their own interpreter or payment for DDS-provided service."
          },
          {
            "case": "TIS authorization absent",
            "expected": "Do not assume use of SSA TIS is permitted."
          },
          {
            "case": "State contracted service also charges for same service",
            "expected": "Do not ignore source no-double-payment contract limitation."
          },
          {
            "case": "CE provider requests SSA TIS",
            "expected": "Do not infer access contrary to B.6."
          },
          {
            "case": "Own interpreter unapproved",
            "expected": "Do not make that helper’s rendition official."
          },
          {
            "case": "Minor insists on participation",
            "expected": "Do not qualify the minor or use substantive unofficial rendition."
          },
          {
            "case": "Qualified help unavailable mid-contact",
            "expected": "Preserve source rescheduling/notification/flag conditions; no date promise."
          },
          {
            "case": "Same approved own interpreter statement already exists",
            "expected": "Do not require a duplicate interpreter SSA-795 solely by default."
          },
          {
            "case": "Different own interpreter",
            "expected": "Check H.6 new-statement condition."
          },
          {
            "case": "SSA/DDS provided interpreter",
            "expected": "Do not impose own-interpreter SSA-795 requirement."
          },
          {
            "case": "Interpreter agrees to sign but signed form unreturned",
            "expected": "Do not make final determination from agreement alone."
          },
          {
            "case": "Interpreter refuses to sign",
            "expected": "Do not use the agreement branch or infer denial."
          },
          {
            "case": "Signature attempts not yet unsuccessful",
            "expected": "Do not automatically invoke H.10 second-interpreter response."
          },
          {
            "case": "Appropriate replacement service available",
            "expected": "Do not infer I.3 unavailability termination condition."
          },
          {
            "case": "Misconduct not established",
            "expected": "Do not make a fraud or qualification finding from selection."
          },
          {
            "case": "eCAT unavailable for a non-eCAT case",
            "expected": "Use source SSA-5002 alternative with SSA-795 exception; no arbitrary substitution."
          },
          {
            "case": "Translation rather than spoken interpretation needed",
            "expected": "Keep linked authorized-translation procedure separate."
          }
        ],
        "exact_source_spans": [
          {
            "id": "DI23040.001:A",
            "start": 200,
            "end": 2004,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "A. \nPolicy for LEP individuals\n\nSocial Security Administration (SSA) is committed to providing fair and equitable service to the American public, regardless of an individual’s ability to communicate effectively in English.\n\nWe recognize that using qualified interpreters, including bilingual staff who can communicate directly with claimants in their primary language, efficiently facilitates our processes, deters fraud, and assures that we do not disadvantage individuals with limited English proficiency (LEP).\n\nDisability determination services (DDS) will provide an interpreter (free of charge) to any individual requesting language assistance, or when it is evident that such assistance is necessary to ensure that the individual is not disadvantaged.\n\nNOTE: DDS will not require individuals needing language assistance to provide their own interpreters.\n\nIndividuals have the option of using their own interpreter, such as a family member, friend, or third party, if the interpreter meets SSA criteria as a qualified interpreter. For more information regarding qualified interpreter, see DI 23040.001B.3.\n\nThe DDS must first review the claims folder for documentation of a qualified interpreter approved by the field office (FO) prior to obtaining information about the individual’s interpreter, see DI 23040.001C.1. For information on documentation requirements when using an interpreter, see DI 23040.001G and DI 23040.001H.\n\nA minor child (under age 18) cannot serve as a qualified interpreter due to the nature and complexities of the disability determination process. For more information regarding when a minor child may assist with interpretation, see DI 23040.001E.5.\n\nSpecial handling procedures apply to claims for LEP individuals, see DI 23007.005C, DI 22510.016A and DI 28075.005F.3.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:B3",
            "start": 2501,
            "end": 3707,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "A qualified interpreter is an individual or vendor who is able to read and speak fluently in English and the language or dialect of the individual needing language assistance, and who meets the following criteria;\n\n•\n\nProvides an accurate interpretation of questions and responses by both the LEP individual and the DDS staff member (usually a disability examiner (DE)); i.e., does not self-initiate follow-up questions or infer facts or dates not provided by the individual or the DDS employee;\n\n•\n\nDemonstrates familiarity with basic terminology used in the disability determination process, including medical and social welfare terminology when necessary;\n\n•\n\nHas knowledge of and experience in applying the protocols and procedures for delivering interpreter services;\n\n•\n\nAgrees to comply with SSA's disclosure and confidentiality of information requirements, see GN 03301.004; and\n\n•\n\nHas no personal stake in the outcome of the case that would create a conflict of interest. An individual who is a potential or actual claimant or beneficiary on the same record as the individual needing language assistance can act as a qualified interpreter, providing that there is no other conflict of interest.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:B45",
            "start": 3707,
            "end": 4302,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "4. \nTranslator\n\nA translator is an individual who can read and write English and another language and can accurately translate written material from one language to another.\n\nNOTE: For translation of foreign language documents, see DI 23045.001.\n\n5. \nAuthorized Translator\n\nAn authorized translator is a translator who SSA certifies through an official authorization process and accurately translates written documents and evidence from a non-English language into English. For additional information, see GN 00301.340.\n\nNOTE: This definition is not applicable to non-SSA translation services.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:B6",
            "start": 4302,
            "end": 5479,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "6. \nTelephone Interpreter Service (TIS)\n\nSSA has a nationwide Blanket Purchase Agreement with a private company, Language Select, for TIS in more than 120 languages and dialects. TIS is accessible to all SSA and if authorized, DDS public contact employees. Interpreters are available immediately, 24 hours a day and 7 days a week. The instructions for this service are accessible on the intranet through the Multilanguage Resources page.\n\nThe DDSs may use the service provided they are not charged for the same service through a State contracted interpreter service or Indirect Cost Agreement. The DDS would need to adjust those agreements prior to participating in the SSA contract to ensure SSA does not pay both providers for the same service. DDS staff must ensure that they have authorization from their State prior to using SSA’s TIS. To obtain a Language Select telephone interpreter see instructions in GN 00203.011. Third-party vendors and Consultative Examination (CE) providers cannot request service from the SSA provided TIS.\n\nNOTE: Upon contacting TIS, you must provide your three-digit State Agency or Detailed Office/Organization Resource System (DOORS) code.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:C",
            "start": 5479,
            "end": 8949,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "C. \nProcedure – Identifying the need for an interpreter\n1. \n\nReview the claims folder for a foreign language indicator. If a foreign language indicator does not exist, determine if an interpreter or sign language interpreter is needed by reviewing the following documents in the claims folder:\n\n•\n\nDisability Report-Adult (SSA-3368-BK);\n\n•\n\nReport of Contact (SSA-5002);\n\n•\n\nStatement of Claimant or Other Person (SSA-795);\n\n•\n\nRemarks in eView for electronic cases or on the Disability Transmittal Sheet for paper folders; or\n\n•\n\nAny forms or documents that may indicate an interpreter is required.\n\nNOTE: If a sign language interpreter is necessary, follow the instructions in GN 00203.012.\n\n2. \n\nInform the individual that the DDS will provide interpreter services free of charge.\n\n3. \n\nAssure the individual that the DDS will provide him or her with service equal to that provided to individuals who are fluent in English.\n\n4. \n\nExplain to the individual that SSA may have materials (i.e., pamphlets, publications, or other materials) in his or her language by accessing the Multilanguage Gateway on the internet.\n\n5. \n\nBe alert to the language needs of any individual having difficulty understanding, hearing or speaking English, and be sensitive to the cultural differences that could adversely affect communication with the individual.\n\n6. \n\nDetermine whether the individual wants further communication in English, or another language, including sign language. If the individual does not want additional communication conducted in English, determine and document which language he or she prefers.\n\nPrior to scheduling additional communication, CE, or contacting the claimant by telephone, do the following:\n\n•\n\nObtain interpreter services through the State-contracted interpreter service, or SSA TIS if authorized.\n\n•\n\nExplain that the individual may bring his or her own interpreter during contact with the DDS, or during CEs, provided SSA or DDS has approved him or her as a qualified interpreter. For more information on qualified interpreters and the approval process, see DI 23040.001B.3 and DI 23040.001H in this section. If SSA or DDS has not approved the claimant’s interpreter, he or she may participate during the claimant contact or CE, but the official interpretation will be that of an SSA or DDS provided interpreter.\n\n7. \n\nDocument all LEP actions, except for actions requiring the use of a SSA Form 795, using the electronic claims analysis tool (eCAT) in the section titled “Claim communication.” For non-eCAT claims, use a SSA Form 5002 to document all LEP actions, except when a SSA-795 is required.\n\n8. \n\nProvide an interpreter whenever it is difficult to understand the individual, or when it is evident that language assistance is required to ensure that the individual is not disadvantaged, even if the individual does not request an interpreter.\n\n9. \n\nUse the following options when you do not know the language for which assistance is required:\n\n•\n\nThe TIS, which employs trained operators who can identify key words in foreign languages and effectively determine the language for which assistance is required, is accessible only if approved by your DDS, or\n\n•\n\nThe State-contracted interpreter service, if not authorized to use TIS, for assistance in identifying the language for which interpreter services is required.\n\n10. \n\nFor situations involving the use of an individual’s own interpreter, follow instructions in DI 23040.001E.4.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:D",
            "start": 8949,
            "end": 10446,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "D. \nQualified Interpreter Sources\n\nIn priority order, the DDS will accept the following list of qualified interpreters if they satisfy the requirements outlined in DI 23040.001B.3:\n\n1. \n\nDDS bilingual employees including bilingual CE providers, and\n\n•\n\nEmployees of the Veterans Administration Regional Office in Manila,\n\n•\n\nU.S. Military Consular Officers,\n\n•\n\nOfficials of foreign government liaison agencies, and\n\n•\n\nDesignated employees of the Federal Benefits Unit of a U.S. Foreign Service Post, who are fluent in the language that needs interpretation;\n\n2. \n\nOther bilingual State employees;\n\n3. \n\nSSA bilingual field office (FO) employees, see DI 23040.001E.2;\n\n4. \n\nNon-DDS interpreters in the community who have an agreement with the DDS to provide interpretations and who do not charge a fee for interpreter services, for example:\n\n•\n\nmembers of church groups,\n\n•\n\nuniversity employees or students,\n\n•\n\nemployees of other Federal, State or local agencies,\n\n•\n\nethnic social service agencies, or\n\n•\n\nmembers of advocacy groups.\n\n5. \n\nEmployees of vendors contracted by the DDS to provide interpreter services. This category also includes all interpreters working for the nationwide SSA TIS; and\n\n6. \n\nNon-DDS interpreters in the community who charge a fee for interpreter services; for example:\n\n•\n\nmembers of church groups,\n\n•\n\nuniversity employees or students,\n\n•\n\nemployees of other Federal, State or local agencies, ethnic social service agencies, or\n\n•\n\nmembers of advocacy groups\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:E1",
            "start": 10517,
            "end": 11154,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Whenever there is a foreign language indicator on a claim or the DDS has reason to believe an individual has LEP, any notice that requires the individual to contact the DDS regarding his or her claim (for example, additional claimant contact or a CE) must include the following statement:\n\n“We provide free interpreter services to conduct your Social Security business. However, if you prefer to have your own interpreter, you may do so, but with the understanding that our own interpreter may be present.”\n\nNOTE: Under no circumstances should any notice to individuals contain language requiring them to provide their own interpreter.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:E3",
            "start": 12176,
            "end": 12837,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "3. \nNeed for interpreter discovered during claimant contact or CE\n\nThe DDS will perform the following actions:\n\n•\n\nContact the TIS or State-contracted interpreter service immediately to continue the claimant contact or CE with the LEP individual.\n\n•\n\nReschedule the claimant contact or CE if a qualified interpreter is not readily available.\n\n•\n\nInform the claimant that we will notify him or her as to when we will continue the claimant contact or CE\n\n•\n\nTake action to have the claimant contact or CE rescheduled;\n\n•\n\nArrange to have a qualified interpreter present at the rescheduled appointment, see DI 23040.001D;\n\n•\n\nAdd a LEP flag to the claims folder.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:E4",
            "start": 12837,
            "end": 13401,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "4. \nUse of individual’s own interpreter\n\nThough the individual is aware that the DDS will provide a qualified interpreter, he or she has the option of providing his or her own interpreter during additional contact with DDS or during a CE. However, the DE or other DDS staff member should defer to the interpreter signed SSA-795, if included in the disability claims folder, prior to determining whether the individual’s own interpreter is qualified per DI 23040.001B.3. The DDS staff must adhere to the SSA guidelines provided in DI 23040.001H and DI 23040.001I.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:E5",
            "start": 13401,
            "end": 14812,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "5. \nUse of a minor child interpreter\n\nA minor child can never serve as a qualified interpreter. When an individual insists on having a minor child interpret for him or her during contact with DDS or during a CE, he or she may do so, but the DDS must also provide a qualified interpreter. In this situation, the qualified interpreter's rendition is the official interpretation of the contact or examination.\n\nIn the individual’s preferred language and with the assistance of a qualified interpreter, the DDS staff must take the following actions:\n\n•\n\nExplain that the disability process may involve complex and sensitive matters relating to medical and other issues discussed during the disability application process.\n\n•\n\nAdvise the individual that the DDS cannot use a minor child (under age 18) as a qualified interpreter and that we must obtain the services of either a State-contracted interpreter service or TIS.\n\n•\n\nExplain that we will use a minor child only to:\n\na. \n\nidentify the language the individual speaks;\n\nb. \n\ninterpret the general purpose of the telephone call or examination; and\n\nc. \n\nassist in rescheduling a future appointment if the business cannot be completed that day without the assistance of a qualified interpreter.\n\n•\n\nDirect all questions to the individual requiring language assistance.\n\n•\n\nDocument all actions in the file, see DI 23040.001C.7. for documentation instructions.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H13",
            "start": 16406,
            "end": 16916,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "H. \nAdditional actions to take when the individual prefers to use his or her own interpreter\n\nThe DE or Other DDS staff member must:\n\n1. \n\nExplain that the DDS will provide a qualified interpreter at no cost to assist him or her in conducting business with the DDS, so he or she is not disadvantaged.\n\n2. \n\nIdentify the interpreter and determine his or her qualifications before conducting claimant contact or scheduling the CE.\n\n3. \n\nExplain that the DDS only pays for interpreter services it provides.\n\n4. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H4",
            "start": 16916,
            "end": 17725,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "When the claimant provides his or her own interpreter, the DDS must have the claimant sign a SSA-795 with the following statement included:\n\n“Social Security Administration has offered an interpreter free of charge to me. However, I have chosen to provide my own interpreter. I understand that the interpreter I provide must be a qualified interpreter as defined by SSA. However, if SSA does not deem my interpreter as qualified, SSA will provide an interpreter free of charge to me.”\n\n“The claimant contact or CE was conducted in (state language) which is my preferred language. This statement was read to me in (state language). I understand it.”\n\nThe statement should also include any additional actions taken to ensure his or her understanding of material covered during the claimant contact or CE.\n\n5. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H5",
            "start": 17725,
            "end": 18003,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Make appropriate annotation(s) on the SSA-795 to identify the preferred spoken and written language of the individual and to issue foreign language notices, if available. Currently, only English and Spanish notices are systems generated for Title II and Title XVI claims.\n\n6. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H6",
            "start": 18003,
            "end": 19382,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Determine if the FO obtained a previous SSA-795 specifying use of the individual’s own interpreter. If an SSA-795 was not obtained at the FO, or if the interpreter is a different individual than was used previously, before conducting claimant contact or scheduling the CE, obtain an SSA-795 from the individual's own interpreter with the following statements and information:\n\n•\n\n“I am acting as an interpreter for (individual's name) to provide accurate communication between (individual's name) and DDS”;\n\n•\n\n“I can read, speak and understand English and (language), which is the language or dialect of (individual's name)”;\n\n•\n\n“Although Social Security Administration has offered (individual’s name) an interpreter free of charge to him or her, (individual’s name) chooses me to serve as his or her interpreter.”\n\n•\n\nInterpreter's name, address and telephone number;\n\n•\n\nRelationship, if any, of the interpreter to the individual (For example, son, mother, friend, minister);\n\n•\n\nAny relevant comments that the interpreter wishes to include; and\n\n•\n\nAny relevant comments the DDS staff deems necessary to document over the interpreter's signature.\n\nNOTE: Interpreters that SSA or DDS provides do not have to sign a SSA-795. In addition, a second SSA-795 is only necessary if the individual’s own interpreter is different from the interpreter previously used at the FO.\n\n7. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H7",
            "start": 19382,
            "end": 19741,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Remind interpreters that SSA policy prohibits them from disclosing any Social Security Number or other personal information they have obtained during the agency proceedings without SSA's permission. Annotate the SSA-795 to show that the interpreter received this reminder. For additional information about disclosure, see GN 03301.004 and GN 03325.000.\n\n8. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H9",
            "start": 20043,
            "end": 20965,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Take the following actions when the DDS conducts claimant contact by telephone with the individual’s own interpreter and a qualified interpreter source is not readily available:\n\n•\n\nExplain the LEP policy and procedures as outlined in this subsection, including the need for a signed SSA-795;\n\n•\n\nTerminate the claimant contact if the interpreter states that he or she will not sign the SSA-795 and follow the procedures in DI 23040.001I.3; or\n\n•\n\nContinue the claimant contact and proceed without the signed SSA-795 if the interpreter agrees to sign the SSA-795;\n\n•\n\nMail the SSA-795 to the interpreter's address and the applicable disability forms or materials to the individual’s address; or\n\n•\n\nMail the SSA-795 with any applicable disability forms or materials if the interpreter and the individual have the same address.\n\n•\n\nDo not make a final determination until the interpreter returns the signed SSA-795.\n\n10. \n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:H10",
            "start": 20965,
            "end": 21399,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "Take the following actions when attempts to obtain the interpreter's signed SSA-795 are unsuccessful:\n\n•\n\nLocate a second interpreter using the qualified interpreter listing found in DI 23040.001D;\n\n•\n\nNotify the FO, if appropriate, that the claimant contact or CE is being repeated with a second interpreter; and\n\n•\n\nReschedule the individual with a second interpreter to verify the information obtained at the prior contact or CE.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          },
          {
            "id": "DI23040.001:I",
            "start": 21399,
            "end": 22917,
            "offset_units": "UTF-16 code units in exact UTF-8-decoded main text; end exclusive",
            "exact_text": "I. \nActions to take when DDS is not satisfied with the claimant-provided interpreter\n1. \n\nThe DE or other DDS staff member must take the following actions when it appears the interpreter:\n\n•\n\nIs not acting in the individual’s best interest; or\n\n•\n\nIs not providing accurate information to the DDS staff; or\n\n•\n\nIs engaging in fraudulent activity.\n\n2. \n\nRemind the individual needing language assistance that the DDS will provide free interpreter service to ensure the individual is not disadvantaged.\n\n3. \n\nAfter determining that the services of a qualified interpreter are necessary:\n\n•\n\nTerminate the claimant contact or CE if the appropriate interpreter service is not available;\n\n•\n\nInform the individual that the DDS will provide a qualified interpreter at the time of his or her rescheduled appointment; and\n\n•\n\nDocument the file stating the reason DDS terminated the communication or examination. See DI 23040.001C.7 for documentation instructions.\n\n4. \n\nBefore conducting the claimant contact or CE, explain that the appropriate interpreter service must be obtained before the contact or examination can continue. The individual and his or her own interpreter can remain (upon request) during the claimant contact or exam; however, DDS will direct all questions to the individual and he or she must provide all responses in his or her own preferred language.\n\n5. \n\nIf DDS suspects fraud at any time during the contact, CE or development of the disability determination, follow the procedures in GN 04111.035.\n\n",
            "whole_sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32"
          }
        ],
        "step_source_span_refs": {
          "dds-language-preference-source-1": [
            "DI23040.001:C"
          ],
          "dds-language-preference-source-2": [
            "DI23040.001:A",
            "DI23040.001:B6",
            "DI23040.001:C"
          ],
          "dds-language-preference-source-3": [
            "DI23040.001:C",
            "DI23040.001:E1"
          ],
          "dds-own-interpreter-source-1": [
            "DI23040.001:A",
            "DI23040.001:E4"
          ],
          "dds-own-interpreter-source-2": [
            "DI23040.001:B3",
            "DI23040.001:B45",
            "DI23040.001:C"
          ],
          "dds-interpreter-mid-contact-source-1": [
            "DI23040.001:B6",
            "DI23040.001:E3"
          ],
          "dds-interpreter-mid-contact-source-2": [
            "DI23040.001:E3"
          ],
          "dds-interpreter-mid-contact-source-3": [
            "DI23040.001:D",
            "DI23040.001:E3"
          ],
          "dds-interpreter-mid-contact-source-4": [
            "DI23040.001:E3"
          ],
          "dds-minor-participation-source-1": [
            "DI23040.001:A",
            "DI23040.001:E5"
          ],
          "dds-minor-participation-source-2": [
            "DI23040.001:E5"
          ],
          "dds-minor-participation-source-3": [
            "DI23040.001:C",
            "DI23040.001:E5"
          ],
          "dds-own-interpreter-paperwork-source-1": [
            "DI23040.001:A",
            "DI23040.001:E4",
            "DI23040.001:H13"
          ],
          "dds-own-interpreter-paperwork-source-2": [
            "DI23040.001:H4"
          ],
          "dds-own-interpreter-paperwork-source-3": [
            "DI23040.001:H6",
            "DI23040.001:H9"
          ],
          "dds-own-interpreter-paperwork-source-4": [
            "DI23040.001:H5",
            "DI23040.001:H7"
          ],
          "dds-interpreter-signature-pending-source-1": [
            "DI23040.001:H6",
            "DI23040.001:H9"
          ],
          "dds-interpreter-signature-pending-source-2": [
            "DI23040.001:H9",
            "DI23040.001:I"
          ],
          "dds-interpreter-signature-pending-source-3": [
            "DI23040.001:H9"
          ],
          "dds-interpreter-signature-pending-source-4": [
            "DI23040.001:H10"
          ],
          "dds-interpreter-replacement-source-1": [
            "DI23040.001:I"
          ],
          "dds-interpreter-replacement-source-2": [
            "DI23040.001:C",
            "DI23040.001:I"
          ],
          "dds-interpreter-replacement-source-3": [
            "DI23040.001:I"
          ]
        }
      }
    },
    "source_reviews": {
      "SSI7": {
        "package_sha256": "4528fcfbb70ea0bad441cfb1012de5cdf2ae1e1f78bae16839a940b925cbbdbb",
        "full_primary_semantic_peer_sha256": "be0faae29613a5ca324821e5dec9efaa4bb81a025fd064d6eadd8a6e2683e748"
      },
      "interpreter7": {
        "package_sha256": "320566fc4f848dc18d6ea5f365a1c7913cb621061b11e0ecef772fdd05a21b78",
        "full_primary_semantic_peer_sha256": "8fe8d77ce1aab24d73bd06c5eba15b20ef18892696d28927431f99b01a2442da"
      }
    },
    "public_capture_provenance": [
      {
        "url": "/service/sources/r33-SSI7-SI00502.142-main.txt",
        "sha256": "7aff85a356bdf738661448a92fad1c7280493c92b02c1f374206215d93fb127b",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r33-SSI7-SI00502.142-body-rendered.html.txt",
        "sha256": "1cf14e3f3cda827f142d2c1eea9f03dd6d01cbac09033f99b3ccc02cf958f515",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r33-interpreter7-DI23040.001-main.txt",
        "sha256": "e4d435835e356779187f8b4e70492612ec736ba559b0cbe917d5b4e60d36bf32",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      },
      {
        "url": "/service/sources/r33-interpreter7-DI23040.001-body-rendered.html.txt",
        "sha256": "787afe9061e9873d52ddb0cead6b1feb22767fcea6352c748a5ccf4a73a086d9",
        "type": "Actual @Browser rendered main/body/DOM/links/tables; not raw HTTP"
      }
    ],
    "limits": [
      "SSI status, historical residence, current lawful presence and every other eligibility factor remain separate findings. No case eligibility or payment outcome is established.",
      "DDS interpreter qualifications, prior statements, permission, pending signatures and no-final-determination restrictions remain source-conditioned. No language service or completed signature is inferred.",
      "All linked-target and publisher-locator holds remain; no automatic successful rejoin or native acceptance."
    ],
    "no_native_acceptance_or_new_links": true
  },
  "next13_ecdr_wu_iar": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "THIRTEEN_SELECTED_SOURCE_SEQUENCES_REVIEWED_NO_CASE_FINDING",
    "checked_on": "2026-11-01",
    "selected_flow_count": 13,
    "card_count": 38,
    "flows": {
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-xvi-before-initiation": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-xvi-before-initiation",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-xvi-before-initiation",
        "entry_conditions": [
          "An eCDR cessation hearing appeal is being prepared.",
          "The case is Title XVI-only or concurrent.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-xvi-before-initiation-source-step-1",
            "title": "Update the SSI record before starting EDCS",
            "kind": "ssa",
            "actor": "FO claims specialist",
            "action": "For a Title XVI-only or concurrent case, use MSSICS to update the SSI record (SSID) to document the medical cessation appeal and the benefit-continuation election when applicable, before initiating the eCDR appeal in EDCS. This order is before initiation, not merely before transfer, and does not establish an approved election.",
            "conditions": [
              "An eCDR cessation hearing appeal is being prepared.",
              "The case is Title XVI-only or concurrent.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.1 IMPORTANT",
            "source_context_refs": [
              "DI81010.257:B-intro",
              "DI81010.257:B1"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-direct-ssr": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-direct-ssr",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-direct-ssr",
        "entry_conditions": [
          "The .257B.1 Title XVI/concurrent preparation instruction applies.",
          "A Direct SSR update is required.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-direct-ssr-source-step-1",
            "title": "Enter the required fields under the Direct SSR condition",
            "kind": "ssa",
            "actor": "FO",
            "action": "When a Direct SSR update is required, the FO can manually enter the required fields in EDCS on the CDR Information and Claims Information pages. This conditional entry provision does not authorize bypassing every mainframe update or promise EDCS-to-SSR synchronization.",
            "conditions": [
              "The .257B.1 Title XVI/concurrent preparation instruction applies.",
              "A Direct SSR update is required.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.1 IMPORTANT",
            "source_context_refs": [
              "DI81010.257:B1"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-missing-827-3881": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-missing-827-3881",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-missing-827-3881",
        "entry_conditions": [
          "An eCDR cessation hearing is being prepared for the hearing office.",
          "SSA-827 has not yet been obtained, or the applicable SSI-childhood SSA-3881 has not yet been obtained.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-missing-827-3881-source-step-1",
            "title": "Keep the specified form requirements",
            "kind": "ssa",
            "actor": "FO",
            "action": "The source calls for one SSA-827 and, for an SSI childhood disability claim, an SSA-3881. Keep those applicability limits and the separate hearing-request requirements; this missing-form instruction does not waive the claimant-signed HA-501 or signed written hearing request.",
            "conditions": [
              "An eCDR cessation hearing is being prepared for the hearing office.",
              "SSA-827 has not yet been obtained, or the applicable SSI-childhood SSA-3881 has not yet been obtained.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact.",
              "SSA-3881 applies only when the hearing request is for an SSI childhood disability claim."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.1 forms bullet",
            "source_context_refs": [
              "DI81010.257:B1"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          },
          {
            "id": "ecdr-cessation-hearing-evidence-missing-827-3881-source-step-2",
            "title": "Do not hold the hearing solely for these missing forms",
            "kind": "ssa",
            "actor": "FO",
            "action": "Do not delay sending the eCDR hearing to the hearing office in order to obtain SSA-3881 or SSA-827. If an SSA-827 is provided, the source separately calls for faxing it to the CEF. This does not establish that all other transfer conditions are satisfied, promise completed receipt, or create a general no-follow-up rule for every missing hearing document.",
            "conditions": [
              "An eCDR cessation hearing is being prepared for the hearing office.",
              "SSA-827 has not yet been obtained, or the applicable SSI-childhood SSA-3881 has not yet been obtained.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.1 forms NOTE and SSI-only note",
            "source_context_refs": [
              "DI81010.257:B1",
              "DI81010.257:B2"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-paper-cpd": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-paper-cpd",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-paper-cpd",
        "entry_conditions": [
          "The eCDR cessation determination used a paper CPD folder.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-paper-cpd-source-step-1",
            "title": "Keep the paper comparison folder with relevant documents",
            "kind": "ssa",
            "actor": "FO",
            "action": "For a cessation determination made using a paper comparison-point decision (CPD) folder, place the SSA-827 and relevant documents, including submitted medical evidence, in that folder as available. Keep the separate no-delay instruction for a missing SSA-827 or applicable SSA-3881; this card does not make obtaining those missing forms a new transfer prerequisite.",
            "conditions": [
              "The eCDR cessation determination used a paper CPD folder.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 A; B.1 no-delay; B.3 paper CPD",
            "source_context_refs": [
              "DI81010.257:A",
              "DI81010.257:B1",
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          },
          {
            "id": "ecdr-cessation-hearing-evidence-paper-cpd-source-step-2",
            "title": "Attach the EDCS routing form",
            "kind": "ssa",
            "actor": "FO",
            "action": "Print an EDCS routing form and attach it to the top of the paper CPD folder. Do not treat a routing form as proof that the folder or its contents were received.",
            "conditions": [
              "The eCDR cessation determination used a paper CPD folder.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.3 paper CPD",
            "source_context_refs": [
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          },
          {
            "id": "ecdr-cessation-hearing-evidence-paper-cpd-source-step-3",
            "title": "Send the paper folder to the hearing office",
            "kind": "ssa",
            "actor": "FO",
            "action": "Send the paper folder to the hearing office. The transfer instruction separately calls for mailing associated paper folders at the time of electronic transfer. Sending is not a finding that transfer or receipt occurred.",
            "conditions": [
              "The eCDR cessation determination used a paper CPD folder.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.2; B.3",
            "source_context_refs": [
              "DI81010.257:B2",
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents",
        "entry_conditions": [
          "The CPD folder is a CEF.",
          "Paper documents or forms are being sent.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents-source-step-1",
            "title": "Attach the routing form to the relevant paper documents",
            "kind": "ssa",
            "actor": "FO",
            "action": "When the CPD folder is electronic and paper documents or forms are being sent, attach the EDCS routing form to the relevant documents, including submitted medical evidence. A paper-folder indicator default of No applies when an electronic CPD is linked; that conditional default does not eliminate this paper-document route.",
            "conditions": [
              "The CPD folder is a CEF.",
              "Paper documents or forms are being sent.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.2 PFI note; B.3 CEF CPD",
            "source_context_refs": [
              "DI81010.257:B2",
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          },
          {
            "id": "ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents-source-step-2",
            "title": "Mail those documents to the hearing office",
            "kind": "ssa",
            "actor": "FO",
            "action": "Mail the relevant paper documents with the routing form to the hearing office. This is a source routing instruction, not a finding of successful mailing, scanning or office receipt.",
            "conditions": [
              "The CPD folder is a CEF.",
              "Paper documents or forms are being sent.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.3 CEF CPD",
            "source_context_refs": [
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-no-paper-documents": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "ecdr-cessation-hearing-evidence-no-paper-documents",
        "full_route": "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-no-paper-documents",
        "entry_conditions": [
          "The eCDR hearing routing instruction applies.",
          "No paper documents or forms are being sent.",
          "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
        ],
        "steps": [
          {
            "id": "ecdr-cessation-hearing-evidence-no-paper-documents-source-step-1",
            "title": "Do not print an unnecessary routing form",
            "kind": "ssa",
            "actor": "FO",
            "action": "Do not print an EDCS routing form when no paper documents or forms are being sent. This condition does not establish whether a paper folder exists or waive the separate requirement to send an associated paper folder. It also does not settle missing-form or hearing-request requirements.",
            "conditions": [
              "The eCDR hearing routing instruction applies.",
              "No paper documents or forms are being sent.",
              "The selected eCDR cessation ALJ-hearing preparation/routing scope must apply; choosing this illustration establishes neither the hearing stage nor any case fact."
            ],
            "source": "ecdr_DI81010_257",
            "section": "DI81010.257 B.3 last paragraph; B.2",
            "source_context_refs": [
              "DI81010.257:B2",
              "DI81010.257:B3"
            ],
            "qualifications": [
              "This is selected FO preparation and routing for an eCDR cessation ALJ-hearing appeal, not adult initial intake, a completed phone/online filing, an initial medical-cessation reconsideration/DHO hearing, or a benefit/appeal-merits decision.",
              "Good-cause and statutory benefit continuation requests retain their own source conditions. The source calls for a claimant-signed SSA-792 for a continuation request; these cards do not decide good cause, timeliness, benefit continuation or eligibility.",
              "Linked targets retain their exact existing source objects and historical unreviewed-link status in this journey. These cards use the .257 instruction itself without silently expanding a linked target or changing its source review flag.",
              "No actual record update, valid consent, evidence sufficiency, electronic transfer, hearing-office receipt, decision or successful return is established.",
              "B.4 decision-alert/master-record follow-up remains outside these six sequences. Its 5 versus 3-5 day wording is not reconciled into a uniform clock or SLA. Native observations, all fourteen typed relationship scopes and other source holds remain unchanged."
            ]
          }
        ],
        "rejoin": {
          "status": "not_established",
          "automatic_transition": false,
          "unknowns": [
            "Actual hearing applicability, record/evidence preparation, transfer, receiving-office action and completed outcome remain unverified."
          ]
        }
      },
      "apply-disability/initial-wu-representative-time": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "initial-wu-representative-time",
        "full_route": "apply-disability/initial-wu-representative-time",
        "entry_conditions": [
          "The claimant has an appointed representative (AR).",
          "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
          "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
          "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
        ],
        "steps": [
          {
            "id": "initial-wu-representative-time-1",
            "title": "Involve the appointed representative",
            "kind": "action",
            "actor": "DDS",
            "action": "Make a reasonable effort to involve the AR under linked DI23007.005A. Its detailed reasonable-effort criteria are not captured here.",
            "conditions": [
              "The claimant has an appointed representative (AR).",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C1",
            "source_context_refs": [
              "DI23005.001:C1"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "initial-wu-representative-time-2",
            "title": "Allow requested locating time",
            "kind": "action",
            "actor": "DDS",
            "action": "When the AR requests more time to locate the claimant, allow a MINIMUM of 10 ADDITIONAL CALENDAR days. This conditional minimum is not an overall decision deadline.",
            "conditions": [
              "The claimant has an appointed representative (AR).",
              "AR requests more time to locate claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C1",
            "source_context_refs": [
              "DI23005.001:C1"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "initial-wu-representative-time-3",
            "title": "Confirm contact details before changing DCPS",
            "kind": "action",
            "actor": "DDS",
            "action": "An AR-provided address or telephone number cannot be used to change claimant personal information in DCPS without first confirming with the claimant that it is current and reachable, UNLESS the AR is a parent of a minor child OR a legal guardian. This exception does not make all ARs guardians.",
            "conditions": [
              "The claimant has an appointed representative (AR).",
              "AR provides updated claimant contact information.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C1",
            "source_context_refs": [
              "DI23005.001:C1"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "initial-wu-representative-time-4",
            "title": "Document the efforts",
            "kind": "action",
            "actor": "DDS",
            "action": "Document the case file under C.4: locating efforts in a DCPS Case Note OR on the Case Development Worksheet (CDW), preserving those alternatives.",
            "conditions": [
              "The claimant has an appointed representative (AR).",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C1, C4",
            "source_context_refs": [
              "DI23005.001:C1",
              "DI23005.001:C4"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "initial-wu-representative-time-5",
            "title": "If still unknown, evaluate evidence under D",
            "kind": "action",
            "actor": "DDS",
            "action": "After involving the AR, if whereabouts remain unknown, develop and evaluate the claim and make the disability determination under D; do not decide unfavorably solely due to WU. Full D evidence/notice instructions remain required, not replaced by this contact card.",
            "conditions": [
              "The claimant has an appointed representative (AR).",
              "Whereabouts remain unknown after AR involvement.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C1, D",
            "source_context_refs": [
              "DI23005.001:C1",
              "DI23005.001:D"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant location, contact confirmation, reasonable effort sufficiency and completed response periods are not established.",
            "Source-directed subsequent evidence review/notice/FO-or-DQB routing is an instruction, not proof of successful case continuation or entitlement."
          ]
        }
      },
      "apply-disability/initial-wu-search-alternatives": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "initial-wu-search-alternatives",
        "full_route": "apply-disability/initial-wu-search-alternatives",
        "entry_conditions": [
          "No AR AND special handling does not apply.",
          "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
          "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
          "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
        ],
        "steps": [
          {
            "id": "initial-wu-search-alternatives-1",
            "title": "Postmaster request alternative",
            "kind": "action",
            "actor": "DDS",
            "action": "Mail SSA-L2001 (Address Information Request) to the postmaster and allow 15 CALENDAR days to respond. This is one locating alternative, not a required action in every case.",
            "conditions": [
              "No AR AND special handling does not apply.",
              "DDS selects the postmaster action.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C3",
            "source_context_refs": [
              "DI23005.001:C3"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "at-least-one-locating-action"
          },
          {
            "id": "initial-wu-search-alternatives-2",
            "title": "Third-party contact alternative",
            "kind": "action",
            "actor": "DDS",
            "action": "Make a reasonable effort to involve a third party provided by claimant or another appropriate individual, such as a legal guardian, following C.2. Detailed special-contact rules linked in C.2 remain separately held.",
            "conditions": [
              "No AR AND special handling does not apply.",
              "DDS selects the third-party/appropriate-individual action.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C3, C2",
            "source_context_refs": [
              "DI23005.001:C3",
              "DI23005.001:C2"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "at-least-one-locating-action"
          },
          {
            "id": "initial-wu-search-alternatives-3",
            "title": "FO assistance alternative and conditional follow-up",
            "kind": "action",
            "actor": "DDS",
            "action": "Send an FO assistance request through DCPS and allow 15 CALENDAR days. ONLY if FO has not responded after those 15 days, send a follow-up message and allow 10 CALENDAR days. DDS retains FULL jurisdiction while FO attempts to locate claimant. These extra 10 days do not attach to the postmaster/third-party alternatives.",
            "conditions": [
              "No AR AND special handling does not apply.",
              "DDS selects FO assistance; follow-up applies only if FO does not respond after 15calendar days.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C3",
            "source_context_refs": [
              "DI23005.001:C3"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "at-least-one-locating-action"
          },
          {
            "id": "initial-wu-search-alternatives-4",
            "title": "Document locating efforts",
            "kind": "action",
            "actor": "DDS",
            "action": "Document all C.3 locating efforts in a DCPS Case Note OR on the CDW.",
            "conditions": [
              "No AR AND special handling does not apply.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C4",
            "source_context_refs": [
              "DI23005.001:C4"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "initial-wu-search-alternatives-5",
            "title": "After at least one action, proceed if still unknown",
            "kind": "action",
            "actor": "DDS",
            "action": "If WU remains after AT LEAST ONE listed action, DDS need not make additional locating attempts and MAY proceed with D disability determination. Federal quality reviewers will not cite a deficiency for deferring locating to FO instead of DDS attempting itself; this does not waive documentation or evidence evaluation.",
            "conditions": [
              "No AR AND special handling does not apply.",
              "At least one listed locating action taken, and whereabouts remain unknown.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C3, D",
            "source_context_refs": [
              "DI23005.001:C3",
              "DI23005.001:D"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant location, contact confirmation, reasonable effort sufficiency and completed response periods are not established.",
            "Source-directed subsequent evidence review/notice/FO-or-DQB routing is an instruction, not proof of successful case continuation or entitlement."
          ]
        },
        "alternative_groups": [
          {
            "id": "at-least-one-locating-action",
            "label": "Take at least one of the source locating alternatives",
            "logic": "source_conditions_determine_branch",
            "note": "AT LEAST ONE is required, not all three and not necessarily exactly one. Only the FO-assistance alternative has conditional 15+10calendar-day follow-up and full DDS jurisdiction."
          }
        ]
      },
      "apply-disability/wu-special-handling-contacts": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wu-special-handling-contacts",
        "full_route": "apply-disability/wu-special-handling-contacts",
        "entry_conditions": [
          "Special handling applies; linked DI23007.001A criteria are not inferred.",
          "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
          "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
          "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
        ],
        "steps": [
          {
            "id": "wu-special-handling-contacts-1",
            "title": "Use designated contacts and the conditional second contact",
            "kind": "action",
            "actor": "DDS",
            "action": "Make a reasonable effort to involve designated third-party contacts from the CURRENT level of adjudication, following linked DI23007.010C.\n\nWhen TWO individuals were designated and the first is unproductive, make a reasonable effort to involve the other. This is conditional, not a requirement to invent a second contact.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Claimant designated third-party contact(s).",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2",
            "source_context_refs": [
              "DI23005.001:C2"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "designated-contact-state"
          },
          {
            "id": "wu-special-handling-contacts-3",
            "title": "If claimant elected no contact, use C.3",
            "kind": "action",
            "actor": "DDS",
            "action": "If claimant elected not to designate a third party, take AT LEAST ONE C.3 locating action. The cross-reference applies here despite C.3 opening otherwise describing no AR/no special handling. Keep selected-action timing, FO jurisdiction and documentation limits; do not require all alternatives.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Claimant elected NOT to designate a third-party contact.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2, C3",
            "source_context_refs": [
              "DI23005.001:C2",
              "DI23005.001:C3"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "designated-contact-state"
          },
          {
            "id": "wu-special-handling-contacts-4",
            "title": "Locate contact information and document all efforts",
            "kind": "action",
            "actor": "DDS",
            "action": "Find designated contacts in section2 Contacts of SSA-3368-BK or SSA-3441-BK, or possibly Remarks. Document ALL third-party involvement efforts under C.4 in DCPS Case Note OR CDW.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2, C4",
            "source_context_refs": [
              "DI23005.001:C2",
              "DI23005.001:C4"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant location, contact confirmation, reasonable effort sufficiency and completed response periods are not established.",
            "Source-directed subsequent evidence review/notice/FO-or-DQB routing is an instruction, not proof of successful case continuation or entitlement."
          ]
        },
        "alternative_groups": [
          {
            "id": "designated-contact-state",
            "label": "Designated-contact versus no-designation circumstances",
            "logic": "source_conditions_determine_branch",
            "note": "The no-designation action applies only when claimant elected no contact. Two-contact follow-up applies only after first of two is unproductive; not all cards apply universally."
          }
        ]
      },
      "apply-disability/wu-evidence-notice": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wu-evidence-notice",
        "full_route": "apply-disability/wu-evidence-notice",
        "entry_conditions": [
          "Required C locating actions completed, but unsuccessful in locating claimant.",
          "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
          "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
          "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
        ],
        "steps": [
          {
            "id": "wu-evidence-notice-1",
            "title": "Complete remaining development without a WU-only denial",
            "kind": "action",
            "actor": "DDS",
            "action": "Do NOT make an unfavorable determination solely because whereabouts are unknown. Follow sequential evaluation and complete development not requiring claimant involvement; linked sequential-evaluation details are not newly reviewed.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-2",
            "title": "Assess severe medically determinable impairment",
            "kind": "action",
            "actor": "DDS",
            "action": "Based on evidence in file, determine whether a severe medically determinable impairment (MDI) exists, as discussed in linked DI24505.001; no impairment finding is selected by this illustration.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-3",
            "title": "Assess listing level",
            "kind": "action",
            "actor": "DDS",
            "action": "Determine whether any MDI meets OR equals a listing, based on file evidence. This card does not establish a listing result.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-4",
            "title": "Determine residual functional capacity",
            "kind": "action",
            "actor": "DDS",
            "action": "Determine claimant RFC based on evidence in file; no RFC value or capacity is inferred here.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-5",
            "title": "Review available vocational evidence",
            "kind": "action",
            "actor": "DDS",
            "action": "Review vocational evidence IF AVAILABLE to decide if information suffices for a medical-vocational determination; do not assert vocational evidence always exists or is sufficient.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-6",
            "title": "Consider a closed period",
            "kind": "action",
            "actor": "DDS",
            "action": "Determine whether file evidence suffices to allow a closed period of disability; linked DI25510.001 criteria remain unreviewed, and no closed period is granted by this example.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-7",
            "title": "Explain the effect of WU",
            "kind": "action",
            "actor": "DDS",
            "action": "Include a thorough explanation in the DDE of how WU affects the disability determination.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-8",
            "title": "Complete source-specified SSA-831 entries",
            "kind": "action",
            "actor": "DDS",
            "action": "Put claimant LAST KNOWN address in SSA-831 item5 Name and Address of Claimant, and “Claimant’s whereabouts unknown” in item34 Remarks.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-9",
            "title": "Send appropriate notice",
            "kind": "action",
            "actor": "DDS",
            "action": "Send the appropriate notice to claimant at the LAST KNOWN address. No successful delivery, appeal start date or specific notice template is inferred.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-evidence-notice-10",
            "title": "Route according to Federal-review selection",
            "kind": "action",
            "actor": "DDS",
            "action": "Return case to FO OR, IF selected for Federal review, send to Disability Quality Branch. The conditional alternative is not a universal FO→DQB sequence or a completed receipt.",
            "conditions": [
              "Required C locating actions completed, but unsuccessful in locating claimant.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 D, C-intro",
            "source_context_refs": [
              "DI23005.001:D",
              "DI23005.001:C-intro"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant location, contact confirmation, reasonable effort sufficiency and completed response periods are not established.",
            "Source-directed subsequent evidence review/notice/FO-or-DQB routing is an instruction, not proof of successful case continuation or entitlement."
          ]
        }
      },
      "apply-ssi/iar-state-guardian-signature-conflict": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "iar-state-guardian-signature-conflict",
        "full_route": "apply-ssi/iar-state-guardian-signature-conflict",
        "entry_conditions": [
          "The paper IAR authorization was signed by a State IAR representative who is also the representative payee OR legal guardian for the SSI applicant.",
          "The specified signer conflict is being reviewed; a State contact name or general signer category does not establish a valid applicant-side authorization."
        ],
        "steps": [
          {
            "id": "iar-state-guardian-signature-conflict-source-1",
            "title": "Return the conflicted signature for correction",
            "kind": "action",
            "actor": "FO",
            "action": "Return the paper authorization to the State. Notify the State to obtain an appropriate signature and explain why the original signature was not acceptable.",
            "conditions": [
              "The paper IAR authorization was signed by a State IAR representative who is also the representative payee OR legal guardian for the SSI applicant.",
              "The specified signer conflict is being reviewed; a State contact name or general signer category does not establish a valid applicant-side authorization."
            ],
            "source": "iarforeturn",
            "section": "D.2 second bullet",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "The source identifies a potential conflict of interest. This flow uses the express D.2 return procedure; the original SI02003.005 citation and historical review flags are retained and its full permitted-signer framework is not newly reconstructed.",
              "Published FO procedure only; selecting this example does not establish a valid authorization, completed correction, actual reimbursement/payment, SSI eligibility or a successful case rejoin."
            ]
          },
          {
            "id": "iar-state-guardian-signature-conflict-source-2",
            "title": "Keep the authorization-life rule in force",
            "kind": "action",
            "actor": "FO",
            "action": "When returning the authorization for signatures, advise the State that the 30-day rule for the effective life of the authorization still applies.",
            "conditions": [
              "The paper IAR authorization was signed by a State IAR representative who is also the representative payee OR legal guardian for the SSI applicant.",
              "The specified signer conflict is being reviewed; a State contact name or general signer category does not establish a valid applicant-side authorization."
            ],
            "source": "iarforeturn",
            "section": "D.2 note; D.1",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "The source identifies a 30-calendar-day rule. Returning the form does not itself reset that clock, waive the rule or establish a new correction deadline; no individual timeliness finding is made.",
              "Published FO procedure only; selecting this example does not establish a valid authorization, completed correction, actual reimbursement/payment, SSI eligibility or a successful case rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "The source does not demonstrate that the State obtained a valid corrected authorization, that an exception applies, or that SSA accepted a new form, completed reimbursement or returned this case to its usual path."
          ]
        }
      },
      "apply-ssi/iar-missing-signature-date-return": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "iar-missing-signature-date-return",
        "full_route": "apply-ssi/iar-missing-signature-date-return",
        "entry_conditions": [
          "The paper IAR authorization is missing a required signature OR date from the SSI applicant OR State IAR representative.",
          "The D.2 incomplete-signature/date return applies in both initial-claim AND posteligibility situations, as alternative case contexts."
        ],
        "steps": [
          {
            "id": "iar-missing-signature-date-return-source-1",
            "title": "Return the incomplete form and request the missing information",
            "kind": "action",
            "actor": "FO",
            "action": "Return the paper authorization to the State and notify the State to obtain the missing signatures or dates. This procedure applies to both initial claims and posteligibility situations.",
            "conditions": [
              "The paper IAR authorization is missing a required signature OR date from the SSI applicant OR State IAR representative.",
              "The D.2 incomplete-signature/date return applies in both initial-claim AND posteligibility situations, as alternative case contexts."
            ],
            "source": "iarforeturn",
            "section": "D.2 first bullet",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "A missing signature/date is distinct from a signature supplied by a person with the specified State guardian/payee conflict. The source does not prescribe a new customer notice or an automatic denial of the SSI claim.",
              "Published FO procedure only; selecting this example does not establish a valid authorization, completed correction, actual reimbursement/payment, SSI eligibility or a successful case rejoin."
            ]
          },
          {
            "id": "iar-missing-signature-date-return-source-2",
            "title": "Advise that the existing 30-day rule still applies",
            "kind": "action",
            "actor": "FO",
            "action": "When returning the authorization for signatures, advise the State that the 30-day rule for the effective life of the authorization applies to the returned form.",
            "conditions": [
              "The paper IAR authorization is missing a required signature OR date from the SSI applicant OR State IAR representative.",
              "The D.2 incomplete-signature/date return applies in both initial-claim AND posteligibility situations, as alternative case contexts."
            ],
            "source": "iarforeturn",
            "section": "D.2 note; D.1",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "The 30-calendar-day rule is not restarted or waived by this return. This source supplies no correction-processing turnaround or extension calculation.",
              "Published FO procedure only; selecting this example does not establish a valid authorization, completed correction, actual reimbursement/payment, SSI eligibility or a successful case rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "The source does not demonstrate that the State obtained a valid corrected authorization, that an exception applies, or that SSA accepted a new form, completed reimbursement or returned this case to its usual path."
          ]
        }
      },
      "apply-ssi/iar-second-authorization-pending": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "iar-second-authorization-pending",
        "full_route": "apply-ssi/iar-second-authorization-pending",
        "entry_conditions": [
          "A GR code is already pending on the SSR and SSA receives a subsequent IAR authorization.",
          "Before applying the return rule, distinguish a new initial-claim OR new posteligibility event: D.3 excepts authorizations for those new events."
        ],
        "steps": [
          {
            "id": "iar-second-authorization-pending-source-1",
            "title": "Return only when the new-event exception does not apply",
            "kind": "action",
            "actor": "FO",
            "action": "If the subsequent authorization is for neither a new initial claim nor a new posteligibility event, return it to the State office with a notation that the claimant has already authorized payment to another State IAR agency.",
            "conditions": [
              "A GR code is already pending on the SSR and SSA receives a subsequent IAR authorization.",
              "Before applying the return rule, distinguish a new initial-claim OR new posteligibility event: D.3 excepts authorizations for those new events.",
              "The subsequent authorization is for neither a new initial claim nor a new posteligibility event."
            ],
            "source": "iarforeturn",
            "section": "D.3",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "The pending-GR trigger AND absence of either new-event exception govern the return. D.3 does not say that an excepted form is automatically valid or accepted, does not prescribe a customer notice and does not resolve SSI eligibility or which agency is ultimately paid.",
              "Published FO procedure only; selecting this example does not establish a valid authorization, completed correction, actual reimbursement/payment, SSI eligibility or a successful case rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "The source does not demonstrate that the State obtained a valid corrected authorization, that an exception applies, or that SSA accepted a new form, completed reimbursement or returned this case to its usual path."
          ]
        }
      }
    },
    "original_records": {
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-xvi-before-initiation": {
        "id": "ecdr-cessation-hearing-evidence-xvi-before-initiation",
        "title": "The hearing is Title XVI-only or concurrent",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "Before initiating the eCDR appeal in EDCS, use MSSICS to update SSID with the medical cessation appeal and applicable SBC election. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. The timing is BEFORE EDCS initiation, not merely before transfer. R109_E033 retains its historical broader pretransfer description; it is not silently refreshed.",
        "source": "ecdr_DI81010_257",
        "section": "B.1",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.1",
            "start": 1394,
            "end": 4862,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "59c4304c0ea530b97455eaf72143905feaa7180d3eddc2815c24b5cd4788babc",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "MSSICS",
          "EDCS",
          "Title XVI eCDR Appeal SSR Pretransfer Synchronization"
        ],
        "entity_ids": [
          "APP_MSSICS",
          "APP_EDCS",
          "R109_E033"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "The timing is BEFORE EDCS initiation, not merely before transfer. R109_E033 retains its historical broader pretransfer description; it is not silently refreshed."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "An eCDR cessation hearing appeal is being prepared.",
          "The case is Title XVI-only or concurrent."
        ],
        "condition_logic": "all",
        "when": "An eCDR cessation hearing appeal is being prepared.; The case is Title XVI-only or concurrent.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.1",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_81010_020E_1_",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_135",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_090",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_12027_001",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-direct-ssr": {
        "id": "ecdr-cessation-hearing-evidence-direct-ssr",
        "title": "A Direct SSR update is required",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "The FO can manually enter the required fields in EDCS on the CDR Information and Claims Information pages. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. This conditional entry provision does not authorize bypassing all mainframe updates or create a general EDCS-to-SSR synchronization promise.",
        "source": "ecdr_DI81010_257",
        "section": "B.1",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.1",
            "start": 1394,
            "end": 4862,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "59c4304c0ea530b97455eaf72143905feaa7180d3eddc2815c24b5cd4788babc",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "EDCS",
          "Title XVI eCDR Appeal SSR Pretransfer Synchronization"
        ],
        "entity_ids": [
          "APP_EDCS",
          "R109_E033"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "This conditional entry provision does not authorize bypassing all mainframe updates or create a general EDCS-to-SSR synchronization promise."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "The .257B.1 Title XVI/concurrent preparation instruction applies.",
          "A Direct SSR update is required."
        ],
        "condition_logic": "all",
        "when": "The .257B.1 Title XVI/concurrent preparation instruction applies.; A Direct SSR update is required.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.1",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_81010_020E_1_",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_135",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_090",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_12027_001",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-missing-827-3881": {
        "id": "ecdr-cessation-hearing-evidence-missing-827-3881",
        "title": "SSA-827 or SSA-3881 has not yet been obtained",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "Obtain the specified forms, but do not delay sending the eCDR hearing to the HO to obtain SSA-827 or SSA-3881. If provided, fax SSA-827 into the CEF. Mail other supplied forms, including SSA-3881, to the HO for scanning or contract scanning. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. The source still requires a signed HA-501 or written statement; the no-delay note does not waive that request. The no-delay note does not validate invalid consent, waive authorization for requesting records or extend to all missing forms.",
        "source": "ecdr_DI81010_257",
        "section": "B.1",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.1",
            "start": 1394,
            "end": 4862,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "59c4304c0ea530b97455eaf72143905feaa7180d3eddc2815c24b5cd4788babc",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "EDCS",
          "CEF"
        ],
        "entity_ids": [
          "APP_EDCS",
          "REPO_CEF"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "The source still requires a signed HA-501 or written statement; the no-delay note does not waive that request.",
          "The no-delay note does not validate invalid consent, waive authorization for requesting records or extend to all missing forms."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "An eCDR cessation hearing is being prepared for the hearing office.",
          "SSA-827 has not yet been obtained, or the applicable SSI-childhood SSA-3881 has not yet been obtained."
        ],
        "condition_logic": "all",
        "when": "An eCDR cessation hearing is being prepared for the hearing office.; SSA-827 has not yet been obtained, or the applicable SSI-childhood SSA-3881 has not yet been obtained.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.1",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_81010_020E_1_",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_135",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_81010_090",
            "section": "Linked cross-reference only; target contents unreviewed here."
          },
          {
            "source": "ecdr_link_DI_12027_001",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-paper-cpd": {
        "id": "ecdr-cessation-hearing-evidence-paper-cpd",
        "title": "A paper CPD folder was used",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "Place SSA-827 and other relevant documents including submitted medical evidence in the paper folder; print and attach the EDCS routing form to its top and send the folder to HO. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. B.2 additionally requires mailing associated paper folders at electronic transfer; no disposal or replacement by the electronic folder is inferred.",
        "source": "ecdr_DI81010_257",
        "section": "B.3",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.3",
            "start": 5794,
            "end": 6712,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "696fadde15ac67024732c55938b0fd2b13db797e9834ed8aca149ad5555a7f04",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "EDCS",
          "EDCS eCDR Prior Comparison Point Decision Folder Linking"
        ],
        "entity_ids": [
          "APP_EDCS",
          "R109_E034"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "B.2 additionally requires mailing associated paper folders at electronic transfer; no disposal or replacement by the electronic folder is inferred."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "The eCDR cessation determination used a paper CPD folder."
        ],
        "condition_logic": "all",
        "when": "The eCDR cessation determination used a paper CPD folder.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.3",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents": {
        "id": "ecdr-cessation-hearing-evidence-electronic-cpd-paper-documents",
        "title": "The CPD is electronic and paper documents are sent",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "Attach the EDCS routing form to other relevant documents including submitted medical evidence and mail them to HO. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. A linked electronic CPD defaults PFI to No under B.2; that default does not eliminate the separately stated paper-document mailing route.",
        "source": "ecdr_DI81010_257",
        "section": "B.3",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.3",
            "start": 5794,
            "end": 6712,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "696fadde15ac67024732c55938b0fd2b13db797e9834ed8aca149ad5555a7f04",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "EDCS",
          "CEF",
          "EDCS eCDR Prior Comparison Point Decision Folder Linking"
        ],
        "entity_ids": [
          "APP_EDCS",
          "REPO_CEF",
          "R109_E034"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "A linked electronic CPD defaults PFI to No under B.2; that default does not eliminate the separately stated paper-document mailing route."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "The CPD folder is a CEF.",
          "Paper documents or forms are being sent."
        ],
        "condition_logic": "all",
        "when": "The CPD folder is a CEF.; Paper documents or forms are being sent.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.3",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "ecdr-cessation-hearing-evidence/ecdr-cessation-hearing-evidence-no-paper-documents": {
        "id": "ecdr-cessation-hearing-evidence-no-paper-documents",
        "title": "No paper documents or forms are being sent",
        "you": "Keep the hearing request and SSA correspondence; respond to the case-specific requests from SSA. This research view creates no new customer duty.",
        "ssa": "Do not print an EDCS routing form. Source qualifications: Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time. Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests. DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures. Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance. B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated. This condition does not decide whether a paper folder exists or waive a required paper-folder shipment.",
        "source": "ecdr_DI81010_257",
        "section": "B.3",
        "source_provenance": [
          {
            "source_code": "DI81010.257",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010257",
            "locator": "B.3",
            "start": 5794,
            "end": 6712,
            "text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
            "span_sha256": "696fadde15ac67024732c55938b0fd2b13db797e9834ed8aca149ad5555a7f04",
            "offset_unit": "Unicode codepoints in browser visible main text",
            "capture_type": "browser_visible_main_text",
            "parsed_dom_sha256": "b3f592847131c31b4cf5597bd97fa74698b783ee468073dd3c8f943cd9e0b13c",
            "raw_http_bytes_claimed": false,
            "effective_date_display": "09/01/2026 - Present",
            "transmittal": "TN93 (09-26)",
            "checked_on": "2026-10-31",
            "download_url": "/service/sources/DI81010.257-current-browser.txt"
          }
        ],
        "owner": "Field office; hearing office for the stated received-document scanning",
        "systems": [
          "EDCS"
        ],
        "entity_ids": [
          "APP_EDCS"
        ],
        "route": "FO eCDR hearing preparation → source-qualified hearing-office routing",
        "next": "Retain the source-specific conditions. Sending does not establish receipt, successful processing or a completed next state.",
        "timing": "No end-to-end processing duration established; relative sequence is stated where applicable.",
        "verification": "Selected current browser-visible .257 context source-pinned; internal execution unverified.",
        "review_status": "Selected .257 preparation/routing source scope reviewed; cross-reference procedures and internal execution unverified.",
        "qualifications": [
          "Source-defined staff handling, not proof of an individual transfer, filing acceptance, consent validity, medical sufficiency, payment outcome or completion time.",
          "Good-cause handling and statutory benefit continuation are source cross-references; this walkthrough does not decide good cause, timeliness, SBC eligibility or continuation. The source calls for a signed SSA-792 when processing continuation requests.",
          "DI11005.057 authorization, DI81010.135 disposition, DI81010.090 barcode handling, DI12010.001 hearing requests and other cross-references remain bounded unreviewed links here; do not infer their full procedures.",
          "Current source navigation does not refresh inherited native statuses, evidence, observation dates or canonical acceptance.",
          "B.4 decision-alert and master-record follow-up is outside this bounded preparation/routing workflow; no completed rejoin is demonstrated.",
          "This condition does not decide whether a paper folder exists or waive a required paper-folder shipment."
        ],
        "rejoin_unknowns": [
          {
            "detail": "Successful hearing-office receipt, subsequent processing and completed case-specific rejoin are not established."
          }
        ],
        "conditions": [
          "The eCDR hearing routing instruction applies.",
          "No paper documents or forms are being sent."
        ],
        "condition_logic": "all",
        "when": "The eCDR hearing routing instruction applies.; No paper documents or forms are being sent.",
        "source_qualified_branch": {
          "source_code": "DI81010.257",
          "locator": "B.3",
          "scope": "Conditional source-defined hearing handling; not an eligibility determination."
        },
        "additional_sources": [
          {
            "source": "ecdr_link_DI_11005_057",
            "section": "Linked cross-reference only; target contents unreviewed here."
          }
        ]
      },
      "apply-disability/initial-wu-representative-time": {
        "id": "initial-wu-representative-time",
        "title": "DDS cannot locate an applicant with a representative",
        "when": "An initial or reconsideration claimant cannot be located at the last address or reached by phone.",
        "you": "Keep contact details current; a representative seeking more time to locate you can ask DDS.",
        "ssa": "Make reasonable efforts to involve the appointed representative. If the representative requests more time to locate the claimant, allow at least ten additional calendar days and document efforts. Confirm claimant contact details before changing them in DCPS, except when the representative is a minor child’s parent or a legal guardian.",
        "route": "DDS → appointed representative / claimant contact confirmation",
        "next": "CDR, prehearing and DHU cases follow separate policies.",
        "source": "ddswhereaboutsunknown",
        "section": "A; C.1",
        "timing": "At least ten additional calendar days when the representative requests locating time.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "apply-disability/initial-wu-search-alternatives": {
        "id": "initial-wu-search-alternatives",
        "title": "DDS search alternatives when an applicant cannot be found",
        "when": "An initial/reconsideration claimant has no appointed representative and special handling does not apply.",
        "you": "Contact SSA with current information if you learn the claim is awaiting contact.",
        "ssa": "DDS takes at least one specified locating action: a postmaster SSA-L2001 request, reasonable third-party contact efforts, or an FO assistance request through DCPS. The postmaster has 15 calendar days; the FO has 15, followed by a message allowing ten more if unanswered. DDS retains jurisdiction during FO efforts and documents the search in DCPS or the case development worksheet. Unsuccessful locating alone cannot support an unfavorable determination.",
        "route": "DDS → selected locating contact / FO assistance → DDS evaluation",
        "next": "DDS continues evidence development that does not require claimant involvement.",
        "source": "ddswhereaboutsunknown",
        "section": "C.3-4; D opening",
        "timing": "15-day postmaster or FO response periods; ten-day additional FO follow-up applies only to that route.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "apply-disability/wu-special-handling-contacts": {
        "id": "wu-special-handling-contacts",
        "title": "Special handling when an applicant cannot be located",
        "when": "Special handling applies to an initial/reconsideration claimant whose whereabouts are unknown.",
        "you": "Keep designated contact information current when communicating with SSA.",
        "ssa": "Make reasonable efforts to involve designated contacts for the current adjudication level. If the first of two contacts is unproductive, involve the other. If none was designated, take at least one C.3 locating action. Check SSA-3368/3441 Contacts or Remarks and document efforts.",
        "route": "DDS → designated contacts / locating development",
        "next": "The contact protections apply before the later evidence evaluation.",
        "source": "ddswhereaboutsunknown",
        "section": "C.2",
        "timing": "No overall processing duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "apply-disability/wu-evidence-notice": {
        "id": "wu-evidence-notice",
        "title": "Determination after required locating efforts fail",
        "when": "Required initial/reconsideration locating efforts remain unsuccessful.",
        "you": "If you reconnect with SSA, ask about the determination and current contact record.",
        "ssa": "Do not decide adversely solely because whereabouts are unknown. Evaluate available evidence and complete development not requiring claimant involvement; explain the effect in the determination explanation. Put the last address in SSA-831 item 5 and whereabouts-unknown remarks in item 34; send the appropriate notice to that address, then return to FO or Disability Quality Branch if selected for federal review.",
        "route": "DDS → last-known-address notice → FO / Disability Quality Branch",
        "next": "The evidence evaluation determines the outcome.",
        "source": "ddswhereaboutsunknown",
        "section": "D",
        "timing": "No overall processing duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "apply-ssi/iar-state-guardian-signature-conflict": {
        "id": "iar-state-guardian-signature-conflict",
        "title": "The State IAR agency also acts as guardian or payee applicant",
        "when": "A State interim-assistance-reimbursement agency representative signs the applicant’s portion of an IAR authorization while the agency has the specified guardian/payee role.",
        "you": "Ask SSA or the State what signature is needed and keep any request for correction. A State contact name does not replace the required applicant-side signature.",
        "ssa": "SI 02003.005 B.4 prohibits the State IAR representative from signing the applicant portion in this conflict situation. The field office returns the authorization for a valid signature. SI 02003.020 D.2 directs staff to explain why the signature is unacceptable, request an appropriate signature and advise that the 30-day rule still applies to returned authorizations. The general permitted-signer list does not remove this State-agency conflict restriction.",
        "route": "Field-office signature review → State authorization return and correction request",
        "next": "This addresses reimbursement authorization validity, not automatic denial of the SSI claim. Other eligibility and payment requirements remain separate.",
        "source": "iarvalidsignature",
        "section": "B.3–4",
        "additional_sources": [
          {
            "source": "iarforeturn",
            "section": "D.2"
          }
        ],
        "timing": "Returning a form for signatures does not itself waive the applicable 30-day authorization rule; no correction-processing duration is specified.",
        "review_status": "Selected conflict/signature-return requirements checked; automated-notification timing and authorization-life details require separate review."
      },
      "apply-ssi/iar-missing-signature-date-return": {
        "id": "iar-missing-signature-date-return",
        "title": "An IAR form lacks a required signature or date",
        "when": "The SSI applicant or State IAR representative has not signed and dated the authorization.",
        "you": "Respond to the State’s correction request and keep the completed form information. Ask which signature or date is missing.",
        "ssa": "SI 02003.020 D.2 directs the field office to return the paper authorization to the State and notify it to obtain missing signatures or dates. This applies to initial claims and posteligibility cases. Staff advise the State that the applicable 30-day authorization rule still applies to forms returned for signatures.",
        "route": "Field office completeness review → State obtains missing signatures/dates",
        "next": "The State must obtain the missing information; the return does not establish a fresh deadline or an automatic waiver. SSI eligibility remains separately reviewed.",
        "source": "iarforeturn",
        "section": "D.2 first bullet and note",
        "timing": "The applicable 30-day authorization rule continues; this subsection gives no correction turnaround time.",
        "review_status": "General incomplete-signature/date path verified separately from State-agency guardian/payee conflict."
      },
      "apply-ssi/iar-second-authorization-pending": {
        "id": "iar-second-authorization-pending",
        "title": "A second IAR authorization arrives while one is pending",
        "when": "A reimbursement code is already pending on the SSI record and SSA receives another authorization.",
        "you": "Tell SSA and the State whether this concerns a new initial claim or a new posteligibility event, and keep the authorization information.",
        "ssa": "Under SI 02003.020 D.3, the field office returns subsequent authorizations to the State unless they concern a new initial-claim or posteligibility event. The return notation explains that the claimant already authorized payment to another State IAR agency. Staff must check that exception before treating the form as a duplicate.",
        "route": "Field office pending-authorization review → State office return when D.3 applies",
        "next": "The return concerns reimbursement authorization. The subsection does not prescribe a customer notice or decide SSI eligibility.",
        "source": "iarforeturn",
        "section": "D.3",
        "timing": "No return-processing duration is specified.",
        "review_status": "Pending-code trigger, new-event exception and State return checked; no invented customer notification adopted."
      }
    },
    "corrected_legacy_records": {
      "apply-disability/initial-wu-representative-time": {
        "id": "initial-wu-representative-time",
        "title": "DDS cannot locate an applicant with a representative",
        "when": "An initial or reconsideration claimant with an appointed representative cannot be located at the last known address AND cannot be reached by telephone.",
        "you": "Keep contact details current; a representative seeking more time to locate you can ask DDS.",
        "ssa": "Make reasonable efforts to involve the appointed representative. If the representative requests more time to locate the claimant, allow at least ten additional calendar days and document efforts. Confirm claimant contact details before changing them in DCPS, except when the representative is a minor child’s parent or a legal guardian.",
        "route": "DDS → appointed representative / claimant contact confirmation",
        "next": "CDR, prehearing and DHU cases follow separate policies.",
        "source": "ddswhereaboutsunknown",
        "section": "A; C.1",
        "timing": "At least ten additional calendar days when the representative requests locating time.",
        "review_status": "Official subsection checked2026-10-17"
      },
      "apply-disability/wu-special-handling-contacts": {
        "id": "wu-special-handling-contacts",
        "title": "Special handling when an applicant cannot be located",
        "when": "Special handling applies to an initial/reconsideration claimant whose whereabouts are unknown.",
        "you": "Keep designated contact information current when communicating with SSA.",
        "ssa": "Make reasonable efforts to involve designated contacts for the current adjudication level. If the first of two contacts is unproductive, involve the other. If the claimant elected not to designate a third-party contact, take at least one C.3 locating action. Check SSA-3368/3441 Contacts or Remarks and document efforts.",
        "route": "DDS → designated contacts / locating development",
        "next": "The contact protections apply before the later evidence evaluation.",
        "source": "ddswhereaboutsunknown",
        "section": "C.2",
        "timing": "No overall processing duration specified.",
        "review_status": "Official subsection checked2026-10-17"
      }
    },
    "legacy_summary_corrections": [
      {
        "route": "apply-disability/initial-wu-representative-time",
        "field": "when",
        "original": "An initial or reconsideration claimant cannot be located at the last address or reached by phone.",
        "replacement": "An initial or reconsideration claimant with an appointed representative cannot be located at the last known address AND cannot be reached by telephone.",
        "source_context_ref": "DI23005.001:A",
        "reason": "Fresh primary A uses both unavailableaddress AND unreachablephone; oldORsummary is preserved in original/inverse, not accepted as newWUdefinition."
      },
      {
        "route": "apply-disability/wu-special-handling-contacts",
        "field": "ssa",
        "original": "Make reasonable efforts to involve designated contacts for the current adjudication level. If the first of two contacts is unproductive, involve the other. If none was designated, take at least one C.3 locating action. Check SSA-3368/3441 Contacts or Remarks and document efforts.",
        "replacement": "Make reasonable efforts to involve designated contacts for the current adjudication level. If the first of two contacts is unproductive, involve the other. If the claimant elected not to designate a third-party contact, take at least one C.3 locating action. Check SSA-3368/3441 Contacts or Remarks and document efforts.",
        "source_context_ref": "DI23005.001:C2",
        "exact_source_quote": "When the claimant elected not to designate a third party contact, DDS must take at least one of the actions listed in DI 23005.001C.3. in this section.",
        "source_quote_start": 3390,
        "source_quote_end": 3541,
        "reason": "No-designation-on-file alone is broader than claimant elected not to designate; newflowalreadycorrect, sourcecardsnotchanged."
      }
    ],
    "source_contexts": {
      "eCDR6": [
        {
          "id": "DI81010.257:whole",
          "source_code": "DI81010.257",
          "locator": "Whole captured current main text, including B4 held source context",
          "start": 0,
          "end": 8100,
          "exact_text": "Effective Dates: 09/01/2026 - Present\nPrevious | Next\n\nTN 93 (09-26)\n\nDI 81010.257 Electronic Continuing Disability Review (eCDR) Cessation Hearing Appeal\nA. \nBackground for CDR hearing appeal\n\nThe Field Office (FO) serves as the starting point for CDRs and CDR appeals. Most CDRs are processed electronically through all adjudicative levels. The eCDR may have either a paper or electronic Comparison Point Decision (CPD) folder. The Electronic Disability Collect System (EDCS) provides the capability to link eCPD folders to the current eCDR. Paper CPD folders follow the eCDR to each adjudicative component (Disability Determination Services [DDS], Office of Hearing Operations [OHO], etc.)\n\nB. \nFO responsibilities for eCDR ALJ hearings\n\nAn individual may choose to appeal a cessation determination. The individual contacts the FO to complete the necessary hearing forms. In order to process the request:\n\n•\n\nfollow instructions in Request for Administrative Law Judge (ALJ) Hearing DI 12010.001;\n\n•\n\nreviews MBR, SSR, and DCF, etc.; and\n\n•\n\ndevelops good cause for late filing per GN 03101.020 Good Cause for Extending the Time Limit to File an Appeal, if appropriate.\n\nREMINDER: Process requests for continuation of benefits per Processing Statutory Benefit Continuation (SBC) DI 12027.010 and obtain an SSA-792 (Statutory Benefit Continuation Election Statement) signed by the claimant.\n\n1. \nCompleting eCDR hearing requests in EDCS\n\nProcess eCDR hearings in EDCS and view them in eView.\n\nIMPORTANT: When the CDR is a Title XVI only or concurrent, before initiating the eCDR appeal in EDCS, the CS must use MSSICS to update the SSID to document the filing of the medical cessation appeal as well as the SBC election, if applicable. If Direct SSR update is required, the FO can manually enter the required fields in EDCS on the CDR Information and Claims Information pages.\n\nTo process the eCDR hearing, EDCS users must open EDCS and establish a record by completing the following actions:\n\n•\n\nSelect CDR Hearing from the Select Case Level screen;\n\n•\n\nSelect OK button;\n\n•\n\nEnter the appeal filing date on the Confirm Case Creation screen, if it did not propagate from MSSICCS;\n\n•\n\nSelect Create Case button;\n\nKey in the CDR information, the SSA-3367 (Disability Report-Field Office), and the SSA-3441 (Disability Report-Appeal) data in EDCS on the Form(s) Selection screen;\n\nNOTE: The Copy from Prior button in EDCS will be enabled if information is available to copy from prior level(s). For more information see Creating Electronic Disability Collect System (EDCS) Cases - DI 81010.020E.1.\n\n•\n\nEnter the reason for the appeal and limited data similar to the eCDR Initial CDR including:\n\na. \n\nthe SSN,\n\nb. \n\nclaim type,\n\nc. \n\nname,\n\nd. \n\naddress,\n\ne. \n\nstatutory benefit continuation (SBC) information\n\nf. \n\nattorney representative name and address, and\n\ng. \n\nrepresentative payee name and address;\n\nREMINDER: Verify and update the appropriate address, telephone number, and representative information on the mainframe before transferring the hearing in EDCS.\n\n•\n\nObtain a paper HA-501 (Request for Hearing by Administrative Law Judge) or written statement signed by the claimant and one SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)). Also obtain an SSA-3881 (Questionnaire for Children Claiming SSI Benefits) for SSI childhood disability claims. NOTE: Do not delay sending the eCDR hearing to the HO to obtain an SSA-3881 or an SSA-827;\n\n•\n\nFax the front and back of the HA-501 or written statement signed by the claimant into the CEF, then dispose of the form per instructions in Storing Non-Medical Evidence in the Certified Electronic Folder DI 81010.135;\n\nNOTE: For SSI only appeals recorded in MSSICS, the FO may print the appeal request from MSSICS and fax a copy into the CEF. If one is provided, fax the SSA-827 to the CEF. For more detailed information about SSA-827 requirements for a hearing request, see Field Office Instructions for Obtaining Form SSA-827 - DI 11005.057.\n\n•\n\nFax a good cause for late filing statement signed by the claimant into the CEF when appropriate;\n\n•\n\nFax medical evidence submitted by the individual with the eCDR hearing request into the CEF per Faxing Documents into the Certified Electronic Folder (CEF) Using Barcodes DI 81010.090;\n\n•\n\nFax any development regarding Statutory Benefit Continuation (SBC) (for example, Report of Contact, SSA-792, and any other documentation per Statutory Benefit Continuation (SBC) DI 12027.001 into the CEF. Dispose of the development per Storing Non-Medical Evidence in the Certified Electronic Folder DI 81010.135; and\n\n•\n\nMail other forms (SSA-3881 and, SSA-821 (Work Activity Report-Employee), etc.) provided for the eCDR hearing to the HO. The HO scans the document into the CEF or sends the document to the contract scanner.\n\n2. \nTransferring the eCDR hearing in EDCS\n\nWhen transferring the eCDR request for hearing, the FO must:\n\n•\n\nReview the claim to resolve any edits;\n\n•\n\nSelect the Transfer/Updates tab in EDCS;\n\n•\n\nAnswer the paper folder indicator (PFI) question (NOTE: if an electronic CPD is linked to the eCDR, the PFI will default to No);\n\n•\n\nEnsure Title II Statutory Benefit Continuation (SBC) fields are completed\n\n•\n\nTransfer all parts of an eCDR, concurrent or multiple entitlements at the same time.\n\n•\n\nMail all paper folder(s) associated with the case to the hearing office at the time of electronic transfer\n\nNOTE 1: The DCF CDRI screen automatically records the appeal(s) on the DCF after EDCS transfer. For more information on transferring the eCDR reconsideration, see MSOM CDR 001.025.\n\nNOTE 2: The EDCS automatic updates to the DCF are for appeal cases only, the FO must still add initial CDR case movement manually or through WAC\n\n3. \nRouting the paper folder or documents\n\nThe EDCS routing form generates at the point of transfer if a paper folder is involved. (The CR has the option to print or cancel print of the routing form.)\n\nIf a paper CPD folder was used to make the cessation determination:\n\n•\n\nPlace the SSA-827 and any other relevant documents including medical evidence submitted by the individual in the paper folder;\n\n•\n\nPrint and attach an EDCS routing form to the top of the folder; and\n\n•\n\nSend the folder to the HO.\n\nIf the CPD folder is a CEF, attach the EDCS routing form to t any other relevant documents including medical evidence submitted by the individual and mail them to the HO.\n\nDo not print an EDCS routing form if there are no paper documents or forms (for example, SSA-827s, SSA-792s, etc.) being sent. For more information on routing SSA-827s, see Field Office Instructions for Obtaining Form SSA-827 DI 11005.057.\n\n4. \nFO processing of eCDR hearing decisions\n\nWhen the FO receives an alert on the EDCS Claims Actions page notifying them of the HO decision on an eCDR appeal:\n\nTitle II only cases:\n\n•\n\nReview the MBR to ensure the applicable information received from EDCS and the DCF updated automatically.\n\n•\n\nNo Post-entitlement Online System (POS) action is required.\n\n•\n\nVerify SBC termination, if applicable.\n\n•\n\nEnsure the MBR is updated within 5 days. If the MBR does not update in 5 days, technicians should proceed with manual action to update the MBR.\n\nTitle XVI and Concurrent cases:\n\n•\n\nReview both the SSID and MBR to ensure medical cessation appeal determination automatically posted;\n\n•\n\nVerify the SBC benefits have ended for BOTH titled programs\n\n•\n\nNo POS action is required for the Title II claim.\n\n•\n\nEnsure both the MBR and SSID are updated within 5 days. If the MBR and or SSID do not update in 3-5 days, technicians should proceed with manual actions to update the MBR and or SSID.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0481010257\n\t\nDI 81010.257 - Electronic Continuing Disability Review (eCDR) Cessation Hearing Appeal - 09/01/2026\nBatch run: 09/01/2026\nRev:09/01/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
          "span_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5"
        },
        {
          "id": "DI81010.257:A",
          "source_code": "DI81010.257",
          "locator": "A",
          "start": 155,
          "end": 694,
          "exact_text": "A. \nBackground for CDR hearing appeal\n\nThe Field Office (FO) serves as the starting point for CDRs and CDR appeals. Most CDRs are processed electronically through all adjudicative levels. The eCDR may have either a paper or electronic Comparison Point Decision (CPD) folder. The Electronic Disability Collect System (EDCS) provides the capability to link eCPD folders to the current eCDR. Paper CPD folders follow the eCDR to each adjudicative component (Disability Determination Services [DDS], Office of Hearing Operations [OHO], etc.)\n\n",
          "span_sha256": "1cb1752749cb5133e31b3a95ab96a7e06204e7340e24e563c92b2ecf807b78af"
        },
        {
          "id": "DI81010.257:B-intro",
          "source_code": "DI81010.257",
          "locator": "B-intro",
          "start": 694,
          "end": 1394,
          "exact_text": "B. \nFO responsibilities for eCDR ALJ hearings\n\nAn individual may choose to appeal a cessation determination. The individual contacts the FO to complete the necessary hearing forms. In order to process the request:\n\n•\n\nfollow instructions in Request for Administrative Law Judge (ALJ) Hearing DI 12010.001;\n\n•\n\nreviews MBR, SSR, and DCF, etc.; and\n\n•\n\ndevelops good cause for late filing per GN 03101.020 Good Cause for Extending the Time Limit to File an Appeal, if appropriate.\n\nREMINDER: Process requests for continuation of benefits per Processing Statutory Benefit Continuation (SBC) DI 12027.010 and obtain an SSA-792 (Statutory Benefit Continuation Election Statement) signed by the claimant.\n\n",
          "span_sha256": "21ed2437541666cdc360e9cf81ab7bed5c86a04c8c78fadba94f8d593def75df"
        },
        {
          "id": "DI81010.257:B1",
          "source_code": "DI81010.257",
          "locator": "B1",
          "start": 1394,
          "end": 4862,
          "exact_text": "1. \nCompleting eCDR hearing requests in EDCS\n\nProcess eCDR hearings in EDCS and view them in eView.\n\nIMPORTANT: When the CDR is a Title XVI only or concurrent, before initiating the eCDR appeal in EDCS, the CS must use MSSICS to update the SSID to document the filing of the medical cessation appeal as well as the SBC election, if applicable. If Direct SSR update is required, the FO can manually enter the required fields in EDCS on the CDR Information and Claims Information pages.\n\nTo process the eCDR hearing, EDCS users must open EDCS and establish a record by completing the following actions:\n\n•\n\nSelect CDR Hearing from the Select Case Level screen;\n\n•\n\nSelect OK button;\n\n•\n\nEnter the appeal filing date on the Confirm Case Creation screen, if it did not propagate from MSSICCS;\n\n•\n\nSelect Create Case button;\n\nKey in the CDR information, the SSA-3367 (Disability Report-Field Office), and the SSA-3441 (Disability Report-Appeal) data in EDCS on the Form(s) Selection screen;\n\nNOTE: The Copy from Prior button in EDCS will be enabled if information is available to copy from prior level(s). For more information see Creating Electronic Disability Collect System (EDCS) Cases - DI 81010.020E.1.\n\n•\n\nEnter the reason for the appeal and limited data similar to the eCDR Initial CDR including:\n\na. \n\nthe SSN,\n\nb. \n\nclaim type,\n\nc. \n\nname,\n\nd. \n\naddress,\n\ne. \n\nstatutory benefit continuation (SBC) information\n\nf. \n\nattorney representative name and address, and\n\ng. \n\nrepresentative payee name and address;\n\nREMINDER: Verify and update the appropriate address, telephone number, and representative information on the mainframe before transferring the hearing in EDCS.\n\n•\n\nObtain a paper HA-501 (Request for Hearing by Administrative Law Judge) or written statement signed by the claimant and one SSA-827 (Authorization to Disclose Information to the Social Security Administration (SSA)). Also obtain an SSA-3881 (Questionnaire for Children Claiming SSI Benefits) for SSI childhood disability claims. NOTE: Do not delay sending the eCDR hearing to the HO to obtain an SSA-3881 or an SSA-827;\n\n•\n\nFax the front and back of the HA-501 or written statement signed by the claimant into the CEF, then dispose of the form per instructions in Storing Non-Medical Evidence in the Certified Electronic Folder DI 81010.135;\n\nNOTE: For SSI only appeals recorded in MSSICS, the FO may print the appeal request from MSSICS and fax a copy into the CEF. If one is provided, fax the SSA-827 to the CEF. For more detailed information about SSA-827 requirements for a hearing request, see Field Office Instructions for Obtaining Form SSA-827 - DI 11005.057.\n\n•\n\nFax a good cause for late filing statement signed by the claimant into the CEF when appropriate;\n\n•\n\nFax medical evidence submitted by the individual with the eCDR hearing request into the CEF per Faxing Documents into the Certified Electronic Folder (CEF) Using Barcodes DI 81010.090;\n\n•\n\nFax any development regarding Statutory Benefit Continuation (SBC) (for example, Report of Contact, SSA-792, and any other documentation per Statutory Benefit Continuation (SBC) DI 12027.001 into the CEF. Dispose of the development per Storing Non-Medical Evidence in the Certified Electronic Folder DI 81010.135; and\n\n•\n\nMail other forms (SSA-3881 and, SSA-821 (Work Activity Report-Employee), etc.) provided for the eCDR hearing to the HO. The HO scans the document into the CEF or sends the document to the contract scanner.\n\n",
          "span_sha256": "59c4304c0ea530b97455eaf72143905feaa7180d3eddc2815c24b5cd4788babc"
        },
        {
          "id": "DI81010.257:B2",
          "source_code": "DI81010.257",
          "locator": "B2",
          "start": 4862,
          "end": 5794,
          "exact_text": "2. \nTransferring the eCDR hearing in EDCS\n\nWhen transferring the eCDR request for hearing, the FO must:\n\n•\n\nReview the claim to resolve any edits;\n\n•\n\nSelect the Transfer/Updates tab in EDCS;\n\n•\n\nAnswer the paper folder indicator (PFI) question (NOTE: if an electronic CPD is linked to the eCDR, the PFI will default to No);\n\n•\n\nEnsure Title II Statutory Benefit Continuation (SBC) fields are completed\n\n•\n\nTransfer all parts of an eCDR, concurrent or multiple entitlements at the same time.\n\n•\n\nMail all paper folder(s) associated with the case to the hearing office at the time of electronic transfer\n\nNOTE 1: The DCF CDRI screen automatically records the appeal(s) on the DCF after EDCS transfer. For more information on transferring the eCDR reconsideration, see MSOM CDR 001.025.\n\nNOTE 2: The EDCS automatic updates to the DCF are for appeal cases only, the FO must still add initial CDR case movement manually or through WAC\n\n",
          "span_sha256": "511c53d6f5631163116b6790323f9c4903cccba297b34477ab15ea445db18d8f"
        },
        {
          "id": "DI81010.257:B3",
          "source_code": "DI81010.257",
          "locator": "B3",
          "start": 5794,
          "end": 6712,
          "exact_text": "3. \nRouting the paper folder or documents\n\nThe EDCS routing form generates at the point of transfer if a paper folder is involved. (The CR has the option to print or cancel print of the routing form.)\n\nIf a paper CPD folder was used to make the cessation determination:\n\n•\n\nPlace the SSA-827 and any other relevant documents including medical evidence submitted by the individual in the paper folder;\n\n•\n\nPrint and attach an EDCS routing form to the top of the folder; and\n\n•\n\nSend the folder to the HO.\n\nIf the CPD folder is a CEF, attach the EDCS routing form to t any other relevant documents including medical evidence submitted by the individual and mail them to the HO.\n\nDo not print an EDCS routing form if there are no paper documents or forms (for example, SSA-827s, SSA-792s, etc.) being sent. For more information on routing SSA-827s, see Field Office Instructions for Obtaining Form SSA-827 DI 11005.057.\n\n",
          "span_sha256": "696fadde15ac67024732c55938b0fd2b13db797e9834ed8aca149ad5555a7f04"
        }
      ],
      "WU4": [
        {
          "id": "DI23005.001:whole",
          "start": 0,
          "end": 7624,
          "exact_text": "Effective Dates: 09/11/2024 - Present\nPrevious | Next\n\nTN 14 (04-25)\n\nDI 23005.001 Processing Whereabouts Unknown Disability Cases in the Disability Determination Services (DDS)\nA. \nDefinition of whereabouts unknown (WU)\n\nFor initial and reconsideration claims, consider a claimant's whereabouts to be unknown when the DDS cannot locate the claimant at their last known address and they cannot be reached by telephone (e.g., their phone number is disconnected).\n\nWhen a WU situation arises during a medical continuing disability review (CDR), follow the instructions in DI 28075.007 Whereabouts Unknown (WU) During a Medical Continuing Disability Review (CDR).\n\nWhen a WU situation arises during a pre-hearing review, follow the instructions in DI 29005.027.\n\nWhen a WU situation arises while the case is at the disability hearing unit, follow the instructions in DI 33015.033.\n\nB. \nWhen WU arises in the field office (FO)\n\nThe FO must review the claim to determine whether a medical determination is necessary. Before transferring a WU claim to the DDS, the FO must resolve any substantial gainful activity (SGA) issues (DI 10505.000) and provide an accurate potential onset date (POD) (DI 25501.220).\n\nFor additional information about FO responsibilities when a WU situation arises, see DI 11055.085.\n\nC. \nWhen WU arises at the DDS\n\nWhen a claimant’s whereabouts become unknown while the case is at the DDS, adjudicators must either attempt to locate the claimant or request FO assistance with locating the claimant. Additionally, when the claimant has an appointed representative (AR) or requires special handling, specific instructions apply.\n\n•\n\nFor additional information on represented claimants, see DI 31001.010.\n\n•\n\nFor additional information on special handling criteria, see DI 23007.001A.\n\n1. \nAR involved\n\nWhen a claimant's whereabouts become unknown and they have an AR, the DDS must make a reasonable effort to involve the AR by following the instructions in DI 23007.005A. When the AR requests more time to locate the claimant, the DDS will allow them a minimum of 10 additional calendar days. Document the case file following the instructions in DI 23005.001C.4., in this section.\n\nIf, after involving the AR, the claimant's whereabouts remain unknown, follow the appropriate process to develop the claim, evaluate the evidence, and make a disability determination as set forth in DI 23005.001D, in this section.\n\nNOTE: Although an AR might provide the claimant's updated contact information, the DDS may not change the claimant’s personal information in the Disability Case Processing System (DCPS) without first confirming with the claimant that this is the current mailing address or telephone number where they can be reached (unless the AR is a parent of a minor child or a legal guardian). For more information about the scope of AR authority, see GN 03910.025A.\n\n2. \nSpecial handling applies\n\nWhen a claimant's whereabouts become unknown and special handling applies, the DDS must make a reasonable effort to involve the designated third party contact(s) from the current level of adjudication, following the instructions in DI 23007.010C.\n\nWhen the claimant designates two individuals who we can contact if the claimant becomes unavailable and the first contact person is not productive, the DDS must make a reasonable effort to involve the other contact person.\n\nWhen the claimant elected not to designate a third party contact, DDS must take at least one of the actions listed in DI 23005.001C.3. in this section.\n\nThe designated third party contact(s) is documented in Section 2 – ‟Contacts” of the Forms SSA-3368-BK and SSA-3441-BK, or a contact person might be documented in the ‟Remarks” section of these forms. Document all efforts to involve the third party, following DI 23005.001C.4 in the section.\n\n3. \nDDS efforts to locate the claimant\n\nWhen the claimant does not have an AR and special handling does not apply, the DDS must take at least one of the following actions to attempt to locate a claimant whose whereabouts are unknown.\n\n•\n\nMail the Form SSA-L2001 (Address Information Request) to the postmaster and allow them 15 calendar days to respond;\n\n•\n\nMake a reasonable effort to involve the third party (or parties) if the claimant provided one, or other appropriate individual(s) (e.g., legal guardian), following the instructions in DI 23005.001C.2. in this section.\n\n•\n\nSend the FO an assistance request through DCPS and allow them 15 calendar days to respond. If the FO does not respond after 15 calendar days have passed, the DDS must send a follow up message and allow the FO 10 calendar days to respond. The DDS must retain full jurisdiction of the case while the FO attempts to locate the claimant.\n\nIf the claimant's whereabouts remain unknown after taking at least one of the listed actions above, there is no need for the DDS to make additional attempts to locate the claimant and they may proceed with making a disability determination, following the instructions in DI 23005.001D in this section.\n\nIMPORTANT: Subsequent Federal quality reviewers will not cite a deficiency if the DDS does not attempt to locate the claimant and defers to the FO for assistance with locating the claimant, instead. For additional information about Group I documentation deficiencies involving WU, see DI 30005.203A.21.\n\n4. \nDocument efforts to locate the claimant\n\nThe DDS must document all efforts to locate the claimant listed in DI 23005.001C.3 in a Case Note in DCPS, or on the Case Development Worksheet (CDW).\n\nD. \nWU considerations when making a disability determination\n\nDo not make an unfavorable determination solely because a claimant's whereabouts are unknown. When the DDS completes the required action(s) listed in DI 23005.001C but is unsuccessful in locating the claimant, follow the steps of the sequential evaluation process and complete any development that does not require the claimant's involvement.\n\nFor additional information on the sequential evaluation process, see DI 22001.001.\n\nBased on the evidence in file, the DDS must:\n\n1. \n\nDetermine whether a severe, medically determinable impairment (MDI) exists, as discussed in DI 24505.001;\n\n2. \n\nDetermine whether any MDI(s) meets or equals a listing;\n\n3. \n\nDetermine the claimant's residual functional capacity (RFC);\n\n4. \n\nReview the vocational evidence, if available, to determine whether the information is sufficient to make a medical-vocational determination;\n\n5. \n\nDetermine whether the case evidence is sufficient to allow a closed period of disability, as discussed in DI 25510.001;\n\n6. \n\nEnsure the disability determination explanation (DDE) includes a thorough explanation of how the WU situation affects the disability determination;\n\n7. \n\nInclude the following when completing the Form SSA-831 (Disability Determination and Transmittal):\n\n•\n\nThe claimant’s last known address in Item 5, Name and Address of Claimant, and\n\n•\n\n“Claimant’s whereabouts unknown” in Item 34, Remarks.\n\n8. \n\nSend the appropriate notice to the claimant at their last known address; and\n\n9. \n\nReturn the case to the FO or, if selected for Federal review, send the case to the Disability Quality Branch.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0423005001\n\t\nDI 23005.001 - Processing Whereabouts Unknown Disability Cases in the Disability Determination Services (DDS) - 09/11/2024\nBatch run: 10/13/2026\nRev:09/11/2024\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
          "span_sha256": "c6a8f3c28c1bb5250e632cb4504e6bd7645339c0112ecef4550c7735eb4fe01c",
          "source_code": "DI23005.001",
          "locator": "Whole visible captured content; not rawHTTP"
        },
        {
          "id": "DI23005.001:A",
          "start": 178,
          "end": 879,
          "exact_text": "A. \nDefinition of whereabouts unknown (WU)\n\nFor initial and reconsideration claims, consider a claimant's whereabouts to be unknown when the DDS cannot locate the claimant at their last known address and they cannot be reached by telephone (e.g., their phone number is disconnected).\n\nWhen a WU situation arises during a medical continuing disability review (CDR), follow the instructions in DI 28075.007 Whereabouts Unknown (WU) During a Medical Continuing Disability Review (CDR).\n\nWhen a WU situation arises during a pre-hearing review, follow the instructions in DI 29005.027.\n\nWhen a WU situation arises while the case is at the disability hearing unit, follow the instructions in DI 33015.033.\n\n",
          "span_sha256": "cd66399d714a2361ad5da0b70692d04ab133c2ebac33b2444239c81fad1ec07c",
          "source_code": "DI23005.001",
          "locator": "A"
        },
        {
          "id": "DI23005.001:B",
          "start": 879,
          "end": 1304,
          "exact_text": "B. \nWhen WU arises in the field office (FO)\n\nThe FO must review the claim to determine whether a medical determination is necessary. Before transferring a WU claim to the DDS, the FO must resolve any substantial gainful activity (SGA) issues (DI 10505.000) and provide an accurate potential onset date (POD) (DI 25501.220).\n\nFor additional information about FO responsibilities when a WU situation arises, see DI 11055.085.\n\n",
          "span_sha256": "b154d33f0e467753815d50f75171a6751d67605741a3f54f7d9ed6c6b49340eb",
          "source_code": "DI23005.001",
          "locator": "B"
        },
        {
          "id": "DI23005.001:C-intro",
          "start": 1304,
          "end": 1803,
          "exact_text": "C. \nWhen WU arises at the DDS\n\nWhen a claimant’s whereabouts become unknown while the case is at the DDS, adjudicators must either attempt to locate the claimant or request FO assistance with locating the claimant. Additionally, when the claimant has an appointed representative (AR) or requires special handling, specific instructions apply.\n\n•\n\nFor additional information on represented claimants, see DI 31001.010.\n\n•\n\nFor additional information on special handling criteria, see DI 23007.001A.\n\n",
          "span_sha256": "9c91a046439efbe2309687f8a62ee3ab50c7ee03c17cb245ad3a9995b58985fa",
          "source_code": "DI23005.001",
          "locator": "C-intro"
        },
        {
          "id": "DI23005.001:C1",
          "start": 1803,
          "end": 2888,
          "exact_text": "1. \nAR involved\n\nWhen a claimant's whereabouts become unknown and they have an AR, the DDS must make a reasonable effort to involve the AR by following the instructions in DI 23007.005A. When the AR requests more time to locate the claimant, the DDS will allow them a minimum of 10 additional calendar days. Document the case file following the instructions in DI 23005.001C.4., in this section.\n\nIf, after involving the AR, the claimant's whereabouts remain unknown, follow the appropriate process to develop the claim, evaluate the evidence, and make a disability determination as set forth in DI 23005.001D, in this section.\n\nNOTE: Although an AR might provide the claimant's updated contact information, the DDS may not change the claimant’s personal information in the Disability Case Processing System (DCPS) without first confirming with the claimant that this is the current mailing address or telephone number where they can be reached (unless the AR is a parent of a minor child or a legal guardian). For more information about the scope of AR authority, see GN 03910.025A.\n\n",
          "span_sha256": "a565b338c8d94ca4c0d579e85163d0711fe87cc033a29553614211363dde64ce",
          "source_code": "DI23005.001",
          "locator": "C1"
        },
        {
          "id": "DI23005.001:C2",
          "start": 2888,
          "end": 3836,
          "exact_text": "2. \nSpecial handling applies\n\nWhen a claimant's whereabouts become unknown and special handling applies, the DDS must make a reasonable effort to involve the designated third party contact(s) from the current level of adjudication, following the instructions in DI 23007.010C.\n\nWhen the claimant designates two individuals who we can contact if the claimant becomes unavailable and the first contact person is not productive, the DDS must make a reasonable effort to involve the other contact person.\n\nWhen the claimant elected not to designate a third party contact, DDS must take at least one of the actions listed in DI 23005.001C.3. in this section.\n\nThe designated third party contact(s) is documented in Section 2 – ‟Contacts” of the Forms SSA-3368-BK and SSA-3441-BK, or a contact person might be documented in the ‟Remarks” section of these forms. Document all efforts to involve the third party, following DI 23005.001C.4 in the section.\n\n",
          "span_sha256": "7bc997d9a264315779549d47d95fc79ad516f916eff583e3361185cca3dde702",
          "source_code": "DI23005.001",
          "locator": "C2"
        },
        {
          "id": "DI23005.001:C3",
          "start": 3836,
          "end": 5358,
          "exact_text": "3. \nDDS efforts to locate the claimant\n\nWhen the claimant does not have an AR and special handling does not apply, the DDS must take at least one of the following actions to attempt to locate a claimant whose whereabouts are unknown.\n\n•\n\nMail the Form SSA-L2001 (Address Information Request) to the postmaster and allow them 15 calendar days to respond;\n\n•\n\nMake a reasonable effort to involve the third party (or parties) if the claimant provided one, or other appropriate individual(s) (e.g., legal guardian), following the instructions in DI 23005.001C.2. in this section.\n\n•\n\nSend the FO an assistance request through DCPS and allow them 15 calendar days to respond. If the FO does not respond after 15 calendar days have passed, the DDS must send a follow up message and allow the FO 10 calendar days to respond. The DDS must retain full jurisdiction of the case while the FO attempts to locate the claimant.\n\nIf the claimant's whereabouts remain unknown after taking at least one of the listed actions above, there is no need for the DDS to make additional attempts to locate the claimant and they may proceed with making a disability determination, following the instructions in DI 23005.001D in this section.\n\nIMPORTANT: Subsequent Federal quality reviewers will not cite a deficiency if the DDS does not attempt to locate the claimant and defers to the FO for assistance with locating the claimant, instead. For additional information about Group I documentation deficiencies involving WU, see DI 30005.203A.21.\n\n",
          "span_sha256": "25c4c2106a0de217f7befba90fffc401dac622e77d021e2ba440717173ba7661",
          "source_code": "DI23005.001",
          "locator": "C3"
        },
        {
          "id": "DI23005.001:C4",
          "start": 5358,
          "end": 5555,
          "exact_text": "4. \nDocument efforts to locate the claimant\n\nThe DDS must document all efforts to locate the claimant listed in DI 23005.001C.3 in a Case Note in DCPS, or on the Case Development Worksheet (CDW).\n\n",
          "span_sha256": "d4736a3a3d328cacedf554cc8fd49c10946dd50fd016ec145bd7c39f62a19a5f",
          "source_code": "DI23005.001",
          "locator": "C4"
        },
        {
          "id": "DI23005.001:D",
          "start": 5555,
          "end": 7204,
          "exact_text": "D. \nWU considerations when making a disability determination\n\nDo not make an unfavorable determination solely because a claimant's whereabouts are unknown. When the DDS completes the required action(s) listed in DI 23005.001C but is unsuccessful in locating the claimant, follow the steps of the sequential evaluation process and complete any development that does not require the claimant's involvement.\n\nFor additional information on the sequential evaluation process, see DI 22001.001.\n\nBased on the evidence in file, the DDS must:\n\n1. \n\nDetermine whether a severe, medically determinable impairment (MDI) exists, as discussed in DI 24505.001;\n\n2. \n\nDetermine whether any MDI(s) meets or equals a listing;\n\n3. \n\nDetermine the claimant's residual functional capacity (RFC);\n\n4. \n\nReview the vocational evidence, if available, to determine whether the information is sufficient to make a medical-vocational determination;\n\n5. \n\nDetermine whether the case evidence is sufficient to allow a closed period of disability, as discussed in DI 25510.001;\n\n6. \n\nEnsure the disability determination explanation (DDE) includes a thorough explanation of how the WU situation affects the disability determination;\n\n7. \n\nInclude the following when completing the Form SSA-831 (Disability Determination and Transmittal):\n\n•\n\nThe claimant’s last known address in Item 5, Name and Address of Claimant, and\n\n•\n\n“Claimant’s whereabouts unknown” in Item 34, Remarks.\n\n8. \n\nSend the appropriate notice to the claimant at their last known address; and\n\n9. \n\nReturn the case to the FO or, if selected for Federal review, send the case to the Disability Quality Branch.\n\n",
          "span_sha256": "a4b0c212f9502664763609e042349cc33b8963dd858df1a6437473491ee3e190",
          "source_code": "DI23005.001",
          "locator": "D"
        }
      ],
      "IAR3": [
        {
          "id": "SI02003.020:whole",
          "start": 0,
          "end": 7573,
          "exact_text": "Effective Dates: 08/29/2024 - Present\nPrevious | Next\n\nTN 25 (08-24)\n\nSI 02003.020 Field Office Processing of IAR Authorizations\nA. \nDescription of processing IAR authorizations under eIAR\n\nOn November 20, 2010, SSA implemented the eIAR system. The eIAR system changes IAR accounting from a paper process to an electronic process and reduces field office (FO) involvement with processing IAR payments and notices.\n\nStates access the eIAR system using the Government to Government Services Online (GSO) website. SSA regional office IAR coordinators also access eIAR on the GSO website.\n\nThe eIAR process begins when the State notifies SSA that an individual has signed an IAR authorization. The State notifies SSA using either the manual notification or automated notification process. After SSA receives notification that the State agency has a valid authorization, the GR code is posted on the SSI record and eIAR control of the reimbursement process begins.\n\nSSA communicates with the State about an IAR case using the eIAR screens and email messages generated by the eIAR system. The eIAR system processes most reimbursements to completion without FO involvement when the FO inputs the SSI claim allowance. The FO must complete an underpayment review to build the UPV: V on the SSR before the eIAR system can process a reimbursement.\n\nNOTE: Field offices do not have access to the eIAR site. SSA regional office IAR coordinators have view and query access.\n\nB. \nProcedure for processing IAR authorizations in manual notification States\n\nIn a manual notification State, the State sends the original paper authorization form to the FO to notify SSA that it has a valid authorization for reimbursement. The FO:\n\n•\n\ndate stamps the authorization form;\n\n•\n\nreviews the form to ensure that it is completed correctly, signed by the State and the individual, and received by the FO within 30 days from the date that the individual signed the authorization;\n\n•\n\ninputs the GR code if no GR code of “R” or “F” is already posted on the SSR. The GR code must be posted to the individual’s SSR before SSA releases the retroactive benefits. For information about posting the GR code, see MSOM MSSICS 023.006 and SM 01005.623. Do not change or delete a GR code present on a record unless it was input erroneously (e.g., State and county code input as 12435, correct code is 12345).\n\nIMPORTANT: Do not delete a Grant Reimbursement Code (GRC). Contact your eIAR Regional Coordinator, if expedited processing is required or there is justification for the GRC deletion.\n\n•\n\ninputs the corrected application date if the authorization form identifies a protective filing and reviews eligibility back to the protective filing date;\n\n•\n\nnotifies DDS or the Office of Hearings Operations (OHO) of the protective filing date if a disability claim is pending at DDS or OHO;\n\n•\n\nfaxes a copy of the signed authorization form into the appropriate electronic folder to document the protective filing date; and\n\n•\n\nshreds the paper form after faxing a copy to the electronic folder.\n\nThe eIAR system will:\n\n•\n\ncontrol the case;\n\n•\n\npost information on the eIAR screens;\n\n•\n\nautomatically send appropriate notifications and follow-ups to the State; and\n\n•\n\nprocess the IAR reimbursement to the State when the FO completes the prepayment review and inputs an allowance for the claim to build the UPV:V to the SSR.\n\nNOTE: The correct application date must be on the SSR at the time the UPV: V is built so the eIAR system uses the correct IAR period to process the case.\n\nREMINDER: Process workloads in the proper sequence, e.g. review terminated records for underpayments. The GR code must be brought forward from a terminated record to a start-dated record if there will an underpayment on the start-dated record.\n\nC. \nProcess for IAR authorizations in automated notification States\n1. \nElectronic interface notifies SSA of the authorization\n\nIn an automated notification State:\n\n•\n\nthe State sends the IAR authorization information to SSA through an electronic interface with the Supplemental Security Record (SSR);\n\n•\n\nthe electronic interface sends information that the State has a valid authorization, the date the authorization was signed, and the date the State received the authorization; and\n\n•\n\nThe system automatically posts a GR code to the SSR when the State IAR file interfaces with the SSR and matches an established SSI claim.\n\n2. \nPR-73 alert sent to the FO\n\nFor an automated notification State:\n\n•\n\nthe system automatically sends a PR-73 alert to the servicing FO when the date of the State GR code input precedes the SSI application date on the SSR;\n\n•\n\nthe PR-73 alert shows the date the State received a signed authorization; and\n\n•\n\nif the PR-73 alert indicates a protective filing date that is earlier than the application date, redevelop the claim back to the protective filing date.\n\nFor more information about the PR-73 alert, see SM 01015.090.\n\nD. \nProcedure for returning IAR authorizations to States\n1. \n30-calendar day rule\n\nUnder eIAR, the 30-calendar day rule still applies. If the State submits an authorization to SSA more than 30 days after the individual signed the authorization, the FO must return the authorization to the State. Use the following language when returning the form to the State.\n\n“Authorization is not effective because it was not received by SSA within 30 calendar days of the day the individual or their representative payee or legal guardian signed the authorization.”\n\nIf the State does not meet the 30-day deadline, the authorization is not effective and SSA will pay the SSI recipient the retroactive payments according to normal SSI payment rules. In this situation, the State can ask the recipient for reimbursement, but SSA will not assist the State with its request to the recipient. For more information about the 30-calendar day rule, see SI 02003.006, Effective Life if an IAR Authorization.\n\n2. \nAuthorization is not properly signed\n\nWhen an individual or State does not properly sign authorization:\n\n•\n\nReturn the paper authorization to the State if the SSI applicant or State IAR representative did not sign and date the authorization. This process applies to both initial claims and PE situations. Notify the State to obtain the missing signatures or dates; and\n\n•\n\nReturn the paper authorization to the State if it signed by a State IAR representative who is also representative payee or legal guardian for the SSI applicant. The State signing in this manner would result in a potential conflict of interest as described in SI 02003.005B.4. Notify the State to obtain an appropriate signature and explain why the original signature was not acceptable.\n\nNOTE: When returning an authorization to the State, advise the State that the 30-day rule for the effective life of the authorization applies to authorizations returned for signatures.\n\n3. \nMultiple Authorizations\n\nIf there is a GR code that is already pending on the SSR any subsequent authorizations are returned to the State unless the authorization is for a new IC or PE event. Return it to the State office with a notation that the claimant has already authorized payment to another State IAR agency.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0502003020\n\t\nSI 02003.020 - Field Office Processing of IAR Authorizations - 08/29/2024\nBatch run: 12/18/2024\nRev:08/29/2024\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
          "whole_sha256": "b431cab7d16a4bd22943d61103c27ea78b8b73789d32ecd43236379906476239"
        }
      ]
    },
    "source_review_sha256s": {
      "eCDR6": "56c6ddd0627b1c7cc92d955967815b2e6baceb9a929c82da782d7599e4e4ba16",
      "WU4_full": "706d7735d8d8242bef593021fa4361d471192f45513371b8bb0f748d98877e88",
      "WU4_R3": "49e354c0b5717a02eb6965c6524e4dac4414c107905489f6480cd2b222cebf26",
      "IAR3": "a41a5bda043bf02cfec6ddc7aa19bad0a4fd34e9b080b4c569418d5277480598"
    },
    "holds": {
      "eCDR6": [
        "B4 decision-alert follow-up unmodeled; retain 5 vs3-5day wording and no uniform SLA.",
        "No later ALJ/DHO/source-term-equivalence or prototypeinitial current-deployment inference from merely linked target.",
        "All eight unreviewed-link source objects remain neutral/history-preserved even where another separately bounded journey later reviewed target claims.",
        "No sourcebookkeeping current-native-status or historical broaderR109_E033 pretransfer rewrite.",
        "Existing14relationship typed currentB1-B3 versus olderadjacent/B4unmodeled context scopes remain exact; no new edge or source co-occurrence promotion.",
        "Medical-evidence/original/form-disposition holds in other source workflows are not resolved here.",
        "ALJ hearing continuation, late goodcause, filing/consent/medical sufficiency and actualcase transfer outcomes remain unverified."
      ],
      "WU4": "Unreviewed; source-ownedstaffinstructions only, no native/source status update",
      "IAR3": [
        "All original SI02003.005/source history/status fields remain exactly retained; no full linked signer/authorization-life framework reconstructed.",
        "Source-named SSR/GR/eIAR and regional access statements do not establish new native identities, interfaces or runtime/current-operation acceptance.",
        "The separately held coordinator/code-deletion authority and prior IAR025 eight-flow package are unchanged and outside this family.",
        "No completed correction, actual validity, acceptance, reimbursement, SSI entitlement or successful rejoin established."
      ]
    },
    "public_capture_provenance": [
      {
        "source_code": "DI81010.257",
        "whole_text_sha256": "f429fe4c62a5efefa5b9c5db9a8a4214135e23ca1526df2f15879dedf52febc5",
        "public_url": "/service/sources/next13-DI81010.257-main.txt",
        "type": "Retained whole rendered primary capture; not raw HTTP"
      },
      {
        "source_code": "DI23005.001",
        "whole_text_sha256": "c6a8f3c28c1bb5250e632cb4504e6bd7645339c0112ecef4550c7735eb4fe01c",
        "public_url": "/service/sources/next13-DI23005.001-main.txt",
        "type": "Retained whole rendered primary capture; not raw HTTP"
      },
      {
        "source_code": "SI02003.020",
        "whole_text_sha256": "b431cab7d16a4bd22943d61103c27ea78b8b73789d32ecd43236379906476239",
        "public_url": "/service/sources/next13-SI02003.020-main.txt",
        "type": "Retained whole rendered primary capture; not raw HTTP"
      }
    ],
    "limits": [
      "Only six eCDR hearing, four DDS whereabouts-unknown and three IAR-return sequences. Source conditions remain facts to establish.",
      "Exactly two WU legacy summaries corrected, with entire old literals retained here; all source objects and earlier check dates remain unchanged.",
      "eCDR B4 five-day vs3–5-day comparison remains held; no timing precedence, completion or automatic insertion/rejoin established.",
      "IAR signer, pending-code, new IC/PE and30-calendar-day qualifications remain separate; no GR deletion authority or broader linked rules established.",
      "No native identity, permission, operation, eligibility, benefit outcome or source/native acceptance inferred."
    ],
    "source_representation_history": {
      "correction_proposal_sha256": "f2ceb05451870f9736fdd4ee268440b32228e663236e8dad4f8b9c19d33175a6",
      "independent_source_peer_sha256": "3b3f928a3b2b7ea2b8b003634761360cadf55f7d9c59d0319fc96442163b72bd",
      "old_four_card_flow": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "wu-special-handling-contacts",
        "full_route": "apply-disability/wu-special-handling-contacts",
        "entry_conditions": [
          "Special handling applies; linked DI23007.001A criteria are not inferred.",
          "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
          "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
          "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
        ],
        "steps": [
          {
            "id": "wu-special-handling-contacts-1",
            "title": "Involve current-level designated contacts",
            "kind": "action",
            "actor": "DDS",
            "action": "Make a reasonable effort to involve designated third-party contacts from the CURRENT level of adjudication, following linked DI23007.010C.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Claimant designated third-party contact(s).",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2",
            "source_context_refs": [
              "DI23005.001:C2"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "designated-contact-state"
          },
          {
            "id": "wu-special-handling-contacts-2",
            "title": "Use the other of two contacts if needed",
            "kind": "action",
            "actor": "DDS",
            "action": "When TWO individuals were designated and the first is unproductive, make a reasonable effort to involve the other. This is conditional, not a requirement to invent a second contact.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Two designated individuals; first contact not productive.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2",
            "source_context_refs": [
              "DI23005.001:C2"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          },
          {
            "id": "wu-special-handling-contacts-3",
            "title": "If claimant elected no contact, use C.3",
            "kind": "action",
            "actor": "DDS",
            "action": "If claimant elected not to designate a third party, take AT LEAST ONE C.3 locating action. The cross-reference applies here despite C.3 opening otherwise describing no AR/no special handling. Keep selected-action timing, FO jurisdiction and documentation limits; do not require all alternatives.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Claimant elected NOT to designate a third-party contact.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2, C3",
            "source_context_refs": [
              "DI23005.001:C2",
              "DI23005.001:C3"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ],
            "alternative_group": "designated-contact-state"
          },
          {
            "id": "wu-special-handling-contacts-4",
            "title": "Locate contact information and document all efforts",
            "kind": "action",
            "actor": "DDS",
            "action": "Find designated contacts in section2 Contacts of SSA-3368-BK or SSA-3441-BK, or possibly Remarks. Document ALL third-party involvement efforts under C.4 in DCPS Case Note OR CDW.",
            "conditions": [
              "Special handling applies; linked DI23007.001A criteria are not inferred.",
              "Initial or reconsideration disability claim, with claimant not locatable at last known address AND not reachable by telephone.",
              "Whereabouts became unknown while the case is at DDS; this source directs CDR, pre-hearing review and disability hearing unit cases to separate uncaptured policies.",
              "Selecting the illustration establishes no case fact, successful contact, disability outcome or completed system action."
            ],
            "source": "ddswhereaboutsunknown",
            "section": "DI23005.001 C2, C4",
            "source_context_refs": [
              "DI23005.001:C2",
              "DI23005.001:C4"
            ],
            "qualifications": [
              "All linked targets remain linked-unreviewed here, including AR reasonable effort, special-handling criteria/contact procedure, sequential evaluation/MDI/closed-period rules and FO SGA/POD responsibilities. No source status is upgraded by this flow.",
              "Staff instructions refer to DCPS/Case Note/CDW forms as published; no native API, actual system access, transferred jurisdiction or processing-time observation is established.",
              "Do not decide unfavorably solely because whereabouts are unknown. Required locating actions and evidence evaluation are separate; lack of contact is not a disability finding."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant location, contact confirmation, reasonable effort sufficiency and completed response periods are not established.",
            "Source-directed subsequent evidence review/notice/FO-or-DQB routing is an instruction, not proof of successful case continuation or entitlement."
          ]
        },
        "alternative_groups": [
          {
            "id": "designated-contact-state",
            "label": "Designated-contact versus no-designation circumstances",
            "logic": "source_conditions_determine_branch",
            "note": "The no-designation action applies only when claimant elected no contact. Two-contact follow-up applies only after first of two is unproductive; not all cards apply universally."
          }
        ]
      },
      "old_to_new_card_map": {
        "wu-special-handling-contacts-1": "wu-special-handling-contacts-1",
        "wu-special-handling-contacts-2": "wu-special-handling-contacts-1",
        "wu-special-handling-contacts-3": "wu-special-handling-contacts-3",
        "wu-special-handling-contacts-4": "wu-special-handling-contacts-4"
      },
      "reason": "Merge first source contact instruction and its conditional two-contact followup into the SAME designated-contact branch card. Keep no-contact election as separate adjacent alternative; common location/documentation card follows both branches. No sourceinstruction reordered between branches, no helper/schema waiver.",
      "all_old_source_instructions_and_predicates_retained": true
    }
  },
  "uat4_selected": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "FOUR_SELECTED_UAT_SOURCE_SEQUENCES_REVIEWED_NOT_CASE_FINDING",
    "checked_on": "2026-11-01",
    "selected_flow_count": 4,
    "card_count": 13,
    "flows": {
      "disability-intake-evidence/disability-evidence-uat-limited-mainframe-update": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-uat-limited-mainframe-update",
        "full_route": "disability-intake-evidence/disability-evidence-uat-limited-mainframe-update",
        "entry_conditions": [
          "EDCS jurisdiction was transferred",
          "An eligible limited mainframe change is needed",
          "Only the selected published predicate applies; choosing this example does not establish eligibility for UAT or a completed transaction."
        ],
        "steps": [
          {
            "id": "disability-evidence-uat-limited-mainframe-update-1",
            "title": "Correct the eligible source claim information",
            "kind": "action",
            "actor": "FO",
            "action": "Correct the eligible information in MCS or MSSICS before using UAT to repropagate limited data. Examples are claimant name, address, telephone; this is not direct editing of the locked EDCS disability-report forms.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "An eligible limited mainframe change is needed"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A,B",
            "source_context_refs": [
              "DI81010.095:A",
              "DI81010.095:B"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-limited-mainframe-update-2",
            "title": "Open the transferred case and Mainframe Updates",
            "kind": "action",
            "actor": "FO",
            "action": "Open the case in EDCS and select Transfer/Updates. In UAT review changes on Summary of Updates, Mainframe Updates tab. This retains the source-record correction before review/send order.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "An eligible limited mainframe change is needed"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 B",
            "source_context_refs": [
              "DI81010.095:B"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-limited-mainframe-update-3",
            "title": "Send the reviewed update",
            "kind": "action",
            "actor": "FO",
            "action": "Click OK to send update to DDS or OHO. For Mainframe Updates, EDCS determines office with current jurisdiction and notifies that office; selecting a scenario does not perform the action.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "An eligible limited mainframe change is needed"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 B",
            "source_context_refs": [
              "DI81010.095:B"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-limited-mainframe-update-4",
            "title": "Keep the display and history limits",
            "kind": "action",
            "actor": "FO",
            "action": "UAT does NOT rewrite disability reports viewable in eView. Updated MCS/MSSICS data is shown under Case Data. EDCS produces a ROC for FIRST UAT action only; do not infer a new ROC for each subsequent change.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "An eligible limited mainframe change is needed"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A",
            "source_context_refs": [
              "DI81010.095:A"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual eligible change/filing dates/case jurisdiction/destination and any exclusion must be established.",
            "Sending an update/claim or published automatic alert does not prove human review/receipt/case completion or return to a usual path."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-uat-generic-information": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-uat-generic-information",
        "full_route": "disability-intake-evidence/disability-evidence-uat-generic-information",
        "entry_conditions": [
          "EDCS jurisdiction was transferred",
          "New or changed generic information needs documenting",
          "Only the selected published predicate applies; choosing this example does not establish eligibility for UAT or a completed transaction."
        ],
        "steps": [
          {
            "id": "disability-evidence-uat-generic-information-1",
            "title": "Use Other Updates for generic information",
            "kind": "action",
            "actor": "FO",
            "action": "Open EDCS case and select Transfer/Updates then Other Updates; use an SSA-5002 created in EDCS for new/changed generic information such as medication or new provider. This does not directly edit the original disability report.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "New or changed generic information needs documenting"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A,B,C",
            "source_context_refs": [
              "DI81010.095:A",
              "DI81010.095:B",
              "DI81010.095:C"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-generic-information-2",
            "title": "Enter and review the new information",
            "kind": "action",
            "actor": "FO",
            "action": "Enter new/changed information in the space provided and review ALL changes on Other Updates before sending.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "New or changed generic information needs documenting"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 C",
            "source_context_refs": [
              "DI81010.095:C"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-generic-information-3",
            "title": "Send with the source-specific destination behavior",
            "kind": "action",
            "actor": "FO",
            "action": "Click OK to send update to DDS or OHO. Other Updates determines current jurisdiction office automatically and notifies it; no actual receipt/human review established.",
            "conditions": [
              "EDCS jurisdiction was transferred",
              "New or changed generic information needs documenting"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 B,C",
            "source_context_refs": [
              "DI81010.095:B",
              "DI81010.095:C"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual eligible change/filing dates/case jurisdiction/destination and any exclusion must be established.",
            "Sending an update/claim or published automatic alert does not prove human review/receipt/case completion or return to a usual path."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-document-addition-without-uat": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-document-addition-without-uat",
        "full_route": "disability-intake-evidence/disability-evidence-document-addition-without-uat",
        "entry_conditions": [
          "A form or document is being added to CEF",
          "No separate eligible data update or added-claim action is required",
          "Only the selected published predicate applies; choosing this example does not establish eligibility for UAT or a completed transaction."
        ],
        "steps": [
          {
            "id": "disability-evidence-document-addition-without-uat-1",
            "title": "Do not initiate UAT merely to add a form or document",
            "kind": "action",
            "actor": "FO",
            "action": "Do NOT initiate UAT when adding forms, such as UniForms, or documents, such as faxed medical records, to CEF. This selected route has no separate eligible data-update or added claim requirement; their distinct UAT instructions are not waived.",
            "conditions": [
              "A form or document is being added to CEF",
              "No separate eligible data update or added-claim action is required"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A",
            "source_context_refs": [
              "DI81010.095:A"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-document-addition-without-uat-2",
            "title": "Keep the automatic alert scope limited",
            "kind": "action",
            "actor": "FO",
            "action": "The source says adding a document to CEF posts an automatic alert to DDS/OHO case processing systems. This is NOT evidence that UAT ran, that FO/PC universally receives notification, or that alert was reviewed. No alert latency measured.",
            "conditions": [
              "A form or document is being added to CEF",
              "No separate eligible data update or added-claim action is required"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A",
            "source_context_refs": [
              "DI81010.095:A"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual eligible change/filing dates/case jurisdiction/destination and any exclusion must be established.",
            "Sending an update/claim or published automatic alert does not prove human review/receipt/case completion or return to a usual path."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-uat-add-claim": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-uat-add-claim",
        "full_route": "disability-intake-evidence/disability-evidence-uat-add-claim",
        "entry_conditions": [
          "At least one claim is already under DDS or OHO jurisdiction",
          "UAT filing-date and case-age guards permit adding the claim",
          "Only the selected published predicate applies; choosing this example does not establish eligibility for UAT or a completed transaction."
        ],
        "steps": [
          {
            "id": "disability-evidence-uat-add-claim-1",
            "title": "Check transferred-claim and date restrictions",
            "kind": "action",
            "actor": "FO",
            "action": "At least one claim on the case must already have been transferred to DDS or OHO. UAT is blocked if the claim effective filing date is more than 13 months LATER THAN the current claim’s effective filing date. When a NEW claim is being added, it is also blocked if the initial or reconsideration claim’s effective filing date is more than 18 months LATER THAN the EDCS case establishment date, OR the hearing-level claim’s effective filing date is more than 24 months LATER THAN the EDCS case establishment date. Keep each claim-level predicate and comparison origin distinct; an earlier filing date does not trigger these stated later-than restrictions. These are internal utility restrictions, not benefit-filing deadlines. When blocked, EDCS displays an edit and returns the user to the previous page.",
            "conditions": [
              "At least one claim is already under DDS or OHO jurisdiction",
              "UAT filing-date and case-age guards permit adding the claim"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 A,D",
            "source_context_refs": [
              "DI81010.095:A",
              "DI81010.095:D"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-add-claim-2",
            "title": "Select the pending FO claim in Transfer Claims",
            "kind": "action",
            "actor": "FO",
            "action": "Open the EDCS case, choose Transfer/Updates then Transfer Claims, and select the claim pending at FO. Transfer Claims permits office choice from dropdown or manual destination, unlike automatic office determination in the other UAT tabs.",
            "conditions": [
              "At least one claim is already under DDS or OHO jurisdiction",
              "UAT filing-date and case-age guards permit adding the claim"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 B,D",
            "source_context_refs": [
              "DI81010.095:B",
              "DI81010.095:D"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-add-claim-3",
            "title": "Send to the authorized adjudicative destination",
            "kind": "action",
            "actor": "FO",
            "action": "Click OK to send claim to DDS or OHO as applicable. NEVER route an ADDED claim directly to OQR even if a claim is pending there; send added claim to DDS first for decision, then DDS routes to OQR. This does not assert a completed DDS decision or OQR receipt.",
            "conditions": [
              "At least one claim is already under DDS or OHO jurisdiction",
              "UAT filing-date and case-age guards permit adding the claim"
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 D",
            "source_context_refs": [
              "DI81010.095:D"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          },
          {
            "id": "disability-evidence-uat-add-claim-4",
            "title": "Keep an excluded added claim separate",
            "kind": "action",
            "actor": "FO",
            "action": "IF added claim is an EDCS exclusion, follow linked DI81010.030/MDF conversion instructions; this selected flow does not newly establish their criteria or completed conversion. Preserve required paper route review rather than assuming electronic addition succeeds.",
            "conditions": [
              "At least one claim is already under DDS or OHO jurisdiction",
              "UAT filing-date and case-age guards permit adding the claim",
              "Added claim is an EDCS exclusion, if this conditional card applies."
            ],
            "source": "dis72_DI81010_095",
            "section": "DI81010.095 D",
            "source_context_refs": [
              "DI81010.095:D"
            ],
            "qualifications": [
              "Published UAT internal blocks: claim effective filing date more than 13 months after current claim effective filing date; when ADDING a new initial/reconsideration claim, effective filing date more than 18 months after EDCS case establishment; when ADDING a hearing-level claim, more than 24 months after establishment. Preserve each predicate and comparison origin; these are utility restrictions, not filing/appeal deadlines.",
              "UAT Mainframe Updates and Other Updates automatically determine the office with jurisdiction and notify it; Transfer Claims allows destination choice from list or manual entry. Do not generalize automatic destination to added claims.",
              "UAT does not update disability reports viewable in eView; MCS/MSSICS updated data appears under eView Case Data. Only FIRST UAT action produces a Record of Change; subsequent actions do not produce additional ROCs.",
              "Source publication only: no actual UAT permission/record change/alert receipt/human review/claim decision/native API or successful rejoin observed. Original source objects/history/relationship scopes unchanged.",
              "Linked DI81010.045, DI81005.045 and DI81010.030/MDF conversion details remain unreviewed here. Whole E escalation instructions retained context, not mapped as one of these 4 flows."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual eligible change/filing dates/case jurisdiction/destination and any exclusion must be established.",
            "Sending an update/claim or published automatic alert does not prove human review/receipt/case completion or return to a usual path."
          ]
        }
      }
    },
    "original_records": {
      "disability-intake-evidence/disability-evidence-uat-limited-mainframe-update": {
        "id": "disability-evidence-uat-limited-mainframe-update",
        "title": "Selected mainframe information changes after transfer",
        "when": "EDCS jurisdiction was transferred; An eligible limited mainframe change is needed",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Correct the source claim record, review Mainframe Updates in UAT and send the update to the office with jurisdiction. Scope and qualifications: Limited examples include name, address and telephone. The original EDCS disability reports are locked; changed data is shown in eView Case Data rather than rewriting the report. Only the first UAT action creates a new record-of-change snapshot under the cited note.",
        "route": "Published handling by FO; see the cited instructions.",
        "next": "Check the source record, pending change and destination.",
        "source": "dis72_DI81010_095",
        "section": "A",
        "additional_sources": [
          {
            "source": "dis72_DI81010_095",
            "section": "B"
          }
        ],
        "owner": "FO",
        "systems": [
          "MCS",
          "MSSICS",
          "UAT",
          "EDCS",
          "eView"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-view",
        "conditions": [
          "EDCS jurisdiction was transferred",
          "An eligible limited mainframe change is needed"
        ],
        "condition_logic": "all",
        "qualifications": [
          "Limited examples include name, address and telephone.",
          "The original EDCS disability reports are locked; changed data is shown in eView Case Data rather than rewriting the report.",
          "Only the first UAT action creates a new record-of-change snapshot under the cited note."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "A",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 320,
            "end": 2667,
            "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          },
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "B",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 2667,
            "end": 3749,
            "span_sha256": "83ab63ea0b115911f3273bc2587da1c05a68b0ecd2934d4b9b61528d8c215a9a",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-uat-limited-mainframe-update",
          "parent_stage_id": "evidence-view",
          "title": "Selected mainframe information changes after transfer",
          "conditions": [
            "EDCS jurisdiction was transferred",
            "An eligible limited mainframe change is needed"
          ],
          "ui_text": {
            "when": "EDCS jurisdiction was transferred; An eligible limited mainframe change is needed",
            "ssa_action": "Correct the source claim record, review Mainframe Updates in UAT and send the update to the office with jurisdiction.",
            "what_to_check": "Check the source record, pending change and destination."
          },
          "owner": "FO",
          "entity_ids": [
            "APP_MCS",
            "APP_MSSICS",
            "UTIL_EDCS_UAT",
            "APP_EDCS",
            "APP_EVIEW"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "A",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 320,
              "end": 2667,
              "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            },
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "B",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 2667,
              "end": 3749,
              "span_sha256": "83ab63ea0b115911f3273bc2587da1c05a68b0ecd2934d4b9b61528d8c215a9a",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "Limited examples include name, address and telephone.",
            "The original EDCS disability reports are locked; changed data is shown in eView Case Data rather than rewriting the report.",
            "Only the first UAT action creates a new record-of-change snapshot under the cited note."
          ],
          "existing_relationship_ids": [
            "R33REL007",
            "R33REL008",
            "R33REL010"
          ],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      },
      "disability-intake-evidence/disability-evidence-uat-generic-information": {
        "id": "disability-evidence-uat-generic-information",
        "title": "New information needs a post-transfer contact report",
        "when": "EDCS jurisdiction was transferred; New or changed generic information needs documenting",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Use UAT Other Updates to create an SSA-5002, review the change and send it to DDS or OHO. Scope and qualifications: Examples include medication or a newly identified provider. Creating a contact report is distinct from directly editing original disability-report forms.",
        "route": "Published handling by FO; see the cited instructions.",
        "next": "Confirm the report of contact and receiving office.",
        "source": "dis72_DI81010_095",
        "section": "A",
        "additional_sources": [
          {
            "source": "dis72_DI81010_095",
            "section": "C"
          }
        ],
        "owner": "FO",
        "systems": [
          "UAT",
          "SSA-5002",
          "CEF"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-view",
        "conditions": [
          "EDCS jurisdiction was transferred",
          "New or changed generic information needs documenting"
        ],
        "condition_logic": "all",
        "qualifications": [
          "Examples include medication or a newly identified provider.",
          "Creating a contact report is distinct from directly editing original disability-report forms."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "A",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 320,
            "end": 2667,
            "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          },
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "C",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 3749,
            "end": 4390,
            "span_sha256": "02674e8ad3de6f72bf30c74643b3dce37b52e88980b37e32b11b0a24753d5f1d",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-uat-generic-information",
          "parent_stage_id": "evidence-view",
          "title": "New information needs a post-transfer contact report",
          "conditions": [
            "EDCS jurisdiction was transferred",
            "New or changed generic information needs documenting"
          ],
          "ui_text": {
            "when": "EDCS jurisdiction was transferred; New or changed generic information needs documenting",
            "ssa_action": "Use UAT Other Updates to create an SSA-5002, review the change and send it to DDS or OHO.",
            "what_to_check": "Confirm the report of contact and receiving office."
          },
          "owner": "FO",
          "entity_ids": [
            "UTIL_EDCS_UAT",
            "FORM_SSA5002",
            "REPO_CEF"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "A",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 320,
              "end": 2667,
              "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            },
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "C",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 3749,
              "end": 4390,
              "span_sha256": "02674e8ad3de6f72bf30c74643b3dce37b52e88980b37e32b11b0a24753d5f1d",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "Examples include medication or a newly identified provider.",
            "Creating a contact report is distinct from directly editing original disability-report forms."
          ],
          "existing_relationship_ids": [
            "R49_REL044",
            "R49_REL045"
          ],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      },
      "disability-intake-evidence/disability-evidence-document-addition-without-uat": {
        "id": "disability-evidence-document-addition-without-uat",
        "title": "Add a form or document after transfer",
        "when": "A form or document is being added to CEF; No separate eligible data update or added-claim action is required",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Use the applicable document-addition route; do not start UAT solely for adding the document. Scope and qualifications: The cited automatic alert is to DDS/OHO case-processing systems. It does not establish universal PC/FO notification, successful human review or measured latency.",
        "route": "Published handling by Authorized component; see the cited instructions.",
        "next": "Verify actual folder placement separately from alert generation.",
        "source": "dis72_DI81010_095",
        "section": "A",
        "additional_sources": [],
        "owner": "Authorized component",
        "systems": [
          "EDCS",
          "eView",
          "CEF"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-view",
        "conditions": [
          "A form or document is being added to CEF",
          "No separate eligible data update or added-claim action is required"
        ],
        "condition_logic": "all",
        "qualifications": [
          "The cited automatic alert is to DDS/OHO case-processing systems.",
          "It does not establish universal PC/FO notification, successful human review or measured latency."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "A",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 320,
            "end": 2667,
            "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-document-addition-without-uat",
          "parent_stage_id": "evidence-view",
          "title": "Add a form or document after transfer",
          "conditions": [
            "A form or document is being added to CEF",
            "No separate eligible data update or added-claim action is required"
          ],
          "ui_text": {
            "when": "A form or document is being added to CEF; No separate eligible data update or added-claim action is required",
            "ssa_action": "Use the applicable document-addition route; do not start UAT solely for adding the document.",
            "what_to_check": "Verify actual folder placement separately from alert generation."
          },
          "owner": "Authorized component",
          "entity_ids": [
            "APP_EDCS",
            "APP_EVIEW",
            "REPO_CEF"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "A",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 320,
              "end": 2667,
              "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "The cited automatic alert is to DDS/OHO case-processing systems.",
            "It does not establish universal PC/FO notification, successful human review or measured latency."
          ],
          "existing_relationship_ids": [],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      },
      "disability-intake-evidence/disability-evidence-uat-add-claim": {
        "id": "disability-evidence-uat-add-claim",
        "title": "Add an eligible claim to a transferred case",
        "when": "At least one claim is already under DDS or OHO jurisdiction; UAT filing-date and case-age guards permit adding the claim",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Use Transfer Claims and route the added claim to the appropriate office; DDS decides it before any OQR routing. Scope and qualifications: Never send an added claim directly to OQR. An EDCS-excluded added claim requires paper-folder conversion review. The source blockers below are internal utility guards, not filing or appeal deadlines. Utility guard — UAT blocked: Claim effective filing date is more than 13 months after the current claim effective filing date. Utility guard — UAT blocked: New initial/reconsideration claim effective filing date is more than 18 months after EDCS case establishment. Utility guard — UAT blocked: New hearing-level claim effective filing date is more than 24 months after EDCS case establishment.",
        "route": "Published handling by FO; see the cited instructions.",
        "next": "Check all applicable guards and the added claim destination.",
        "source": "dis72_DI81010_095",
        "section": "A",
        "additional_sources": [
          {
            "source": "dis72_DI81010_095",
            "section": "D"
          }
        ],
        "owner": "FO",
        "systems": [
          "UAT",
          "EDCS",
          "DDS"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-view",
        "conditions": [
          "At least one claim is already under DDS or OHO jurisdiction",
          "UAT filing-date and case-age guards permit adding the claim"
        ],
        "condition_logic": "all",
        "qualifications": [
          "Never send an added claim directly to OQR.",
          "An EDCS-excluded added claim requires paper-folder conversion review.",
          "The source blockers below are internal utility guards, not filing or appeal deadlines."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "A",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 320,
            "end": 2667,
            "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          },
          {
            "source_code": "DI81010.095",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
            "locator": "D",
            "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
            "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
            "start": 4390,
            "end": 5241,
            "span_sha256": "83057bdb2a5a264c901948342c5aef46db1ecbacea718afb9eb608b36b13cc2a",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-uat-add-claim",
          "parent_stage_id": "evidence-view",
          "title": "Add an eligible claim to a transferred case",
          "conditions": [
            "At least one claim is already under DDS or OHO jurisdiction",
            "UAT filing-date and case-age guards permit adding the claim"
          ],
          "ui_text": {
            "when": "At least one claim is already under DDS or OHO jurisdiction; UAT filing-date and case-age guards permit adding the claim",
            "ssa_action": "Use Transfer Claims and route the added claim to the appropriate office; DDS decides it before any OQR routing.",
            "what_to_check": "Check all applicable guards and the added claim destination."
          },
          "owner": "FO",
          "entity_ids": [
            "UTIL_EDCS_UAT",
            "APP_EDCS",
            "ORG_DDS"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "A",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 320,
              "end": 2667,
              "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            },
            {
              "source_code": "DI81010.095",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010095",
              "locator": "D",
              "text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
              "raw_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
              "start": 4390,
              "end": 5241,
              "span_sha256": "83057bdb2a5a264c901948342c5aef46db1ecbacea718afb9eb608b36b13cc2a",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "Never send an added claim directly to OQR.",
            "An EDCS-excluded added claim requires paper-folder conversion review.",
            "The source blockers below are internal utility guards, not filing or appeal deadlines."
          ],
          "existing_relationship_ids": [],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "guard_conditions": [
            {
              "effect": "UAT blocked",
              "condition": "Claim effective filing date is more than 13 months after the current claim effective filing date"
            },
            {
              "effect": "UAT blocked",
              "condition": "New initial/reconsideration claim effective filing date is more than 18 months after EDCS case establishment"
            },
            {
              "effect": "UAT blocked",
              "condition": "New hearing-level claim effective filing date is more than 24 months after EDCS case establishment"
            }
          ],
          "condition_logic": "all",
          "journey_scope_label": "Related added-claim path"
        }
      }
    },
    "source_contexts": [
      {
        "id": "DI81010.095:whole",
        "source_code": "DI81010.095",
        "start": 0,
        "end": 6411,
        "exact_text": "SSA - POMS: DI 81010.095 - Using the Update-After-Transfer (UAT) Utility - 09/09/2009\nSkip to content\nSocial Security\nSearch\nMenu\nLanguages\nSign in / up\nProgram Operations Manual System (POMS)\nEffective Dates: 09/09/2009 - Present\nPrevious | Next\nTN 67 (12-23)\nDI 81010.095 Using the Update-After-Transfer (UAT) Utility\nA. Overview\nAfter transferring jurisdiction of an Electronic Disability Collect System (EDCS)\ncase, use the UAT utility to:\n•\nUpdate certain Modernized Claims System (MCS) or Modernized Supplemental Security\nIncome Claims System (MSSICS), or Consolidated Claims Experience (CCE) changes in\nEDCS;\n•\nAdd information to the Certified Electronic Folder (CEF) by creating an SSA – 5002\n(Report of Contact) in EDCS;\n•\nAdd a claim. To add a claim, at least one claim must already have been transferred\nto the jurisdiction of the Disability Determination Services (DDS) or the Office of\nHearings Operations (OHO); or\n•\nAdd an escalated claim to a case. To add an escalated claim, at least one claim must\nalready be at the reconsideration or hearing level.\nThe field office user can access the UAT utility after they select a disability case\nfrom the Disability Case Selection page. EDCS then displays a primary page with a\ncase function toolbar that allows the user to select the Transfer/Updates link. The\nTransfer/Updates link directs the user to the UAT page, which displays the Summary\nof Updates screen. The Summary of Updates screen is broken down into tabs:\n•\nMainframe Updates,\n•\nOther Updates, and\n•\nTransfer Claims.\nNOTE: Do not initiate the UAT when adding forms (such UniForms), or documents (such as faxing\nmedical records) to the CEF. An automatic alert posts to the DDS and OHO's case processing\nsystems when adding a document to a CEF.\nThe UAT process will be blocked in the following situations:\n•\nThe claim effective filing date is more than 13 months later than the current claim's\neffective filing date; or\n•\nA new claim is being added and the initial or reconsideration level claim's effective\nfiling date is more than 18 months later than the EDCS case establishment date; or\na new claim is being added and the hearing level claim's effective filing date is\nmore than 24 months later than the EDCS case establishment date.\nIn these instances, EDCS will display an edit message and return the user to the previous\npage.\nNOTE: UATs are not displayed and do not update the disability reports viewable in eView.\nData updated from MCS or MSSICS is shown under the Case Data Tab in eView (see Case\nData Tab - DI 81005.045. EDCS produces a Record of Change for the first UAT action only. Subsequent actions\ndo not produce additional ROCs..\nB. Updating Certain MCS or MSSICS Changes in EDCS\nOnce an EDCS case is transferred, EDCS locks and no changes can be made directly to\nthe disability report forms. Limited data can be repropagated into EDCS (e.g., claimant\nname, address, and telephone number) using the UAT procedure. See DI 81010.045 for more information.\nTo update MCS or MSSICS information on a case after transfer of jurisdiction of an\nEDCS case:\n•\nCorrect the information in MCS or MSSICS;\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates tab on the toolbar at the top of the EDCS screen path;\n•\nReview the changes on the Summary of Updates screen on the Mainframe Updates tab;\nand\n•\nClick the OK button to send update to DDS or OHO.\nNOTE: For UATs on the Mainframe Updates and Other Updates tab, EDCS will automatically\ndetermine the office that currently has jurisdiction and notify the office of the\nupdate. For UATs on Transfer Claims tab, EDCS allows users to choose which office\nthe claim(s) should be transferred to from a drop-down list, or it will allow them\nto manually enter an office destination.\nC. Creating an SSA-5002 in EDCS\nAdd information to the CEF by creating an SSA-5002 in EDCS. Users can use this method\nto add new or changed generic information. For example, this method can be used to\nupdate information on a disability report, such as new medication or a new provider\nsource.\nTo update information via an SSA-5002 in EDCS:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Other Updates tab, and enter the new or changed information in the space\nprovided;\n•\nReview all changes on the Other Updates tab; and\n•\nClick the OK button to send update to DDS or OHO.\nD. Adding a Claim to a Case\nUse the UAT utility to add a claim to a case if at least one claim on the case has\nbeen transferred to the jurisdiction of the DDS or OHO.\nTo add a claim in EDCS:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Transfer Claims tab;,\n•\nSelect the claim pending at the field office; and\n•\nClick the OK button to send the claim to DDS or OHO.\nREMINDERS for adding a claim:\n•\nNever route an added claim to the Office of Quality Review (OQR), even if a claim\nis pending at OQR. Send the added claim to DDS, who must first make a decision and\nthen route the claim to OQR.\n•\nIf the added claim is an EDCS exclusion, see Certified Electronic Folder (CEF) Exclusions\n- DI 81010.030 or instructions on converting the case to a paper Modular Disability Folder (MDF).\nE. Adding an Escalated Claim to a Case\nUse the UAT utility to add an escalated claim to a case if there is at least one claim\nat the reconsideration or hearing level, and a new claim needs to be escalated to\nthat same level.\nTo add an escalated claim:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Transfer Claims tab;\n•\nSelect the claim pending at the field office; and\n•\nClick the OK button to send the escalated claim to DDS or OHO.\nNOTE: Never route an “escalated” claim to OQR, even if there is a pending claim in OQR.\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0481010095\nDI 81010.095 - Using the Update-After-Transfer (UAT) Utility - 09/09/2009\nBatch run: 04/28/2025\nRev:09/09/2009\nImportant Information:\nAccessibility\nFOIA\nOpen Government\nGlossary\nPrivacy\nReport Fraud, Waste or Abuse\nSite Map\nWebsite Policies\nOther Government Websites:\nBenefits.gov\nDisability.gov\nHealthcare.gov\nMyMoney.gov\nRegulations.gov\nUSA.gov\nOther Government Sites\nFollow:\nTwitter\nFacebook\nYouTube\nBlog\nMore Social Media\nThis website is produced and published at U.S. taxpayer expense.\n",
        "span_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
        "locator": "Whole retained captured text; capturepublication not currentruntime"
      },
      {
        "id": "DI81010.095:A",
        "source_code": "DI81010.095",
        "start": 320,
        "end": 2667,
        "exact_text": "A. Overview\nAfter transferring jurisdiction of an Electronic Disability Collect System (EDCS)\ncase, use the UAT utility to:\n•\nUpdate certain Modernized Claims System (MCS) or Modernized Supplemental Security\nIncome Claims System (MSSICS), or Consolidated Claims Experience (CCE) changes in\nEDCS;\n•\nAdd information to the Certified Electronic Folder (CEF) by creating an SSA – 5002\n(Report of Contact) in EDCS;\n•\nAdd a claim. To add a claim, at least one claim must already have been transferred\nto the jurisdiction of the Disability Determination Services (DDS) or the Office of\nHearings Operations (OHO); or\n•\nAdd an escalated claim to a case. To add an escalated claim, at least one claim must\nalready be at the reconsideration or hearing level.\nThe field office user can access the UAT utility after they select a disability case\nfrom the Disability Case Selection page. EDCS then displays a primary page with a\ncase function toolbar that allows the user to select the Transfer/Updates link. The\nTransfer/Updates link directs the user to the UAT page, which displays the Summary\nof Updates screen. The Summary of Updates screen is broken down into tabs:\n•\nMainframe Updates,\n•\nOther Updates, and\n•\nTransfer Claims.\nNOTE: Do not initiate the UAT when adding forms (such UniForms), or documents (such as faxing\nmedical records) to the CEF. An automatic alert posts to the DDS and OHO's case processing\nsystems when adding a document to a CEF.\nThe UAT process will be blocked in the following situations:\n•\nThe claim effective filing date is more than 13 months later than the current claim's\neffective filing date; or\n•\nA new claim is being added and the initial or reconsideration level claim's effective\nfiling date is more than 18 months later than the EDCS case establishment date; or\na new claim is being added and the hearing level claim's effective filing date is\nmore than 24 months later than the EDCS case establishment date.\nIn these instances, EDCS will display an edit message and return the user to the previous\npage.\nNOTE: UATs are not displayed and do not update the disability reports viewable in eView.\nData updated from MCS or MSSICS is shown under the Case Data Tab in eView (see Case\nData Tab - DI 81005.045. EDCS produces a Record of Change for the first UAT action only. Subsequent actions\ndo not produce additional ROCs..\n",
        "span_sha256": "57b7992e27f1c159c2c8e9fbcb78e2eb33c6c822395934e4a0b6383d403fa930",
        "locator": "A"
      },
      {
        "id": "DI81010.095:B",
        "source_code": "DI81010.095",
        "start": 2667,
        "end": 3749,
        "exact_text": "B. Updating Certain MCS or MSSICS Changes in EDCS\nOnce an EDCS case is transferred, EDCS locks and no changes can be made directly to\nthe disability report forms. Limited data can be repropagated into EDCS (e.g., claimant\nname, address, and telephone number) using the UAT procedure. See DI 81010.045 for more information.\nTo update MCS or MSSICS information on a case after transfer of jurisdiction of an\nEDCS case:\n•\nCorrect the information in MCS or MSSICS;\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates tab on the toolbar at the top of the EDCS screen path;\n•\nReview the changes on the Summary of Updates screen on the Mainframe Updates tab;\nand\n•\nClick the OK button to send update to DDS or OHO.\nNOTE: For UATs on the Mainframe Updates and Other Updates tab, EDCS will automatically\ndetermine the office that currently has jurisdiction and notify the office of the\nupdate. For UATs on Transfer Claims tab, EDCS allows users to choose which office\nthe claim(s) should be transferred to from a drop-down list, or it will allow them\nto manually enter an office destination.\n",
        "span_sha256": "83ab63ea0b115911f3273bc2587da1c05a68b0ecd2934d4b9b61528d8c215a9a",
        "locator": "B"
      },
      {
        "id": "DI81010.095:C",
        "source_code": "DI81010.095",
        "start": 3749,
        "end": 4390,
        "exact_text": "C. Creating an SSA-5002 in EDCS\nAdd information to the CEF by creating an SSA-5002 in EDCS. Users can use this method\nto add new or changed generic information. For example, this method can be used to\nupdate information on a disability report, such as new medication or a new provider\nsource.\nTo update information via an SSA-5002 in EDCS:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Other Updates tab, and enter the new or changed information in the space\nprovided;\n•\nReview all changes on the Other Updates tab; and\n•\nClick the OK button to send update to DDS or OHO.\n",
        "span_sha256": "02674e8ad3de6f72bf30c74643b3dce37b52e88980b37e32b11b0a24753d5f1d",
        "locator": "C"
      },
      {
        "id": "DI81010.095:D",
        "source_code": "DI81010.095",
        "start": 4390,
        "end": 5241,
        "exact_text": "D. Adding a Claim to a Case\nUse the UAT utility to add a claim to a case if at least one claim on the case has\nbeen transferred to the jurisdiction of the DDS or OHO.\nTo add a claim in EDCS:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Transfer Claims tab;,\n•\nSelect the claim pending at the field office; and\n•\nClick the OK button to send the claim to DDS or OHO.\nREMINDERS for adding a claim:\n•\nNever route an added claim to the Office of Quality Review (OQR), even if a claim\nis pending at OQR. Send the added claim to DDS, who must first make a decision and\nthen route the claim to OQR.\n•\nIf the added claim is an EDCS exclusion, see Certified Electronic Folder (CEF) Exclusions\n- DI 81010.030 or instructions on converting the case to a paper Modular Disability Folder (MDF).\n",
        "span_sha256": "83057bdb2a5a264c901948342c5aef46db1ecbacea718afb9eb608b36b13cc2a",
        "locator": "D"
      },
      {
        "id": "DI81010.095:E",
        "source_code": "DI81010.095",
        "start": 5241,
        "end": 5834,
        "exact_text": "E. Adding an Escalated Claim to a Case\nUse the UAT utility to add an escalated claim to a case if there is at least one claim\nat the reconsideration or hearing level, and a new claim needs to be escalated to\nthat same level.\nTo add an escalated claim:\n•\nOpen the case in EDCS;\n•\nSelect Transfer/Updates on the toolbar at the top of the EDCS screen path;\n•\nSelect the Transfer Claims tab;\n•\nSelect the claim pending at the field office; and\n•\nClick the OK button to send the escalated claim to DDS or OHO.\nNOTE: Never route an “escalated” claim to OQR, even if there is a pending claim in OQR.\n",
        "span_sha256": "373fab30638690a8c627fcfa9c2cd5ae4966bfed6a0a2c7a4eb2a5ad0f20915d",
        "locator": "E"
      }
    ],
    "whole_text_sha256": "05dc03c608ab3395009886cbad27b97e74544f6d9fa67bdbd22fd4975d869cec",
    "raw_capture_sha256": "c9806d9149b94bcced77cb764bbacbe2abbbf899e7d309e49dfaf1028a9dc395",
    "captured_utc": "2026-10-31T00:36:52.504763+00:00",
    "review_scope": "Whole retained DI81010.095 A-E read for selected A-D4routes. E escalatedclaim remains context/unmodeled; linked contents not promoted.",
    "source_peer_sha256": "123624c11dba52c342e04fd8bde2c482ff2d5726fc59a43956c2cf17102dd603",
    "directional_correction": {
      "prior_R1_patch_sha256": "37266588e9ebed92b1c0c360dc1fbd2ae8432829e59a806e5e3bf907a3010a32",
      "hold": "D5 HOLD1d4c4db1 directional-date predicate",
      "route": "disability-intake-evidence/disability-evidence-uat-add-claim",
      "card_id": "disability-evidence-uat-add-claim-1",
      "field": "action",
      "original_R1_action": "AtleastONEclaim on case must already be transferred to DDS or OHO. Apply sourceA internalblocks: >13months effective-date difference; for newinitial/reconsideration >18months from EDCSestablishment, or hearing-level >24months. These separateconditionalguards are not benefitfiling deadlines; blockedprocess displays edit and returns previouspage.",
      "replacement_R2_action": "At least one claim on the case must already have been transferred to DDS or OHO. UAT is blocked if the claim effective filing date is more than 13 months LATER THAN the current claim’s effective filing date. When a NEW claim is being added, it is also blocked if the initial or reconsideration claim’s effective filing date is more than 18 months LATER THAN the EDCS case establishment date, OR the hearing-level claim’s effective filing date is more than 24 months LATER THAN the EDCS case establishment date. Keep each claim-level predicate and comparison origin distinct; an earlier filing date does not trigger these stated later-than restrictions. These are internal utility restrictions, not benefit-filing deadlines. When blocked, EDCS displays an edit and returns the user to the previous page.",
      "exact_primary_direction_spans": [
        {
          "start": 1827,
          "end": 1938,
          "exact_text": "The claim effective filing date is more than 13 months later than the current claim's\neffective filing date; or",
          "span_sha256": "01658bd7b3682057fc7e37ac60a1b5a633a19ed05befa0127ebb4f2ab62460b7",
          "coordinate_system": "whole retained source Unicode codepoints"
        },
        {
          "start": 1941,
          "end": 2256,
          "exact_text": "A new claim is being added and the initial or reconsideration level claim's effective\nfiling date is more than 18 months later than the EDCS case establishment date; or\na new claim is being added and the hearing level claim's effective filing date is\nmore than 24 months later than the EDCS case establishment date.",
          "span_sha256": "85914ae8b85e77b242edd43175f5800fc2ae8b2e28488f25ab854fc625215758",
          "coordinate_system": "whole retained source Unicode codepoints"
        }
      ],
      "source_contexts_pins_unchanged": true,
      "only_one_action_changed": true,
      "WU4representation_fix": "Root/lead-owned separate corrected3card representation, not touched here"
    },
    "source_patch_sha256": "aad8629604a50c50a925ac329eae6a0a40685cbdd429a937a428befe4c1ec859",
    "limits": [
      "All source521 objects, original dates/status/history and prior245flows retained exactly.",
      "13LATERcurrentclaimfilingdate vs NEWinitial/recon18/hearing24LATEREDCSestablishment are internalutilityblocks, not filingdeadlines.",
      "OnlyfirstUATactionproducesROC; reportsarenotrewritten. Mainframe/Otherautojurisdiction differs fromTransferClaimschoice.",
      "Addingforms/documentsalone doesnotinitiateUAT; publishedalert notactualreceipt/review. NeveraddedclaimdirectlytoOQR; exclusionconversionlinkedheld.",
      "No nativeidentity/operation/permission/eligibility/caseoutcome or successfulrejoin is inferred."
    ]
  },
  "iar2_selected": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "TWO_SELECTED_IAR_PROTECTIVE_FILING_SEQUENCES_SOURCE_REVIEWED_NOT_CASE_FINDINGS",
    "checked_on": "2026-11-01",
    "selected_flow_count": 2,
    "card_count": 10,
    "flows": {
      "apply-ssi/iar-manual-earlier-filing-development": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "iar-manual-earlier-filing-development",
        "full_route": "apply-ssi/iar-manual-earlier-filing-development",
        "entry_conditions": [
          "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
          "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
          "This is a manual-notification State case; do not substitute the automated PR-73 date rule."
        ],
        "steps": [
          {
            "id": "iar-manual-earlier-filing-development-source-1",
            "title": "Check the initial-claim protective-filing scope",
            "kind": "action",
            "actor": "FO",
            "action": "Before using an earlier filing date, apply the earlier-date AND initial-claim alternatives in SI02003.007 A. An authorization alone is not a completed SSI application.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule."
            ],
            "source": "iarprotectivefiling",
            "section": "A",
            "source_context_refs": [
              "SI02003.007:whole"
            ],
            "qualifications": [
              "The postdenial alternative requires appeal reversal AND the source-conditioned use for reimbursement if retroactive payment is due; denial alone does not satisfy it. The separate post-withdrawal rule in B.2 is retained as context, not silently added to this route.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-manual-earlier-filing-development-source-2",
            "title": "Use the manual State receipt date and application condition",
            "kind": "action",
            "actor": "FO",
            "action": "Use the date the State IAR representative signed the authorization as the date received by the State. If the individual files an application within 60 days of that State receipt date, use that receipt date as the protective filing date subject to the initial-claim scope. If the application is filed more than 60 days after State receipt of the signed authorization, use the SSI application filing date as the effective filing date.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule."
            ],
            "source": "iarprotectivefiling",
            "section": "B.1 manual notification; B.1 common more-than-60-day instruction; B.4 qualification",
            "source_context_refs": [
              "SI02003.007:whole"
            ],
            "qualifications": [
              "The 60-day condition is an application/protective-filing rule, not an SSA processing SLA. SI02003.007 B.4 says late State notification beyond 30 calendar days after State receipt makes the authorization nonbinding with no effective life for reimbursement, but it still serves as protective filing if the application is filed within 60 days of State receipt. Do not silently turn reimbursement ineffectiveness into loss of that protective filing.",
              "Within 60 days includes the stated boundary; the source does not specify working days or supply an individual date computation. The manual State-representative signature date is not replaced with the individual-signature presumption from the automated rule.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-manual-earlier-filing-development-source-3",
            "title": "Redevelop a processed claim only on the stated trigger",
            "kind": "action",
            "actor": "FO",
            "action": "If an effective IAR authorization is discovered after the initial claim was processed AND the signed authorization establishes an earlier protective filing date, redevelop the claim based on that earlier protective filing date.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule.",
              "An effective IAR authorization was discovered after processing AND its signed authorization establishes an earlier protective filing date."
            ],
            "source": "iarprotectivefiling",
            "section": "B.3",
            "source_context_refs": [
              "SI02003.007:whole"
            ],
            "qualifications": [
              "The effective-authorization requirement here belongs to B.3 postprocessing redevelopment. It is not a blanket condition that erases the distinct late-notification protective-filing rule in B.4.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-manual-earlier-filing-development-source-4",
            "title": "Correct the application date and review the earlier period",
            "kind": "action",
            "actor": "FO",
            "action": "Under the manual-notification instructions, input the corrected application date if the authorization identifies a protective filing and review eligibility back to that protective filing date.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule.",
              "The selected action is within SI02003.020 B manual-notification processing and the authorization identifies a protective filing date; the applicable source prerequisites have been checked."
            ],
            "source": "iarforeturn",
            "section": "B protective-filing input and eligibility-review bullet",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "SI02003.020 B separately checks correct completion, State and individual signatures, and FO receipt within 30 days from the individual signature date. This receipt anchor is distinct from the State-receipt anchor in SI02003.007 B.4. This card does not expand reimbursement processing to an ineffective form or negate the separate protective-filing rule.",
              "A date correction or review does not establish eligibility or payment. The source also requires the correct application date on the SSR when UPV:V is built; reimbursement/prepayment processing, GR-code authority and actual system operation are not reproduced or adopted by this flow.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-manual-earlier-filing-development-source-5",
            "title": "Notify the pending disability component when applicable",
            "kind": "action",
            "actor": "FO",
            "action": "Notify DDS OR the Office of Hearings Operations of the protective filing date if a disability claim is pending at DDS or OHO.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule.",
              "The selected action is within SI02003.020 B manual-notification processing and the authorization identifies a protective filing date; the applicable source prerequisites have been checked.",
              "A disability claim is pending at DDS OR OHO."
            ],
            "source": "iarforeturn",
            "section": "B pending-DDS-or-OHO notification bullet",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "SI02003.020 B separately checks correct completion, State and individual signatures, and FO receipt within 30 days from the individual signature date. This receipt anchor is distinct from the State-receipt anchor in SI02003.007 B.4. This card does not expand reimbursement processing to an ineffective form or negate the separate protective-filing rule.",
              "This is the source’s conditional manual-processing notification. It is not proof of a sent/received alert, component review or a successful transfer. It is not automatically assigned to the automated PR-73 branch.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-manual-earlier-filing-development-source-6",
            "title": "Document the signed form before disposing of the paper",
            "kind": "action",
            "actor": "FO",
            "action": "Fax a copy of the signed authorization to the appropriate electronic folder to document the protective filing date. Shred the paper form only after faxing that copy to the electronic folder.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is a manual-notification State case; do not substitute the automated PR-73 date rule.",
              "The selected action is within SI02003.020 B manual-notification processing and the authorization identifies a protective filing date; the applicable source prerequisites have been checked.",
              "The signed authorization is available for documentation."
            ],
            "source": "iarforeturn",
            "section": "B electronic-folder fax and subsequent paper-shredding bullets",
            "source_context_refs": [
              "SI02003.020:whole"
            ],
            "qualifications": [
              "SI02003.020 B separately checks correct completion, State and individual signatures, and FO receipt within 30 days from the individual signature date. This receipt anchor is distinct from the State-receipt anchor in SI02003.007 B.4. This card does not expand reimbursement processing to an ineffective form or negate the separate protective-filing rule.",
              "The sequence is fax first, shred afterward. No successful upload/legibility check, current system identity or authority to discard an unrecorded original is inferred.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "The actual authorization/receipt/application dates, applicable initial-claim branch, any appeal reversal or postprocessing trigger, eligibility for the earlier period and completed follow-through remain unverified. No automatic return to a usual claim path is established."
          ]
        }
      },
      "apply-ssi/iar-automated-alert-earlier-filing": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "iar-automated-alert-earlier-filing",
        "full_route": "apply-ssi/iar-automated-alert-earlier-filing",
        "entry_conditions": [
          "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
          "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
          "This is an automated-notification State PR-73 case; a GR-code input date that triggers an alert is not itself established as the protective filing date."
        ],
        "steps": [
          {
            "id": "iar-automated-alert-earlier-filing-source-1",
            "title": "Check the source scope before treating the alert as an earlier filing",
            "kind": "action",
            "actor": "FO",
            "action": "Apply the SI02003.007 A earlier-date AND initial-claim alternatives before using a protective filing date. The PR-73 alert is a review trigger, not an application, a payable award or a finding that the required case conditions exist.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is an automated-notification State PR-73 case; a GR-code input date that triggers an alert is not itself established as the protective filing date."
            ],
            "source": "iarprotectivefiling",
            "section": "A; B.1 automated notification; SI02003.020 C.2 context",
            "source_context_refs": [
              "SI02003.007:whole",
              "SI02003.020:whole"
            ],
            "qualifications": [
              "Under SI02003.020 C.2 the system sends PR-73 when State GR-code input predates the SSI application date; this trigger does not establish the final protected date. The A postdenial alternative still requires appeal reversal and the stated conditional reimbursement use.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-automated-alert-earlier-filing-source-2",
            "title": "Read the alert and keep the individual-signature presumption",
            "kind": "action",
            "actor": "FO",
            "action": "Use the State receipt date shown on PR-73 for the protective-filing review. SI02003.007 B.1 presumes State receipt on the date the individual signed. If the State representative signed earlier than the individual, use the individual-signature date as the protective filing date.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is an automated-notification State PR-73 case; a GR-code input date that triggers an alert is not itself established as the protective filing date."
            ],
            "source": "iarprotectivefiling",
            "section": "B.1 automated notification; SI02003.020 C.2 alert-date statement",
            "source_context_refs": [
              "SI02003.007:whole",
              "SI02003.020:whole"
            ],
            "qualifications": [
              "Preserve this stated signature-order condition. Do not take an earlier State-representative signature as the protected date, equate the State GR-input date with receipt, or invent a general latest-of-all-dates rule. No individual signatures or dates have been authenticated here.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-automated-alert-earlier-filing-source-3",
            "title": "Apply the common more-than-60-day limit",
            "kind": "action",
            "actor": "FO",
            "action": "If the SSI application was filed more than 60 days after State receipt of the signed authorization, use the application filing date as the effective filing date. Otherwise, apply the source’s automated date rule with the initial-claim scope; the alert does not remove the application condition.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is an automated-notification State PR-73 case; a GR-code input date that triggers an alert is not itself established as the protective filing date."
            ],
            "source": "iarprotectivefiling",
            "section": "B.1 common more-than-60-day instruction; B.4 qualification",
            "source_context_refs": [
              "SI02003.007:whole"
            ],
            "qualifications": [
              "The 60-day condition is an application/protective-filing rule, not an SSA processing SLA. SI02003.007 B.4 says late State notification beyond 30 calendar days after State receipt makes the authorization nonbinding with no effective life for reimbursement, but it still serves as protective filing if the application is filed within 60 days of State receipt. Do not silently turn reimbursement ineffectiveness into loss of that protective filing.",
              "Do not convert the 60-day filing condition into a resolution deadline for PR-73. The separate 30-calendar-day reimbursement-notification rule is not substituted for this application period.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          },
          {
            "id": "iar-automated-alert-earlier-filing-source-4",
            "title": "Redevelop only when the alert establishes an earlier protected date",
            "kind": "action",
            "actor": "FO",
            "action": "If PR-73 indicates a protective filing date earlier than the SSI application date, redevelop the claim back to that protective filing date. If the authorization is discovered after the initial claim was processed, SI02003.007 B.3 requires an effective authorization AND a signed authorization establishing an earlier protected date for that postprocessing redevelopment.",
            "conditions": [
              "An SSI initial-claim IAR protective-filing date is being reviewed; the signed authorization and application dates must be established.",
              "An earlier date may be used under SI02003.007 A only if it precedes the application filing date AND either (the State received the authorization before the SSI claim was denied) OR (SSA received it after denial, that denial was reversed through appeal, AND the authorization will be used to reimburse the State if a retroactive payment is due). These are required source conditions, not findings established by selecting this example.",
              "This is an automated-notification State PR-73 case; a GR-code input date that triggers an alert is not itself established as the protective filing date.",
              "PR-73 indicates an earlier protective filing date and the applicable source date rules permit that date."
            ],
            "source": "iarforeturn",
            "section": "C.2 final bullet; SI02003.007 B.3 postprocessing qualification",
            "source_context_refs": [
              "SI02003.020:whole",
              "SI02003.007:whole"
            ],
            "qualifications": [
              "The automated C.2 instruction supplies redevelopment, not the manual B fax/shred or DDS/OHO notification procedure. Those manual actions are not silently imported into this automated route. The B.3 trigger is conditional, not an additional sequential redevelopment to perform twice.",
              "Published date/development instructions only. This illustration does not establish a signed or effective authorization, an accepted earlier filing date, eligibility, a payable amount, completed system input or a successful case rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "The actual authorization/receipt/application dates, applicable initial-claim branch, any appeal reversal or postprocessing trigger, eligibility for the earlier period and completed follow-through remain unverified. No automatic return to a usual claim path is established."
          ]
        }
      }
    },
    "original_records": {
      "apply-ssi/iar-manual-earlier-filing-development": {
        "id": "iar-manual-earlier-filing-development",
        "title": "A manual State IAR form shows an earlier SSI filing date",
        "when": "The authorization meets SI 02003.007 A and establishes a date earlier than the application date.",
        "you": "Provide the signed authorization and SSI application information. Complete the application promptly; the authorization alone does not complete the SSI claim.",
        "ssa": "For manual notification, use the State receipt date, represented by the State representative’s signature date, if the application is filed within 60 days of State receipt. Beyond 60 days use the application filing date. If an effective authorization is discovered after processing, redevelop from the earlier protected date. The field office corrects the application date, reviews earlier eligibility, documents the signed form in the electronic folder and notifies DDS or OHO when a disability claim is pending there.",
        "route": "Field office filing-date/eligibility review → pending DDS or Office of Hearings Operations case notification",
        "next": "SSA reviews the earlier period; an earlier filing date does not by itself establish eligibility or a payment amount.",
        "source": "iarprotectivefiling",
        "section": "A; B.1 manual notification; B.3",
        "additional_sources": [
          {
            "source": "iarforeturn",
            "section": "B protective-filing procedures"
          }
        ],
        "timing": "Application within 60 days of State receipt is required for this manual-State rule; this is a filing condition, not an SSA processing estimate.",
        "review_status": "Manual-State selected workflow verified. Automated PR-73 date rules, withdrawal and denial-reversal cases remain separately scoped."
      },
      "apply-ssi/iar-automated-alert-earlier-filing": {
        "id": "iar-automated-alert-earlier-filing",
        "title": "An automated State IAR alert identifies an earlier filing date",
        "when": "A PR-73 alert reaches the servicing field office because State reimbursement-code input predates the SSI application date.",
        "you": "Keep the signed authorization and application information; respond to SSA requests needed to review the earlier period.",
        "ssa": "The field office checks the State receipt date shown on the alert. SI 02003.007 B.1 presumes receipt on the individual’s signature date and uses that individual-signature date when the State representative signed earlier. If the application was filed more than 60 days after State receipt, use the application date. When the alert identifies an earlier protective filing date, SI 02003.020 C.2 directs redevelopment back to that date.",
        "route": "Automated State interface → servicing field office PR-73 review → earlier-period claim redevelopment",
        "next": "SSA reviews the protected period; the alert does not by itself establish a payable award.",
        "source": "iarprotectivefiling",
        "section": "B.1 automated notification",
        "additional_sources": [
          {
            "source": "iarforeturn",
            "section": "C.1–2"
          }
        ],
        "timing": "The 60-day application condition is separate from the State’s 30-day reimbursement-notification rule. No alert-resolution duration is stated.",
        "review_status": "Selected automated date rule and field-office redevelopment checked against live subsections; no customer no-action guarantee adopted."
      }
    },
    "source_contexts": [
      {
        "id": "SI02003.007:whole",
        "start": 0,
        "end": 3571,
        "exact_text": "Effective Dates: 11/19/2010 - Present\nPrevious | Next\n\nTN 13 (11-10)\n\nSI 02003.007 IAR Authorization Used as Protective Filing\nA. \nPolicy when IAR authorization is a protective filing for an initial claim\n\nAn IAR authorization is a protective filing for an initial claim if it provides an earlier filing date than the application filing date and:\n\n•\n\nthe State receives it before the SSI claim is denied; or\n\n•\n\nSSA receives it after we have denied the SSI claim, but the denial is reversed through the appeal process and the authorization will be used to reimburse the State if a retroactive payment is due the claimant.\n\nNOTE: Effective with the implementation of eIAR, all IAR authorizations for all manual and automated IAR States contain protective filing and closeout language.\n\n \n\nB. \nPolicy for determining the protective filing date based on IAR authorization\n\nThe date the State received the signed IAR authorization and the date the individual filed the SSI application are the controlling dates for determining protective filing.\n\n1. \nSSI initial claims\n\nDetermine the filing date as follows:\n\n•\n\nManual Notification State: Use the date the State received the IAR authorization as the protective filing date if the individual files an application within 60 days of the date the State received the authorization. Use the date the State IAR representative signed the authorization as the date received by the State.\n\n•\n\nAutomated Notification State: Use the date the State received the IAR authorization (as shown on the PR-73 alert) as the protective filing date. In these situations, we presume that the State received the authorization on the date the individual signed it. However, if the date the State representative signed the authorization is earlier than the date the individual signed the authorization, use the date the individual signed the authorization as the protective filing date.\n\n•\n\nUse the date the individual files the SSI application as the effective filing date if the individual files the application more than 60 days after the date the State received the signed IAR authorization. For more information about automated notification States, see SI 02003.020C.\n\n2. \nAuthorization received after withdrawal of SSI application\n\nAn IAR authorization received by the State after the date of a withdrawal of an SSI application serves as a protective filing if the individual files an SSI application within 60 days of the date the State receives the signed authorization.\n\n3. \nAuthorization discovered after initial claim was processed\n\nIf we discover an effective IAR authorization after the initial claim was processed and the signed authorization establishes an earlier protective filing date, it is necessary to redevelop the claim based on the protective filing date.\n\n4. \nEffect of 30 calendar day rule on protective filing date\n\nIf the State fails to notify SSA within 30 calendar days of the receipt of an IAR authorization, the authorization is not binding and has no effective life. However, the authorization still serves as a protective filing date for SSI if the individual files an application within 60 days of the date the State receives the authorization.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0502003007\n\t\nSI 02003.007 - IAR Authorization Used as Protective Filing - 11/19/2010\nBatch run: 05/09/2011\nRev:11/19/2010\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "whole_sha256": "8f24b23f0b196e1c0851c0775ad07f0e42a744238225105e4a183665ce2f2bfd",
        "whole_text_url": "/service/sources/iar2-SI02003.007-main.txt"
      },
      {
        "id": "SI02003.020:whole",
        "start": 0,
        "end": 7573,
        "exact_text": "Effective Dates: 08/29/2024 - Present\nPrevious | Next\n\nTN 25 (08-24)\n\nSI 02003.020 Field Office Processing of IAR Authorizations\nA. \nDescription of processing IAR authorizations under eIAR\n\nOn November 20, 2010, SSA implemented the eIAR system. The eIAR system changes IAR accounting from a paper process to an electronic process and reduces field office (FO) involvement with processing IAR payments and notices.\n\nStates access the eIAR system using the Government to Government Services Online (GSO) website. SSA regional office IAR coordinators also access eIAR on the GSO website.\n\nThe eIAR process begins when the State notifies SSA that an individual has signed an IAR authorization. The State notifies SSA using either the manual notification or automated notification process. After SSA receives notification that the State agency has a valid authorization, the GR code is posted on the SSI record and eIAR control of the reimbursement process begins.\n\nSSA communicates with the State about an IAR case using the eIAR screens and email messages generated by the eIAR system. The eIAR system processes most reimbursements to completion without FO involvement when the FO inputs the SSI claim allowance. The FO must complete an underpayment review to build the UPV: V on the SSR before the eIAR system can process a reimbursement.\n\nNOTE: Field offices do not have access to the eIAR site. SSA regional office IAR coordinators have view and query access.\n\nB. \nProcedure for processing IAR authorizations in manual notification States\n\nIn a manual notification State, the State sends the original paper authorization form to the FO to notify SSA that it has a valid authorization for reimbursement. The FO:\n\n•\n\ndate stamps the authorization form;\n\n•\n\nreviews the form to ensure that it is completed correctly, signed by the State and the individual, and received by the FO within 30 days from the date that the individual signed the authorization;\n\n•\n\ninputs the GR code if no GR code of “R” or “F” is already posted on the SSR. The GR code must be posted to the individual’s SSR before SSA releases the retroactive benefits. For information about posting the GR code, see MSOM MSSICS 023.006 and SM 01005.623. Do not change or delete a GR code present on a record unless it was input erroneously (e.g., State and county code input as 12435, correct code is 12345).\n\nIMPORTANT: Do not delete a Grant Reimbursement Code (GRC). Contact your eIAR Regional Coordinator, if expedited processing is required or there is justification for the GRC deletion.\n\n•\n\ninputs the corrected application date if the authorization form identifies a protective filing and reviews eligibility back to the protective filing date;\n\n•\n\nnotifies DDS or the Office of Hearings Operations (OHO) of the protective filing date if a disability claim is pending at DDS or OHO;\n\n•\n\nfaxes a copy of the signed authorization form into the appropriate electronic folder to document the protective filing date; and\n\n•\n\nshreds the paper form after faxing a copy to the electronic folder.\n\nThe eIAR system will:\n\n•\n\ncontrol the case;\n\n•\n\npost information on the eIAR screens;\n\n•\n\nautomatically send appropriate notifications and follow-ups to the State; and\n\n•\n\nprocess the IAR reimbursement to the State when the FO completes the prepayment review and inputs an allowance for the claim to build the UPV:V to the SSR.\n\nNOTE: The correct application date must be on the SSR at the time the UPV: V is built so the eIAR system uses the correct IAR period to process the case.\n\nREMINDER: Process workloads in the proper sequence, e.g. review terminated records for underpayments. The GR code must be brought forward from a terminated record to a start-dated record if there will an underpayment on the start-dated record.\n\nC. \nProcess for IAR authorizations in automated notification States\n1. \nElectronic interface notifies SSA of the authorization\n\nIn an automated notification State:\n\n•\n\nthe State sends the IAR authorization information to SSA through an electronic interface with the Supplemental Security Record (SSR);\n\n•\n\nthe electronic interface sends information that the State has a valid authorization, the date the authorization was signed, and the date the State received the authorization; and\n\n•\n\nThe system automatically posts a GR code to the SSR when the State IAR file interfaces with the SSR and matches an established SSI claim.\n\n2. \nPR-73 alert sent to the FO\n\nFor an automated notification State:\n\n•\n\nthe system automatically sends a PR-73 alert to the servicing FO when the date of the State GR code input precedes the SSI application date on the SSR;\n\n•\n\nthe PR-73 alert shows the date the State received a signed authorization; and\n\n•\n\nif the PR-73 alert indicates a protective filing date that is earlier than the application date, redevelop the claim back to the protective filing date.\n\nFor more information about the PR-73 alert, see SM 01015.090.\n\nD. \nProcedure for returning IAR authorizations to States\n1. \n30-calendar day rule\n\nUnder eIAR, the 30-calendar day rule still applies. If the State submits an authorization to SSA more than 30 days after the individual signed the authorization, the FO must return the authorization to the State. Use the following language when returning the form to the State.\n\n“Authorization is not effective because it was not received by SSA within 30 calendar days of the day the individual or their representative payee or legal guardian signed the authorization.”\n\nIf the State does not meet the 30-day deadline, the authorization is not effective and SSA will pay the SSI recipient the retroactive payments according to normal SSI payment rules. In this situation, the State can ask the recipient for reimbursement, but SSA will not assist the State with its request to the recipient. For more information about the 30-calendar day rule, see SI 02003.006, Effective Life if an IAR Authorization.\n\n2. \nAuthorization is not properly signed\n\nWhen an individual or State does not properly sign authorization:\n\n•\n\nReturn the paper authorization to the State if the SSI applicant or State IAR representative did not sign and date the authorization. This process applies to both initial claims and PE situations. Notify the State to obtain the missing signatures or dates; and\n\n•\n\nReturn the paper authorization to the State if it signed by a State IAR representative who is also representative payee or legal guardian for the SSI applicant. The State signing in this manner would result in a potential conflict of interest as described in SI 02003.005B.4. Notify the State to obtain an appropriate signature and explain why the original signature was not acceptable.\n\nNOTE: When returning an authorization to the State, advise the State that the 30-day rule for the effective life of the authorization applies to authorizations returned for signatures.\n\n3. \nMultiple Authorizations\n\nIf there is a GR code that is already pending on the SSR any subsequent authorizations are returned to the State unless the authorization is for a new IC or PE event. Return it to the State office with a notation that the claimant has already authorized payment to another State IAR agency.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0502003020\n\t\nSI 02003.020 - Field Office Processing of IAR Authorizations - 08/29/2024\nBatch run: 12/18/2024\nRev:08/29/2024\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
        "whole_sha256": "b431cab7d16a4bd22943d61103c27ea78b8b73789d32ecd43236379906476239",
        "whole_text_url": "/service/sources/iar2-SI02003.020-main.txt"
      }
    ],
    "source_freshness": {
      "SI02003.007": {
        "captured_utc": "2026-11-01T10:37:24.617Z",
        "method": "@Browser root IAB tab66 rendered #content including preserved footer; fullbody and DOMsnapshot retained separately",
        "displayed_effective": "11/19/2010 - Present",
        "TN": "13 (11-10)",
        "unchanged_original_source_object": true
      },
      "SI02003.020": {
        "captured_utc": "2026-11-01T00:56:54.165Z",
        "method": "Actual @Browser rendered whole main/body/HTML/DOM/links/tables; not raw HTTP",
        "reuse_scope": "Whole retained7573-character source newly read for B/manual and C.2 automated; old selected B coordinator-only review is not substituted for new review.",
        "unchanged_original_source_object": true
      }
    },
    "source_peer_sha256": "0094d5d563c35ddfb3f2dc238f7970dd6ac13cc68c06d1e31d436831069aa958",
    "source_patch_sha256": "315300388e765cac25d1dce35b0eae1737684e0f4b407165d641b9ed7fbd2fb3",
    "source_package_sha256": "285ba7aef783c5a592fb3864bb7316dbb3b2ac6abc285490fe39713ec3f3f25e",
    "review_scope": "Only two initial-claim IAR protective-filing sequences: SI02003.007 A/B conditions plus SI02003.020 B manual and C.2 automated notification. Whole captured contexts supplied; other linked targets and separate withdrawal/authorization-life operations remain held.",
    "holds": [
      "Original legacy records/source metadata/review dates/statuses retained verbatim; new wording derives from captured primaries, not replacement-character legacy text.",
      "Reimbursement validity/effective life and SSI protective filing are distinct. SI02003.007B.4 late30calendar-day State notification does not by itself erase within60-day protective filing; .020B individual-signature receipt check has a different anchor.",
      "Only the selected initial-claim routes are sequenced. Separate post-withdrawal B.2, independent appeal/reversal case determination, authorization-life/signature frameworks and no-new-GR-deletion authority remain outside new operational findings.",
      "No manual electronic-folder/DDS/OHO actions transferred to automated C.2 without primary support. No duplicate postprocessing redevelopment action is prescribed.",
      "No system/native identity, current access, actual update/alert/receipt/payment/eligibility, measured processing time or successful rejoin adopted."
    ],
    "source_native_acceptance": false
  },
  "repropagation4_selected": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "FOUR_OPTIONAL_REPROPAGATION_SOURCE_PATHWAYS_SOURCE_PLACEMENT_REVIEWED_NOT_CASE_FINDING",
    "selected_flow_count": 4,
    "card_count": 7,
    "checked_on": "2026-11-01",
    "flows": {
      "disability-intake-evidence/disability-evidence-edcs-repropagate-eligible-mainframe-data": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-edcs-repropagate-eligible-mainframe-data",
        "full_route": "disability-intake-evidence/disability-evidence-edcs-repropagate-eligible-mainframe-data",
        "entry_conditions": [
          "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "steps": [
          {
            "id": "disability-evidence-edcs-repropagate-eligible-mainframe-data-reprop-eligible-1",
            "title": "Check case restrictions",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. Repropagation is not possible in any of these states.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
              "Before manual repropagation"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 B",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          },
          {
            "id": "disability-evidence-edcs-repropagate-eligible-mainframe-data-reprop-eligible-2",
            "title": "Use the source-described trigger",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Repropagation occurs automatically when case jurisdiction is transferred. Without transferring, staff can select REPROP from the Case Disability Selection page. The automatic transfer trigger does not authorize manual repropagation after the case is in another component’s jurisdiction.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
              "Eligible case; transferring jurisdiction or choosing REPROP without transfer"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 A",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          },
          {
            "id": "disability-evidence-edcs-repropagate-eligible-mainframe-data-reprop-eligible-3",
            "title": "Limit the expected overlay",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The function collects and propagates that information into EDCS and overlays non-editable fields, such as claimant name/date of birth, claimant address/telephone, language preference, number holder SSN, claim types, alleged onset date, number holder date of death and attorney representation. These are examples, not an exhaustive all-field guarantee. No visible change is apparent when mainframe data has not changed since original propagation. Mainframe changes to alleged conditions or DLI do not replace those EDCS entries.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
              "If new or modified mainframe data is found"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 C",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Source does not establish operating entry, successful completion or an automatic return to the usual path.",
            "The transferred-case DI81010.095 cross-reference does not establish automatic entry into UAT or broaden existing UAT predicates."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-edcs-repropagation-blocked-and-transferred-handoff": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-edcs-repropagation-blocked-and-transferred-handoff",
        "full_route": "disability-intake-evidence/disability-evidence-edcs-repropagation-blocked-and-transferred-handoff",
        "entry_conditions": [
          "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "steps": [
          {
            "id": "disability-evidence-edcs-repropagation-blocked-and-transferred-handoff-reprop-blocked-1",
            "title": "Do not use repropagation in the listed states",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. The source supplies no unlock, reopening, jurisdiction override or retry procedure.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
              "Any B restriction"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 B",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          },
          {
            "id": "disability-evidence-edcs-repropagation-blocked-and-transferred-handoff-reprop-blocked-2",
            "title": "Use the transferred-case cross-reference",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "The B note directs use of Update-After-Transfer to update information when the case is transferred and links DI81010.095. Retain that policy handoff; .045 does not establish UAT eligibility for every data field or every added claim. Existing reviewed UAT4 guards remain authoritative and are not replaced.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
              "Case is transferred"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 B",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Source does not establish operating entry, successful completion or an automatic return to the usual path.",
            "The transferred-case DI81010.095 cross-reference does not establish automatic entry into UAT or broaden existing UAT predicates."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-edcs-child-additional-repropagated-fields": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-edcs-child-additional-repropagated-fields",
        "full_route": "disability-intake-evidence/disability-evidence-edcs-child-additional-repropagated-fields",
        "entry_conditions": [
          "Child claim undergoing otherwise eligible repropagation; C.1 new/modified-mainframe-data condition and B restrictions retained.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action.",
          "A separately labelled related child-claim scenario covers only additional repropagated fields described in DI 81010.045 C.2; it does not describe complete child disability intake."
        ],
        "steps": [
          {
            "id": "disability-evidence-edcs-child-additional-repropagated-fields-reprop-child-1",
            "title": "Include the child-specific field examples",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "Additional fields that can repropagate are applicant relationship to child, applicant information, applicant name (first, middle, last, suffix or agency name), and applicant address/phone. This does not establish child-case creation, adult-claim applicability, or a guaranteed change if there is no new/modified mainframe data.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Child claim undergoing otherwise eligible repropagation; C.1 new/modified-mainframe-data condition and B restrictions retained.",
              "Child claim, otherwise eligible repropagation"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 C",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Source does not establish operating entry, successful completion or an automatic return to the usual path.",
            "The transferred-case DI81010.095 cross-reference does not establish automatic entry into UAT or broaden existing UAT predicates."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-edcs-dli-condition-direct-edit": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-edcs-dli-condition-direct-edit",
        "full_route": "disability-intake-evidence/disability-evidence-edcs-dli-condition-direct-edit",
        "entry_conditions": [
          "Date Last Insured or Alleged Disabling Condition needs a change; not a blanket instruction to edit every propagated field or bypass a locked/transferred case.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "steps": [
          {
            "id": "disability-evidence-edcs-dli-condition-direct-edit-reprop-direct-edit-1",
            "title": "Use the field-specific EDCS exception",
            "kind": "ssa",
            "actor": "SSA staff",
            "action": "These two fields cannot repropagate. If changes are necessary, edit them in EDCS. Mainframe changes do not replace their EDCS entries. The paragraph supplies no authorization to bypass case state restrictions, no transaction details, and no completed-correction proof.",
            "next": "Source does not establish successful completion or automatic journey rejoin.",
            "conditions": [
              "Date Last Insured or Alleged Disabling Condition needs a change; not a blanket instruction to edit every propagated field or bypass a locked/transferred case.",
              "A necessary change concerns Date Last Insured or Alleged Disabling Condition"
            ],
            "source": "dis72_DI81010_045",
            "section": "DI81010.045 D",
            "source_context_refs": [
              "DI81010.045:A",
              "DI81010.045:B",
              "DI81010.045:C",
              "DI81010.045:D"
            ],
            "qualifications": [
              "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
              "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
              "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
              "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
            ]
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Source does not establish operating entry, successful completion or an automatic return to the usual path.",
            "The transferred-case DI81010.095 cross-reference does not establish automatic entry into UAT or broaden existing UAT predicates."
          ]
        }
      }
    },
    "original_records": {
      "disability-intake-evidence/disability-evidence-edcs-repropagate-eligible-mainframe-data": {
        "id": "disability-evidence-edcs-repropagate-eligible-mainframe-data",
        "title": "Repropagate eligible mainframe data",
        "when": "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
        "you": "No additional customer duty is established by this published SSA staff instruction.",
        "ssa": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. Repropagation is not possible in any of these states. Repropagation occurs automatically when case jurisdiction is transferred. Without transferring, staff can select REPROP from the Case Disability Selection page. The automatic transfer trigger does not authorize manual repropagation after the case is in another component’s jurisdiction. The function collects and propagates that information into EDCS and overlays non-editable fields, such as claimant name/date of birth, claimant address/telephone, language preference, number holder SSN, claim types, alleged onset date, number holder date of death and attorney representation. These are examples, not an exhaustive all-field guarantee. No visible change is apparent when mainframe data has not changed since original propagation. Mainframe changes to alleged conditions or DLI do not replace those EDCS entries.",
        "route": "Optional related published staff-handling scenario; no actual transaction or automatic transition.",
        "next": "Review all conditions and full A-D source context. Operating entry and rejoin remain unresolved.",
        "source": "dis72_DI81010_045",
        "section": "DI81010.045 A, DI81010.045 B, DI81010.045 C",
        "owner": "SSA staff",
        "systems": [
          "EDCS"
        ],
        "timing": "No operating duration or completed-action promise is established.",
        "scope": "Selected optional EDCS data-handling source example; not a complete disability intake procedure.",
        "conditions": [
          "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "condition_logic": "all",
        "qualifications": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
          "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
        ],
        "parent_stage_id": "evidence-view",
        "review_status": "Source and thematic placement reviewed; isolated runtime candidate requires independent schema/export/UI review."
      },
      "disability-intake-evidence/disability-evidence-edcs-repropagation-blocked-and-transferred-handoff": {
        "id": "disability-evidence-edcs-repropagation-blocked-and-transferred-handoff",
        "title": "Keep blocked repropagation separate from UAT",
        "when": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
        "you": "No additional customer duty is established by this published SSA staff instruction.",
        "ssa": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. The source supplies no unlock, reopening, jurisdiction override or retry procedure. The B note directs use of Update-After-Transfer to update information when the case is transferred and links DI81010.095. Retain that policy handoff; .045 does not establish UAT eligibility for every data field or every added claim. Existing reviewed UAT4 guards remain authoritative and are not replaced.",
        "route": "Optional related published staff-handling scenario; no actual transaction or automatic transition.",
        "next": "Review all conditions and full A-D source context. Operating entry and rejoin remain unresolved.",
        "source": "dis72_DI81010_045",
        "section": "DI81010.045 B",
        "owner": "SSA staff",
        "systems": [
          "EDCS"
        ],
        "timing": "No operating duration or completed-action promise is established.",
        "scope": "Selected optional EDCS data-handling source example; not a complete disability intake procedure.",
        "conditions": [
          "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "condition_logic": "all",
        "qualifications": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
          "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
        ],
        "parent_stage_id": "evidence-view",
        "review_status": "Source and thematic placement reviewed; isolated runtime candidate requires independent schema/export/UI review."
      },
      "disability-intake-evidence/disability-evidence-edcs-child-additional-repropagated-fields": {
        "id": "disability-evidence-edcs-child-additional-repropagated-fields",
        "title": "Keep additional child-claim fields scoped to child claims",
        "when": "Child claim undergoing otherwise eligible repropagation; C.1 new/modified-mainframe-data condition and B restrictions retained.",
        "you": "No additional customer duty is established by this published SSA staff instruction.",
        "ssa": "Additional fields that can repropagate are applicant relationship to child, applicant information, applicant name (first, middle, last, suffix or agency name), and applicant address/phone. This does not establish child-case creation, adult-claim applicability, or a guaranteed change if there is no new/modified mainframe data.",
        "route": "Optional related published staff-handling scenario; no actual transaction or automatic transition.",
        "next": "Review all conditions and full A-D source context. Operating entry and rejoin remain unresolved.",
        "source": "dis72_DI81010_045",
        "section": "DI81010.045 C",
        "owner": "SSA staff",
        "systems": [
          "EDCS"
        ],
        "timing": "No operating duration or completed-action promise is established.",
        "scope": "A separately labelled related child-claim scenario covers only additional repropagated fields described in DI 81010.045 C.2; it does not describe complete child disability intake.",
        "conditions": [
          "Child claim undergoing otherwise eligible repropagation; C.1 new/modified-mainframe-data condition and B restrictions retained.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action.",
          "A separately labelled related child-claim scenario covers only additional repropagated fields described in DI 81010.045 C.2; it does not describe complete child disability intake."
        ],
        "condition_logic": "all",
        "qualifications": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
          "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
        ],
        "parent_stage_id": "evidence-view",
        "review_status": "Source and thematic placement reviewed; isolated runtime candidate requires independent schema/export/UI review."
      },
      "disability-intake-evidence/disability-evidence-edcs-dli-condition-direct-edit": {
        "id": "disability-evidence-edcs-dli-condition-direct-edit",
        "title": "Edit DLI or alleged disabling condition in EDCS when necessary",
        "when": "Date Last Insured or Alleged Disabling Condition needs a change; not a blanket instruction to edit every propagated field or bypass a locked/transferred case.",
        "you": "No additional customer duty is established by this published SSA staff instruction.",
        "ssa": "These two fields cannot repropagate. If changes are necessary, edit them in EDCS. Mainframe changes do not replace their EDCS entries. The paragraph supplies no authorization to bypass case state restrictions, no transaction details, and no completed-correction proof.",
        "route": "Optional related published staff-handling scenario; no actual transaction or automatic transition.",
        "next": "Review all conditions and full A-D source context. Operating entry and rejoin remain unresolved.",
        "source": "dis72_DI81010_045",
        "section": "DI81010.045 D",
        "owner": "SSA staff",
        "systems": [
          "EDCS"
        ],
        "timing": "No operating duration or completed-action promise is established.",
        "scope": "Selected optional EDCS data-handling source example; not a complete disability intake procedure.",
        "conditions": [
          "Date Last Insured or Alleged Disabling Condition needs a change; not a blanket instruction to edit every propagated field or bypass a locked/transferred case.",
          "Optional source illustration only; selection does not establish case facts, jurisdiction, permissions or a completed action."
        ],
        "condition_logic": "all",
        "qualifications": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin.",
          "Navigation order is not an operating sequence. This optional scenario has no automatic insertion or rejoin."
        ],
        "parent_stage_id": "evidence-view",
        "review_status": "Source and thematic placement reviewed; isolated runtime candidate requires independent schema/export/UI review."
      }
    },
    "reviewed_source_capsules": {
      "disability-intake-evidence/disability-evidence-edcs-repropagate-eligible-mainframe-data": {
        "id": "edcs-repropagate-eligible-mainframe-data",
        "title": "Repropagate eligible mainframe data",
        "entry": "Selected EDCS case; none of the B restrictions applies. No new action is promised merely because a user reports a discrepancy.",
        "cards": [
          {
            "id": "reprop-eligible-1",
            "title": "Check case restrictions",
            "actor": "SSA staff",
            "condition": "Before manual repropagation",
            "action": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. Repropagation is not possible in any of these states.",
            "evidence": {
              "start": 850,
              "end": 893,
              "exact_text": "Repropagation is not possible if a case is:",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          },
          {
            "id": "reprop-eligible-2",
            "title": "Use the source-described trigger",
            "actor": "SSA staff",
            "condition": "Eligible case; transferring jurisdiction or choosing REPROP without transfer",
            "action": "Repropagation occurs automatically when case jurisdiction is transferred. Without transferring, staff can select REPROP from the Case Disability Selection page. The automatic transfer trigger does not authorize manual repropagation after the case is in another component’s jurisdiction.",
            "evidence": {
              "start": 382,
              "end": 552,
              "exact_text": "Occurs automatically when the jurisdiction of the case is transferred, or you can choose to “REPROP” from the Case Disability Selection page in EDCS without transferring.",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          },
          {
            "id": "reprop-eligible-3",
            "title": "Limit the expected overlay",
            "actor": "SSA staff",
            "condition": "If new or modified mainframe data is found",
            "action": "The function collects and propagates that information into EDCS and overlays non-editable fields, such as claimant name/date of birth, claimant address/telephone, language preference, number holder SSN, claim types, alleged onset date, number holder date of death and attorney representation. These are examples, not an exhaustive all-field guarantee. No visible change is apparent when mainframe data has not changed since original propagation. Mainframe changes to alleged conditions or DLI do not replace those EDCS entries.",
            "evidence": {
              "start": 1300,
              "end": 1479,
              "exact_text": "If new or modified mainframe data is found, the repropagate function collects the information, propagates the data into the EDCS system, and overlays non-editable fields, such as:",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          }
        ],
        "additional_evidence": [
          {
            "start": 557,
            "end": 663,
            "exact_text": "Is not apparent to the user if no changes have been made to the mainframe since original data propagation.",
            "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
          },
          {
            "start": 668,
            "end": 814,
            "exact_text": "Updates some fields in EDCS, but does NOT replace EDCS entries if allegations of conditions and/or date last insured are changed in the mainframe.",
            "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
          }
        ],
        "handoff": "No success, correction transaction, retry, timing, acknowledgment or rejoin specified.",
        "review_status": "UNREVIEWED_SOURCE_PROPOSAL_NO_ADOPTION",
        "native_system_ids": [],
        "policy_holds": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin."
        ]
      },
      "disability-intake-evidence/disability-evidence-edcs-repropagation-blocked-and-transferred-handoff": {
        "id": "edcs-repropagation-blocked-and-transferred-handoff",
        "title": "Keep blocked repropagation separate from UAT",
        "entry": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction.",
        "cards": [
          {
            "id": "reprop-blocked-1",
            "title": "Do not use repropagation in the listed states",
            "actor": "SSA staff",
            "condition": "Any B restriction",
            "action": "Case is locked, transferred to another component’s jurisdiction, closed with no pending claims, or not in the acting staff member’s jurisdiction. The source supplies no unlock, reopening, jurisdiction override or retry procedure.",
            "evidence": {
              "start": 850,
              "end": 893,
              "exact_text": "Repropagation is not possible if a case is:",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          },
          {
            "id": "reprop-blocked-2",
            "title": "Use the transferred-case cross-reference",
            "actor": "SSA staff",
            "condition": "Case is transferred",
            "action": "The B note directs use of Update-After-Transfer to update information when the case is transferred and links DI81010.095. Retain that policy handoff; .045 does not establish UAT eligibility for every data field or every added claim. Existing reviewed UAT4 guards remain authoritative and are not replaced.",
            "evidence": {
              "start": 1050,
              "end": 1254,
              "exact_text": "NOTE: Use the “Update-After-Transfer” utility to update any information if the case is transferred. See Using the Update-After-Transfer Utility - DI 81010.095, for more information on using this function.",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          }
        ],
        "handoff": {
          "policy": "DI81010.095",
          "existing_reviewed_family": "UAT4 only within its previously reviewed limited-update/add-claim/document-addition scope",
          "operational_entry": "Unresolved; no automatic route insertion/rejoin or UAT execution asserted"
        },
        "review_status": "UNREVIEWED_SOURCE_PROPOSAL_NO_ADOPTION",
        "native_system_ids": [],
        "policy_holds": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin."
        ]
      },
      "disability-intake-evidence/disability-evidence-edcs-child-additional-repropagated-fields": {
        "id": "edcs-child-additional-repropagated-fields",
        "title": "Keep additional child-claim fields scoped to child claims",
        "entry": "Child claim undergoing otherwise eligible repropagation; C.1 new/modified-mainframe-data condition and B restrictions retained.",
        "cards": [
          {
            "id": "reprop-child-1",
            "title": "Include the child-specific field examples",
            "actor": "SSA staff",
            "condition": "Child claim, otherwise eligible repropagation",
            "action": "Additional fields that can repropagate are applicant relationship to child, applicant information, applicant name (first, middle, last, suffix or agency name), and applicant address/phone. This does not establish child-case creation, adult-claim applicability, or a guaranteed change if there is no new/modified mainframe data.",
            "evidence": {
              "start": 1781,
              "end": 1841,
              "exact_text": "Additional fields that can repropagate for child claims are:",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          }
        ],
        "handoff": "Optional qualified child subjourney candidate only; existing exact route binding unresolved.",
        "review_status": "UNREVIEWED_SOURCE_PROPOSAL_NO_ADOPTION",
        "native_system_ids": [],
        "policy_holds": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin."
        ]
      },
      "disability-intake-evidence/disability-evidence-edcs-dli-condition-direct-edit": {
        "id": "edcs-dli-condition-direct-edit",
        "title": "Edit DLI or alleged disabling condition in EDCS when necessary",
        "entry": "Date Last Insured or Alleged Disabling Condition needs a change; not a blanket instruction to edit every propagated field or bypass a locked/transferred case.",
        "cards": [
          {
            "id": "reprop-direct-edit-1",
            "title": "Use the field-specific EDCS exception",
            "actor": "SSA staff",
            "condition": "A necessary change concerns Date Last Insured or Alleged Disabling Condition",
            "action": "These two fields cannot repropagate. If changes are necessary, edit them in EDCS. Mainframe changes do not replace their EDCS entries. The paragraph supplies no authorization to bypass case state restrictions, no transaction details, and no completed-correction proof.",
            "evidence": {
              "start": 2150,
              "end": 2216,
              "exact_text": "NOTE: If changes to these fields are necessary, edit them in EDCS.",
              "coordinate_system": "Unicode codepoints in captured content_text; not raw HTML/UTF8 byte offsets"
            },
            "source": "DI81010.045",
            "source_context_sections": [
              "A",
              "B",
              "C",
              "D"
            ],
            "next": "Source does not establish successful completion or automatic journey rejoin."
          }
        ],
        "handoff": "Unknown operating entry and rejoin; D does not explain locked/transferred access or conflict resolution.",
        "review_status": "UNREVIEWED_SOURCE_PROPOSAL_NO_ADOPTION",
        "native_system_ids": [],
        "policy_holds": [
          "Source revision01/24/2008 and batch11/07/2023 retained as displayed; no assertion of current EDCS runtime validation.",
          "Existing EDCS/mainframe labels only; no new native entities, links, APIs or system operation evidence.",
          "Original .035/UAT4 records/source statuses remain untouched; no automatic insertion or rejoin."
        ]
      }
    },
    "source_contexts": [
      {
        "section": "A",
        "start": 149,
        "end": 816,
        "exact_text": "A. \nOverview\n\nRepropagation of data in EDCS:\n\n•\n\nIs a process similar to that of initial data propagation from SSA's mainframe systems.\n\n•\n\nCauses the system to check for data on the mainframe systems for the selected EDCS case.\n\n•\n\nOccurs automatically when the jurisdiction of the case is transferred, or you can choose to “REPROP” from the Case Disability Selection page in EDCS without transferring.\n\n•\n\nIs not apparent to the user if no changes have been made to the mainframe since original data propagation.\n\n•\n\nUpdates some fields in EDCS, but does NOT replace EDCS entries if allegations of conditions and/or date last insured are changed in the mainframe.\n\n",
        "id": "DI81010.045:A",
        "source": "dis72_DI81010_045",
        "whole_text_sha256": "11353eb538ed4969ffae7b5c2f0187ff1c5df43c7aada8bb5f67cf625945d636",
        "span_sha256": "f2a60ea309b98e253308327c19fd695735a7cb0ded2e590cbd695a27bdc8a873",
        "whole_text_url": "/service/sources/repropagation4-DI81010.045-main.txt",
        "coordinates": "Unicode codepoints in captured complete content_text"
      },
      {
        "section": "B",
        "start": 816,
        "end": 1256,
        "exact_text": "B. \nWhen Data Cannot Repropagate\n\nRepropagation is not possible if a case is:\n\n•\n\nLocked;\n\n•\n\nTransferred to the jurisdiction of another component;\n\n•\n\nClosed (no pending claims left on the case); or\n\n•\n\nNot in your jurisdiction.\n\n \n\nNOTE: Use the “Update-After-Transfer” utility to update any information if the case is transferred. See Using the Update-After-Transfer Utility - DI 81010.095, for more information on using this function.\n\n",
        "id": "DI81010.045:B",
        "source": "dis72_DI81010_045",
        "whole_text_sha256": "11353eb538ed4969ffae7b5c2f0187ff1c5df43c7aada8bb5f67cf625945d636",
        "span_sha256": "a8f71182dcd5e5fe6490379eabb682fddaa31715b7bd1b887517be36cc284b2c",
        "whole_text_url": "/service/sources/repropagation4-DI81010.045-main.txt",
        "coordinates": "Unicode codepoints in captured complete content_text"
      },
      {
        "section": "C",
        "start": 1256,
        "end": 2017,
        "exact_text": "C. \nFields that Repropagate\n1. \nAll Claims\n\nIf new or modified mainframe data is found, the repropagate function collects the information, propagates the data into the EDCS system, and overlays non-editable fields, such as:\n\n•\n\nClaimant’s Name and date of birth;\n\n•\n\nClaimant’s Address and telephone number;\n\n•\n\nLanguage Preference;\n\n•\n\nNumber Holder’s SSN;\n\n•\n\nClaim Type(s);\n\n•\n\nAlleged Onset Date;\n\n•\n\nNumber Holder Date of Death; and\n\n•\n\nAttorney Representation.\n\n2. \nAdditional Fields that Repropagate for Child Claims\n\nAdditional fields that can repropagate for child claims are:\n\n•\n\nApplicant Relationship to Child;\n\n•\n\nApplicant Information;\n\n•\n\nApplicant Name (First, Middle, Last, Suffix, or Agency Name); and\n\n•\n\nApplicant Address and phone number.\n\n",
        "id": "DI81010.045:C",
        "source": "dis72_DI81010_045",
        "whole_text_sha256": "11353eb538ed4969ffae7b5c2f0187ff1c5df43c7aada8bb5f67cf625945d636",
        "span_sha256": "0b4f4fb310b912998a9f52ef2b077459b505d2c55f1d3a5da9501ce656e30a41",
        "whole_text_url": "/service/sources/repropagation4-DI81010.045-main.txt",
        "coordinates": "Unicode codepoints in captured complete content_text"
      },
      {
        "section": "D",
        "start": 2017,
        "end": 2218,
        "exact_text": "D. \nFields That Do Not Repropagate\n\nFields that cannot repropagate are:\n\n•\n\nDate Last Insured; and\n\n•\n\nAlleged Disabling Condition.\n\nNOTE: If changes to these fields are necessary, edit them in EDCS.\n\n",
        "id": "DI81010.045:D",
        "source": "dis72_DI81010_045",
        "whole_text_sha256": "11353eb538ed4969ffae7b5c2f0187ff1c5df43c7aada8bb5f67cf625945d636",
        "span_sha256": "8cb8d7d208f6166bb90d4e6231f5844fbcc09508019ab4f04cf3cc205cd46b76",
        "whole_text_url": "/service/sources/repropagation4-DI81010.045-main.txt",
        "coordinates": "Unicode codepoints in captured complete content_text"
      }
    ],
    "source": {
      "code": "DI81010.045",
      "title": "Data Repropagation in Electronic Disability Collect System (EDCS)",
      "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010045",
      "kind": "POMS",
      "revision": "2008-01-24",
      "transmittal": "Basic (01-08)",
      "checked_on": "2026-11-01",
      "captured_utc": "2026-11-01T12:45:12.746Z",
      "review_status": "Complete captured A-D reviewed for four optional source-specific examples; no runtime/case/native acceptance",
      "verification_scope": "Source/placement peers only; four scenarios7cards3/2/1/1, unknown entry/rejoin. Source revision and browser capture date distinct.",
      "preserved_text_sha256": "11353eb538ed4969ffae7b5c2f0187ff1c5df43c7aada8bb5f67cf625945d636",
      "preserved_browser_capture_sha256": "fda0c82102e4e07bc71611624ff7702cf1d2ed9ea39e78a3112b781611193517",
      "source_provenance": {
        "capture_kind": "Browser visible complete content_text/DOM, not rawHTTP",
        "content_text_url": "/service/sources/repropagation4-DI81010.045-main.txt",
        "source_revision": "2008-01-24",
        "batch_run": "2023-11-07",
        "source_peer_sha256": "138d93881bc7522b242778f1c71fd60c08ae857bac512122d35c107e16f40332",
        "native_operation_verified": false
      }
    },
    "source_peer_sha256": "138d93881bc7522b242778f1c71fd60c08ae857bac512122d35c107e16f40332",
    "placement_peer_sha256": "ade61a95f0c458bed114d91711fadfd36c6b017c9d4f958538999d5a4e11ad37",
    "root_scope_disposition_sha256": "818418eb6dad4a0a4f14739f6e957b0cd44bcf62bec52b441289fc1982a4f2f3",
    "source_proposal_sha256": "c761e0f8704f7c16a8c2baed4ef1acde22fdfe2b7c203a1afd668e3f2c4a2fa2",
    "source_native_acceptance": false,
    "limits": [
      "Exact existing record/entry placement requires thematic binding peer after source peer",
      "No automatic rejoin/success/observed transfer latency",
      "All .095 detailed UAT qualifiers remain in original reviewed UAT4 package; .045 handoff alone cannot broaden them",
      "Original .035 and .095 source statuses/history and all251 priorflows preserved.",
      "Child-only additional fields are a narrowly labelled related scenario; no complete child intake coverage.",
      "A automatictransfer trigger and B alreadytransferred jurisdiction restriction remain distinct. D is not a bypass for blocked states."
    ],
    "original_capsule_status_note": "Each reviewed_source_capsules review_status is preserved from original c761 source-proposal generation. Source and placement acceptance are recorded separately by their exact peer hashes above; runtime integration remains independently gated."
  },
  "evidence_disposition3_selected": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "SOURCE_REVIEWED_DISPOSITION3_INTEGRATION_PENDING_RUNTIME_PEER",
    "selected_flow_count": 3,
    "card_count": 9,
    "flows": {
      "disability-intake-evidence/disability-evidence-fo-afterrelease-duplicate": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-fo-afterrelease-duplicate",
        "full_route": "disability-intake-evidence/disability-evidence-fo-afterrelease-duplicate",
        "entry_conditions": [
          "DDS released jurisdiction to FO",
          "Paper medical evidence exactly duplicates evidence already in CEF before the determination",
          "Source-only candidate; entry facts are not determined by route selection."
        ],
        "steps": [
          {
            "id": "disability-evidence-fo-afterrelease-duplicate-compare",
            "title": "Compare after DDS releases jurisdiction",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Review eView and compare the received paper medical evidence with the CEF record. Similarity alone is insufficient: the following disposition requires an exact duplicate already present before the DDS determination.",
            "conditions": [
              "DDS released jurisdiction to FO; received material is paper medical evidence."
            ],
            "source": "dis72_DI81010_125",
            "section": "C",
            "source_context_refs": [
              "DI81010.125:C"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          },
          {
            "id": "disability-evidence-fo-afterrelease-duplicate-dispose-record",
            "title": "Apply only the qualified duplicate disposition",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "If the paper evidence is an exact duplicate of evidence in the CEF before DDS made its determination, destroy that paper document and add a folder message naming the source and recording submission of duplicative medical evidence. This research view does not authorize actual deletion.",
            "conditions": [
              "Exact duplication AND presence in CEF before the DDS determination."
            ],
            "source": "dis72_DI81010_125",
            "section": "C.1",
            "source_context_refs": [
              "DI81010.125:C"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "DDS receipt, action, appeal/reopening eligibility and return to the usual path are not established."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-fo-afterrelease-new": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-fo-afterrelease-new",
        "full_route": "disability-intake-evidence/disability-evidence-fo-afterrelease-new",
        "entry_conditions": [
          "DDS released jurisdiction to FO",
          "All or part of the paper medical evidence is new",
          "Source-only candidate; entry facts are not determined by route selection."
        ],
        "steps": [
          {
            "id": "disability-evidence-fo-afterrelease-new-compare",
            "title": "Identify any new part",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Review eView and compare the received paper medical evidence. The new-evidence branch applies when all or any part is not duplicative.",
            "conditions": [
              "DDS released jurisdiction to FO; received material is paper medical evidence."
            ],
            "source": "dis72_DI81010_125",
            "section": "C",
            "source_context_refs": [
              "DI81010.125:C"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          },
          {
            "id": "disability-evidence-fo-afterrelease-new-notify",
            "title": "Notify DDS that new evidence requires action",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Prepare a message or SSA-5002 notifying DDS that new evidence in file requires action.",
            "conditions": [
              "All or part of the received evidence is not duplicative."
            ],
            "source": "dis72_DI81010_125",
            "section": "C.2",
            "source_context_refs": [
              "DI81010.125:C"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          },
          {
            "id": "disability-evidence-fo-afterrelease-new-mail",
            "title": "Mail evidence and report through SSA-408",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Mail the evidence and SSA-5002 to DDS via SSA-408 (Route Slip). New evidence may be considered an implied appeal request; GN03102.100C.2 and DI27501.005 are linked dependencies, not reviewed eligibility, reopening or deadline decisions. The source permits a message OR SSA-5002 for notification yet separately names SSA-5002 in its mailing instruction; no invented substitute or automatic completion is supplied.",
            "conditions": [
              "All or part of the received evidence is new; this does not establish DDS receipt or action."
            ],
            "source": "dis72_DI81010_125",
            "section": "C.2",
            "source_context_refs": [
              "DI81010.125:C"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "DDS receipt, action, appeal/reopening eligibility and return to the usual path are not established."
          ]
        }
      },
      "disability-intake-evidence/disability-evidence-fo-electronic-evidence": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "disability-evidence-fo-electronic-evidence",
        "full_route": "disability-intake-evidence/disability-evidence-fo-electronic-evidence",
        "entry_conditions": [
          "FO receives medical evidence electronically, such as CD or WorkTrack",
          "Source-only candidate; entry facts are not determined by route selection."
        ],
        "steps": [
          {
            "id": "disability-evidence-fo-electronic-evidence-no-print",
            "title": "Keep electronic evidence electronic",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "When FO receives electronic medical evidence, such as Compact Disc or Worktrack, do not print the information.",
            "conditions": [
              "FO receives medical evidence in electronic format."
            ],
            "source": "dis72_DI81010_125",
            "section": "D",
            "source_context_refs": [
              "DI81010.125:D"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          },
          {
            "id": "disability-evidence-fo-electronic-evidence-upload",
            "title": "Use the electronic-upload alternative",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "FO may electronically upload the evidence using Upload Document in the Case Documents screen. Upload and routing the received item are alternatives, not cumulative mandatory steps.",
            "conditions": [
              "Electronic-upload alternative is used."
            ],
            "source": "dis72_DI81010_125",
            "section": "D",
            "source_context_refs": [
              "DI81010.125:D"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established.",
            "alternative_group": "electronic-handling"
          },
          {
            "id": "disability-evidence-fo-electronic-evidence-route",
            "title": "Use the received-item routing alternative",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Alternatively, route the received item to DDS or ODAR along with other claimant- or representative-supplied evidence. The next label instruction is conditional on this physical-item route.",
            "conditions": [
              "Received-item routing alternative is used."
            ],
            "source": "dis72_DI81010_125",
            "section": "D",
            "source_context_refs": [
              "DI81010.125:D"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established.",
            "alternative_group": "electronic-handling"
          },
          {
            "id": "disability-evidence-fo-electronic-evidence-label",
            "title": "Protect privacy on the routed-item label",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "Attach a label with claimant name, the last four SSN digits preceded by five Xs in SSN format (XXX-XX-1234), FO receipt date, and submitting source name. The source states this masked format protects privacy if the electronic evidence is returned to its source; it does not require a return in every case.",
            "conditions": [
              "The received electronic item is routed rather than only uploaded."
            ],
            "source": "dis72_DI81010_125",
            "section": "D",
            "source_context_refs": [
              "DI81010.125:D"
            ],
            "qualifications": [
              "Published staff-handling illustration only; selecting it establishes no individual case facts or customer duty.",
              "No verified native transaction, completed action, new system identity, relationship or automatic rejoin is asserted.",
              "Existing source objects, provenance, additional_sources and original legacy wording remain unchanged pending independent review."
            ],
            "next": "No completed action or automatic rejoin established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "DDS receipt, action, appeal/reopening eligibility and return to the usual path are not established."
          ]
        },
        "alternative_groups": [
          {
            "id": "electronic-handling",
            "label": "Electronic upload OR routing the received item",
            "note": "The published alternatives are not cumulative duties. The final masked-label instruction applies to the received-item routing alternative only.",
            "logic": "source_conditions_determine_branch"
          }
        ]
      }
    },
    "original_records": {
      "disability-intake-evidence/disability-evidence-fo-afterrelease-duplicate": {
        "id": "disability-evidence-fo-afterrelease-duplicate",
        "title": "Evidence after DDS release duplicates the decided record",
        "when": "DDS released jurisdiction to FO; Paper medical evidence exactly duplicates evidence already in CEF before the determination",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Compare with eView and record that duplicate medical evidence was submitted. Scope and qualifications: Exact duplication and pre-determination presence are both required. Source specifies paper duplicate destruction only for this qualified branch; this is distinct from the unresolved critical-case source-disposition overlap. This research view does not authorize deletion of any real case record.",
        "route": "Published handling by FO; see the cited instructions.",
        "next": "Verify exact duplication rather than treating similar material as duplicate.",
        "source": "dis72_DI81010_125",
        "section": "C",
        "additional_sources": [],
        "owner": "FO",
        "systems": [
          "eView",
          "CEF"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-office",
        "conditions": [
          "DDS released jurisdiction to FO",
          "Paper medical evidence exactly duplicates evidence already in CEF before the determination"
        ],
        "condition_logic": "all",
        "qualifications": [
          "Exact duplication and pre-determination presence are both required.",
          "Source specifies paper duplicate destruction only for this qualified branch; this is distinct from the unresolved critical-case source-disposition overlap.",
          "This research view does not authorize deletion of any real case record."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.125",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
            "locator": "C",
            "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
            "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
            "start": 4415,
            "end": 5368,
            "span_sha256": "5118faca7ddc0e45d808c374ecc0fc97c39441d10bbbe738ce86b814210e7766",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-fo-afterrelease-duplicate",
          "parent_stage_id": "evidence-office",
          "title": "Evidence after DDS release duplicates the decided record",
          "conditions": [
            "DDS released jurisdiction to FO",
            "Paper medical evidence exactly duplicates evidence already in CEF before the determination"
          ],
          "ui_text": {
            "when": "DDS released jurisdiction to FO; Paper medical evidence exactly duplicates evidence already in CEF before the determination",
            "ssa_action": "Compare with eView and record that duplicate medical evidence was submitted.",
            "what_to_check": "Verify exact duplication rather than treating similar material as duplicate."
          },
          "owner": "FO",
          "entity_ids": [
            "APP_EVIEW",
            "REPO_CEF"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.125",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
              "locator": "C",
              "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
              "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
              "start": 4415,
              "end": 5368,
              "span_sha256": "5118faca7ddc0e45d808c374ecc0fc97c39441d10bbbe738ce86b814210e7766",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "Exact duplication and pre-determination presence are both required.",
            "Source specifies paper duplicate destruction only for this qualified branch; this is distinct from the unresolved critical-case source-disposition overlap.",
            "This research view does not authorize deletion of any real case record."
          ],
          "existing_relationship_ids": [],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      },
      "disability-intake-evidence/disability-evidence-fo-afterrelease-new": {
        "id": "disability-evidence-fo-afterrelease-new",
        "title": "New medical evidence reaches FO after DDS release",
        "when": "DDS released jurisdiction to FO; All or part of the paper medical evidence is new",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Notify DDS with a message or SSA-5002 and mail the evidence and contact report using the applicable route slip. Scope and qualifications: New evidence may imply an appeal request; that conclusion needs the cited appeal/reopening crossreferences. Do not promise reopening, a changed determination or a new appeal deadline.",
        "route": "Published handling by FO to DDS; see the cited instructions.",
        "next": "Confirm DDS receives the new evidence and evaluates the appropriate next action.",
        "source": "dis72_DI81010_125",
        "section": "C",
        "additional_sources": [
          {
            "source": "dis72_DI81020_060",
            "section": "C"
          }
        ],
        "owner": "FO to DDS",
        "systems": [
          "eView",
          "CEF",
          "SSA-5002",
          "DDS"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-office",
        "conditions": [
          "DDS released jurisdiction to FO",
          "All or part of the paper medical evidence is new"
        ],
        "condition_logic": "all",
        "qualifications": [
          "New evidence may imply an appeal request; that conclusion needs the cited appeal/reopening crossreferences.",
          "Do not promise reopening, a changed determination or a new appeal deadline."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.125",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
            "locator": "C",
            "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
            "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
            "start": 4415,
            "end": 5368,
            "span_sha256": "5118faca7ddc0e45d808c374ecc0fc97c39441d10bbbe738ce86b814210e7766",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          },
          {
            "source_code": "DI81020.060",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481020060",
            "locator": "C",
            "text_sha256": "15392ccaa63f9f2e9a36a6324b83d365b3f8977fecddd2b0fc8aaeaa29e10810",
            "raw_sha256": "79baf3d9283a3f402eaab2839a7c71eb999f805f2a23b2e157742fe8659e1c29",
            "start": 2413,
            "end": 3530,
            "span_sha256": "82e5eb6eb362392ced1f553ed5dc8ebfe2c73a2f73564bbf6c99a85b105d0ff2",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-fo-afterrelease-new",
          "parent_stage_id": "evidence-office",
          "title": "New medical evidence reaches FO after DDS release",
          "conditions": [
            "DDS released jurisdiction to FO",
            "All or part of the paper medical evidence is new"
          ],
          "ui_text": {
            "when": "DDS released jurisdiction to FO; All or part of the paper medical evidence is new",
            "ssa_action": "Notify DDS with a message or SSA-5002 and mail the evidence and contact report using the applicable route slip.",
            "what_to_check": "Confirm DDS receives the new evidence and evaluates the appropriate next action."
          },
          "owner": "FO to DDS",
          "entity_ids": [
            "APP_EVIEW",
            "REPO_CEF",
            "FORM_SSA5002",
            "ORG_DDS"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.125",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
              "locator": "C",
              "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
              "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
              "start": 4415,
              "end": 5368,
              "span_sha256": "5118faca7ddc0e45d808c374ecc0fc97c39441d10bbbe738ce86b814210e7766",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            },
            {
              "source_code": "DI81020.060",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481020060",
              "locator": "C",
              "text_sha256": "15392ccaa63f9f2e9a36a6324b83d365b3f8977fecddd2b0fc8aaeaa29e10810",
              "raw_sha256": "79baf3d9283a3f402eaab2839a7c71eb999f805f2a23b2e157742fe8659e1c29",
              "start": 2413,
              "end": 3530,
              "span_sha256": "82e5eb6eb362392ced1f553ed5dc8ebfe2c73a2f73564bbf6c99a85b105d0ff2",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "New evidence may imply an appeal request; that conclusion needs the cited appeal/reopening crossreferences.",
            "Do not promise reopening, a changed determination or a new appeal deadline."
          ],
          "existing_relationship_ids": [],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      },
      "disability-intake-evidence/disability-evidence-fo-electronic-evidence": {
        "id": "disability-evidence-fo-electronic-evidence",
        "title": "Electronic medical evidence reaches the field office",
        "when": "FO receives medical evidence electronically, such as CD or WorkTrack",
        "you": "This is a published staff-handling scenario. No additional customer duty is inferred from selecting it.",
        "ssa": "Do not print; upload through Case Documents or route the received item with the other submitted evidence. Scope and qualifications: If routing the item, label claimant name, masked last-four SSN, receipt date and submitting source. Upload and physical routing are alternatives in the source; do not portray both as always required.",
        "route": "Published handling by FO to DDS/ODAR; see the cited instructions.",
        "next": "Check indexing and destination; do not expose an unmasked SSN in a returned-item label.",
        "source": "dis72_DI81010_125",
        "section": "D",
        "additional_sources": [],
        "owner": "FO to DDS/ODAR",
        "systems": [
          "eView",
          "CEF",
          "DDS"
        ],
        "timing": "No overall decision or processing-time promise is established by this branch.",
        "review_status": "Selected source spans and all listed conditions reviewed; development candidate, not a complete exceptional workflow or tested internal transaction.",
        "parent_stage_id": "evidence-office",
        "conditions": [
          "FO receives medical evidence electronically, such as CD or WorkTrack"
        ],
        "condition_logic": "all",
        "qualifications": [
          "If routing the item, label claimant name, masked last-four SSN, receipt date and submitting source.",
          "Upload and physical routing are alternatives in the source; do not portray both as always required."
        ],
        "scope": "adult initial disability; selected evidence-handoff branch",
        "related_workload": "adult initial-claim/evidence context; inspect each condition",
        "source_provenance": [
          {
            "source_code": "DI81010.125",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
            "locator": "D",
            "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
            "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
            "start": 5368,
            "end": 6181,
            "span_sha256": "8f220efa9f1b9c11d66c1ca194a63df1a6a2af476dde47b777d2ba774e186c91",
            "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
            "capture_status": "sha256_verified",
            "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
          }
        ],
        "source_qualified_branch": {
          "id": "disability-evidence-fo-electronic-evidence",
          "parent_stage_id": "evidence-office",
          "title": "Electronic medical evidence reaches the field office",
          "conditions": [
            "FO receives medical evidence electronically, such as CD or WorkTrack"
          ],
          "ui_text": {
            "when": "FO receives medical evidence electronically, such as CD or WorkTrack",
            "ssa_action": "Do not print; upload through Case Documents or route the received item with the other submitted evidence.",
            "what_to_check": "Check indexing and destination; do not expose an unmasked SSN in a returned-item label."
          },
          "owner": "FO to DDS/ODAR",
          "entity_ids": [
            "APP_EVIEW",
            "REPO_CEF",
            "ORG_DDS"
          ],
          "policy_refs": [
            {
              "source_code": "DI81010.125",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
              "locator": "D",
              "text_sha256": "3ee86fea26f44077a12d2aae8263e1caedf73d234e600c847cd3d529250cf4e6",
              "raw_sha256": "24aab0deb5732f10e58b26b3c90d2d550868af69792929d865f17be6b8c2de90",
              "start": 5368,
              "end": 6181,
              "span_sha256": "8f220efa9f1b9c11d66c1ca194a63df1a6a2af476dde47b777d2ba774e186c91",
              "offset_unit": "Unicode codepoints in the pinned UTF-8-decoded text",
              "capture_status": "sha256_verified",
              "context_scope": "Full selected subsection span; includes its listed notes and exceptions"
            }
          ],
          "qualifications": [
            "If routing the item, label claimant name, masked last-four SSN, receipt date and submitting source.",
            "Upload and physical routing are alternatives in the source; do not portray both as always required."
          ],
          "existing_relationship_ids": [],
          "existing_journey_id": "apply-disability",
          "existing_step_ids": [
            "apply-disability-3"
          ],
          "scope": "adult initial disability; selected evidence-handoff branch",
          "status": "source_checked_draft",
          "timing": {
            "kind": "not_established",
            "text": "No overall decision or processing-time promise is established by this branch."
          },
          "condition_logic": "all",
          "journey_scope_label": "Adult initial-claim evidence path"
        }
      }
    },
    "source_contexts": [
      {
        "id": "DI81010.125:C",
        "source": "dis72_DI81010_125",
        "section": "C",
        "text": "C. \nReceiving paper medical evidence after DDS releases jurisdiction to the FO\n\nDetermine if the medical evidence duplicates evidence in the CEF by:\n\n•\n\nreviewing eView; and\n\n•\n\ncomparing it to the medical evidence received.\n\n1. \nDuplicate evidence\n\nIf the evidence is an exact duplicate of evidence in the CEF before the DDS made the disability determination:\n\n•\n\nDestroy the paper document; and\n\n•\n\nAdd a message to the folder, including the name of the source, that duplicative medical evidence was submitted.\n\n2. \nNew evidence\n\nIf all or part of the evidence is not duplicative (i.e., new evidence):\n\n•\n\nPrepare a message or a SSA-5002 to notify the DDS that new evidence in file requires action; and\n\n•\n\nMail the evidence and SSA-5002 to DDS via SSA-408 (Route Slip).\n\nREMINDER: Receipt of new evidence may be considered an implied request for an appeal, see GN 03102.100C.2. For more information on revisions and reopenings, see Reopenings and Revisions DI 27501.005.\n\n",
        "start": 4392,
        "end": 5367,
        "offset_unit": "Unicode codepoints in exact captured visible_text",
        "text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
        "span_sha256": "15e42ed9fd7cadf157314280f1107d3e1b5f3f449e9c520437e5e5b676b69cc2"
      },
      {
        "id": "DI81010.125:D",
        "source": "dis72_DI81010_125",
        "section": "D",
        "text": "D. \nReceiving medical evidence in an electronic format in the FO\n\nIf the FO receives electronic medical evidence (e.g., Compact Disc or Worktrack), do not print the information. The FO may electronically upload the evidence via the Upload Document button in the Case Documents screen, or route the item received to DDS or ODAR along with any other claimant or representative-supplied evidence. Attach a label that contains the following:\n\n•\n\nClaimant’s name;\n\n•\n\nLast four digits of the claimant’s SSN preceded by five “Xs” in the SSN format (e.g., XXX-XX-1234). This SSN format is necessary to ensure the privacy of the claimant if we return the electronic medical evidence to the source;\n\n•\n\nDate the FO received the electronic medical evidence; and\n\n•\n\nName of the source that submitted the electronic medical evidence.\n\n",
        "start": 5367,
        "end": 6191,
        "offset_unit": "Unicode codepoints in exact captured visible_text",
        "text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
        "span_sha256": "20f4dce661a51f20423d271a255c05c9f5df4819f11bccb850bf15d2eb5e39fb"
      }
    ],
    "source_proposal_sha256": "b33ef5f7cc906369bf1269642183ab31455789bfb39a1948e1d969d31847e959",
    "source_peer_sha256": "d489a316a489a0d0c467d76afa3623294a936b362145f5bb0e9ad077ae997625",
    "source_capture_sha256": "fc80f1d846a7a7fb11f44e5ead54668577344bc1ffc049e5393cc1b416695ae5",
    "whole_source_text_url": "/service/sources/evidence-disposition3-DI81010.125-main.txt",
    "whole_source_text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
    "holds": [
      "GN03102.100C.2 implied appeal criteria not captured/reviewed in this package",
      "DI27501.005 reopening/revision criteria not captured/reviewed in this package",
      "New-evidence notification message OR SSA-5002 versus mailing SSA-5002 wording retained explicitly; no inferred substitute",
      "No critical-case fax disposition or HIT source-location hold resolved"
    ],
    "limits": [
      "Independent full primary and original-record review",
      "Fresh baseline/file lease and fullsource/context binding/render validation before any candidate integration",
      "Channel/actor/export/UI/wholepacket inverse remain future gates"
    ],
    "source_native_acceptance": false,
    "flow_metadata_delta": "Only source-defined electronic-handling alternative-group declaration added to meet unchanged shared schema; source steps, predicates, actions and original records exact."
  },
  "sbc3_selected": {
    "schema": "securitystat.selected-source-sequences/1",
    "status": "SOURCE_PEER_REVIEWED_INTEGRATION_PENDING_INDEPENDENT_RUNTIME_REVIEW",
    "selected_flow_count": 3,
    "card_count": 4,
    "flows": {
      "elect-benefit-continuation/sbc-titleii-reinstatement-edcs-no-payment-update": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "sbc-titleii-reinstatement-edcs-no-payment-update",
        "full_route": "elect-benefit-continuation/sbc-titleii-reinstatement-edcs-no-payment-update",
        "entry_conditions": [
          "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.",
          "EDCS inputs have not updated the payment status."
        ],
        "steps": [
          {
            "id": "sbc-titleii-reinstatement-edcs-no-payment-update-source-step-1",
            "title": "SBC initiation limitation",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "POS is no longer used to initiate SBC.",
            "conditions": [
              "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.",
              "EDCS inputs have not updated the payment status."
            ],
            "source": "sbcprocess",
            "section": "B.7 NOTE",
            "source_context_refs": [
              "SBC3-DI12027.010-B7"
            ],
            "qualifications": [
              "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
              "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
              "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
              "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
              "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
              "This is a bounded subset of the note; may require assistance is not a guarantee of PC action or successful reinstatement.",
              "Do not infer PCACS, fax, email, upload or a physical/interface endpoint from the generic Processing Center reference. POS role limitation concerns initiating SBC, not retirement of the POS application.",
              "Selecting this staff-handling illustration establishes no individual case facts, eligibility, authorization or completed payment action."
            ],
            "next": "Actual input, receipt, payment status and completed rejoin are not established."
          },
          {
            "id": "sbc-titleii-reinstatement-edcs-no-payment-update-source-step-2",
            "title": "Conditional Processing Center assistance",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "SBC reinstatements may require PC assistance in Medicare-only or other Title II cases when EDCS inputs do not update payment status.",
            "conditions": [
              "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.",
              "EDCS inputs have not updated the payment status."
            ],
            "source": "sbcprocess",
            "section": "B.7 NOTE",
            "source_context_refs": [
              "SBC3-DI12027.010-B7"
            ],
            "qualifications": [
              "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
              "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
              "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
              "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
              "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
              "This is a bounded subset of the note; may require assistance is not a guarantee of PC action or successful reinstatement.",
              "Do not infer PCACS, fax, email, upload or a physical/interface endpoint from the generic Processing Center reference. POS role limitation concerns initiating SBC, not retirement of the POS application.",
              "Selecting this staff-handling illustration establishes no individual case facts, eligibility, authorization or completed payment action."
            ],
            "next": "Actual input, receipt, payment status and completed rejoin are not established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ]
        }
      },
      "elect-benefit-continuation/sbc-titleii-edcs-exclusion-eeai": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "sbc-titleii-edcs-exclusion-eeai",
        "full_route": "elect-benefit-continuation/sbc-titleii-edcs-exclusion-eeai",
        "entry_conditions": [
          "An SBC request involves a Title II EDCS exclusion."
        ],
        "steps": [
          {
            "id": "sbc-titleii-edcs-exclusion-eeai-source-step-1",
            "title": "Published SBC system input",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "SBC requests involving a Title II EDCS exclusion require inputs on the EEAI screen in DCF.",
            "conditions": [
              "An SBC request involves a Title II EDCS exclusion."
            ],
            "source": "sbcprocess",
            "section": "B.7.b",
            "source_context_refs": [
              "SBC3-DI12027.010-B7"
            ],
            "qualifications": [
              "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
              "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
              "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
              "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
              "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
              "R133_E0024 and R174_E001 are existing EEAI navigation candidates with their own historical medical-CDR scopes; do not auto-alias them or silently expand either native record.",
              "No T2R/MBR automatic-posting chain is adopted from nearby R174_E002; the captured .010paragraph names EEAI/DCF, not that downstream chain.",
              "Selecting this staff-handling illustration establishes no individual case facts, eligibility, authorization or completed payment action."
            ],
            "next": "Actual input, receipt, payment status and completed rejoin are not established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ]
        }
      },
      "elect-benefit-continuation/sbc-titlexvi-direct-ssr": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "sbc-titlexvi-direct-ssr",
        "full_route": "elect-benefit-continuation/sbc-titlexvi-direct-ssr",
        "entry_conditions": [
          "An SBC request involves Title XVI."
        ],
        "steps": [
          {
            "id": "sbc-titlexvi-direct-ssr-source-step-1",
            "title": "Published SBC system input",
            "kind": "ssa",
            "actor": "FO staff",
            "action": "SBC requests involving Title XVI require a direct SSR update.",
            "conditions": [
              "An SBC request involves Title XVI."
            ],
            "source": "sbcprocess",
            "section": "B.7.b",
            "source_context_refs": [
              "SBC3-DI12027.010-B7"
            ],
            "qualifications": [
              "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
              "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
              "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
              "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
              "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
              "Do not generalize this to all Title II requests, all contact changes or unconditional EDCS-to-SSR synchronization.",
              "B.7refers Title XVI/concurrent handling and electronic appeal/SBC establishment to DI81010.230. Neither that target nor the listed MSOM/SM instructions is expanded in this package.",
              "Selecting this staff-handling illustration establishes no individual case facts, eligibility, authorization or completed payment action."
            ],
            "next": "Actual input, receipt, payment status and completed rejoin are not established."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ]
        }
      }
    },
    "original_records": {
      "elect-benefit-continuation/sbc-titleii-reinstatement-edcs-no-payment-update": {
        "id": "sbc-titleii-reinstatement-edcs-no-payment-update",
        "title": "EDCS inputs have not updated the Title II SBC reinstatement payment status",
        "parent_journey_id": "elect-benefit-continuation",
        "parent_step_id": "elect-benefit-continuation-3",
        "conditions": [
          "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.",
          "EDCS inputs have not updated the payment status."
        ],
        "condition_logic": "all",
        "ui_text": {
          "ssa_action": "The source says SBC reinstatements may require Processing Center assistance in the stated cases. POS is no longer used to initiate SBC. Modes of requesting assistance are referred to GN01070.228; no mode is invented here.",
          "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
        },
        "entity_ids": [
          "APP_EDCS",
          "APP_POS"
        ],
        "policy_refs": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "qualifications": [
          "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
          "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
          "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
          "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
          "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
          "This is a bounded subset of the note; may require assistance is not a guarantee of PC action or successful reinstatement.",
          "Do not infer PCACS, fax, email, upload or a physical/interface endpoint from the generic Processing Center reference. POS role limitation concerns initiating SBC, not retirement of the POS application."
        ],
        "rejoin_unknowns": [
          "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
        ],
        "status": "source_qualified_navigation_research",
        "source_qualified_branch": {
          "id": "sbc-titleii-reinstatement-edcs-no-payment-update",
          "title": "EDCS inputs have not updated the Title II SBC reinstatement payment status",
          "parent_journey_id": "elect-benefit-continuation",
          "parent_step_id": "elect-benefit-continuation-3",
          "conditions": [
            "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.",
            "EDCS inputs have not updated the payment status."
          ],
          "condition_logic": "all",
          "ui_text": {
            "ssa_action": "The source says SBC reinstatements may require Processing Center assistance in the stated cases. POS is no longer used to initiate SBC. Modes of requesting assistance are referred to GN01070.228; no mode is invented here.",
            "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
          },
          "entity_ids": [
            "APP_EDCS",
            "APP_POS"
          ],
          "policy_refs": [
            {
              "id": "DI12027.010-B.7",
              "source_code": "DI12027.010",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
              "start": 4160,
              "end": 5416,
              "exact_text": "7. \nSystems inputs\n\nThe Electronic Disability Collect System (EDCS) has functionality to:\n\n•\n\nautomate benefit terminations,\n\n•\n\ncommunicate record updates to the Disability Control File (DCF), and\n\n•\n\ninitiate Title II SBC payment and Medicare actions in medical cessation appeals.\n\nNOTE: \n\nThe Post-entitlement Online System (POS) is no longer used to initiate SBC. SBC reinstatements may require assistance from the Processing Center (PC) in Medicare-only continuations and other Title II cases when EDCS inputs do not update the payment status. For modes of requesting PC assistance, see GN 01070.228.\n\nFor Title XVI and concurrent cases, follow instructions in DI 81010.230.\n\na. \nElectronic process\n\nEstablish the appeal and SBC requests in applicable processing systems, following instructions in DI 81010.230.\n\nb. \nSystem limitations and exclusions\n\nSBC requests involving a Title II EDCS exclusion will require inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF. For an explanation of the system inputs, see CDR 001.025.\n\nSBC requests involving Title XVI will require a direct SSR update. For an explanation of the system inputs, see MSOM BUSSR 002.010, MSOM BUSSR 002.020, MSOM MSSICS 020.015, SM 01305.580, SM 01305.585, and SM 01601.685.\n\n",
              "offset_unit": "Unicode codepoints in captured browser-visible main text",
              "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
              "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
              "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
              "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
              "raw_http_bytes_claimed": false,
              "captured_utc": "2026-10-31T07:52:09.938Z"
            }
          ],
          "qualifications": [
            "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
            "Existing Service source sbcprocess and election journey are reused conceptually; no duplicate source, journey, system, alias or native edge is created. R10data remain unchanged.",
            "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
            "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
            "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
            "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
            "This is a bounded subset of the note; may require assistance is not a guarantee of PC action or successful reinstatement.",
            "Do not infer PCACS, fax, email, upload or a physical/interface endpoint from the generic Processing Center reference. POS role limitation concerns initiating SBC, not retirement of the POS application."
          ],
          "rejoin_unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ],
          "status": "source_qualified_research_candidate_no_integration"
        },
        "when": "The workflow concerns an SBC reinstatement in a Medicare-only continuation or another Title II case.; EDCS inputs have not updated the payment status.",
        "you": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer.",
        "ssa": "The source says SBC reinstatements may require Processing Center assistance in the stated cases. POS is no longer used to initiate SBC. Modes of requesting assistance are referred to GN01070.228; no mode is invented here. Source qualifications: Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal. Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed. No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred. Named cross-references remain observed links only until their exact primary scopes are captured and reviewed. Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate. This is a bounded subset of the note; may require assistance is not a guarantee of PC action or successful reinstatement. Do not infer PCACS, fax, email, upload or a physical/interface endpoint from the generic Processing Center reference. POS role limitation concerns initiating SBC, not retirement of the POS application.",
        "route": "Published conditional SBC systems or official-folder handling; no completed payment or receipt inferred.",
        "next": "Actual update, payment status, component receipt and completed rejoin are not demonstrated. Follow separately cited instructions for any further action.",
        "source": "sbcprocess",
        "section": "B.7",
        "source_provenance": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
          "snapshot_path": "/service/sources/DI12027.010-current-browser.txt",
          "report": "/service/sbc-systems-source-provenance.json"
        },
        "systems": [
          "EDCS",
          "POS"
        ],
        "timing": "No processing duration established for this selected source scenario.",
        "owner": "SSA staff following the stated conditional process; PC assistance only where the source says it may be required.",
        "staff_label": "SSA’S PUBLISHED HANDLING",
        "review_status": "Selected current B.7/B.8 source scope linked; other cross-reference procedures, native acceptance and internal execution remain unverified.",
        "source_qualified_branch_history": {
          "scope": "Original pre-integration research snapshot. Its candidate_no_integration status and draft bookkeeping describe that historical snapshot, not current deployment state or source/native acceptance.",
          "source_research_package_sha256": "784627f17feded6ca162ca7cdde190e6d1ca528e3d4f7b8f513badd109ce469c",
          "basis_source_capture_utc": "2026-10-31T07:52:09.938Z",
          "source_acceptance": false
        }
      },
      "elect-benefit-continuation/sbc-titleii-edcs-exclusion-eeai": {
        "id": "sbc-titleii-edcs-exclusion-eeai",
        "title": "The Title II SBC request involves an EDCS exclusion",
        "parent_journey_id": "elect-benefit-continuation",
        "parent_step_id": "elect-benefit-continuation-3",
        "conditions": [
          "An SBC request involves a Title II EDCS exclusion."
        ],
        "condition_logic": "all",
        "ui_text": {
          "ssa_action": "The source requires inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF, with a system-input cross-reference to CDR001.025.",
          "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
        },
        "entity_ids": [
          "DB_DCF"
        ],
        "policy_refs": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "qualifications": [
          "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
          "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
          "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
          "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
          "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
          "R133_E0024 and R174_E001 are existing EEAI navigation candidates with their own historical medical-CDR scopes; do not auto-alias them or silently expand either native record.",
          "No T2R/MBR automatic-posting chain is adopted from nearby R174_E002; the captured .010paragraph names EEAI/DCF, not that downstream chain."
        ],
        "rejoin_unknowns": [
          "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
        ],
        "status": "source_qualified_navigation_research",
        "source_qualified_branch": {
          "id": "sbc-titleii-edcs-exclusion-eeai",
          "title": "The Title II SBC request involves an EDCS exclusion",
          "parent_journey_id": "elect-benefit-continuation",
          "parent_step_id": "elect-benefit-continuation-3",
          "conditions": [
            "An SBC request involves a Title II EDCS exclusion."
          ],
          "condition_logic": "all",
          "ui_text": {
            "ssa_action": "The source requires inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF, with a system-input cross-reference to CDR001.025.",
            "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
          },
          "entity_ids": [
            "DB_DCF"
          ],
          "policy_refs": [
            {
              "id": "DI12027.010-B.7",
              "source_code": "DI12027.010",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
              "start": 4160,
              "end": 5416,
              "exact_text": "7. \nSystems inputs\n\nThe Electronic Disability Collect System (EDCS) has functionality to:\n\n•\n\nautomate benefit terminations,\n\n•\n\ncommunicate record updates to the Disability Control File (DCF), and\n\n•\n\ninitiate Title II SBC payment and Medicare actions in medical cessation appeals.\n\nNOTE: \n\nThe Post-entitlement Online System (POS) is no longer used to initiate SBC. SBC reinstatements may require assistance from the Processing Center (PC) in Medicare-only continuations and other Title II cases when EDCS inputs do not update the payment status. For modes of requesting PC assistance, see GN 01070.228.\n\nFor Title XVI and concurrent cases, follow instructions in DI 81010.230.\n\na. \nElectronic process\n\nEstablish the appeal and SBC requests in applicable processing systems, following instructions in DI 81010.230.\n\nb. \nSystem limitations and exclusions\n\nSBC requests involving a Title II EDCS exclusion will require inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF. For an explanation of the system inputs, see CDR 001.025.\n\nSBC requests involving Title XVI will require a direct SSR update. For an explanation of the system inputs, see MSOM BUSSR 002.010, MSOM BUSSR 002.020, MSOM MSSICS 020.015, SM 01305.580, SM 01305.585, and SM 01601.685.\n\n",
              "offset_unit": "Unicode codepoints in captured browser-visible main text",
              "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
              "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
              "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
              "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
              "raw_http_bytes_claimed": false,
              "captured_utc": "2026-10-31T07:52:09.938Z"
            }
          ],
          "qualifications": [
            "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
            "Existing Service source sbcprocess and election journey are reused conceptually; no duplicate source, journey, system, alias or native edge is created. R10data remain unchanged.",
            "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
            "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
            "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
            "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
            "R133_E0024 and R174_E001 are existing EEAI navigation candidates with their own historical medical-CDR scopes; do not auto-alias them or silently expand either native record.",
            "No T2R/MBR automatic-posting chain is adopted from nearby R174_E002; the captured .010paragraph names EEAI/DCF, not that downstream chain."
          ],
          "rejoin_unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ],
          "status": "source_qualified_research_candidate_no_integration"
        },
        "when": "An SBC request involves a Title II EDCS exclusion.",
        "you": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer.",
        "ssa": "The source requires inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF, with a system-input cross-reference to CDR001.025. Source qualifications: Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal. Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed. No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred. Named cross-references remain observed links only until their exact primary scopes are captured and reviewed. Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate. R133_E0024 and R174_E001 are existing EEAI navigation candidates with their own historical medical-CDR scopes; do not auto-alias them or silently expand either native record. No T2R/MBR automatic-posting chain is adopted from nearby R174_E002; the captured .010paragraph names EEAI/DCF, not that downstream chain.",
        "route": "Published conditional SBC systems or official-folder handling; no completed payment or receipt inferred.",
        "next": "Actual update, payment status, component receipt and completed rejoin are not demonstrated. Follow separately cited instructions for any further action.",
        "source": "sbcprocess",
        "section": "B.7",
        "source_provenance": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
          "snapshot_path": "/service/sources/DI12027.010-current-browser.txt",
          "report": "/service/sbc-systems-source-provenance.json"
        },
        "systems": [
          "DCF"
        ],
        "timing": "No processing duration established for this selected source scenario.",
        "owner": "SSA staff following the stated conditional process; PC assistance only where the source says it may be required.",
        "staff_label": "SSA’S PUBLISHED HANDLING",
        "review_status": "Selected current B.7/B.8 source scope linked; other cross-reference procedures, native acceptance and internal execution remain unverified.",
        "existing_navigation_candidates": [
          {
            "entity_id": "R133_E0024",
            "href": "/technology/#R133_E0024",
            "native_record": {
              "entity_id": "R133_E0024",
              "entity_type": "user_interface",
              "canonical_name": "EDCS Exclusion Appeal Input Screen",
              "acronym": "EEAI",
              "domain": "Disability and appeals",
              "description": "EDCS exclusion input screen used to record certain Title II medical CDR appeal requests into the DCF outside the ordinary EDCS appeal case.",
              "observed_status": "documented",
              "observed_as_of": "2026-10-08",
              "confidence": 5,
              "notes": ""
            },
            "scope": "Separate inherited EEAI candidate; no alias or scope expansion established."
          },
          {
            "entity_id": "R174_E001",
            "href": "/technology/#R174_E001",
            "native_record": {
              "entity_id": "R174_E001",
              "entity_type": "user_interface",
              "canonical_name": "EDCS Exclusion Appeal (EEAI) Screen",
              "acronym": null,
              "domain": "Disability; Appeals",
              "description": "For EDCS-excluded Title II medical-CDR reconsideration and hearings, FO enters appeal request into the DCF using the EEAI screen.",
              "observed_status": "documented_operational",
              "observed_as_of": "2026-10-10",
              "confidence": 5,
              "notes": "2026 POMS section C.2; no database product or transport inferred."
            },
            "scope": "Separate inherited EEAI candidate; no alias or scope expansion established."
          }
        ],
        "source_qualified_branch_history": {
          "scope": "Original pre-integration research snapshot. Its candidate_no_integration status and draft bookkeeping describe that historical snapshot, not current deployment state or source/native acceptance.",
          "source_research_package_sha256": "784627f17feded6ca162ca7cdde190e6d1ca528e3d4f7b8f513badd109ce469c",
          "basis_source_capture_utc": "2026-10-31T07:52:09.938Z",
          "source_acceptance": false
        }
      },
      "elect-benefit-continuation/sbc-titlexvi-direct-ssr": {
        "id": "sbc-titlexvi-direct-ssr",
        "title": "The SBC request involves Title XVI",
        "parent_journey_id": "elect-benefit-continuation",
        "parent_step_id": "elect-benefit-continuation-3",
        "conditions": [
          "An SBC request involves Title XVI."
        ],
        "condition_logic": "all",
        "ui_text": {
          "ssa_action": "The source states a direct SSR update is required. Follow the separately referenced Title XVI/concurrent and system-input instructions; their field-by-field details are not supplied here.",
          "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
        },
        "entity_ids": [
          "SYS_SSR"
        ],
        "policy_refs": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "qualifications": [
          "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
          "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
          "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
          "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
          "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
          "Do not generalize this to all Title II requests, all contact changes or unconditional EDCS-to-SSR synchronization.",
          "B.7refers Title XVI/concurrent handling and electronic appeal/SBC establishment to DI81010.230. Neither that target nor the listed MSOM/SM instructions is expanded in this package."
        ],
        "rejoin_unknowns": [
          "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
        ],
        "status": "source_qualified_navigation_research",
        "source_qualified_branch": {
          "id": "sbc-titlexvi-direct-ssr",
          "title": "The SBC request involves Title XVI",
          "parent_journey_id": "elect-benefit-continuation",
          "parent_step_id": "elect-benefit-continuation-3",
          "conditions": [
            "An SBC request involves Title XVI."
          ],
          "condition_logic": "all",
          "ui_text": {
            "ssa_action": "The source states a direct SSR update is required. Follow the separately referenced Title XVI/concurrent and system-input instructions; their field-by-field details are not supplied here.",
            "customer_action": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer."
          },
          "entity_ids": [
            "SYS_SSR"
          ],
          "policy_refs": [
            {
              "id": "DI12027.010-B.7",
              "source_code": "DI12027.010",
              "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
              "start": 4160,
              "end": 5416,
              "exact_text": "7. \nSystems inputs\n\nThe Electronic Disability Collect System (EDCS) has functionality to:\n\n•\n\nautomate benefit terminations,\n\n•\n\ncommunicate record updates to the Disability Control File (DCF), and\n\n•\n\ninitiate Title II SBC payment and Medicare actions in medical cessation appeals.\n\nNOTE: \n\nThe Post-entitlement Online System (POS) is no longer used to initiate SBC. SBC reinstatements may require assistance from the Processing Center (PC) in Medicare-only continuations and other Title II cases when EDCS inputs do not update the payment status. For modes of requesting PC assistance, see GN 01070.228.\n\nFor Title XVI and concurrent cases, follow instructions in DI 81010.230.\n\na. \nElectronic process\n\nEstablish the appeal and SBC requests in applicable processing systems, following instructions in DI 81010.230.\n\nb. \nSystem limitations and exclusions\n\nSBC requests involving a Title II EDCS exclusion will require inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF. For an explanation of the system inputs, see CDR 001.025.\n\nSBC requests involving Title XVI will require a direct SSR update. For an explanation of the system inputs, see MSOM BUSSR 002.010, MSOM BUSSR 002.020, MSOM MSSICS 020.015, SM 01305.580, SM 01305.585, and SM 01601.685.\n\n",
              "offset_unit": "Unicode codepoints in captured browser-visible main text",
              "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
              "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
              "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
              "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
              "raw_http_bytes_claimed": false,
              "captured_utc": "2026-10-31T07:52:09.938Z"
            }
          ],
          "qualifications": [
            "Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal.",
            "Existing Service source sbcprocess and election journey are reused conceptually; no duplicate source, journey, system, alias or native edge is created. R10data remain unchanged.",
            "Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed.",
            "No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred.",
            "Named cross-references remain observed links only until their exact primary scopes are captured and reviewed.",
            "Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate.",
            "Do not generalize this to all Title II requests, all contact changes or unconditional EDCS-to-SSR synchronization.",
            "B.7refers Title XVI/concurrent handling and electronic appeal/SBC establishment to DI81010.230. Neither that target nor the listed MSOM/SM instructions is expanded in this package."
          ],
          "rejoin_unknowns": [
            "Actual record update, payment status, receipt, correction success and completed next case state are not demonstrated."
          ],
          "status": "source_qualified_research_candidate_no_integration"
        },
        "when": "An SBC request involves Title XVI.",
        "you": "Retain the appeal/election and correspondence; respond to SSA case-specific requests. This research view does not initiate payments or create a staff-system task for the customer.",
        "ssa": "The source states a direct SSR update is required. Follow the separately referenced Title XVI/concurrent and system-input instructions; their field-by-field details are not supplied here. Source qualifications: Conditional source-defined staff handling; source capture does not decide SBC eligibility, election validity, timeliness, payment amount, Medicare entitlement or successful appeal. Current navigation capture is separate from historical native evidence/status; no entity/relationship/source acceptance refreshed. No transport, physical deployment, general automatic synchronization, successful payment reinstatement, completed handoff or rejoin inferred. Named cross-references remain observed links only until their exact primary scopes are captured and reviewed. Whole page not marked reviewed: signature/protective-writing rules, appeal/election time limits and personal eligibility remain outside this B.7/B.8 systems/evidence candidate. Do not generalize this to all Title II requests, all contact changes or unconditional EDCS-to-SSR synchronization. B.7refers Title XVI/concurrent handling and electronic appeal/SBC establishment to DI81010.230. Neither that target nor the listed MSOM/SM instructions is expanded in this package.",
        "route": "Published conditional SBC systems or official-folder handling; no completed payment or receipt inferred.",
        "next": "Actual update, payment status, component receipt and completed rejoin are not demonstrated. Follow separately cited instructions for any further action.",
        "source": "sbcprocess",
        "section": "B.7",
        "source_provenance": [
          {
            "id": "DI12027.010-B.7",
            "source_code": "DI12027.010",
            "url": "https://secure.ssa.gov/poms.nsf/lnx/0412027010",
            "start": 4160,
            "end": 5416,
            "offset_unit": "Unicode codepoints in captured browser-visible main text",
            "text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
            "parsed_dom_sha256": "7333cdf50297b062e7818a5b98952d765bf134e36cece825982330b46f617a9a",
            "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
            "capture_type": "browser_visible_main_text_and_serialized_parsed_DOM",
            "raw_http_bytes_claimed": false,
            "captured_utc": "2026-10-31T07:52:09.938Z",
            "locator": "B.7",
            "download_url": "/service/sources/DI12027.010-current-browser.txt"
          }
        ],
        "source_receipt": {
          "checked_on": "2026-10-31",
          "snapshot_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
          "snapshot_path": "/service/sources/DI12027.010-current-browser.txt",
          "report": "/service/sbc-systems-source-provenance.json"
        },
        "systems": [
          "SSR"
        ],
        "timing": "No processing duration established for this selected source scenario.",
        "owner": "SSA staff following the stated conditional process; PC assistance only where the source says it may be required.",
        "staff_label": "SSA’S PUBLISHED HANDLING",
        "review_status": "Selected current B.7/B.8 source scope linked; other cross-reference procedures, native acceptance and internal execution remain unverified.",
        "source_qualified_branch_history": {
          "scope": "Original pre-integration research snapshot. Its candidate_no_integration status and draft bookkeeping describe that historical snapshot, not current deployment state or source/native acceptance.",
          "source_research_package_sha256": "784627f17feded6ca162ca7cdde190e6d1ca528e3d4f7b8f513badd109ce469c",
          "basis_source_capture_utc": "2026-10-31T07:52:09.938Z",
          "source_acceptance": false
        }
      }
    },
    "source_contexts": [
      {
        "start": 4160,
        "end": 5416,
        "text": "7. \nSystems inputs\n\nThe Electronic Disability Collect System (EDCS) has functionality to:\n\n•\n\nautomate benefit terminations,\n\n•\n\ncommunicate record updates to the Disability Control File (DCF), and\n\n•\n\ninitiate Title II SBC payment and Medicare actions in medical cessation appeals.\n\nNOTE: \n\nThe Post-entitlement Online System (POS) is no longer used to initiate SBC. SBC reinstatements may require assistance from the Processing Center (PC) in Medicare-only continuations and other Title II cases when EDCS inputs do not update the payment status. For modes of requesting PC assistance, see GN 01070.228.\n\nFor Title XVI and concurrent cases, follow instructions in DI 81010.230.\n\na. \nElectronic process\n\nEstablish the appeal and SBC requests in applicable processing systems, following instructions in DI 81010.230.\n\nb. \nSystem limitations and exclusions\n\nSBC requests involving a Title II EDCS exclusion will require inputs on the EDCS Exclusion Appeal (EEAI) screen in DCF. For an explanation of the system inputs, see CDR 001.025.\n\nSBC requests involving Title XVI will require a direct SSR update. For an explanation of the system inputs, see MSOM BUSSR 002.010, MSOM BUSSR 002.020, MSOM MSSICS 020.015, SM 01305.580, SM 01305.585, and SM 01601.685.\n\n",
        "span_sha256": "6b1a405df0f26a2fe82199a72b50d8f656d7249d91cc4cde70d29279cdfb84c5",
        "id": "SBC3-DI12027.010-B7",
        "section": "B.7",
        "source": "sbcprocess"
      }
    ],
    "source_proposal_sha256": "61bf80feac54e8f72a9c480c5e306c05b5568ac74bc5e8ebac287db35b854186",
    "source_peer_sha256": "e9b9a02c9eebcaa4e37b0fe7874287fb5d227022549dcaf25ace9748958fc9ba",
    "whole_source_text_url": "/service/sources/sbc3-DI12027.010-retained-main.txt",
    "whole_source_text_sha256": "06e295f045ed9d6868a3b845c62380875c35c5af1425f5279659b0139149b4c2",
    "holds": [
      "GN01070.228 modes not expanded; no completed PC handoff.",
      "CDR001.025 and listed MSOM/SM input instructions not expanded.",
      "No personal eligibility, election validity, deadlines, payment success, permissions or rejoin inferred.",
      "All original source/navigation records and source acceptance unchanged."
    ],
    "source_freshness_claim": false,
    "source_native_acceptance": false
  },
  "ordinary_medical_evidence1_selected": {
    "schema": "securitystat.ordinary-medical-evidence1-selected-source/1",
    "status": "SOURCE_ONLY_PENDING_INTEGRATION_RUNTIME_AND_RELEASE",
    "full_route": "disability-intake-evidence/disability-evidence-fo-pretransfer-ordinary",
    "flow": {
      "schema": "securitystat.exception-flow/1",
      "record_id": "disability-evidence-fo-pretransfer-ordinary",
      "full_route": "disability-intake-evidence/disability-evidence-fo-pretransfer-ordinary",
      "entry_conditions": [
        "Paper medical evidence reaches FO before transfer",
        "Case is outside TERI, PD, QDD, CAL and the special-arrangement branch",
        "This optional illustration establishes no individual case facts. Apply the source-specific condition on each card; the initial receipt card does not create a new blanket prerequisite for A.2 forwarding."
      ],
      "steps": [
        {
          "id": "disability-evidence-fo-pretransfer-ordinary-receipt-source",
          "title": "Document submitted evidence and each source",
          "kind": "ssa",
          "actor": "FO staff",
          "action": "When a claimant submits evidence to the FO, document the CEF to show receipt. In EDCS 3367 Remarks, annotate the claimant, applicant or representative submission as applicable and name the source of each document (for example, a physician or hospital). Do not treat function reports as medical evidence.",
          "conditions": [
            "Paper medical evidence reaches FO before transfer",
            "Case is outside TERI, PD, QDD, CAL and the special-arrangement branch",
            "The source receipt instruction applies when a claimant submits evidence; the Remarks instruction identifies claimant, applicant or representative submissions as applicable."
          ],
          "source": "dis72_DI81010_125",
          "section": "A introduction",
          "source_context_refs": [
            "DI81010.125:ordinary-A-introduction",
            "DI81010.125:ordinary-A2",
            "DI81010.125:ordinary-whole-A"
          ],
          "qualifications": [
            "Published FO staff-handling example only; route selection does not establish case facts, permissions, receipt, transfer or successful completion.",
            "Ordinary A.2 branch only: not TERI, PD, QDD, CAL or special-arrangement cases. A.1 page thresholds, x-ray/test-tracing referrals and critical-fax disposition remain distinct, not resolved or admitted by this sequence.",
            "Other disability-related forms such as function reports are not medical evidence under this section.",
            "Original source objects/statuses, legacy qualifications and full raw history are preserved. No new native system, edge or API identity is inferred."
          ],
          "next": "No successful receipt, transfer completion or automatic return to the usual path is established."
        },
        {
          "id": "disability-evidence-fo-pretransfer-ordinary-routing-form",
          "title": "Annotate the routing form, not the evidence",
          "kind": "ssa",
          "actor": "FO staff",
          "action": "For the ordinary A.2 case, annotate the EDCS Routing Form “Attached medical evidence to be scanned”. Do not make annotations on the medical evidence itself.",
          "conditions": [
            "Paper medical evidence reaches FO before transfer",
            "Case is outside TERI, PD, QDD, CAL and the special-arrangement branch"
          ],
          "source": "dis72_DI81010_125",
          "section": "A.2",
          "source_context_refs": [
            "DI81010.125:ordinary-A-introduction",
            "DI81010.125:ordinary-A2",
            "DI81010.125:ordinary-whole-A"
          ],
          "qualifications": [
            "Published FO staff-handling example only; route selection does not establish case facts, permissions, receipt, transfer or successful completion.",
            "Ordinary A.2 branch only: not TERI, PD, QDD, CAL or special-arrangement cases. A.1 page thresholds, x-ray/test-tracing referrals and critical-fax disposition remain distinct, not resolved or admitted by this sequence.",
            "Other disability-related forms such as function reports are not medical evidence under this section.",
            "Original source objects/statuses, legacy qualifications and full raw history are preserved. No new native system, edge or API identity is inferred."
          ],
          "next": "No successful receipt, transfer completion or automatic return to the usual path is established."
        },
        {
          "id": "disability-evidence-fo-pretransfer-ordinary-forward",
          "title": "Forward under the routing form, with the regional exception",
          "kind": "ssa",
          "actor": "FO staff",
          "action": "Forward the medical evidence under cover of the EDCS Routing Form with the signed SSA-827 forms unless other regional agreements apply. Under this ordinary path, do not maintain paper medical-evidence copies in the FO and do not create a barcode coversheet. The source does not provide a replacement regional procedure here; an applicable agreement remains a separate verified dependency.",
          "conditions": [
            "Paper medical evidence reaches FO before transfer",
            "Case is outside TERI, PD, QDD, CAL and the special-arrangement branch",
            "The default forwarding instruction is qualified by “unless other regional agreements apply”; this view does not determine whether an agreement applies or supply its contents."
          ],
          "source": "dis72_DI81010_125",
          "section": "A.2",
          "source_context_refs": [
            "DI81010.125:ordinary-A-introduction",
            "DI81010.125:ordinary-A2",
            "DI81010.125:ordinary-whole-A"
          ],
          "qualifications": [
            "Published FO staff-handling example only; route selection does not establish case facts, permissions, receipt, transfer or successful completion.",
            "Ordinary A.2 branch only: not TERI, PD, QDD, CAL or special-arrangement cases. A.1 page thresholds, x-ray/test-tracing referrals and critical-fax disposition remain distinct, not resolved or admitted by this sequence.",
            "Other disability-related forms such as function reports are not medical evidence under this section.",
            "Original source objects/statuses, legacy qualifications and full raw history are preserved. No new native system, edge or API identity is inferred."
          ],
          "next": "No successful receipt, transfer completion or automatic return to the usual path is established."
        }
      ],
      "rejoin": {
        "status": "unknown",
        "automatic_transition": false,
        "unknowns": [
          "The source does not establish DDS receipt, scanning completion, a decision time or an automatic return to the usual journey.",
          "Other applicable regional agreements must be verified separately; no substitute forwarding process is invented."
        ]
      }
    },
    "source_contexts": [
      {
        "id": "DI81010.125:ordinary-A-introduction",
        "source": "dis72_DI81010_125",
        "section": "A introduction",
        "start": 237,
        "end": 874,
        "exact_text": "A. \nReceiving paper medical evidence prior to case transfer\n\nIn all cases, when a claimant submits evidence to the field office (FO), document the certified electronic folder (CEF) to show it was received.\n\nIn the “Remarks” section of the Electronic Disability Collect System (EDCS) 3367:\n\n•\n\nAnnotate that the claimant, applicant, or representative submitted evidence to the FO ( e.g., hospital summary, physician notes, medical report) ; and\n\n•\n\nShow the name of the source for each document (e.g., Dr. John Smith, Mercy Hospital).\n\nNOTE: We do not consider other disability-related forms, such as function reports, medical evidence.\n\n",
        "span_sha256": "ea403d44db1d8ffb3a37fb9ff0af304fa6fb09ebe4f1adb4a477012d799d4f9c",
        "whole_visible_text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
        "offset_unit": "Unicode codepoints of complete pinned capture visible_text"
      },
      {
        "id": "DI81010.125:ordinary-A2",
        "source": "dis72_DI81010_125",
        "section": "A.2",
        "start": 2574,
        "end": 3145,
        "exact_text": "2. \nAll other cases (not TERI, PD, QDD, CAL, or special arrangement cases)\n\nFor all other cases:\n\n•\n\nAnnotate the EDCS Routing Form “Attached medical evidence to be scanned”. Do not make any annotations on the actual medical evidence; and\n\n•\n\nForward the medical evidence under cover of the EDCS Routing Form along with the signed SSA-827 (Authorization to Disclose Information to the Social Security Administration) forms unless other regional agreements apply.\n\nNOTE: Do not maintain paper copies of the medical evidence in the FO. Do not create a barcode coversheet.\n\n",
        "span_sha256": "cbf3487b82abe1894fcccacfb99552ed77456c0aa455598460a35c932d78a334",
        "whole_visible_text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
        "offset_unit": "Unicode codepoints of complete pinned capture visible_text"
      },
      {
        "id": "DI81010.125:ordinary-whole-A",
        "source": "dis72_DI81010_125",
        "section": "A whole context",
        "start": 237,
        "end": 3145,
        "exact_text": "A. \nReceiving paper medical evidence prior to case transfer\n\nIn all cases, when a claimant submits evidence to the field office (FO), document the certified electronic folder (CEF) to show it was received.\n\nIn the “Remarks” section of the Electronic Disability Collect System (EDCS) 3367:\n\n•\n\nAnnotate that the claimant, applicant, or representative submitted evidence to the FO ( e.g., hospital summary, physician notes, medical report) ; and\n\n•\n\nShow the name of the source for each document (e.g., Dr. John Smith, Mercy Hospital).\n\nNOTE: We do not consider other disability-related forms, such as function reports, medical evidence.\n\n1. \nTerminal Illness (TERI), Presumptive Disability (PD), Quick Disability Determination (QDD), Compassionate Allowance (CAL) or special arrangement cases\na. \nEvidence is 15 pages or less\n\nWhen the paper evidence submitted totals 15 pages or less:\n\n•\n\nCreate a barcode for each source of evidence, using the applicable document type\n\n“0180 - Claimant-Supplied Evidence” or, “5032 - Attorney-Supplied Evidence”;\n\n•\n\nFax the evidence into the CEF per Faxing Documents into the Certified Electronic Folder (CEF) Using Barcodes DI 81010.090;\n\n•\n\nVerify in eView under the “Case Documents” tab that you successfully faxed the evidence into the CEF and that all pages are legible; and\n\n•\n\nShred the evidence after you verify that you successfully faxed it into the CEF, unless other procedures require you to return the evidence to the claimant.\n\nNOTE: Store the evidence in the official paper folder if the official folder is paper and the evidence was faxed into an electronic folder.\n\nb. \nEvidence is more than 15 pages\n\nWhen the paper evidence submitted totals more than 15 pages handle the evidence per instructions DI 81010.125A.2. in this section.\n\nNOTE: For electronic evidence more than 15 pages, the FO can electronically upload the evidence into the electronic folder per instructions in DI 81010.125D in this section.\n\nIf regional or local arrangements are in place for faxing medical evidence into the CEF, or if time permits, you may fax more than 15 pages of medical evidence into the CEF for these cases.\n\nEXCEPTION: Do not attempt to fax x-rays or actual medical test tracings (e.g., EEGs, EKGs, pulmonary function studies). Handle those per instructions DI 81010.125A.2. in this section\n\n2. \nAll other cases (not TERI, PD, QDD, CAL, or special arrangement cases)\n\nFor all other cases:\n\n•\n\nAnnotate the EDCS Routing Form “Attached medical evidence to be scanned”. Do not make any annotations on the actual medical evidence; and\n\n•\n\nForward the medical evidence under cover of the EDCS Routing Form along with the signed SSA-827 (Authorization to Disclose Information to the Social Security Administration) forms unless other regional agreements apply.\n\nNOTE: Do not maintain paper copies of the medical evidence in the FO. Do not create a barcode coversheet.\n\n",
        "span_sha256": "594f014efc06a236496aae3558afa6f1c021a9b0e7fa1de9cf96565b2896a684",
        "whole_visible_text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
        "offset_unit": "Unicode codepoints of complete pinned capture visible_text"
      }
    ],
    "evidence": [
      {
        "step_id": "disability-evidence-fo-pretransfer-ordinary-receipt-source",
        "spans": [
          {
            "start": 298,
            "end": 442,
            "quote": "In all cases, when a claimant submits evidence to the field office (FO), document the certified electronic folder (CEF) to show it was received.",
            "sha256": "fe27401464c137486da6adcc8e16c8849484aa48a6017eaf3f90cf1bf32fc526",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          },
          {
            "start": 530,
            "end": 615,
            "quote": "Annotate that the claimant, applicant, or representative submitted evidence to the FO",
            "sha256": "87ff500d54ca94efa7f08967ac4ca18e6487ba6456c02f5df3fd9d5a11e462aa",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          },
          {
            "start": 685,
            "end": 730,
            "quote": "Show the name of the source for each document",
            "sha256": "9b5341f54d7c1ad13a521108488c33b439847065020bfe7fffde1fb53d088743",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          },
          {
            "start": 778,
            "end": 872,
            "quote": "We do not consider other disability-related forms, such as function reports, medical evidence.",
            "sha256": "bd10995ea1e0bf81f2124b0d8f7ba24faffc05d184e0883d5d2b75f3a08f818a",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          }
        ]
      },
      {
        "step_id": "disability-evidence-fo-pretransfer-ordinary-routing-form",
        "spans": [
          {
            "start": 2578,
            "end": 2648,
            "quote": "All other cases (not TERI, PD, QDD, CAL, or special arrangement cases)",
            "sha256": "118c2826f81b90587cd2b66a90fa1c0e3f2ec31aa1aca86fd8c047ee84fd8a59",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          },
          {
            "start": 2675,
            "end": 2812,
            "quote": "Annotate the EDCS Routing Form “Attached medical evidence to be scanned”. Do not make any annotations on the actual medical evidence; and",
            "sha256": "b674fdab083af20538fbaa9f5c223611a5d9a0abd309bca1dff24e639fb79907",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          }
        ]
      },
      {
        "step_id": "disability-evidence-fo-pretransfer-ordinary-forward",
        "spans": [
          {
            "start": 2817,
            "end": 3036,
            "quote": "Forward the medical evidence under cover of the EDCS Routing Form along with the signed SSA-827 (Authorization to Disclose Information to the Social Security Administration) forms unless other regional agreements apply.",
            "sha256": "f226e134a6d6f604e4abfde5cc06a52a1f8316e462ff2477dac0deb33b74c421",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          },
          {
            "start": 3044,
            "end": 3143,
            "quote": "Do not maintain paper copies of the medical evidence in the FO. Do not create a barcode coversheet.",
            "sha256": "3ecd5f8244cbac57b3f77166f8e760f0321fbf27f442d317a7e018b2000e8df2",
            "offset_unit": "Unicode codepoints in pinned complete visible_text"
          }
        ]
      }
    ],
    "source_capture_sha256": "fc80f1d846a7a7fb11f44e5ead54668577344bc1ffc049e5393cc1b416695ae5",
    "source_visible_text_sha256": "a4e9b2e9afd30bdeb4767126719aa93aefe8fb68a00e9a6c66291bb8b77df2d1",
    "source_url": "https://secure.ssa.gov/poms.nsf/lnx/0481010125",
    "full_captured_text_existing_URL": "/service/sources/evidence-disposition3-DI81010.125-main.txt",
    "source_peer_sha256": "817160e8a0c3bef5299f2d169d6fdab6a4707cf619551acb500f863d6c410725",
    "limits": [
      "FOcritical-case fax document disposition remains held; this noncritical A.2 example does not resolve it",
      "HIT Request/Response folder-location conflict remains held and unrelated",
      "Regional agreement content not captured or inferred; default forwarding may not apply",
      "Current candidate267 source-derived data only; full integration/context/schema/actor/export/UI and fresh baseline lease still required before release"
    ],
    "context_scope": "Aintro/A2 ordinary staff handling only. Whole A context includes distinct A1 critical/fax conditions for boundary comparison; it does not resolve those holds. No regional agreement contents, receipt, permission, completion or automatic rejoin inferred."
  },
  "paper_report_before_transfer1_selected": {
    "flow": {
      "schema": "securitystat.exception-flow/1",
      "record_id": "disability-evidence-fo-paper-report-before-transfer",
      "full_route": "disability-intake-evidence/disability-evidence-fo-paper-report-before-transfer",
      "entry_conditions": [
        "FO receives a paper disability-report form for an EDCS claim before transfer.",
        "This is the existing adult initial-claim branch; selection does not establish actual case facts or completion."
      ],
      "steps": [
        {
          "id": "disability-evidence-fo-paper-report-before-transfer-source-step-1",
          "title": "Preserve the official EDCS report",
          "kind": "ssa",
          "actor": "FO staff",
          "action": "The EDCS version is the official record. Enter all disability-report responses together with information the claimant provided during the disability interview into EDCS, and destroy the paper form.",
          "conditions": [
            "FO receives a paper disability-report form for an EDCS claim before transfer.",
            "This is the existing adult initial-claim branch; selection does not establish actual case facts or completion."
          ],
          "source": "r18_nonmedical135",
          "section": "B.1",
          "source_context_refs": [
            "DI81010.135:paper-report-B1-whole"
          ],
          "qualifications": [
            "Do not collect or store Disability Starter Kit worksheets in the EF.",
            "The separate after-transfer instruction requires comparison and recording new/changed information through EDCS Update-After-Transfer; this before-transfer branch does not invoke UAT.",
            "Paper EDCS-exclusion cases retain the paper official record under B.2; they are not covered by this EDCS branch.",
            "Original DI81020.055 source/provenance/qualifications remain unchanged; no new source-status approval for that source.",
            "No new entity IDs, customer duties, automatic entry, handoff completion, rejoin or processing-time promise."
          ]
        },
        {
          "id": "disability-evidence-fo-paper-report-before-transfer-source-step-2",
          "title": "Describe relevant unusual appearance when applicable",
          "kind": "ssa",
          "actor": "FO staff",
          "action": "When something unusual about the paper report appearance could be relevant to the disability determination, describe the relevant information in the Remarks section of the EDCS3367. Examples include unusual drawings, extensive writing in margins or unusual language.",
          "conditions": [
            "FO receives a paper disability-report form for an EDCS claim before transfer.",
            "This is the existing adult initial-claim branch; selection does not establish actual case facts or completion.",
            "The unusual appearance information could be relevant to the disability determination."
          ],
          "source": "r18_nonmedical135",
          "section": "B.1",
          "source_context_refs": [
            "DI81010.135:paper-report-B1-whole"
          ],
          "qualifications": [
            "Do not collect or store Disability Starter Kit worksheets in the EF.",
            "The separate after-transfer instruction requires comparison and recording new/changed information through EDCS Update-After-Transfer; this before-transfer branch does not invoke UAT.",
            "Paper EDCS-exclusion cases retain the paper official record under B.2; they are not covered by this EDCS branch.",
            "Original DI81020.055 source/provenance/qualifications remain unchanged; no new source-status approval for that source.",
            "No new entity IDs, customer duties, automatic entry, handoff completion, rejoin or processing-time promise."
          ]
        }
      ],
      "rejoin": {
        "status": "unknown",
        "automatic_transition": false,
        "unknowns": [
          "Selected source establishes no completed transfer, DDS receipt or automatic return to the usual journey."
        ]
      }
    },
    "source_contexts": [
      {
        "id": "DI81010.135:paper-report-B1-whole",
        "source": "r18_nonmedical135",
        "section": "B.1 whole including after-transfer instruction and worksheet note",
        "start": 1354,
        "end": 2420,
        "exact_text": "The EDCS version of the disability report is deemed the official record. When processing a paper disability report take the following action:\n\n•\n\nEnter all disability report responses in conjunction with any information provided by the claimant during a disability interview into EDCS, and destroy the paper form.\n\n•\n\nWhen something is unusual about the appearance of the paper report (e.g., there are unusual drawings, extensive writing in the margins, or unusual language) and that information could be relevant to the disability determination annotate the “Remarks” section of the EDCS 3367 with a description of the relevant information included on the paper report.\n\n•\n\nWhen a paper disability report is received after the claim has been transferred to the Disability Determination Services (DDS) or Hearings Office (HO), compare it to what is already on EDCS, record any new or changed information using the EDCS Update-After-Transfer function, and destroy the paper form.\n\nNOTE: Do not collect or store worksheets from the Disability Starter Kits in the EF.\n\n",
        "span_sha256": "59ececd09ec95c9b2affc4d3999e180bad19ff52692e6f324359a8e2050807f1",
        "whole_visible_text_sha256": "e58fbb11401ac2449de2559a1df0edef5d4d48c0d9e5162956aa83ac2fea2b3b",
        "offset_unit": "Unicode codepoints of complete pinned capture visible_text"
      }
    ],
    "whole_source_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 10/17/2023 - Present\nPrevious | Next\n\nTN 63 (10-23)\n\nDI 81010.135 Storing Non-Medical Evidence in the Electronic Folder (EF)\n\nWhenever possible, annotate new non-medical evidence electronically via Modernized Claims System (MCS), Modernized Supplemental Security Income Claims System (MSSICS), Consolidated Claims Experience (CCE), Interactive Computation Facility (ICF), Shared Process, or Post-Entitlement Online System (POS) per instructions:\n\n•\n\nElectronic Evidence Documentation and Retention - GN 00301.286;\n\n•\n\nMaterial Essential to Claims Folder Documentation - GN 00301.290; and\n\n•\n\nNonessential Material to be Omitted from Title II and Title XVI Claims Folders - GN 00301.295.\n\nA. \nEvidence for pending claims or appeals\n\nWhen a copy of a document must be stored in the file for pending claims or appeals:\n\n•\n\nFax the documents into the EF per Faxing Documents into the Certified Electronic Folder (CEF) Using Barcodes - DI 81010.090.\n\n•\n\nShred the document after successful faxing, unless other procedures require the return of the evidence to the claimant.\n\nB. \nReceiving paper disability reports\n1. \nReceiving a paper disability report in the field office (FO) for Electronic Disability Collect System (EDCS) claims\n\nThe EDCS version of the disability report is deemed the official record. When processing a paper disability report take the following action:\n\n•\n\nEnter all disability report responses in conjunction with any information provided by the claimant during a disability interview into EDCS, and destroy the paper form.\n\n•\n\nWhen something is unusual about the appearance of the paper report (e.g., there are unusual drawings, extensive writing in the margins, or unusual language) and that information could be relevant to the disability determination annotate the “Remarks” section of the EDCS 3367 with a description of the relevant information included on the paper report.\n\n•\n\nWhen a paper disability report is received after the claim has been transferred to the Disability Determination Services (DDS) or Hearings Office (HO), compare it to what is already on EDCS, record any new or changed information using the EDCS Update-After-Transfer function, and destroy the paper form.\n\nNOTE: Do not collect or store worksheets from the Disability Starter Kits in the EF.\n\n2. \nReceiving a Paper Disability Report for EDCS Exclusion and Paper Cases\n\nIf a case is excluded from EDCS processing:\n\n•\n\nRetain the paper version of the disability report as the official record;\n\n•\n\nReview and complete the paper report;\n\n•\n\nObtain any incomplete or missing information or clarify as necessary; and\n\n•\n\nFile the paper report in the applicable section of the Modular Disability Folder (MDF).\n\nNOTE: For more information on exclusion cases, see Certified Electronic Folder (CEF) Exclusions - DI 81010.030.\n\n3. \nOther non-medical evidence\n\nWhen the claimant, representative, or third-party submits non-medical evidence take the following action:\n\n•\n\nAnnotate non-medical evidence on the SSA Mainframe system whenever possible (See Electronic Evidence Documentation and Retention - GN 00301.286A.2.).\n\n•\n\nWhen non-medical evidence must be stored in the disability folder, create a barcode and fax the document into the EF.\n\nREMINDER: As a general rule, if a document is signed, a signature is required, and it cannot be recorded using attestation, the original document should be faxed into eView. Also fax all Workers’ Compensation/Public Disability Benefits (WC/PDB) proofs for EDCS claims into eView.\n\nC. \nPost-entitlement (PE) material\n1. \nDetermine whether the documents need to be stored in the claims file\n•\n\nIf possible, record the evidence in MCS, RPOC or CCE Report of Contact page. Refer to What Information is Needed on EVID screen and CCE Report of Contact page in PE Situations to Identify the Type of Evidence Submitted - GN 00301.288.\n\n•\n\nMost folder documentation can be summarized on the EVID screen or CCE Report of Contact page.\n\nSome documents cannot be summarized and must be faxed into eView. To determine whether the document needs to be stored in the claims folder follow Electronic Evidence Documentation and Retention - GN 00301.286. As a general rule, if a document is signed, a signature is required, and it cannot be recorded using attestation, the original document should be faxed into eView. Also fax all WC/PDB (Workers Compensation/Public Disability Benefits) proofs for EDCS claims into eView.\n\nExamples include:\n\n–\n\nSigned Employer Report of Monthly Earnings (SSA-725s),\n\n–\n\nRepresentative appointment and fee documents,\n\n–\n\nSubsidy questionnaires,\n\n–\n\nCourt decisions,\n\n–\n\nCessation or Continuance of Disability or Blindness Determination and Transmittal for work CDRs (SSA 832/833s) and SSA-725.\n\n•\n\nPost entitlement material pertaining to non-disabled auxiliary beneficiaries entitled on the disabled Number Holder’s (NH) claim should also be stored in eView under the NH’s SSN. If the auxiliary is disabled i.e., CDB, DWB all post entitlement material will be stored in eView using the beneficiary’s BOAN.\n\n•\n\nTrailer Mail – follow Processing Trailer Material for CEF Cases - DI 81020.140. Trailer material must not be routed to the PC as was done in the former paper folder environment.\n\n2. \nTo store a document for an EDCS case in eView:\n•\n\nCreate a barcoded cover sheet, in EDCS or eView, for the document per Faxing Documents into the CEF - DI 81010.090.\n\n•\n\nSelect the appropriate document type for the form/document that is being added to eView. If the document is not on the list, use the generic document type for the section:\n\nIf the document should be filed in:\tUse Document Type:\n\n\nA section -- Yellow Front\n\n\t\n\n7010 - Misc Payment Documents\n\n\n\n\nB section -- Red\n\n\t\n\n7011- Misc Jurisdictional Documents/Notices\n\n\n\n\nC section -- Green\n\n\t\n\n7012 - Misc Current Development/Temporary\n\n\n\n\nD section -- Orange\n\n\t\n\n7013 - Misc Non Disability Development\n\n\n\n\nE section -- Blue\n\n\t\n\n7014 - Misc Disability Development\n\n\n\n\nF section – Yellow Back\n\n\t\n\n7015 - Misc Medical Records\n\n•\n\nFax the document to the appropriate Regional DMA fax number per Faxing Documents into the CEF Using Barcodes - DI81010.090. (See Storing Non-Medical Evidence in the EF - DI 81010.135C.3., for important information about documents that require Program Center action.)\n\n•\n\nAccess eView, and open the document to verify that all pages of the document were successfully faxed into eView.\n\n•\n\nIf the image does not appear, follow local procedures for reporting problems when faxed documents are not immediately available in eView.\n\n•\n\nWhen the document has been successfully added to eView, destroy the paper document, even if it is signed. Keep in mind that any original documents should be returned to the claimant/beneficiary.\n\n3. \nIf action is required in the PC the following is needed in addition to faxing into eView:\n•\n\nUse the SSA-409 (Post Adjudicative Routing) to notify the PC of the action to be taken. Clearly identify the actionable material so it can be assigned an appropriate TOEL.\n\n•\n\nAnnotate the SSA-409 with a remark indicating the material has been faxed to the designated section in eView.\n\n•\n\nFax the SSA-409 to the PC’s Paperless Processing Center System (PPC) using the Paperless fax number.\n\nPC fax numbers are available here.\n\n•\n\nFax the document into the appropriate section using the appropriate Regional DMA fax number. (See Faxing Documents into the CEF Using Barcodes - DI 81010.090 for a list of Regional DMA fax numbers).\n\nIMPORTANT NOTE: eView will not alert the PC to take an action on the document. This is why you must also fax the SSA-409 to the PC’s Paperless fax number.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0481010135\n\t\nDI 81010.135 - Storing Non-Medical Evidence in the Electronic Folder (EF) - 10/17/2023\nBatch run: 09/18/2025\nRev:10/17/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
    "source_visible_text_sha256": "e58fbb11401ac2449de2559a1df0edef5d4d48c0d9e5162956aa83ac2fea2b3b",
    "source_peer_sha256": "1960f9d914592149f9f7f33fe4e9827a425452d2ec2ad004bde5d8cb6b6a5e0c",
    "qualifications": [
      "Do not collect or store Disability Starter Kit worksheets in the EF.",
      "The separate after-transfer instruction requires comparison and recording new/changed information through EDCS Update-After-Transfer; this before-transfer branch does not invoke UAT.",
      "Paper EDCS-exclusion cases retain the paper official record under B.2; they are not covered by this EDCS branch.",
      "Original DI81020.055 source/provenance/qualifications remain unchanged; no new source-status approval for that source.",
      "No new entity IDs, customer duties, automatic entry, handoff completion, rejoin or processing-time promise."
    ],
    "source_capture_sha256": "2d53d06b801241208407cb568b117922fca2576ac47b97e91f01ef0b0fc47dd8"
  },
  "cpas_bundle_certificate1_selected": {
    "schema": "securitystat.selected-cpas-bundle-source/1",
    "source_code": "DI11005.017",
    "retained_primary_text": "Effective Dates: 10/21/2026 - Present\nPrevious | Next\n\nTN 141 (10-26)\n\nDI 11005.017 Commercial Product Alternative Signature Process for Certain Forms and Writings\nA. \nPolicy - Commercial product alternative signature(s) (CPAS)\n\nIndividuals may use a commercial software product (commercial product) to affix their signatures to the forms or writings listed in this section. In this section, these signatures are referred to as CPAS.\n\nNOTE: Individuals may also use other signature and submission methods permitted by current agency policy.\n\nAccept the CPAS on any of the forms and writings listed in this section if it meets the criteria described in this section.\n\nB. \nApproved forms and writings and controlling date for CPAS\n1. \nForms and writings approved for CPAS process\n\nThe CPAS process is used only with the following agency forms and writings (collectively referred to in this section as forms):\n\n•\n\nSSA-1696 Claimants Appointment of a Representative\n\n•\n\nSSA-1693 Fee Agreement for Representation Before the Social Security Administration, and other written fee agreements\n\n•\n\nSSA-16 Application for Disability Insurance Benefits (DIB). This includes the online version sent to the claimant with the SSA-L2 cover letter after a third party completes and submits the DIB/SSI internet claim\n\n•\n\nSSA-8000 Application for Supplemental Security Income (SSI)\n\n•\n\nSSA-8001 Application for Supplemental Security Income (SSI) (Deferred or Abbreviated)\n\n•\n\nSSA-820 Work Activity Report - Self Employment\n\n•\n\nSSA-821 Work Activity Report - Employee\n\nIMPORTANT: Forms submitted through the e1696 and e1693 AdobeSign portals (SSA-1696 APP & SSA-1693 APP) or Upload Documents are not processed under this section because they are completed and submitted through the portal. Process these forms following the established procedure for each form.\n\n2. \nControlling date when using CPAS\na. \nForm(s) signed using CPAS submitted on or after January 18, 2025\n\nAccept the signature(s) on forms received on or after January 18, 2025 according to the instructions in this section.\n\nb. \nForm(s) submitted before January 18, 2025 and signed using CPAS\n•\n\nIf the individual's signature on a form was previously verified, no further action is necessary. Continue to process the form.\n\n•\n\nIf the individual's signature on the form was not previously verified, and it meets the CPAS criteria, accept the signature according to the instructions in this section.\n\n•\n\nIf a form was submitted but not processed (rare occurrence) before January 18, 2025, and the individual's signature that does not meet CPAS criteria, contact the Area Director for assistance on how to process the form.\n\nC. \nCPAS requirements\n1. \nCriteria\n\nIn this section, \"signatures\" refers to that of the appropriate signers. See chart in subsection D for more information about appropriate signers.\n\na. \n\nTo be acceptable, the commercial product must:\n\ni. Affix a signers name in the signature area of the form;\n\nii. Affix the date the form was signed in the signature area of the form or on an appended signature certificate page; and\n\niii. Affix the time the form was signed in the signature area of the form or on an appended signature certificate page.\n\nb. \n\nTo determine whether the signature is a valid CPAS, consider the following:\n\ni. Signature\n\nThe signature area includes the signature box and the space directly surrounding the signature and date boxes.\n\nThe signature must be in the signature area of the form. It cannot be appended on a separate signature certificate page.\n\nii. Date and time stamp\n\nThe date AND time of the signature must be included at the time of the submission. They may appear either in the signature area or on an appended signature certificate page submitted with the form.\n\niii. Appended signature certificate page\n\nIf the time or date is missing from the signature area of the form, an individual may include an appended signature certificate page to meet those CPAS requirements.\n\nIf the submission includes multiple forms that require an appended signature certificate page, the submitter must append a separate signature certificate page to each of these forms at the time of submission.\n\nDO NOT accept the signature certificate page if it is submitted separately or later.\n\nIf an appended signature certificate page is needed to meet CPAS requirements and it is not appended to the form at the time the form is submitted, REJECT the form.\n\nc. \n\nIf these criteria are met, accept the CPAS and process the form following the form's established procedure.\n\nd. \n\nIf the criteria are not met, do not process the form. Follow existing policy to dispose of the form, notify the submitter the form cannot be accepted, and explain why the criteria are not met. Follow existing procedures to obtain a policy-compliant signature.\n\nTo notify the submitter that the form cannot be accepted, the field office or payment center will send the following notice:\n\n[Submitter's Name]\n\n[Submitter's Address]\n\nWe cannot accept your form(s) because the signers signature on [*F1 or *F2] does not meet the commercial product alternative signature (CPAS) requirements described in DI 11005.017 Commercial Product Alternative Signature Process for Certain Forms and Writings. Specifically, your [*F3 or *F4 or *F5 or *F6].\n\nPlease resubmit [*F1 or *F2] ensuring that our signature requirements are met.\n\nREF C01\n\nREF167\n\nFill-ins:\n\n*F1: Form SSA-XXXX\n\n*F2: Your forms\n\n*F3: Form is not approved for commercial product alternative signature under DI 11005.017.\n\n*F4: Form is missing required information (i.e., date and/or time) and it is not accompanied by an appended signature certificate page that includes this information.\n\n*F5: Submission includes one or more forms that did not include all the required information (i.e., date and/or time) and each was not accompanied by an appended signature certificate page that included this information.\n\n*F6: Submission includes one or more forms that are missing the required information (i.e., date and/or time), and only includes one appended signature certificate page, thus disqualifying the entire submission from being accepted. Note that each form missing this information must be accompanied by an appended signature certificate page that contains this information.\n\n2. \nMethod(s) of submission\na. \n\nUse of a CPAS does not affect the method(s) by which the forms listed in this section must be submitted. Individuals may submit a CPAS-signed form using any method currently accepted for that form.\n\nb. \n\nDo not accept faxed submissions of forms SSA-16, SSA-8000, or SSA-8001 as valid applications, see GN 00204.001. However, a faxed benefit application form will establish a protective filing date as long as it meets the protective writing criteria outlined in GN 00204.010B. See GN 00204.010E (Establishing that any document that meets the GN 00204.010B criteria must be treated as a protective writing).\n\n3. \nProcessing forms\na. \n\nAfter verifying that the CPAS requirements are met, document the CPAS per the instructions in subsection E.\n\nb. \n\nProcess the form following established agency procedures for the specific form.\n\nc. \n\nIf an appended signature page is used to meet the CPAS requirements, ensure that the appended page remains with the form in the claim(s) folder.\n\n4. \nRecord-keeping requirements for submitters\na. \n\nIn this section, submitter means the individual who files any or all the forms listed in this section.\n\nb. \n\nThe submitter must ensure the commercial product used can generate an audit trail and must maintain a digital certificate that shows the following:\n\n•\n\nThe form was signed using a commercial product,\n\n•\n\nThe signature details, i.e., name of the person(s) who signed the form, date the form was signed, and time the form was signed,\n\n•\n\nThe email address(es) and IP address(es) associated with each signature,\n\n•\n\nWhether the form was changed after signature, and\n\n•\n\nAn identifier that connects the audit trail to the signed form to which it applies.\n\nIMPORTANT: Agency staff are not responsible for confirming that the commercial product used to sign the form can generate an audit trail with a digital certificate that meets these requirements. The audit trail with a digital certificate is different from an appended signature page containing the date and/or time used to complete the criteria to use CPAS.\n\nc. \n\nThe submitter must retain the audit trail with a digital certificate for at least three years from the date they submit the form to the agency and, if requested, they must show the unredacted digital certificate in its entirety. If the agency rejects or questions the signature, staff may ask the submitter for additional information (including information about the process used to obtain the signature).\n\nNOTE: Before referring an individual for a suspected issue (including fraud) related to CPAS, staff must request the original digital certificate from the submitter's audit trail as part of the required development of the case referral.\n\n5. \nBundled forms\n\nWhen multiple forms listed in this section are received together:\n\n•\n\nEach CPAS for each of the forms must meet the requirements in this section.\n\n•\n\nIf an appended signature certificate page is needed to meet the CPAS requirements for one or more forms in a bundle, each such form must include its own appended signature certificate page.\n\nIMPORTANT: DO NOT accept multiple forms bundled together with only one appended signature certificate page for the entire bundle if multiple forms in the bundle require an appended signature certificate page to meet the CPAS requirements. Each form must meet the CPAS or other agency signature requirements individually.\n\n6. \nSSA-827 forms submitted with CPAS\n\nSSA-827 forms submitted with a CPAS require attestation before they can be accepted. To obtain attestation follow applicable policy and procedure, see DI 11005.056D and DI 22501.007.\n\nD. \nDetermining if the CPAS meets the criteria\n\nAccept a CPAS and process the form if:\n\n1. \n\nThe form is listed in this section.\n\n2. \n\nThe signer(s) is an appropriate signer.\n\nNOTE: There is no requirement for all appropriate signers to use the same method to sign the same form. For example, if a claimant uses CPAS to sign a form, their representative(s) is not required to use CPAS to sign the same form. Representatives may sign the forms listed in this section using CPAS or other methods such as pen and ink or a rubber stamp, as per existing policy for paper submissions.\n\nThe following table sets out the appropriate signers for each form:\n\nForms' Required Signatures\n\nForm\n\n\t\n\nWho must sign\n\n\t\n\nCurrent instructions\n\n\n\n\nSSA-1696\n\n\t\n\nClaimant (or parent, legal guardian) and Representative\n\n\t\n\nGN 03910.040\n\n\n\n\nSSA-1693 and other written fee agreements\n\n\t\n\nClaimant and all representatives seeking a fee\n\n\t\n\nGN 03940.003\n\n\n\n\nSSA-16 (This includes the online version of the SSA-16 application sent to the claimant with the SSA-L2 cover letter after a third party completes and submits the DIB/SSI internet claim)\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-8000\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-8001\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-820\n\n\t\n\nClaimant, Beneficiary, or Representative Payee\n\n\t\n\nDI 10510.025\n\n\n\n\nSSA-821\n\n\t\n\nClaimant, Beneficiary, or Representative Payee\n\n\t\n\nDI 10505.035\n\n3. \n\nThe signature affixed by a commercial product is included in the signature area of the form.\n\n4. \n\nThe date and time stamps are either in the signature area of the form or on an appended signature certificate page submitted with each individual form.\n\nE. \nDocumentation for CPAS\n\nAfter confirming that the criteria in this section are met, take the following steps to document the CPAS:\n\nNOTE: These required coding steps in Registration, Appointment, and Services for Representatives (RASR) and DW01 are necessary to identify CPAS usage.\n\n1. \nForm SSA-1696\n\nProcess new notices of appointment in RASR per existing policy. If the form meets CPAS criteria, select the checkbox that reads, Select this box if the claimant signed with a Commercial Product Alternative Signature (CPAS) on the signature screen, see screenshot.\n\nNOTE: The CPAS box does not appear if the entry is an update to a previously processed appointment. Failure to code the CPAS in the first entry cannot be corrected in RASR. If CPAS was not coded in the first RASR entry, staff should annotate the DW01 screen. It is not necessary to annotate the DW01 screen if the CPAS is coded in RASR.\n\n2. \nForms SSA-1693, SSA-820, and SSA-821 (field office employees only)\n\nInput the current date as the receipt date.\n\n•\n\nFor initial claims, add the CPAS issue on the MCS DW01 screen and the Development Worksheet in CCE SSI.\n\n•\n\nIf a hearing office is unable to make the change in RASR, it will send an assistance request to a field office to complete the action.\n\n•\n\nFor post-entitlement cases, establish an SSA-5002 and store in the electronic folder associated with the claim.\n\n•\n\nFor paper folders, store in Evidence Portal.\n\n3. \nForms SSA-16, SSA-8000, and SSA-8001\n\nFollow the instructions in GN 00201.015.\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0411005017\n\t\nDI 11005.017 - Commercial Product Alternative Signature Process for Certain Forms and Writings - 10/21/2026\nBatch run: 10/21/2026\nRev:10/21/2026\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
    "retained_primary_sha256": "f09d9b552b77ea64fa299c5d1c66f9be8d3d2f1a6a460ca91f4cf287c658e50f",
    "selected_dated_scope": "Existing cpas source object revision2025-12-10 remains byteexact; this retained whole page displays2026-10-21. No global source freshness/status promotion; selected dated provenance only, peer must adjudicate.",
    "flow": {
      "schema": "securitystat.exception-flow/1",
      "record_id": "bundle-one-certificate",
      "full_route": "commercial-signature-defect/bundle-one-certificate",
      "entry_conditions": [
        "A bundle includes multiple forms listed in DI11005.017 B.1 received on or after January18,2025; this view does not decide actual receipt date or form eligibility.",
        "Multiple forms need an appended signature certificate because required date and/or time is absent from their signature areas.",
        "Forms completed and submitted through e1696/e1693 AdobeSign portals or Upload Documents follow their established portal/form procedures, not this CPAS branch.",
        "This selected illustration is not a determination that any form, signer, signature or submission is acceptable."
      ],
      "steps": [
        {
          "id": "bundle-one-certificate-append",
          "title": "Append each needed date/time page at submission",
          "kind": "you",
          "actor": "Submitter",
          "action": "For each form that needs an appended signature certificate page to supply its missing date and/or time, append that form's own page when submitting the form. One shared page for multiple forms needing one is not acceptable. A required page sent separately or later cannot cure that submission.",
          "conditions": [
            "A bundle includes multiple forms listed in DI11005.017 B.1 received on or after January18,2025; this view does not decide actual receipt date or form eligibility.",
            "Multiple forms need an appended signature certificate because required date and/or time is absent from their signature areas.",
            "Forms completed and submitted through e1696/e1693 AdobeSign portals or Upload Documents follow their established portal/form procedures, not this CPAS branch.",
            "This selected illustration is not a determination that any form, signer, signature or submission is acceptable."
          ],
          "source": "cpas",
          "section": "C.1.b.iii; C.5",
          "source_context_refs": [
            "DI11005.017:C"
          ],
          "qualifications": [
            "Every form and appropriate signer must independently meet all applicable signature requirements; selecting this route establishes no case facts.",
            "The signature must be in the form signature area, not on a certificate; required date AND time must be present at submission on the form or its appended page.",
            "An appended date/time signature page is distinct from the submitter audit-trail digital certificate; staff are not responsible for verifying product audit-trail capability under C.4.",
            "Historical pre-January18,2025 submission/verification/Area Director alternatives are outside this selected current-receipt illustration and remain separately qualified.",
            "No acceptance, rejoin, filing-date protection, completion time, agency disposition execution or native system identity is inferred."
          ],
          "next": "No successful correction or automatic return is established; source-specific alternatives remain conditional."
        },
        {
          "id": "bundle-one-certificate-evaluate",
          "title": "Evaluate each form independently",
          "kind": "ssa",
          "actor": "FO / payment-center staff",
          "action": "Check each form against the applicable approved-form, appropriate-signer and signature/name/date/time criteria. Do not accept multiple forms bundled with only one appended page when multiple forms require one; the C.1.d F6 notice explains that this disqualifies the entire submission from acceptance. A bundle does not merge each form's requirements.",
          "conditions": [
            "A bundle includes multiple forms listed in DI11005.017 B.1 received on or after January18,2025; this view does not decide actual receipt date or form eligibility.",
            "Multiple forms need an appended signature certificate because required date and/or time is absent from their signature areas.",
            "Forms completed and submitted through e1696/e1693 AdobeSign portals or Upload Documents follow their established portal/form procedures, not this CPAS branch.",
            "This selected illustration is not a determination that any form, signer, signature or submission is acceptable."
          ],
          "source": "cpas",
          "section": "B.1; C.1; C.5; D",
          "source_context_refs": [
            "DI11005.017:B",
            "DI11005.017:C",
            "DI11005.017:D"
          ],
          "qualifications": [
            "Every form and appropriate signer must independently meet all applicable signature requirements; selecting this route establishes no case facts.",
            "The signature must be in the form signature area, not on a certificate; required date AND time must be present at submission on the form or its appended page.",
            "An appended date/time signature page is distinct from the submitter audit-trail digital certificate; staff are not responsible for verifying product audit-trail capability under C.4.",
            "Historical pre-January18,2025 submission/verification/Area Director alternatives are outside this selected current-receipt illustration and remain separately qualified.",
            "No acceptance, rejoin, filing-date protection, completion time, agency disposition execution or native system identity is inferred."
          ],
          "next": "No successful correction or automatic return is established; source-specific alternatives remain conditional."
        },
        {
          "id": "bundle-one-certificate-criteria-met",
          "title": "If all applicable criteria are met, use form-specific processing",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "Accept the CPAS only if the criteria are met. Document it under the applicable subsection E instructions and process the form following its established procedure. If an appended page is used to meet CPAS requirements, ensure it remains with the form in the claims folder. This card does not supply or complete linked form-specific procedures.",
          "conditions": [
            "A bundle includes multiple forms listed in DI11005.017 B.1 received on or after January18,2025; this view does not decide actual receipt date or form eligibility.",
            "Multiple forms need an appended signature certificate because required date and/or time is absent from their signature areas.",
            "Forms completed and submitted through e1696/e1693 AdobeSign portals or Upload Documents follow their established portal/form procedures, not this CPAS branch.",
            "This selected illustration is not a determination that any form, signer, signature or submission is acceptable.",
            "The form independently meets all applicable CPAS and signer criteria; not the defective shared-certificate alternative."
          ],
          "source": "cpas",
          "section": "C.1.c; C.3; E",
          "source_context_refs": [
            "DI11005.017:C",
            "DI11005.017:E"
          ],
          "qualifications": [
            "Every form and appropriate signer must independently meet all applicable signature requirements; selecting this route establishes no case facts.",
            "The signature must be in the form signature area, not on a certificate; required date AND time must be present at submission on the form or its appended page.",
            "An appended date/time signature page is distinct from the submitter audit-trail digital certificate; staff are not responsible for verifying product audit-trail capability under C.4.",
            "Historical pre-January18,2025 submission/verification/Area Director alternatives are outside this selected current-receipt illustration and remain separately qualified.",
            "No acceptance, rejoin, filing-date protection, completion time, agency disposition execution or native system identity is inferred."
          ],
          "next": "No successful correction or automatic return is established; source-specific alternatives remain conditional.",
          "alternative_group": "source-result"
        },
        {
          "id": "bundle-one-certificate-criteria-not-met",
          "title": "If criteria fail, do not process and notify the submitter",
          "kind": "ssa",
          "actor": "FO / payment-center staff",
          "action": "Do not process the deficient form. Follow existing policy to dispose of it, notify the submitter it cannot be accepted and explain which CPAS criteria are not met. Use the C.1.d notice with the applicable multiple-form fill-ins; request resubmission meeting signature requirements and follow existing procedures to obtain a policy-compliant signature. Do not treat a separately or later supplied page as acceptance of the rejected submission.",
          "conditions": [
            "A bundle includes multiple forms listed in DI11005.017 B.1 received on or after January18,2025; this view does not decide actual receipt date or form eligibility.",
            "Multiple forms need an appended signature certificate because required date and/or time is absent from their signature areas.",
            "Forms completed and submitted through e1696/e1693 AdobeSign portals or Upload Documents follow their established portal/form procedures, not this CPAS branch.",
            "This selected illustration is not a determination that any form, signer, signature or submission is acceptable.",
            "Applicable CPAS criteria are not met, including multiple needed certificates replaced by one shared page."
          ],
          "source": "cpas",
          "section": "C.1.b.iii; C.1.d F5–F6; C.5",
          "source_context_refs": [
            "DI11005.017:C"
          ],
          "qualifications": [
            "Every form and appropriate signer must independently meet all applicable signature requirements; selecting this route establishes no case facts.",
            "The signature must be in the form signature area, not on a certificate; required date AND time must be present at submission on the form or its appended page.",
            "An appended date/time signature page is distinct from the submitter audit-trail digital certificate; staff are not responsible for verifying product audit-trail capability under C.4.",
            "Historical pre-January18,2025 submission/verification/Area Director alternatives are outside this selected current-receipt illustration and remain separately qualified.",
            "No acceptance, rejoin, filing-date protection, completion time, agency disposition execution or native system identity is inferred."
          ],
          "next": "No successful correction or automatic return is established; source-specific alternatives remain conditional.",
          "alternative_group": "source-result"
        }
      ],
      "alternative_groups": [
        {
          "id": "source-result",
          "label": "Apply the outcome supported by the actual form criteria",
          "logic": "source_conditions_determine_branch",
          "note": "Acceptance and rejection cards are source-conditioned alternatives, not sequential instructions to accept and reject the same form."
        }
      ],
      "rejoin": {
        "status": "unknown",
        "automatic_transition": false,
        "unknowns": [
          "Form-specific disposal/signature acquisition and later processing are linked-policy dependencies, not executed here.",
          "No automatic acceptance, completion date, filing/protective-writing determination or return to usual path is established."
        ]
      }
    },
    "source_contexts": {
      "DI11005.017:B": {
        "start": 667,
        "end": 2666,
        "coordinate_system": "Unicode codepoints of exact retained UTF8 decoded page",
        "text": "B. \nApproved forms and writings and controlling date for CPAS\n1. \nForms and writings approved for CPAS process\n\nThe CPAS process is used only with the following agency forms and writings (collectively referred to in this section as forms):\n\n•\n\nSSA-1696 Claimants Appointment of a Representative\n\n•\n\nSSA-1693 Fee Agreement for Representation Before the Social Security Administration, and other written fee agreements\n\n•\n\nSSA-16 Application for Disability Insurance Benefits (DIB). This includes the online version sent to the claimant with the SSA-L2 cover letter after a third party completes and submits the DIB/SSI internet claim\n\n•\n\nSSA-8000 Application for Supplemental Security Income (SSI)\n\n•\n\nSSA-8001 Application for Supplemental Security Income (SSI) (Deferred or Abbreviated)\n\n•\n\nSSA-820 Work Activity Report - Self Employment\n\n•\n\nSSA-821 Work Activity Report - Employee\n\nIMPORTANT: Forms submitted through the e1696 and e1693 AdobeSign portals (SSA-1696 APP & SSA-1693 APP) or Upload Documents are not processed under this section because they are completed and submitted through the portal. Process these forms following the established procedure for each form.\n\n2. \nControlling date when using CPAS\na. \nForm(s) signed using CPAS submitted on or after January 18, 2025\n\nAccept the signature(s) on forms received on or after January 18, 2025 according to the instructions in this section.\n\nb. \nForm(s) submitted before January 18, 2025 and signed using CPAS\n•\n\nIf the individual's signature on a form was previously verified, no further action is necessary. Continue to process the form.\n\n•\n\nIf the individual's signature on the form was not previously verified, and it meets the CPAS criteria, accept the signature according to the instructions in this section.\n\n•\n\nIf a form was submitted but not processed (rare occurrence) before January 18, 2025, and the individual's signature that does not meet CPAS criteria, contact the Area Director for assistance on how to process the form.\n\n",
        "sha256": "eb84fed936c843b38e0ad30b517314e2949611b149beff846eb94cedbf7a4876"
      },
      "DI11005.017:C": {
        "start": 2666,
        "end": 9931,
        "coordinate_system": "Unicode codepoints of exact retained UTF8 decoded page",
        "text": "C. \nCPAS requirements\n1. \nCriteria\n\nIn this section, \"signatures\" refers to that of the appropriate signers. See chart in subsection D for more information about appropriate signers.\n\na. \n\nTo be acceptable, the commercial product must:\n\ni. Affix a signers name in the signature area of the form;\n\nii. Affix the date the form was signed in the signature area of the form or on an appended signature certificate page; and\n\niii. Affix the time the form was signed in the signature area of the form or on an appended signature certificate page.\n\nb. \n\nTo determine whether the signature is a valid CPAS, consider the following:\n\ni. Signature\n\nThe signature area includes the signature box and the space directly surrounding the signature and date boxes.\n\nThe signature must be in the signature area of the form. It cannot be appended on a separate signature certificate page.\n\nii. Date and time stamp\n\nThe date AND time of the signature must be included at the time of the submission. They may appear either in the signature area or on an appended signature certificate page submitted with the form.\n\niii. Appended signature certificate page\n\nIf the time or date is missing from the signature area of the form, an individual may include an appended signature certificate page to meet those CPAS requirements.\n\nIf the submission includes multiple forms that require an appended signature certificate page, the submitter must append a separate signature certificate page to each of these forms at the time of submission.\n\nDO NOT accept the signature certificate page if it is submitted separately or later.\n\nIf an appended signature certificate page is needed to meet CPAS requirements and it is not appended to the form at the time the form is submitted, REJECT the form.\n\nc. \n\nIf these criteria are met, accept the CPAS and process the form following the form's established procedure.\n\nd. \n\nIf the criteria are not met, do not process the form. Follow existing policy to dispose of the form, notify the submitter the form cannot be accepted, and explain why the criteria are not met. Follow existing procedures to obtain a policy-compliant signature.\n\nTo notify the submitter that the form cannot be accepted, the field office or payment center will send the following notice:\n\n[Submitter's Name]\n\n[Submitter's Address]\n\nWe cannot accept your form(s) because the signers signature on [*F1 or *F2] does not meet the commercial product alternative signature (CPAS) requirements described in DI 11005.017 Commercial Product Alternative Signature Process for Certain Forms and Writings. Specifically, your [*F3 or *F4 or *F5 or *F6].\n\nPlease resubmit [*F1 or *F2] ensuring that our signature requirements are met.\n\nREF C01\n\nREF167\n\nFill-ins:\n\n*F1: Form SSA-XXXX\n\n*F2: Your forms\n\n*F3: Form is not approved for commercial product alternative signature under DI 11005.017.\n\n*F4: Form is missing required information (i.e., date and/or time) and it is not accompanied by an appended signature certificate page that includes this information.\n\n*F5: Submission includes one or more forms that did not include all the required information (i.e., date and/or time) and each was not accompanied by an appended signature certificate page that included this information.\n\n*F6: Submission includes one or more forms that are missing the required information (i.e., date and/or time), and only includes one appended signature certificate page, thus disqualifying the entire submission from being accepted. Note that each form missing this information must be accompanied by an appended signature certificate page that contains this information.\n\n2. \nMethod(s) of submission\na. \n\nUse of a CPAS does not affect the method(s) by which the forms listed in this section must be submitted. Individuals may submit a CPAS-signed form using any method currently accepted for that form.\n\nb. \n\nDo not accept faxed submissions of forms SSA-16, SSA-8000, or SSA-8001 as valid applications, see GN 00204.001. However, a faxed benefit application form will establish a protective filing date as long as it meets the protective writing criteria outlined in GN 00204.010B. See GN 00204.010E (Establishing that any document that meets the GN 00204.010B criteria must be treated as a protective writing).\n\n3. \nProcessing forms\na. \n\nAfter verifying that the CPAS requirements are met, document the CPAS per the instructions in subsection E.\n\nb. \n\nProcess the form following established agency procedures for the specific form.\n\nc. \n\nIf an appended signature page is used to meet the CPAS requirements, ensure that the appended page remains with the form in the claim(s) folder.\n\n4. \nRecord-keeping requirements for submitters\na. \n\nIn this section, submitter means the individual who files any or all the forms listed in this section.\n\nb. \n\nThe submitter must ensure the commercial product used can generate an audit trail and must maintain a digital certificate that shows the following:\n\n•\n\nThe form was signed using a commercial product,\n\n•\n\nThe signature details, i.e., name of the person(s) who signed the form, date the form was signed, and time the form was signed,\n\n•\n\nThe email address(es) and IP address(es) associated with each signature,\n\n•\n\nWhether the form was changed after signature, and\n\n•\n\nAn identifier that connects the audit trail to the signed form to which it applies.\n\nIMPORTANT: Agency staff are not responsible for confirming that the commercial product used to sign the form can generate an audit trail with a digital certificate that meets these requirements. The audit trail with a digital certificate is different from an appended signature page containing the date and/or time used to complete the criteria to use CPAS.\n\nc. \n\nThe submitter must retain the audit trail with a digital certificate for at least three years from the date they submit the form to the agency and, if requested, they must show the unredacted digital certificate in its entirety. If the agency rejects or questions the signature, staff may ask the submitter for additional information (including information about the process used to obtain the signature).\n\nNOTE: Before referring an individual for a suspected issue (including fraud) related to CPAS, staff must request the original digital certificate from the submitter's audit trail as part of the required development of the case referral.\n\n5. \nBundled forms\n\nWhen multiple forms listed in this section are received together:\n\n•\n\nEach CPAS for each of the forms must meet the requirements in this section.\n\n•\n\nIf an appended signature certificate page is needed to meet the CPAS requirements for one or more forms in a bundle, each such form must include its own appended signature certificate page.\n\nIMPORTANT: DO NOT accept multiple forms bundled together with only one appended signature certificate page for the entire bundle if multiple forms in the bundle require an appended signature certificate page to meet the CPAS requirements. Each form must meet the CPAS or other agency signature requirements individually.\n\n6. \nSSA-827 forms submitted with CPAS\n\nSSA-827 forms submitted with a CPAS require attestation before they can be accepted. To obtain attestation follow applicable policy and procedure, see DI 11005.056D and DI 22501.007.\n\n",
        "sha256": "3a8540850c59c58fc959d400b342e7aba36669d0c83b1fcb34fff34fed877816"
      },
      "DI11005.017:D": {
        "start": 9931,
        "end": 11645,
        "coordinate_system": "Unicode codepoints of exact retained UTF8 decoded page",
        "text": "D. \nDetermining if the CPAS meets the criteria\n\nAccept a CPAS and process the form if:\n\n1. \n\nThe form is listed in this section.\n\n2. \n\nThe signer(s) is an appropriate signer.\n\nNOTE: There is no requirement for all appropriate signers to use the same method to sign the same form. For example, if a claimant uses CPAS to sign a form, their representative(s) is not required to use CPAS to sign the same form. Representatives may sign the forms listed in this section using CPAS or other methods such as pen and ink or a rubber stamp, as per existing policy for paper submissions.\n\nThe following table sets out the appropriate signers for each form:\n\nForms' Required Signatures\n\nForm\n\n\t\n\nWho must sign\n\n\t\n\nCurrent instructions\n\n\n\n\nSSA-1696\n\n\t\n\nClaimant (or parent, legal guardian) and Representative\n\n\t\n\nGN 03910.040\n\n\n\n\nSSA-1693 and other written fee agreements\n\n\t\n\nClaimant and all representatives seeking a fee\n\n\t\n\nGN 03940.003\n\n\n\n\nSSA-16 (This includes the online version of the SSA-16 application sent to the claimant with the SSA-L2 cover letter after a third party completes and submits the DIB/SSI internet claim)\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-8000\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-8001\n\n\t\n\nClaimant or Proper Applicant\n\n\t\n\nGN 00204.003\n\n\n\n\nSSA-820\n\n\t\n\nClaimant, Beneficiary, or Representative Payee\n\n\t\n\nDI 10510.025\n\n\n\n\nSSA-821\n\n\t\n\nClaimant, Beneficiary, or Representative Payee\n\n\t\n\nDI 10505.035\n\n3. \n\nThe signature affixed by a commercial product is included in the signature area of the form.\n\n4. \n\nThe date and time stamps are either in the signature area of the form or on an appended signature certificate page submitted with each individual form.\n\n",
        "sha256": "893ac1358693df2b9b484b762be298847fd362bdc3d72c8ea55f8926c194b248"
      },
      "DI11005.017:E": {
        "start": 11645,
        "end": 13168,
        "coordinate_system": "Unicode codepoints of exact retained UTF8 decoded page",
        "text": "E. \nDocumentation for CPAS\n\nAfter confirming that the criteria in this section are met, take the following steps to document the CPAS:\n\nNOTE: These required coding steps in Registration, Appointment, and Services for Representatives (RASR) and DW01 are necessary to identify CPAS usage.\n\n1. \nForm SSA-1696\n\nProcess new notices of appointment in RASR per existing policy. If the form meets CPAS criteria, select the checkbox that reads, Select this box if the claimant signed with a Commercial Product Alternative Signature (CPAS) on the signature screen, see screenshot.\n\nNOTE: The CPAS box does not appear if the entry is an update to a previously processed appointment. Failure to code the CPAS in the first entry cannot be corrected in RASR. If CPAS was not coded in the first RASR entry, staff should annotate the DW01 screen. It is not necessary to annotate the DW01 screen if the CPAS is coded in RASR.\n\n2. \nForms SSA-1693, SSA-820, and SSA-821 (field office employees only)\n\nInput the current date as the receipt date.\n\n•\n\nFor initial claims, add the CPAS issue on the MCS DW01 screen and the Development Worksheet in CCE SSI.\n\n•\n\nIf a hearing office is unable to make the change in RASR, it will send an assistance request to a field office to complete the action.\n\n•\n\nFor post-entitlement cases, establish an SSA-5002 and store in the electronic folder associated with the claim.\n\n•\n\nFor paper folders, store in Evidence Portal.\n\n3. \nForms SSA-16, SSA-8000, and SSA-8001\n\nFollow the instructions in GN 00201.015.\n\n",
        "sha256": "a8555f82d1ac2744016e5f07f405fd131baaddadd38561c6322872d188779d43"
      }
    },
    "exact_support_spans": [
      {
        "start": 3971,
        "end": 4179,
        "text": "If the submission includes multiple forms that require an appended signature certificate page, the submitter must append a separate signature certificate page to each of these forms at the time of submission.",
        "sha256": "b91385c3830ece4e33a0ffe7f16305929673917e0cd18a78686299c090c364fa"
      },
      {
        "start": 4181,
        "end": 4265,
        "text": "DO NOT accept the signature certificate page if it is submitted separately or later.",
        "sha256": "4c7762b455cdff58f9ab2049035e7f7f9b7429d80b0ceca85efbdc0432931136"
      },
      {
        "start": 9115,
        "end": 9190,
        "text": "Each CPAS for each of the forms must meet the requirements in this section.",
        "sha256": "5228068e5d93642757a4f252e37f7b3981cccfe214366a7d57c2235f04477f71"
      },
      {
        "start": 9195,
        "end": 9384,
        "text": "If an appended signature certificate page is needed to meet the CPAS requirements for one or more forms in a bundle, each such form must include its own appended signature certificate page.",
        "sha256": "bbad67a555a395b028e19a0fff8e93767192ab7180520fb754ccc5d1ce4e9aa1"
      },
      {
        "start": 4438,
        "end": 4545,
        "text": "If these criteria are met, accept the CPAS and process the form following the form's established procedure.",
        "sha256": "7636a0cc07da76d357f7f2880407ae324c49bb9337d42d342474d62aa749e09a"
      },
      {
        "start": 4552,
        "end": 4811,
        "text": "If the criteria are not met, do not process the form. Follow existing policy to dispose of the form, notify the submitter the form cannot be accepted, and explain why the criteria are not met. Follow existing procedures to obtain a policy-compliant signature.",
        "sha256": "184e56c1e55198f786f45a36ada956152d1d88cba1adfafa4cb366128340c9ae"
      }
    ],
    "original_record": {
      "id": "bundle-one-certificate",
      "title": "A bundle needs more than one certificate",
      "when": "Several forms lack their own date/time information.",
      "you": "Attach a separate required certificate to each form when submitting.",
      "ssa": "Evaluate each form individually; reject reliance on one shared certificate for multiple forms needing one.",
      "route": "FO / payment-center signature review",
      "next": "A bundle does not merge separate signature requirements.",
      "source": "cpas",
      "section": "C.1.b.iii; C.5",
      "timing": "No completion duration specified",
      "review_status": "Selected branch checked; detailed exceptions remain"
    },
    "original_source_object": {
      "code": "DI 11005.017",
      "title": "Commercial Product Alternative Signature Process for Certain Forms and Writings",
      "url": "https://secure.ssa.gov/poms.nsf/lnx/0411005017",
      "revision": "2025-12-10",
      "kind": "POMS",
      "checked_on": "2026-10-16",
      "verification_scope": "Selected cover-notice and CPAS defect-handling claims checked; no signature execution or personal filing-date determination."
    },
    "source_acceptance_peer": "a57d0afd08c71347a75a2b277ada76e0a9026b34063a9da935d9da28b3a81c9b",
    "no_individual_case_or_global_freshness_adoption": true
  },
  "child_adoption2_selected": {
    "schema": "securitystat.selected-child-adoption-source/1",
    "source_code": "RS00203.035",
    "retained_primary_text": "Skip to content\nSocial Security\nSEARCH\nMENU\nLANGUAGES\nSIGN IN / UP\nProgram Operations Manual System (POMS)\nEffective Dates: 09/06/2023 - Present\nPrevious | Next\n\nTN 47 (04-26)\n\nRS 00203.035 Child's Benefits Termination of Entitlement\nA. \nGeneral information on termination\n\nA child's entitlement ends with the month before the month in which any of the following occurs:\n\n1. \nDeath\n\nThe child dies.\n\n2. \nAttainment of age 18\n\nThe child attains age 18 and is not disabled or a full-time student. A child born on the first day of the month attains age 18 in the previous month based on Agency policy concerning attainment of age.\n\nNOTE: If the child is under a disability, see RS 00203.035B.1. If the child is a full-time student, see RS 00203.035B.2.\n\n3. \nMarriage\n\nThe child marries, with these exceptions:\n\na. \n\nEntitlement does not end if the child is a child disability beneficiary ( CDB ) and the marriage is to a Social Security beneficiary other than:\n\n•\n\na child beneficiary under age 18, or\n\n•\n\na child beneficiary age 18 or 19 entitled because he or she is a full-time student.\n\nAn individual receiving Supplemental Security Income benefits only is not included in the definition of a “Social Security beneficiary.”\n\nb. \n\nAlthough a putative marriage in Louisiana terminates a child's entitlement, a putative marriage in any other state that recognizes such marriages does not. Under the laws of some states, a party to a void marriage may acquire inheritance rights as a spouse. This relationship is a putative marriage. The essential basis of a putative marriage is a good faith belief in the existence of a valid marriage at its inception and a continuous good faith belief (in a life case) or good faith until the worker dies (in a death case). (For information on putative marriages, see GN 00305.085.)\n\nNOTE: For instructions about same-sex marriage, see GN 00210.000.\n\nNOTE: Benefits to a CDB no longer terminate because the benefits of their spouse who is a CDB or disability beneficiary terminate. A CDB whose benefits terminate in or after July 1969 because their spouse's CDB benefits terminated for a reason other than death may have their benefits reinstated.\n\n4. \nNH no longer entitled to disability insurance benefits\n\nEntitlement ends the first month the NH is no longer entitled to a disability insurance benefit, unless the entitlement ended because of their death or entitlement to retirement insurance benefits.\n\nIf the NH is at full retirement age (FRA) when a subsequent disability determination shows that their disability ceased prior to the Disability Insurance Benefits (DIB) to Retirement Insurance Benefits (RIB) conversion, see \"NOTE\" in GN 00201.005B.1.a.\n\n \n\nB. \nSpecial rules\n\nIn addition to the situations listed in child’s benefits termination of entitlement, RS 00203.035A, the following terminating events apply:\n\n1. \nChild disability beneficiary (CDB)\n\nThe entitlement of a CDB ends with the second month following the month he or she ceases to be under a disability, unless in such month he or she is under age 19 and a full-time student.\n\nNOTE: The trial work provision discussed in DI 13010.035 applies to a CDB.\n\n2. \nStudent\n\nThe entitlement of a full-time student age 18-19 ends whenever the following occurs first, unless at such time he or she is entitled to benefits as a CDB:\n\na. \n\nThe month before the month he or she attains age 19, or deemed to have attained age 19.\n\nb. \n\nThe last month he or she is a full-time student. (For information on when student benefits terminate, see RS 00205.325B.)\n\nFor more information on the point at which a particular age is attained, see GN 00302.400.\n\n3. \nLegally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \nStep-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \nPolicy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0300203035\n\t\nRS 00203.035 - Child's Benefits Termination of Entitlement - 09/06/2023\nBatch run: 09/10/2026\nRev:09/06/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
    "retained_primary_sha256": "ebea37b296a71dfba27c9d8e3b7d52a77bcbed616927c0656832684d4a5fb5ad",
    "flows": {
      "adopted-stepchild": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "adopted-stepchild",
        "full_route": "divorce-family-record-actions/adopted-stepchild",
        "entry_conditions": [
          "A divorce affects a child treated as the NH’s stepchild.",
          "The NH has legally adopted the child; an allegation alone does not establish this condition."
        ],
        "steps": [
          {
            "id": "adopted-stepchild-relationship-review",
            "title": "Consider the legally adopted-child relationship",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "When the NH has legally adopted the child, consider the possibility of entitlement as an adopted child instead of treating stepchild divorce termination alone as the final entitlement answer. The source says entitlement may be possible; this card does not determine that the child meets adopted-child entitlement requirements.",
            "conditions": [
              "A divorce affects a child treated as the NH’s stepchild.",
              "The NH has legally adopted the child; an allegation alone does not establish this condition."
            ],
            "source": "childtermination",
            "section": "B.4.a; B.3",
            "source_context_refs": [
              "RS00203.035:B4",
              "RS00203.035:B3"
            ],
            "qualifications": [
              "Selection does not establish a legal adoption, current entitlement or a personal benefit decision.",
              "Other terminating events in RS00203.035 A and B remain applicable; this is not a promise that payments continue.",
              "No new customer evidence duty, system input, completion deadline or automatic rejoin is derived from this page.",
              "The stepchild divorce rule applies when the divorce becomes final in or after July1996: entitlement terminates the following month and the divorce month is the last payable month on the NH’s record. A divorce final before July1996 does not terminate stepchild entitlement under this rule.",
              "If the NH and parent remarry, stepchild re-entitlement requires a new one-year relationship duration and one-half support-met requirement; this is a separate conditional rule, not an instruction to remarry.",
              "Annulment of the adoption is distinct: entitlement based on legal adoption terminates in the month the annulment becomes effective. Marriage-annulment rules in B.4.b are separately retained in full context.",
              "The linked post-entitlement processing and adopted-child eligibility procedures are not implemented by this card."
            ],
            "next": "Relationship-specific development and any later entitlement decision remain outside this selected card."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "This page does not establish the case-specific insertion point, evidence sufficiency, component handoff or successful return to the usual path.",
            "Linked eligibility and post-entitlement procedures, individual dates and actual payment action remain unresolved here."
          ]
        }
      },
      "adoption-alone": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "adoption-alone",
        "full_route": "divorce-family-record-actions/adoption-alone",
        "entry_conditions": [
          "The child is already entitled to child’s benefits.",
          "The event is an adoption, not annulment of the adoption."
        ],
        "steps": [
          {
            "id": "adoption-alone-relationship-review",
            "title": "Do not terminate solely because an entitled child is adopted",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not treat adoption itself as terminating the benefits of a child already entitled. Evaluate any separate terminating event under its applicable rule; this card neither grants entitlement nor resolves an annulment of an adoption.",
            "conditions": [
              "The child is already entitled to child’s benefits.",
              "The event is an adoption, not annulment of the adoption."
            ],
            "source": "childtermination",
            "section": "C; B.3",
            "source_context_refs": [
              "RS00203.035:C",
              "RS00203.035:B3"
            ],
            "qualifications": [
              "Selection does not establish a legal adoption, current entitlement or a personal benefit decision.",
              "Other terminating events in RS00203.035 A and B remain applicable; this is not a promise that payments continue.",
              "No new customer evidence duty, system input, completion deadline or automatic rejoin is derived from this page.",
              "Before November1972, adoption did terminate benefits with certain exceptions. A child whose entitlement terminated because of adoption may be re-entitled beginning November1972 based on an application filed after October30,1972, only if all other re-entitlement requirements are met.",
              "If entitlement is based on legal adoption and the adoption is annulled, B.3 terminates that entitlement in the month the annulment becomes effective; this differs from adoption as a non-termination event."
            ],
            "next": "Relationship-specific development and any later entitlement decision remain outside this selected card."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "This page does not establish the case-specific insertion point, evidence sufficiency, component handoff or successful return to the usual path.",
            "Linked eligibility and post-entitlement procedures, individual dates and actual payment action remain unresolved here."
          ]
        }
      }
    },
    "source_contexts": [
      {
        "id": "RS00203.035:B3",
        "start_codepoint": 3650,
        "end_codepoint": 3873,
        "text": "Legally adopted child\n\nEntitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.\n\n4. \n",
        "utf8_sha256": "a8f6e865ad59245f0093e4f2845cd62098d5086e9700303dc6ee04a3218c1fa9"
      },
      {
        "id": "RS00203.035:B4",
        "start_codepoint": 3873,
        "end_codepoint": 5984,
        "text": "Step-child\na. \nDivorce between parent and NH\n\nIf the marriage (including invalid ceremonial marriage) between the NH and the stepchild's parent ends in a divorce that becomes final in or after July 1996, the stepchild's benefits terminate. The stepchild's entitlement will terminate the month after the month in which the divorce becomes final, i.e., the month of the divorce is the last month for which benefits are payable to the stepchild on the NH's record. This provision is contained in section 104 of P.L. 104-121. For post-entitlement processing instructions, see GN 02602.400.\n\nEXAMPLE: The NH’s stepchild is entitled to child’s benefits on the NH’s record. The NH’s marriage to the stepchild’s parent ends due to divorce on November 08, 2015. The stepchild’s benefits will terminate December 2015, the month after the month the divorce was final. November 2015 is the last month for which the stepchild receives a benefit (payable in December 2015).\n\nCAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.\n\nIf the marriage between the NH and the stepchild's parent ends in a divorce becoming final before July 1996, the divorce will not terminate the stepchild's entitlement. If the divorce is after June 30, 1996, the divorce does terminate the stepchild’s entitlement. If the NH and the stepchild’s parent remarry, the step-child must meet a new one-year duration of relationship and one-half support-met requirement before re-entitlement.\n\nb. \nAnnulment of marriage between parent and NH\n\nWhen an annulment of the marriage between the NH and the stepchild's parent occurs, the following policy applies:\n\nIf the marriage was...\n\n\t\n\nAnd the annulment operates...\n\n\t\n\nThen...\n\n\n\n\nVoid\n\n\t\n\nab initio\n\n\t\n•\n\nNo step relationship ever existed.\n\n•\n\nConsider any benefits paid incorrect (unless child qualifies as stepchild of invalid ceremonial marriage).\n\n\n\n\nVoidable \n\n\t\n\nprospectively only\n\n\t\n\nBenefits will terminate as of the month of the annulment, for annulments in or after September 1996. For annulments prior to September 1996, continue benefits.\n\nC. \n",
        "utf8_sha256": "2ef3bad3d1cdde42a39135bb6f2dc44575a3126799af1854ef47e4303ee35951"
      },
      {
        "id": "RS00203.035:C",
        "start_codepoint": 5984,
        "end_codepoint": 6464,
        "text": "Policy if adoption is a non-termination event\n\nThe adoption of a child already entitled to benefits does not terminate the child's benefits. Prior to November 1972, adoption did terminate benefits with certain exceptions. If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.\n\n \n\n",
        "utf8_sha256": "78f55cbcdad92c5f74f056c3e16d691d28e15a6845dfd644cdd5f96421d47aeb"
      }
    ],
    "exact_support_spans": [
      {
        "start_codepoint": 4834,
        "end_codepoint": 4932,
        "text": "CAUTION: If the NH has legally adopted the child, entitlement may be possible as an adopted child.",
        "utf8_sha256": "6c2017a70fd4f56150d87cde339b8ff65dd428266886a2356978620fc369409c"
      },
      {
        "start_codepoint": 6031,
        "end_codepoint": 6124,
        "text": "The adoption of a child already entitled to benefits does not terminate the child's benefits.",
        "utf8_sha256": "b99e68be0315063868287774824c846002b20aff2290380b77bb1dd0c7f4e12d"
      },
      {
        "start_codepoint": 3673,
        "end_codepoint": 3867,
        "text": "Entitlement to a child's benefit based on a legal adoption terminates if the adoption is annulled. The effective date of the termination to benefits is the month the annulment becomes effective.",
        "utf8_sha256": "8ae99d731ca15836fb7c1c48b894755c143ef788baac33fb1d60de0414ce4523"
      },
      {
        "start_codepoint": 6125,
        "end_codepoint": 6205,
        "text": "Prior to November 1972, adoption did terminate benefits with certain exceptions.",
        "utf8_sha256": "2b52e76519fb8d81ee096ee9b8ae7728d9ac2ffc502883dd8e8663b72ace07b9"
      },
      {
        "start_codepoint": 6206,
        "end_codepoint": 6459,
        "text": "If a child’s entitlement was terminated due to an adoption he or she may be re-entitled to child's benefits beginning November 1972 based on an application filed after October 30, 1972, provided the child meets all other requirements for re-entitlement.",
        "utf8_sha256": "72cbb29788decb47ddf827aa2dc5f8731a6a171ce0a5738afd9468e5e1ee12bd"
      }
    ],
    "original_records": {
      "adopted-stepchild": {
        "id": "adopted-stepchild",
        "title": "The stepchild was legally adopted",
        "when": "Adoption may preserve another child relationship.",
        "you": "Supply requested adoption evidence.",
        "ssa": "Evaluate entitlement as an adopted child rather than applying stepchild termination alone.",
        "route": "FO adopted-child evaluation",
        "next": "The adoption must meet the applicable requirements.",
        "source": "childtermination",
        "section": "B.4.a",
        "timing": "No completion duration specified",
        "review_status": "Selected branch checked; detailed exceptions remain"
      },
      "adoption-alone": {
        "id": "adoption-alone",
        "title": "A child already receiving benefits is adopted",
        "when": "The event is adoption, not annulment of adoption.",
        "you": "Report the event accurately.",
        "ssa": "Do not treat adoption itself as a termination event for an already entitled child.",
        "route": "Child-benefit review",
        "next": "Annulment of an adoption is a separate rule.",
        "source": "childtermination",
        "section": "B.3; C",
        "timing": "No completion duration specified",
        "review_status": "Selected branch checked; detailed exceptions remain"
      }
    },
    "original_sources": {
      "divorceprocessing": {
        "code": "GN 02602.400",
        "title": "Processing Reports of Divorce",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0202602400",
        "revision": "2014-01-07; TN 81 (08-21)",
        "kind": "POMS",
        "checked_on": "2026-10-16",
        "verification_scope": "Selected cited public subsections checked; linked screen manuals and full eligibility adjudication not certified."
      },
      "childtermination": {
        "code": "RS 00203.035",
        "title": "Child’s Benefits Termination of Entitlement",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0300203035",
        "revision": "2023-09-06; TN 47 (04-26)",
        "kind": "POMS",
        "checked_on": "2026-10-16",
        "verification_scope": "Selected cited public subsections checked; linked screen manuals and full eligibility adjudication not certified."
      }
    },
    "source_acceptance_peer": "9a3ac2519633ddd6e3724826e4858a0a8e3075704fa241cb06ed970fa694395c",
    "no_individual_case_or_global_freshness_adoption": true
  },
  "source_next267_selected": {
    "schema": "securitystat.selected-ssn-evidence-assistance/1",
    "retained_primary_text": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
    "retained_primary_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
    "primary_metadata": {
      "path": "C:\\Users\\leedu\\Documents\\Codex\\2026-10-30\\let\\work\\d263c-public378-r1\\service\\sources\\RM10210.120-r22-main.txt",
      "bytes": 2768,
      "sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
      "complete_page_included": true,
      "retained_capture_only": true,
      "fresh_internet_check": false,
      "effective_display": "12/28/2023 - Present",
      "TN": "47 (12-23)",
      "batch": "03/24/2026",
      "source_object_preserved": {
        "code": "RM 10210.120",
        "title": "Assisting Applicants When the SSN Application Cannot Be Filed",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0110210120",
        "revision": "2023-12-28",
        "kind": "POMS",
        "checked_on": "2026-10-16",
        "verification_scope": "Selected public assistance, missing-parent-data and discrepancy instructions checked; complete evidence/second-review scope remains."
      }
    },
    "source_contexts": {
      "whole_primary_sha256": "4729ba155886b855d619717124e886571527831538e01b803f5638dc28b7546c",
      "whole_page": "Effective Dates: 12/28/2023 - Present\nPrevious | Next\n\nTN 47 (12-23)\n\nRM 10210.120 Assisting Applicants When the SSN Application Cannot be Filed\n\nGenerally, applicants are able to submit the required data and required evidence for an SSN. Applicants who are homeless, have amnesia, or who are mentally impaired may need assistance.\n\nIn these situations, assist the applicant when they cannot provide:\n\n•\n\nthe minimum data required to complete an SSN application per RM 10205.015; or\n\n•\n\nthe evidence required to assign an SSN or to issue a replacement card per RM 10210.010 and RM 10210.015 respectively.\n\nA. \nHow to provide assistance\n\nTo maintain the integrity of the enumeration process, make every effort to assist the individual in providing the required information and acceptable evidence. Develop the SSN application as follows:\n\n•\n\nConduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.\n\n•\n\nWork with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).\n\n•\n\nIf pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.\n\n•\n\nSeek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.\n\n•\n\nIf appropriate, request assistance from parallel FOs in pursuing leads.\n\n•\n\nWhen the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.\n\n•\n\nWhen all efforts fail to produce the required evidence, contact the Regional Office for guidance.\n\nNOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.\n\nB. \nReferences\n•\n\nRM 10205.094, Purchasing Documents to Replace Lost Enumeration Evidence\n\n•\n\nRM 10210.005, SSN Type Definitions\n\n•\n\nRM 10215.110, Policy on Providing Written Notice and Second Review When SSN or Card Cannot Be Issued\n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0110210120\n\t\nRM 10210.120 - Assisting Applicants When the SSN Application Cannot be Filed - 12/28/2023\nBatch run: 03/24/2026\nRev:12/28/2023\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
      "quotes": [
        {
          "id": "RM10210.120:A:alphadent",
          "start_codepoint": 841,
          "end_codepoint": 964,
          "text": "Conduct an ALPHADENT search, using all possible spelling variations of the applicant's name, for a previously assigned SSN.",
          "utf8_sha256": "611d14bb3c32d3da53be184596255112e7fef7412a7b0848b67c471211e84e51"
        },
        {
          "id": "RM10210.120:A:evidence-leads",
          "start_codepoint": 969,
          "end_codepoint": 1146,
          "text": "Work with the applicant, or their representative, and suggest leads for possible sources of evidence (e.g., police or court records, past employers, schools, utility companies).",
          "utf8_sha256": "5510a2eaca408a0b2f3871c26738a516a405084800aac6b80715a4ebb327bcbe"
        },
        {
          "id": "RM10210.120:A:record-source-fee",
          "start_codepoint": 1151,
          "end_codepoint": 1257,
          "text": "If pertinent, provide the source and fee for birth, death, divorce, and marriage records per GN 00308.001.",
          "utf8_sha256": "39e6da88511ae0288a6add1f8320c9890b5207b3bce164e17422526136154547"
        },
        {
          "id": "RM10210.120:A:agency-cooperation",
          "start_codepoint": 1262,
          "end_codepoint": 1502,
          "text": "Seek cooperation of local agencies, the Department of Homeland Security (DHS), and other organizations (e.g., rehabilitation programs, advocacy groups, homeless shelters) to assist the individual in obtaining evidence from existing records.",
          "utf8_sha256": "3cb42c5999dc8eeb1a8a613608ce37a00a5b72fa6a8b40716a1aba9f5f1f8cf7"
        },
        {
          "id": "RM10210.120:A:parallel-fo",
          "start_codepoint": 1507,
          "end_codepoint": 1578,
          "text": "If appropriate, request assistance from parallel FOs in pursuing leads.",
          "utf8_sha256": "ce341485403997a070beedb663534b92cf8652029777ddd4e51b1092c5b3e298"
        },
        {
          "id": "RM10210.120:A:benefit-agency",
          "start_codepoint": 1583,
          "end_codepoint": 1755,
          "text": "When the individual needs an SSN for a benefit, contact the agency requiring the SSN to determine what evidence was used to establish eligibility to the particular benefit.",
          "utf8_sha256": "c108a9be1af15a2eb1545205fb590f4cea8d5f9f182af559510933321d8a1d16"
        },
        {
          "id": "RM10210.120:A:regional-guidance",
          "start_codepoint": 1760,
          "end_codepoint": 1857,
          "text": "When all efforts fail to produce the required evidence, contact the Regional Office for guidance.",
          "utf8_sha256": "98781d14e5a03a9ba193182d5e87c2c4bc5298e9f91f60021455bc35461f7294"
        },
        {
          "id": "RM10210.120:A:exhausted-leads-notice",
          "start_codepoint": 1859,
          "end_codepoint": 2117,
          "text": "NOTE: If all leads have been explored and the required data to complete the SS-5 and evidence is still unattainable, do not process the SSN application. If the SSN application cannot be processed, provide the applicant with a written notice per RM 10215.110.",
          "utf8_sha256": "e4a50542cf79a610790fccfc1b40d677b3afbefbf99d1de49de142a955676d8a"
        }
      ],
      "coverage": "Complete introduction, all7assistance bullets, exhaustion NOTE and references/footer retained; no truncated source."
    },
    "flow": {
      "schema": "securitystat.exception-flow/1",
      "record_id": "ssn-evidence-assistance-leads",
      "full_route": "update-citizenship/ssn-evidence-assistance-leads",
      "entry_conditions": [
        "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
        "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests."
      ],
      "steps": [
        {
          "id": "ssn-evidence-assistance-leads-alphadent",
          "title": "Search for a previously assigned SSN",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "Search ALPHADENT using all possible spelling variations of the applicant’s name for a previously assigned SSN.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:alphadent"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-evidence-leads",
          "title": "Work together on possible evidence leads",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "Work with the applicant or representative and suggest possible evidence sources, including police or court records, past employers, schools and utility companies.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:evidence-leads"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-record-source-fee",
          "title": "Provide pertinent record-source and fee information",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "If pertinent, provide the source and fee for birth, death, divorce and marriage records under the linked GN00308.001 instructions.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests.",
            "Record-source and fee information is pertinent."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:record-source-fee"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-agency-cooperation",
          "title": "Seek help obtaining existing records",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "Seek cooperation of local agencies, DHS and other organizations such as rehabilitation programs, advocacy groups or homeless shelters to help obtain evidence from existing records.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:agency-cooperation"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-parallel-fo",
          "title": "Request parallel field-office assistance when appropriate",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "If appropriate, ask parallel field offices to assist in pursuing leads.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests.",
            "Parallel field-office assistance is appropriate."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:parallel-fo"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-benefit-agency",
          "title": "Ask the requiring benefit agency about its evidence",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "When an SSN is needed for a benefit, contact the agency requiring it to determine which evidence established eligibility to that benefit.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests.",
            "The individual needs an SSN for a benefit."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:benefit-agency"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-regional-guidance",
          "title": "Request Regional Office guidance after failed efforts",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "When all efforts fail to produce the required evidence, contact the Regional Office for guidance.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests.",
            "All efforts have failed to produce the required evidence."
          ],
          "source": "ssnassist",
          "section": "A",
          "source_context_refs": [
            "RM10210.120:A:regional-guidance"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        },
        {
          "id": "ssn-evidence-assistance-leads-exhausted-leads-notice",
          "title": "Do not process when required data and evidence remain unattainable",
          "kind": "ssa",
          "actor": "Agency staff",
          "action": "If all leads have been explored and required SS-5 data and evidence remain unattainable, do not process the SSN application. If it cannot be processed, provide a written notice under RM10215.110.",
          "conditions": [
            "An SSN applicant cannot provide the minimum required application data or required evidence to assign an SSN or issue a replacement card.",
            "The applicant needs assistance; homelessness, amnesia and mental impairment are examples in the retained introduction, not exclusive eligibility tests.",
            "All leads have been explored and required data and evidence remain unattainable."
          ],
          "source": "ssnassist",
          "section": "A; exhaustion NOTE",
          "source_context_refs": [
            "RM10210.120:A:exhausted-leads-notice"
          ],
          "qualifications": [
            "Source order is retained; conditional assistance is not a requirement to use every possible evidence source in every case.",
            "This card does not waive required evidence, guarantee an SSN/card, create a new applicant evidence duty or establish a completion deadline."
          ],
          "next": "Follow applicable assistance and evidence requirements; this card does not establish a successful case-specific handoff or automatic rejoin."
        }
      ],
      "rejoin": {
        "status": "unknown",
        "automatic_transition": false,
        "unknowns": [
          "Exact case-specific entry/insertion point and evidence sufficiency remain unknown.",
          "Regional Office or parallel-FO response, component handoff and successful return to processing are not established.",
          "Linked minimum-data, evidence, record-fee and written-notice/second-review procedures are not implemented by this selected sequence."
        ]
      }
    },
    "source_peer_sha256": "c48c43150fff5d0efbea94f7651730164d1d5dd96e4fd5856a7e339628e5032d",
    "original_parent": {
      "id": "update-citizenship",
      "category": "Identity & records",
      "title": "Update citizenship or immigration status",
      "short": "Follow the application and appointment route.",
      "story": "Jane’s citizenship or immigration status changed and she wants her Social Security record updated.",
      "level": "Customer overview",
      "review_status": "Cited core steps checked; exceptions incomplete",
      "scope": "Source-backed core path. Case-specific eligibility, every exception, and internal execution are not fully modeled.",
      "path": [
        "You",
        "Application",
        "Office evidence review",
        "Updated record / card"
      ],
      "channels": {
        "office": "The published route includes an appointment with evidence of identity and new status.",
        "phone": "SSA lists phone support for this task; it does not describe a phone-only status update.",
        "online": "Start online, then attend the appointment described by SSA. This is not an entirely online transaction."
      },
      "checklist": [
        "Start with the official replacement-card application.",
        "Arrange the appointment described by SSA.",
        "Bring proof of identity and the new citizenship or immigration status."
      ],
      "steps": [
        {
          "id": "update-citizenship-1",
          "title": "Start the official request",
          "you": "Begin the replacement-card application online.",
          "ssa": "The published route includes making an appointment.",
          "source": "citizenship",
          "section": "Request a replacement card",
          "owner": "SSA; exact internal assignment not established",
          "systems": [],
          "timing": "No duration specified for this step",
          "verification": "Cited public text checked 2026-10-16; not an independent operational review",
          "route": "Online replacement-card request → SSA appointment",
          "next": "The published customer route includes an appointment. Starting online does not establish that SSA has completed the status update."
        },
        {
          "id": "update-citizenship-2",
          "title": "Bring the evidence",
          "you": "Bring proof of identity and new status to the appointment.",
          "ssa": "Review the information and update supported status information.",
          "source": "citizenship",
          "section": "Request a replacement card",
          "owner": "SSA; exact internal assignment not established",
          "systems": [],
          "timing": "No duration specified for this step",
          "verification": "Cited public text checked 2026-10-16; not an independent operational review",
          "route": "SSA appointment → status-information review; internal assignment not established here",
          "next": "Bring proof of identity and new status. This customer-guidance page does not establish staff screen actions or category-specific verification steps."
        },
        {
          "id": "update-citizenship-3",
          "title": "Receive the card",
          "you": "Check the mailed replacement after the update.",
          "ssa": "The public page describes mailing the replacement card after the update.",
          "source": "citizenship",
          "section": "Request a replacement card",
          "owner": "SSA; exact internal assignment not established",
          "systems": [],
          "timing": "No duration specified for this step",
          "verification": "Cited public text checked 2026-10-16; not an independent operational review",
          "route": "SSA status update → replacement card by mail",
          "next": "SSA describes receipt by mail in 5–10 business days after it updates the information. This period does not begin with the initial application or establish a deadline for completing verification."
        }
      ],
      "decision": null,
      "timing": "SSA’s page estimates card delivery in 5–10 business days after the information is updated. This is not a deadline for completing all verification.",
      "timing_type": "Published delivery estimate",
      "outcome": "An updated status record and replacement-card mailing after SSA completes the update.",
      "gaps": [
        "Remaining exceptions and cross-references still need expanded workflows.",
        "This explains published instructions; actual processing and internal system behavior were not tested."
      ],
      "source_ids": [
        "citizenship",
        "replacementstatus",
        "numident",
        "primarycitizenshipevidence",
        "citizenshipevidencegeneral",
        "citizenshipnoevidence",
        "ssnassist",
        "lostenumerationevidence",
        "statuschangeprocessing",
        "nonworkssn"
      ],
      "branches": [
        {
          "id": "card-suppressed",
          "title": "The record can be corrected but no card can issue",
          "when": "Acceptable correction evidence exists but card eligibility does not.",
          "you": "Ask separately about the record correction and card decision.",
          "ssa": "Update Numident and suppress issuance under the cited conditions.",
          "route": "Enumeration record action",
          "next": "No card does not necessarily mean no record correction.",
          "source": "replacementstatus",
          "section": "D",
          "timing": "No completion duration specified",
          "review_status": "Selected branch checked; detailed exceptions remain"
        },
        {
          "id": "status-replacement-evidence",
          "title": "Identity and current status evidence checks",
          "when": "A citizenship or immigration update includes a replacement-card request.",
          "you": "Bring identity and status evidence; do not mail your immigration document.",
          "ssa": "Check identity against Numident. A foreign-born U.S. citizen supplies citizenship evidence unless already proven there; a work-authorized noncitizen supplies current lawful work-authorized status evidence. Apply the separate non-name correction evidence policy.",
          "route": "SSA enumeration evidence review → supported record update",
          "next": "Evidence and category verification may require further development.",
          "source": "replacementstatus",
          "section": "A; B",
          "timing": "No verification or update duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "citizenship-ranked-evidence",
          "title": "Citizenship evidence availability and record entry",
          "when": "Citizenship information is being updated through a new Numident iteration.",
          "you": "Submit the application, identity proof and supporting citizenship evidence; explain which documents you have or can obtain.",
          "ssa": "Create the new iteration from supported information. Request the highest-probative citizenship evidence available before lower-level evidence; available means possessed or obtainable within ten working days. Record submitted documents in SSNAP Summary Remarks if not already captured.",
          "route": "Enumeration interviewer → supported Numident iteration / evidence record",
          "next": "Ten working days defines document availability, not an update deadline.",
          "source": "numident",
          "section": "A.2; B.1; B.2 citizenship row; B.3 opening",
          "timing": "No processing guarantee; evidence-availability interval only where stated.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "citizenship-unable-update-notice",
          "title": "Written notice when the record or card cannot be updated",
          "when": "SSA cannot update the record or provide the replacement card.",
          "you": "Read the written explanation and respond to any evidence request.",
          "ssa": "Send written notice under the applicable refusal, additional-documentation or card-notice policy referenced in B.5. Do not infer a particular refusal form applies to every case.",
          "route": "SSA enumeration review → applicable written notice",
          "next": "The notice identifies the unresolved issue.",
          "source": "numident",
          "section": "B.5",
          "timing": "No processing guarantee; evidence-availability interval only where stated.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "citizenship-passport-certificate-verification",
          "title": "Passport or citizenship certificate evidence checks",
          "when": "An applicant presents a passport or citizenship/naturalization certificate.",
          "you": "Bring the available document and separate identity evidence as requested.",
          "ssa": "Check passport acceptance criteria: tourist passports have five-year validity when issued under age 16, ten years at age 16 or older; official, diplomatic and military-dependent passports have the stated exception. Current or expired passports must satisfy the criteria. Naturalization and citizenship certificates require DHS verification through the enumeration system. If both a passport and naturalization certificate are presented, select the passport for citizenship proof.",
          "route": "Enumeration document review → citizenship evidence acceptance / verification",
          "next": "Citizenship evidence acceptance does not establish that all identity and update requirements are complete.",
          "source": "primarycitizenshipevidence",
          "section": "Primary evidence table: U.S. passport; Certificates of Naturalization/Citizenship",
          "timing": "No verification completion duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "replacement-citizenship-record-confirmation",
          "title": "Replacement-card record already confirms citizenship",
          "when": "A replacement-card applicant alleges U.S. citizenship.",
          "you": "Provide citizenship evidence if SSA’s record does not confirm it.",
          "ssa": "Check the Numident information used by SSNAP. No new citizenship evidence is required for the listed combinations: U.S. birthplace with blank citizenship code or A, or foreign birthplace with code A. If the record does not confirm citizenship, require evidence whether U.S. or foreign birth is alleged.",
          "route": "SSNAP-used Numident check → evidence exemption / citizenship evidence development",
          "next": "This limited evidence exemption does not waive identity or other requirements.",
          "source": "citizenshipevidencegeneral",
          "section": "A.3.a-b",
          "timing": "No processing duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "citizenship-no-evidence-assistance",
          "title": "Citizenship evidence is unavailable",
          "when": "The applicant alleges citizenship but lacks accepted citizenship documents.",
          "you": "Explain what evidence is missing and what makes obtaining it difficult.",
          "ssa": "Use the allegation-specific assistance route: RM 10210.120 for amnesia, homelessness or mental impairment; GN 00303.300O for the listed foreign-born citizenship allegations; RM 10210.540 for a foreign-born adopted child. Refer to USCIS for an alleged citizenship provision not covered in POMS. The U.S.-born no-proof benefit exception in this table applies only to original SSNs, not replacement-card updates.",
          "route": "SSA evidence assistance → applicable policy / USCIS where specified",
          "next": "Assistance does not itself establish citizenship or card eligibility.",
          "source": "citizenshipnoevidence",
          "section": "Applicant allegation table: selected assistance rows; U.S. born no proof boundary",
          "timing": "No assistance completion duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "ssn-evidence-assistance-leads",
          "title": "Help obtaining missing SSN application evidence",
          "when": "An applicant needs assistance supplying required data or evidence.",
          "you": "Explain the missing information and possible past records or contacts.",
          "ssa": "Search ALPHADENT using name spelling variations for an existing SSN. Work with the applicant or representative on evidence leads, seek agency or organization cooperation and parallel-FO help where appropriate. For an SSN needed for benefits, contact the requiring agency about its evidence. When efforts fail, contact the Regional Office. If all leads are explored and required data/evidence remain unattainable, do not process; provide written notice.",
          "route": "FO evidence assistance → sources / Regional Office → processing or notice",
          "next": "SSA assistance explores evidence leads; it does not waive the required evidence.",
          "source": "ssnassist",
          "section": "Introduction; A",
          "timing": "No assistance completion duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "enumeration-evidence-lost-by-ssa",
          "title": "SSA lost evidence or a returned document never arrived",
          "when": "An enumeration applicant reports lost or unreturned evidence.",
          "you": "Tell SSA which document was submitted and what action or return correspondence you received.",
          "ssa": "Check whether it appears SSA had the evidence, such as an action based on that document. Replace the lost document under the stated exception. If a fee must be paid, use local procedures or have FO management contact regional management.",
          "route": "FO evidence-possession review → replacement / fee management",
          "next": "This exception does not make SSA the purchaser of every enumeration document.",
          "source": "lostenumerationevidence",
          "section": "Opening paragraphs",
          "timing": "No replacement duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "status-most-recent-document",
          "title": "More than one unexpired immigration document",
          "when": "DHS approved a changed status and the applicant presents multiple unexpired documents.",
          "you": "Bring the current DHS-issued documentation and requested identity evidence.",
          "ssa": "Use the immigration document with the most recent issue date as evidence of current status; the approved new-status document supersedes earlier documents. Verify it with DHS before processing the SSN application.",
          "route": "Enumeration evidence review → DHS verification → SSN processing",
          "next": "A pending status-change allegation alone is a separate path.",
          "source": "statuschangeprocessing",
          "section": "A",
          "timing": "No verification or issuance duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "status-card-issuance-choice",
          "title": "A status update may or may not produce a card",
          "when": "The replacement/update case falls under the now-work-authorized processing rule.",
          "you": "Tell SSA whether you need a replacement card and ask whether one will issue.",
          "ssa": "SSNAP uses the application, Numident and verifications to determine the record update and card legend. Issue a replacement if the legend changes or a card is requested, subject to limits. If the legend stays the same and no replacement is needed, suppress issuance on SSNAP Additional Info; tell the applicant whether a card will issue.",
          "route": "Verified status update → card issuance / suppression",
          "next": "An updated record does not always result in a mailed card.",
          "source": "statuschangeprocessing",
          "section": "C opening; C.1.b",
          "timing": "No verification or issuance duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "status-no-longer-work-authorized",
          "title": "The record shows work authorization has ended",
          "when": "SSA reviews evidence that the individual is no longer work authorized.",
          "you": "Provide any claimed valid nonwork reason and requested supporting evidence.",
          "ssa": "If a valid nonwork reason is submitted, follow RM 10211.620 and explain the nonwork card outcome. Without a valid nonwork reason, suppress card issuance in SSNAP Additional Info; update Numident work-authorization and status information.",
          "route": "Enumeration status review → nonwork-card processing / suppressed issuance",
          "next": "The number record and the decision to issue a card are distinct actions.",
          "source": "statuschangeprocessing",
          "section": "C.2",
          "timing": "No DHS or SSA processing duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "status-dhs-change-pending",
          "title": "DHS status change is still pending",
          "when": "The applicant seeks an SSN action while DHS processes a status change.",
          "you": "Bring the requested DHS employment-authorization document or proof of a valid nonwork reason.",
          "ssa": "For a proved valid nonwork reason, follow RM 10211.600; without one advise return after final DHS notification. For claimed employment authorization, request a valid EAD; without it advise contacting DHS for appropriate documentation under the cited rules. Apply the stated EAD requirement to a pending deportation hearing claim.",
          "route": "SSA evidence review → applicable SSN processing / DHS documentation",
          "next": "Pending status by itself does not settle the evidence requirement.",
          "source": "statuschangeprocessing",
          "section": "D.1-2",
          "timing": "No DHS or SSA processing duration specified.",
          "review_status": "Official subsection checked2026-10-17"
        },
        {
          "id": "nonwork-letter-signature",
          "title": "A government letter supports a nonwork SSN reason",
          "when": "The applicant presents a government letter for a claimed qualifying nonwork reason.",
          "you": "Provide the original agency letter and required age, identity and status evidence.",
          "ssa": "The field office checks the dated letterhead, applicant, reason, legal requirement, agency contact, all-other-requirements statement and authorized wet signature. Before acceptance, contact the agency to establish a signature precedent file; replace it when the official leaves. Verify questionable letters and consult regional instructions.",
          "route": "Field office → issuing government agency → nonwork evidence review",
          "next": "Only documentation meeting all criteria can establish the claimed nonwork reason; a request alone does not establish eligibility.",
          "source": "nonworkssn",
          "section": "A.1-3",
          "timing": "No completion period specified.",
          "review_status": "Official subsection independently checked 2026-10-17"
        },
        {
          "id": "nonwork-title-record-documentation",
          "title": "A nonwork request relies on Title II or SSI entitlement",
          "when": "The applicant alleges Title II or Title XVI benefit entitlement as the nonwork basis.",
          "you": "Identify the benefit entitlement claimed and respond to evidence requests.",
          "ssa": "Check MBR and SSID for alleged entitlement to either or both programs. For Title II entitlement only, SSNAP requires the claim number in the Account Number field within Non-Work Reason and Documentation on Proof of Legal Alien Status. Title XVI entitlement documentation requires no account number.",
          "route": "SSA enumeration review → benefit-record verification → SSNAP documentation",
          "next": "SSA verifies the alleged entitlement; the allegation alone does not establish a valid nonwork basis.",
          "source": "nonworkssn",
          "section": "B",
          "timing": "No processing interval specified.",
          "review_status": "Official subsection independently checked 2026-10-17"
        }
      ]
    },
    "no_case_specific_entry_or_successful_rejoin_claim": true
  },
  "dircon7_selected": {
    "schema": "securitystat.selected-dircon-seven/1",
    "whole_primary": "Effective Dates: 07/28/2015 - Present\nPrevious | Next\n\nTN 51 (08-23)\n\nGN 01070.305 Use Of Direct Contact (DIRCON)\nA. \nOverview of payment center (PC) to public contact\n\nProcessing Center personnel should utilize DIRCON whenever possible, bypassing the Field Office (FO). It is only necessary to develop through the FO when face to face contact is required or where the FO is responsible for making a final determination on the issue (such as a representative payee determination).\n\nWhen reference is made to mail direct contact, it refers only to regular mail delivered by the U.S. Postal Service, not e-mail. Per GN 03325.020B, SSNs and other personally identifiable information may be transmitted by e-mail for official business purposes only within SSA’s Microsoft Outlook/Exchange infrastructure. This includes all SSA field offices, headquarters facilities, Program Service Centers and Regional Offices, as well as trusted partners such as the State Disability Determination offices that are listed in SSA’s Microsoft Outlook Global Address List, and the Centers for Medicare and Medicaid Services (CMS). Sending SSNs or other personally identifiable information via e-mail outside of SSA’s Network (i.e., into a commercial e-mail system that is not encrypted and thus not secure) is prohibited.\n\nA pending initial claim or allowance upon appeal is not by itself a reason to develop through the FO. The PC can make phone calls or written requests for evidence just as effectively as the local office.\n\nB. \nPolicy for use of DIRCON\n1. \nLimitations of DIRCON\n\nDIRCON is limited to contact within the United States, Puerto Rico and Virgin Islands, except for those international calls authorized for OIO. OIO development guidelines can be found in POMS GN 00904.200.\n\n2. \nDisclosure\n\nSee GN 03301.005 for Privacy Act guidelines for disclosure. This reference outlines the types of information which may be released to third parties without consent of the claimant / beneficiary.\n\n3. \nWhen to use DIRCON\n\nThe general, but simple, rule is that a PC employee will not refer development to the FO unless face to face contact is required, or where the FO is responsible for making a final determination on the issue (such as a representative payee determination).\n\nThe PC will always obtain information, statement clarifications or required evidence via DIRCON unless a face to face or field contact is needed, or one of the exceptions in GN 01070.305C. or D. below applies.\n\nC. \nClaimant/Beneficiary DIRCON\n\nContact the claimant / beneficiary if the claimant / beneficiary is mentally and physically able. Do not contact the claimant/beneficiary if:\n\n•\n\nThe claimant/beneficiary is unable to pursue their own rights due to young age or physical/mental incapability. (Representative Payee involved);\n\n•\n\nThe claimant / beneficiary has an appointed representative (this may or may not be an attorney). In post-adjudicative situations, check the FEAR data group (available effective COM 12/2006) on the MBR to determine if there is current representative involvement. (See GN 01070.330.)\n\n•\n\nThere is a known language barrier that prohibits oral communication with the claimant / beneficiary. (Mail DIRCON may still be utilized in this instance.)\n\n•\n\nThe information in question involves prisoner suspension. (See GN 02607.600.C and GN 02607.670A.3 for instructions on contacting the FO when additional information is needed in these situations. The Field Offices have established special relationships with correctional facilities in their service areas that will enable them to secure the necessary information.)\n\nD. \nThird Party Contact DIRCON\n1. \nGuidelines for third party contact\na. \n\nAssure contact is the correct evidentiary source. (See GN 03301.005 for Privacy Act guidelines for disclosure.)\n\nb. \n\nDo not interrupt payment until due process is given if evidence leads to adverse action. (See GN 03001.025.)\n\nc. \n\nIf a consent statement is required before a third party will release information, DIRCON can be used to obtain consent, and the request then forwarded to the third party.\n\nd. \n\nDo not attempt direct contact with the third party in instances where certain state and local government agencies have worked out special arrangements with a local SSA FO to provide needed data at no cost. In this situation, it would be appropriate to develop through the servicing FO per DI 52145.001F.1. NOTE\n\n2. \nEmployer (E/R) contact DIRCON\n\nVerify the claimant agrees to E/R contact. For more information on the processing center’s responsibilities in work continuing disability reviews, please refer to DI 13010.023B.\n\nE. \nGeneral considerations for DIRCON\n1. \nTelephone versus mail contact\n\nSend a letter to the individual if the request cannot be handled by telephone (See GN 01070.320.)\n\n2. \nFO development in process\n\nDo not use the direct contact procedure if the FO has promised or started development of the necessary information. Request the FO to furnish the status based on follow-up timeframes shown in GN 01070.440.\n\n \n\nTo Link to this section - Use this URL:\nhttp://policy.ssa.gov/poms.nsf/lnx/0201070305\n\t\nGN 01070.305 - Use Of Direct Contact (DIRCON) - 07/28/2015\nBatch run: 05/13/2026\nRev:07/28/2015\nAccessibility FOIA Open Government Glossary Privacy Report Fraud, Waste or Abuse Site Map Website Policies\n\nThis website is produced and published at U.S. taxpayer expense.",
    "whole_primary_sha256": "21b9fa83bd9ba806c8546567a3258c899771575e20bb2eeb47a6de5b63c0eaad",
    "source_contexts": {
      "whole_primary_sha256": "21b9fa83bd9ba806c8546567a3258c899771575e20bb2eeb47a6de5b63c0eaad",
      "contexts": [
        {
          "id": "GN01070.305:A",
          "start_codepoint": 114,
          "end_codepoint": 1507,
          "text": "A. \nOverview of payment center (PC) to public contact\n\nProcessing Center personnel should utilize DIRCON whenever possible, bypassing the Field Office (FO). It is only necessary to develop through the FO when face to face contact is required or where the FO is responsible for making a final determination on the issue (such as a representative payee determination).\n\nWhen reference is made to mail direct contact, it refers only to regular mail delivered by the U.S. Postal Service, not e-mail. Per GN 03325.020B, SSNs and other personally identifiable information may be transmitted by e-mail for official business purposes only within SSA’s Microsoft Outlook/Exchange infrastructure. This includes all SSA field offices, headquarters facilities, Program Service Centers and Regional Offices, as well as trusted partners such as the State Disability Determination offices that are listed in SSA’s Microsoft Outlook Global Address List, and the Centers for Medicare and Medicaid Services (CMS). Sending SSNs or other personally identifiable information via e-mail outside of SSA’s Network (i.e., into a commercial e-mail system that is not encrypted and thus not secure) is prohibited.\n\nA pending initial claim or allowance upon appeal is not by itself a reason to develop through the FO. The PC can make phone calls or written requests for evidence just as effectively as the local office.\n\n",
          "utf8_sha256": "f7a276a05a5eb330954d8da543cff45f790f11c96fbdc56f0a0abbf531fe7b37"
        },
        {
          "id": "GN01070.305:B",
          "start_codepoint": 1507,
          "end_codepoint": 2473,
          "text": "B. \nPolicy for use of DIRCON\n1. \nLimitations of DIRCON\n\nDIRCON is limited to contact within the United States, Puerto Rico and Virgin Islands, except for those international calls authorized for OIO. OIO development guidelines can be found in POMS GN 00904.200.\n\n2. \nDisclosure\n\nSee GN 03301.005 for Privacy Act guidelines for disclosure. This reference outlines the types of information which may be released to third parties without consent of the claimant / beneficiary.\n\n3. \nWhen to use DIRCON\n\nThe general, but simple, rule is that a PC employee will not refer development to the FO unless face to face contact is required, or where the FO is responsible for making a final determination on the issue (such as a representative payee determination).\n\nThe PC will always obtain information, statement clarifications or required evidence via DIRCON unless a face to face or field contact is needed, or one of the exceptions in GN 01070.305C. or D. below applies.\n\n",
          "utf8_sha256": "948cbcf5cde6c3925368589530d5835b9eb9c3298b7d964ae6763690871171ca"
        },
        {
          "id": "GN01070.305:C",
          "start_codepoint": 2473,
          "end_codepoint": 3611,
          "text": "C. \nClaimant/Beneficiary DIRCON\n\nContact the claimant / beneficiary if the claimant / beneficiary is mentally and physically able. Do not contact the claimant/beneficiary if:\n\n•\n\nThe claimant/beneficiary is unable to pursue their own rights due to young age or physical/mental incapability. (Representative Payee involved);\n\n•\n\nThe claimant / beneficiary has an appointed representative (this may or may not be an attorney). In post-adjudicative situations, check the FEAR data group (available effective COM 12/2006) on the MBR to determine if there is current representative involvement. (See GN 01070.330.)\n\n•\n\nThere is a known language barrier that prohibits oral communication with the claimant / beneficiary. (Mail DIRCON may still be utilized in this instance.)\n\n•\n\nThe information in question involves prisoner suspension. (See GN 02607.600.C and GN 02607.670A.3 for instructions on contacting the FO when additional information is needed in these situations. The Field Offices have established special relationships with correctional facilities in their service areas that will enable them to secure the necessary information.)\n\n",
          "utf8_sha256": "6a437f4d92bd8d5b0680ae7400ca3924dcd9e5d04b3085ef85133800c85ce046"
        },
        {
          "id": "GN01070.305:D",
          "start_codepoint": 3611,
          "end_codepoint": 4622,
          "text": "D. \nThird Party Contact DIRCON\n1. \nGuidelines for third party contact\na. \n\nAssure contact is the correct evidentiary source. (See GN 03301.005 for Privacy Act guidelines for disclosure.)\n\nb. \n\nDo not interrupt payment until due process is given if evidence leads to adverse action. (See GN 03001.025.)\n\nc. \n\nIf a consent statement is required before a third party will release information, DIRCON can be used to obtain consent, and the request then forwarded to the third party.\n\nd. \n\nDo not attempt direct contact with the third party in instances where certain state and local government agencies have worked out special arrangements with a local SSA FO to provide needed data at no cost. In this situation, it would be appropriate to develop through the servicing FO per DI 52145.001F.1. NOTE\n\n2. \nEmployer (E/R) contact DIRCON\n\nVerify the claimant agrees to E/R contact. For more information on the processing center’s responsibilities in work continuing disability reviews, please refer to DI 13010.023B.\n\n",
          "utf8_sha256": "d6c5fe8a0261cea3dd62cae2079f81adf88e4833ac3aa286aa7558e24545b8e3"
        },
        {
          "id": "GN01070.305:E",
          "start_codepoint": 4622,
          "end_codepoint": 5035,
          "text": "E. \nGeneral considerations for DIRCON\n1. \nTelephone versus mail contact\n\nSend a letter to the individual if the request cannot be handled by telephone (See GN 01070.320.)\n\n2. \nFO development in process\n\nDo not use the direct contact procedure if the FO has promised or started development of the necessary information. Request the FO to furnish the status based on follow-up timeframes shown in GN 01070.440.\n\n \n\n",
          "utf8_sha256": "a64960de437024655d06cec7339fed2d866ef769d5049f18be0a6fb465b5ad18"
        }
      ],
      "unique_quotes": [
        {
          "id": "GN01070.305:quote:unable",
          "start_codepoint": 2652,
          "end_codepoint": 2796,
          "text": "The claimant/beneficiary is unable to pursue their own rights due to young age or physical/mental incapability. (Representative Payee involved);",
          "utf8_sha256": "1729f0eae12a51646be98a393f1fff96c15a7fe5406ff45cfaca99fe16172725"
        },
        {
          "id": "GN01070.305:quote:language",
          "start_codepoint": 3087,
          "end_codepoint": 3241,
          "text": "There is a known language barrier that prohibits oral communication with the claimant / beneficiary. (Mail DIRCON may still be utilized in this instance.)",
          "utf8_sha256": "8130492e1da6e936f7f20a650de0da45a801b27f884b47be42d16d4d9038c166"
        },
        {
          "id": "GN01070.305:quote:prisoner",
          "start_codepoint": 3246,
          "end_codepoint": 3609,
          "text": "The information in question involves prisoner suspension. (See GN 02607.600.C and GN 02607.670A.3 for instructions on contacting the FO when additional information is needed in these situations. The Field Offices have established special relationships with correctional facilities in their service areas that will enable them to secure the necessary information.)",
          "utf8_sha256": "bea361d2b04a3edd7269f7f93c76e3330787081fd32e5b8935651b5a30fcd5bc"
        },
        {
          "id": "GN01070.305:quote:evidence",
          "start_codepoint": 3686,
          "end_codepoint": 3797,
          "text": "Assure contact is the correct evidentiary source. (See GN 03301.005 for Privacy Act guidelines for disclosure.)",
          "utf8_sha256": "d6c2071b11f7528a2c85f2363206bee7179280f1af744ba3062a5932e000eb06"
        },
        {
          "id": "GN01070.305:quote:dueprocess",
          "start_codepoint": 3804,
          "end_codepoint": 3912,
          "text": "Do not interrupt payment until due process is given if evidence leads to adverse action. (See GN 03001.025.)",
          "utf8_sha256": "c2f98b1e0b6ee113ecc91073f5aa06b15e36e38c71664e8b14523381761d2250"
        },
        {
          "id": "GN01070.305:quote:consent",
          "start_codepoint": 3919,
          "end_codepoint": 4089,
          "text": "If a consent statement is required before a third party will release information, DIRCON can be used to obtain consent, and the request then forwarded to the third party.",
          "utf8_sha256": "7645505624c51dc13008da69832144afdc63288d8f4c05160ead622b92c8e0d1"
        },
        {
          "id": "GN01070.305:quote:nocost",
          "start_codepoint": 4096,
          "end_codepoint": 4406,
          "text": "Do not attempt direct contact with the third party in instances where certain state and local government agencies have worked out special arrangements with a local SSA FO to provide needed data at no cost. In this situation, it would be appropriate to develop through the servicing FO per DI 52145.001F.1. NOTE",
          "utf8_sha256": "92151de4a460a1735e7f6caf4881fe7527e1bf90f622b1e52fedfb1120d1fc51"
        },
        {
          "id": "GN01070.305:quote:employer",
          "start_codepoint": 4443,
          "end_codepoint": 4620,
          "text": "Verify the claimant agrees to E/R contact. For more information on the processing center’s responsibilities in work continuing disability reviews, please refer to DI 13010.023B.",
          "utf8_sha256": "d5063c7fbf21a1207c27564672f94631fff4739eaf17dbd6a5771ecfa540ed0b"
        },
        {
          "id": "GN01070.305:quote:fo",
          "start_codepoint": 4825,
          "end_codepoint": 5030,
          "text": "Do not use the direct contact procedure if the FO has promised or started development of the necessary information. Request the FO to furnish the status based on follow-up timeframes shown in GN 01070.440.",
          "utf8_sha256": "61e838861bccc0558a0ef449505d201b54e12c969ec7607d967e868cff03340a"
        }
      ],
      "scope": "Complete A-E public primary and all footer retained. Other already-authored source qualifiers/held links preserved unchanged, not newly implemented."
    },
    "primary_metadata": {
      "source_path": "C:\\Users\\leedu\\Documents\\Codex\\2026-10-30\\let\\work\\d263c-public378-r1\\service\\sources\\GN01070.305-dircon-main.txt",
      "bytes": 5435,
      "characters": 5391,
      "sha256": "21b9fa83bd9ba806c8546567a3258c899771575e20bb2eeb47a6de5b63c0eaad",
      "complete_primary_page_retained": true,
      "source_object_preserved": {
        "code": "GN 01070.305",
        "title": "Use Of Direct Contact (DIRCON)",
        "url": "https://secure.ssa.gov/poms.nsf/lnx/0201070305",
        "revision": "07/28/2015; TN51(08-23)",
        "kind": "POMS staff instructions",
        "checked_on": "2026-10-31",
        "verification_scope": "Selected PC contact scopes/exceptions A–E for this bounded journey; not complete workflow or case acceptance."
      },
      "retained_capture_only": true,
      "fresh_internet_check": false,
      "effective_display": "07/28/2015 - Present",
      "TN": "51 (08-23)",
      "batch_display": "05/13/2026"
    },
    "flows": {
      "dircon-claimant-unable-to-pursue-rights": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-claimant-unable-to-pursue-rights",
        "full_route": "pc-direct-evidence-development/dircon-claimant-unable-to-pursue-rights",
        "entry_conditions": [
          "PC staff are considering claimant/beneficiary DIRCON.",
          "Young age or physical/mental incapability prevents the person pursuing their own rights."
        ],
        "steps": [
          {
            "id": "dircon-claimant-unable-to-pursue-rights-contact-boundary",
            "title": "Do not contact a person unable to pursue their own rights",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not contact the claimant or beneficiary directly when young age or physical/mental incapability prevents the person pursuing their own rights. The source notes representative-payee involvement; this does not appoint a payee, determine capability or authorize a substitute recipient.",
            "conditions": [
              "PC staff are considering claimant/beneficiary DIRCON.",
              "Young age or physical/mental incapability prevents the person pursuing their own rights."
            ],
            "source": "dircon305",
            "section": "C; A; B; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:C",
              "GN01070.305:quote:unable"
            ],
            "qualifications": [
              "This does not decide legal capacity, appoint a payee, authorize a substitute contact or establish the become-payee workflow.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN01070.330 B.1 excludes a representative payee from its term representative. Do not merge payee/capability handling with appointed-representative contact categories.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Who may be contacted instead, supporting authority and completed development remain outside the captured instruction.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-oral-language-barrier": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-oral-language-barrier",
        "full_route": "pc-direct-evidence-development/dircon-oral-language-barrier",
        "entry_conditions": [
          "PC staff are considering claimant/beneficiary DIRCON.",
          "A known language barrier prohibits oral communication with the person."
        ],
        "steps": [
          {
            "id": "dircon-oral-language-barrier-oral-boundary",
            "title": "Respect the known oral-language barrier",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not use oral claimant or beneficiary contact when a known language barrier prohibits that communication. This card does not establish an interpreter procedure.",
            "conditions": [
              "PC staff are considering claimant/beneficiary DIRCON.",
              "A known language barrier prohibits oral communication with the person."
            ],
            "source": "dircon305",
            "section": "C; A; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:C",
              "GN01070.305:quote:language"
            ],
            "qualifications": [
              "Mail means regular USPS mail, not email.",
              "This is not an absolute prohibition of all contact, an interpreter procedure, automatic letter adequacy or waiver of other C/D/E exceptions.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN305 mail alternative does not bypass GN330 appointed-representative constraints when representation also applies; a claimant copy under C.3 is part of that specific representative-directed mail procedure.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          },
          {
            "id": "dircon-oral-language-barrier-mail-option",
            "title": "Consider the bounded postal-mail alternative",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Regular postal-mail DIRCON may still be used for this specific oral-language-barrier situation, subject to the other applicable representative, contact, privacy and FO-development restrictions. This is an option, not a finding that a letter is adequate or that other restrictions are waived.",
            "conditions": [
              "PC staff are considering claimant/beneficiary DIRCON.",
              "A known language barrier prohibits oral communication with the person.",
              "Mail contact remains permitted under all other applicable source restrictions."
            ],
            "source": "dircon305",
            "section": "C; A; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:C",
              "GN01070.305:quote:language"
            ],
            "qualifications": [
              "Mail means regular USPS mail, not email.",
              "This is not an absolute prohibition of all contact, an interpreter procedure, automatic letter adequacy or waiver of other C/D/E exceptions.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN305 mail alternative does not bypass GN330 appointed-representative constraints when representation also applies; a claimant copy under C.3 is part of that specific representative-directed mail procedure.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Language accommodation details, letter procedure and delivery/result remain unreviewed.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-prisoner-suspension": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-prisoner-suspension",
        "full_route": "pc-direct-evidence-development/dircon-prisoner-suspension",
        "entry_conditions": [
          "PC staff are considering claimant/beneficiary DIRCON.",
          "The information in question involves prisoner suspension."
        ],
        "steps": [
          {
            "id": "dircon-prisoner-suspension-prisoner-contact-boundary",
            "title": "Keep the prisoner-information FO boundary",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not contact the claimant or beneficiary about the prisoner-suspension information under this exception. When additional information is needed, the source points to the separately cited FO-contact instructions. Those linked procedures, actual prisoner status and any suspension determination are not implemented or decided by this card.",
            "conditions": [
              "PC staff are considering claimant/beneficiary DIRCON.",
              "The information in question involves prisoner suspension."
            ],
            "source": "dircon305",
            "section": "C; D; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:C",
              "GN01070.305:quote:prisoner"
            ],
            "qualifications": [
              "Do not infer prisoner status, automatic suspension, disclosure authority or direct contact with a correctional facility.",
              "GN02607.600 and GN02607.670A.3 are observed unreviewed targets.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Program-specific additional-information procedure and outcome are not established.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-third-party-evidence-controls": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-third-party-evidence-controls",
        "full_route": "pc-direct-evidence-development/dircon-third-party-evidence-controls",
        "entry_conditions": [
          "PC staff are considering a third party as an evidentiary source.",
          "The special no-cost state/local-agency arrangement in D.1.d does not apply."
        ],
        "steps": [
          {
            "id": "dircon-third-party-evidence-controls-correct-source",
            "title": "Identify the correct evidentiary source",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Assure that the third-party contact is the correct evidentiary source. Retain the GN03301.005 disclosure framework and its recorded limits; this card grants no actual disclosure permission.",
            "conditions": [
              "PC staff are considering a third party as an evidentiary source.",
              "The special no-cost state/local-agency arrangement in D.1.d does not apply."
            ],
            "source": "dircon305",
            "section": "D; B; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:D",
              "GN01070.305:quote:evidence"
            ],
            "qualifications": [
              "Consent is conditional on the third party requiring it; this is not a universal consent exemption or a determination that consent is valid.",
              "GN03301.005 A/B is reviewed as a general disclosure framework/examples only; GN03001.025 due-process target remains unreviewed. This draft authorizes no disclosure or adverse-action determination.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN03301.005 directs law/PA/FOIA analysis and refers exception details to later subsections. It is not a complete permission table or a decision that any actual evidence can be disclosed without consent.",
              "Its B.2 tax-return/W2 example prohibits outside disclosure unless specifically authorized by IRS in the stated example. Collection of evidence, third-party release consent and SSA disclosure authority remain different actions.",
              "Historical agency names and examples in the captured page are preserved as source text, not current organizational aliases or new operational systems.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          },
          {
            "id": "dircon-third-party-evidence-controls-adverse-evidence",
            "title": "Preserve due process before payment interruption",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "If evidence leads to adverse action, do not interrupt payment until due process is given. The separately linked GN03001.025 procedure remains outside this selected card; no interruption or adverse-action decision is established.",
            "conditions": [
              "PC staff are considering a third party as an evidentiary source.",
              "The special no-cost state/local-agency arrangement in D.1.d does not apply.",
              "The evidence leads to adverse action."
            ],
            "source": "dircon305",
            "section": "D; B; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:D",
              "GN01070.305:quote:dueprocess"
            ],
            "qualifications": [
              "Consent is conditional on the third party requiring it; this is not a universal consent exemption or a determination that consent is valid.",
              "GN03301.005 A/B is reviewed as a general disclosure framework/examples only; GN03001.025 due-process target remains unreviewed. This draft authorizes no disclosure or adverse-action determination.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN03301.005 directs law/PA/FOIA analysis and refers exception details to later subsections. It is not a complete permission table or a decision that any actual evidence can be disclosed without consent.",
              "Its B.2 tax-return/W2 example prohibits outside disclosure unless specifically authorized by IRS in the stated example. Collection of evidence, third-party release consent and SSA disclosure authority remain different actions.",
              "Historical agency names and examples in the captured page are preserved as source text, not current organizational aliases or new operational systems.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          },
          {
            "id": "dircon-third-party-evidence-controls-conditional-consent",
            "title": "Obtain required consent before forwarding the request",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "If the third party requires a consent statement before releasing information, DIRCON can be used to obtain consent and the request then forwarded to that third party. Do not infer that consent is unnecessary or that an actual statement is sufficient.",
            "conditions": [
              "PC staff are considering a third party as an evidentiary source.",
              "The special no-cost state/local-agency arrangement in D.1.d does not apply.",
              "A consent statement is required before the third party will release information."
            ],
            "source": "dircon305",
            "section": "D; B; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:D",
              "GN01070.305:quote:consent"
            ],
            "qualifications": [
              "Consent is conditional on the third party requiring it; this is not a universal consent exemption or a determination that consent is valid.",
              "GN03301.005 A/B is reviewed as a general disclosure framework/examples only; GN03001.025 due-process target remains unreviewed. This draft authorizes no disclosure or adverse-action determination.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN03301.005 directs law/PA/FOIA analysis and refers exception details to later subsections. It is not a complete permission table or a decision that any actual evidence can be disclosed without consent.",
              "Its B.2 tax-return/W2 example prohibits outside disclosure unless specifically authorized by IRS in the stated example. Collection of evidence, third-party release consent and SSA disclosure authority remain different actions.",
              "Historical agency names and examples in the captured page are preserved as source text, not current organizational aliases or new operational systems.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Consent sufficiency, disclosure limits, due-process procedure and receipt/result are outside this bounded review.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-no-cost-local-arrangement": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-no-cost-local-arrangement",
        "full_route": "pc-direct-evidence-development/dircon-no-cost-local-arrangement",
        "entry_conditions": [
          "A state/local government third party has a special arrangement with the local SSA FO to provide the needed data at no cost."
        ],
        "steps": [
          {
            "id": "dircon-no-cost-local-arrangement-servicing-fo",
            "title": "Use the special no-cost arrangement boundary",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not attempt direct third-party contact for the established special state/local-government arrangement with the local SSA FO to provide the needed data at no cost. The source identifies development through the servicing FO as appropriate under its linked instruction; the existence, terms and completed handoff of a real arrangement remain unestablished.",
            "conditions": [
              "A state/local government third party has a special arrangement with the local SSA FO to provide the needed data at no cost."
            ],
            "source": "dircon305",
            "section": "D; A; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:D",
              "GN01070.305:quote:nocost"
            ],
            "qualifications": [
              "This exception is limited to the established special arrangement, not all government evidence or every no-cost source.",
              "DI52145.001F.1 is observed but unreviewed; no general workers-compensation workflow is adopted.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "A no-cost FO arrangement does not itself decide SSA disclosure authority under GN03301.005. The arrangement target DI52145.001F.1 remains unreviewed.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Existence/terms of the actual arrangement, correct servicing FO and completed transfer remain unverified.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-employer-contact-agreement": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-employer-contact-agreement",
        "full_route": "pc-direct-evidence-development/dircon-employer-contact-agreement",
        "entry_conditions": [
          "PC staff are considering employer contact under DIRCON."
        ],
        "steps": [
          {
            "id": "dircon-employer-contact-agreement-agreement",
            "title": "Verify agreement before employer contact",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Verify that the claimant agrees to employer contact. Do not presume agreement from an application, generic consent, an expired authorization or a documentation step. The linked PC work-CDR responsibilities retain their separate applicability and recorded review limits; this card does not execute that workflow.",
            "conditions": [
              "PC staff are considering employer contact under DIRCON."
            ],
            "source": "dircon305",
            "section": "D; B; E",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:D",
              "GN01070.305:quote:employer"
            ],
            "qualifications": [
              "Agreement is not presumed from an application, generic consent or an expired authorization.",
              "DI13010.023 A/B selected PC work-CDR scope and documentation is now reviewed; linked earnings-verification procedures remain unreviewed. This is not whole-work-review acceptance.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "GN305 D.2 still requires verifying claimant agreement to employer contact. DI023 does not supply a substitute agreement or consent mechanism.",
              "Only an actual PC work-CDR context receives the selected DI023 B.2 documentation refinement; do not impose it on every FO/TSC work report, initial disability intake or SSI monthly wage report.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual claimant agreement, correct evidence/earnings verification, PC case jurisdiction, receipt/result and final outcome remain unestablished.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      },
      "dircon-FO-development-already-promised": {
        "schema": "securitystat.exception-flow/1",
        "record_id": "dircon-FO-development-already-promised",
        "full_route": "pc-direct-evidence-development/dircon-FO-development-already-promised",
        "entry_conditions": [
          "The FO has promised or started development of the necessary information.",
          "PC staff are considering direct contact for that same necessary information."
        ],
        "steps": [
          {
            "id": "dircon-FO-development-already-promised-avoid-duplicate-contact",
            "title": "Do not duplicate the FO’s necessary development",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Do not use DIRCON for the same necessary information that the FO has promised or started to develop. A different FO task on the case alone does not establish this exception.",
            "conditions": [
              "The FO has promised or started development of the necessary information.",
              "PC staff are considering direct contact for that same necessary information."
            ],
            "source": "dircon305",
            "section": "E; A; B",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:E",
              "GN01070.305:quote:fo"
            ],
            "qualifications": [
              "The information must be the same necessary development, not merely another FO task on the case.",
              "The source does not establish the actual direction/class/stage or a blanket elapsed-time rule. Existing .440 directed schedules require their own established predicates.",
              "No automatic clock reset, new request, suppression, case completion or release of payment is inferred.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "DI023 C permits limited PC work-CDR requests for FO assistance and gives a separate servicing FO transfer procedure. It does not erase GN305 E.2 same-information/already-promised-development condition or automatically create a new request.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          },
          {
            "id": "dircon-FO-development-already-promised-request-status",
            "title": "Ask the FO for development status",
            "kind": "ssa",
            "actor": "Agency staff",
            "action": "Request the FO to furnish the status under the separately scoped GN01070.440 follow-up instructions. No universal elapsed-time rule, new development request, automatic clock reset, suppression or completed response is inferred.",
            "conditions": [
              "The FO has promised or started development of the necessary information.",
              "PC staff are considering direct contact for that same necessary information."
            ],
            "source": "dircon305",
            "section": "E; A; B",
            "source_context_refs": [
              "GN01070.305:A",
              "GN01070.305:B",
              "GN01070.305:E",
              "GN01070.305:E",
              "GN01070.305:quote:fo"
            ],
            "qualifications": [
              "The information must be the same necessary development, not merely another FO task on the case.",
              "The source does not establish the actual direction/class/stage or a blanket elapsed-time rule. Existing .440 directed schedules require their own established predicates.",
              "No automatic clock reset, new request, suppression, case completion or release of payment is inferred.",
              "PC staff-directed evidence development only; no customer filing channel, representative selection, benefit determination or operational system permission is established.",
              "A/B geographic and office-role limits remain applicable: United States, Puerto Rico and Virgin Islands, except only authorized OIO international calls; no broad international entitlement is inferred.",
              "E.2 overrides ordinary direct contact when the FO has promised or begun the necessary development. Face-to-face/field-contact and FO final-determination cases retain FO handling.",
              "Selected GN01070.330, DI13010.023 and GN03301.005 contexts are now bounded source-reviewed; their remaining linked targets are unreviewed. None establishes a case-specific permission or an invented procedure. No source/native acceptance, aliases, new graph edges, latency or completed rejoin is established.",
              "DI023 C permits limited PC work-CDR requests for FO assistance and gives a separate servicing FO transfer procedure. It does not erase GN305 E.2 same-information/already-promised-development condition or automatically create a new request.",
              "These are PC staff contact/development instructions, not a customer filing channel or permission to access staff systems.",
              "GN305 geography is United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls; no general international-contact permission is inferred.",
              "Face-to-face/field-contact and FO final-determination matters retain their FO boundary. E.2 blocks DIRCON for the same necessary information when the FO has promised or started its development.",
              "Source conditions can overlap. Choosing one scenario does not establish case facts or displace another applicable contact, representative, privacy or FO-development restriction.",
              "Mail DIRCON means regular USPS mail, not email. Source-described network restrictions do not prove current topology or authorize transmitting actual personal information.",
              "No completed evidence request, system execution, entitlement/payment outcome, new native relationship or successful rejoin is established.",
              "This is PC staff evidence development, not a customer filing channel, eligibility decision or permission to use staff systems.",
              "DIRCON geography is the United States, Puerto Rico and Virgin Islands, except only OIO-authorized international calls. No general international-contact permission is inferred.",
              "Face-to-face/field-contact needs and issues for which the FO makes the final determination retain their FO boundary. A pending initial claim or an allowance on appeal alone does not require FO development.",
              "The E.2 rule for the same necessary information already promised or started by the FO remains applicable. Source conditions may overlap; a selector choice does not establish case facts or displace other restrictions.",
              "Mail means regular USPS mail, not email. The retained source’s network restrictions are not current system topology or authority to transmit personal information.",
              "This sequence adds no customer evidence duty, operational handoff, completed development, entitlement/payment result, automatic rejoin or new native system/graph relationship. Linked procedures retain their recorded review limits."
            ],
            "next": "Only the source-conditioned staff action is described; actual recipient, response, evidence sufficiency and return to the ordinary path remain unestablished."
          }
        ],
        "rejoin": {
          "status": "unknown",
          "automatic_transition": false,
          "unknowns": [
            "Actual promise/start, request direction/class/stage and resulting response are unverified; no automatic transition to an .440 scenario.",
            "The exact case-specific entry/insertion point, actual handoff recipient and successful return to the usual path are unknown.",
            "This source-guided order is editorial; optional/conditional cards are not mandatory serial steps or an executable decision tree."
          ]
        }
      }
    },
    "source_peer_sha256": "d2ab12e407447d41660de0d4bd257ba34bfd666d8aad2d333d704eda7afddb81",
    "unknown_case_entry_handoff_rejoin_preserved": true
  }
}
