Research for community banks and credit unions
Fraud doesn’t stop at one branch. Neither should your visibility.
When a check turns up at a second branch, tellers need to see prior cashing, returned items, and possible duplicate submissions before handing over cash. Halftone is exploring how to bring that evidence and the supervisor’s decision into one case.
Workflow concept · Fictional example
Check exception review
Review the saved decision
Internal decision record
- Amount held
- Duration
- Release date
- Check writer callback
- Hold reason
- Sample suggestion
- Supervisor explanation
Case history
- Teller escalatedWriter history, return evidence and callback outcome attached.
- Decision linked to the check review and teller notes.
Sample · Fictional deposit
Notice of Hold on Check Deposit
Part or all of your check deposit is temporarily unavailable.
- Account ending in
- 7314
- Date of deposit
- November 16, 2026
- Deposit amount
- $485.00
- Amount held
- Funds scheduled to be available
Reason for the hold
The problem
A check can turn up at another branch before the first review is resolved.
A teller may see a possible repeat attempt but still have to call the other branch to learn what was checked or whether someone already placed a hold.
The supervisor needs both attempts and the reason for escalation. Operations needs that same record later to see who decided what and why.
Security principles
Keep check activity inside your institution.
These principles guide the proposed design. Discovery conversations use hypothetical or de-identified examples.
- Institution boundariesKeep branch activity within each institution and collect only approved fields.
- Controlled accessPlan for least-privilege roles, encryption, and agreed retention limits.
- Human decision authorityKeep staff in control and preserve an audit trail of actions and rationale.
Why Halftone
Carry the evidence from the teller to the decision record.
Existing tools can surface check history or flag risk. Halftone’s proposed workflow would give the supervisor both branch attempts, the teller’s notes, and the callback outcome in one case. The same record would show what the supervisor decided and why, including when they chose a different path from the suggested one.
We’re testing whether that handoff still breaks down at banks and credit unions. A future pilot would test whether staff can assemble evidence with fewer manual steps and leave a more complete decision record alongside their existing tools.
Talk to the founder
If you handle checks or review exceptions at a community bank or credit union, we’d like to hear how your team handles a check that turns up at a second branch.
Email the founderWe’ll ask what your systems show, when staff need to call another branch, and where the decision gets recorded. A hypothetical example is enough. Please leave out customer, account, and check details.