SecureOpsGuide

THE PAYMENT CHANGE EXERCISE

From the first request
to the follow-up plan.

A fictional supplier asks your team to change bank details. An urgent message follows. Your team’s decisions shape the discussion that comes next.

01 / Verify

An expected invoice, a familiar thread and new payment instructions.

02 / Authorize

A delivery deadline puts the verification process under pressure.

03 / Respond

Independent confirmation reveals the request was fraudulent.

04 / Contain

An unfamiliar mailbox rule raises questions about account access.

05 / Follow through

The team separates what it knows from what still needs checking.

Export / Keep the record

A decision log, named action owners, due dates and a follow-up review.

What you receive

Before you gather the team

Allow 45–60 minutes, including preparation and debrief. One facilitator shares the screen and records the discussion. Invite finance, IT and an accountable business lead. Role names are sufficient.

Use current desktop Chrome or Edge with JavaScript enabled. No installation, accounts or internet connection are needed for the downloaded exercise. The website is responsive; a shared desktop screen is recommended for running the session.

This is a discussion exercise. Do not send real payments or change live accounts during it. The product does not investigate your systems, assess compliance or provide an independent professional opinion.

A useful record, without an invented score

ILLUSTRATIVE OUTPUT — NOT A CUSTOMER RESULT

Decision
Hold the payment until the known supplier contact confirms the request.
Observation
The team could not identify a backup approver.
Action
Document and test the backup approval route.
Owner / due
Finance lead / date set by the team.

No time-saving percentage or measured effectiveness is claimed. Try the demo to assess the workflow for yourself.

Try the demo →See pricing and license →