Skip to content

Issues checklist

Page reviewed

Money at risk. What to do right now

File: t-scams-fraud-money-at-risk.md

This checklist defines the precise implementation changes required to bring the reviewed page to a publishable, internally consistent, governance-compliant state.

All items are written to be diff-verifiable and implementation-ready.

Required changes Optional refinements Verification steps

Scope of this checklist

This checklist addresses the following:

  • Removal of wording that implied guaranteed outcomes
  • Replacement of advice not explicitly supported by authoritative Irish sources
  • Clarification of language to reflect what banks and public bodies can realistically do
  • Spelling and hyphenation corrections from the editorial sweep

No new advisory logic is introduced.
No additional claims are added.

All changes are limited to evidence alignment, wording precision, and clarity improvements.

Required changes

All items in this section must be completed before approval.

1. Correct spelling in the “Say:” script (Step 5)

In section “2. Protect your money”, replace this exact line:

- **Say:** “I think I’ve been scammed. Please freze my account or card. Please stop or reverse any pending payments. Please block new payes.”

With:

- **Say:** “I think I’ve been scammed. Please freeze my account or card. Please stop or reverse any pending payments. Please block new payees.”
2. Tighten the “Say:” script to remove implied guarantees (C3 constraint)

In section “2. Protect your money”, replace the corrected line from item 1 with:

- **Say:** “I think I’ve been scammed. Please freeze my card or online banking. Please try to stop or reverse any pending payments. Please block new payees.”

This ensures wording does not imply guaranteed outcomes.

3. Rewrite “Ask them to” bullet to remove implied certainty

In section “2. Protect your money”, under “Ask them to:”, replace:

- **Stop or reverse** any pending payment or transfer

With:

- **Try to stop or reverse** any pending payment or transfer
4. Remove unsupported “trace” wording

In the details block “You sent money already”, replace:

- Call your bank immediately. Ask if the payment can be stopped or traced.

With:

- Call your bank immediately. Ask if the payment can be stopped or reversed.
5. Replace unsupported bank app fallback instruction (C7)

In section “2. Protect your money”, delete:

If you cannot call right now, open your bank app and look for actions like **freeze card**, **change password**, or **extra sign-in security**.

Insert:

If you cannot get through straight away, keep trying or use another official contact method listed by your bank (for example in your official banking app or on your bank’s official website).

This removes unsupported implied functionality while retaining supported escalation advice.

6. Replace unsupported evidence-handling guidance (C6) in “You sent money already”

Replace the entire admonition block:

!!! important
    - If you want to share evidence with someone you trust, share a screenshot. Do not forward a live link.
    - Do not share screenshots that include one-time codes, PINs, or passwords.

With:

!!! important
    - Save copies of messages, emails, and transaction details (for example screenshots).
    - Do not share your password, PIN, or one-time codes with anyone.
7. Replace unsupported evidence-handling guidance (C6) in “Save evidence (optional). 60 seconds”

Replace the entire admonition block with the same supported version used in item 6.

Ensure wording is identical.

8. Correct link text hyphenation (Step 5)

Replace:

If you are not sure what happened, start with: [2 minute check](../tasks/t-scams-fraud-2-minute-check.md)

With:

If you are not sure what happened, start with: [2-minute check](../tasks/t-scams-fraud-2-minute-check.md)

Optional refinements

These improvements enhance clarity but are not required for publication.

1. Add definition for “one-time code”

After:

If this involves your bank account, card, or a **one-time code**, treat it as urgent.

Insert:

A one-time code is the short code you receive by text message or in an app to approve a sign-in or payment.
2. Add carer-safe instruction block

In section “Do these 3 things first”, insert before “### 1. Stop the contact”:

If you are helping someone else, do not ask them to share a one-time code with you. If possible, sit with them and let them enter it themselves.

Verification steps

  1. Build the site and confirm no rendering warnings.

  2. Run repository link validation for all internal links on the page, including:

    • ../tasks/t-scams-fraud-2-minute-check.md
    • ../tasks/t-scams-fraud-malware-remote-access.md
    • ../reference/r-scams-fraud-report-and-record.md
    • ../reference/r-scams-fraud-scam-types.md
    • ../tasks/t-scams-fraud-prevent-next-time.md

  3. Confirm both updated !!! important blocks render correctly within their details containers.

  4. Confirm all “Say:” script wording matches exactly and contains no typos.
  5. Confirm no implied certainty remains in payment outcome wording.

Governance artefact trace

This checklist was produced as part of the structured SSH governance pipeline.
Associated run artefacts, inspection notes, and gate records are maintained in the repository to ensure traceability and repeatability.

Applied controls include:

  • C3 wording constraint (no implied guarantees)
  • C6 and C7 unsupported claim removal
  • Step 5 editorial compliance enforcement
  • Diff-verifiable instruction standard (Rule 8)
  • Profile B safe-wording discipline

No advisory expansion or new interpretation was introduced.

Approval status

Step 12 – Issues checklist
Status: Pending implementation and verification