Protecting community funding starts with clear responsibilities

What the review found

The Government Accountability Office published a review of fraud-risk management in Older Americans Act programs (opens in a new tab) in September 2024. Discussing the federal agencies examined, its summary said:

“they haven't assessed fraud risks”

— U.S. Government Accountability Office, September 2024

The report concerned agency risk-management practices. It was not a finding that every local provider had committed fraud. The 2024 findings concerned the agencies’ approach to identifying and managing risk; later progress on the recommendations is a separate question.

The practical question for community leaders is how to protect resources through responsibilities people can understand and carry out.

Follow a delivery through the organization

Imagine a hypothetical meal program receiving a regular delivery. A coordinator checks the boxes, another colleague handles invoices, and a manager approves payment.

The arrangement may work well. It may also depend on assumptions: someone believes another person checked the quantity, while that person thought the check happened when the order was placed.

A useful review begins with the actual sequence. Who requested the goods? Who confirmed that they arrived? Who can explain a difference? These are ordinary questions about stewardship, not accusations about colleagues’ intentions.

Match the check to the risk

Not every transaction needs the same level of review. The appropriate finance and governance leads should consider the size, frequency, complexity, and consequences of the activity.

The goal is a process that catches meaningful problems without making everyday work needlessly difficult. A small program may need different arrangements from a large organization, while still making responsibilities clear.

Document the decisions in language staff can use. If the policy only makes sense to the person who wrote it, the organization has not yet created a dependable routine.

Make exceptions visible

A missing delivery, an urgent purchase, or an unfamiliar supplier can be legitimate. It can also bypass the usual checks if nobody knows how an exception should be handled.

Agree who can authorize an exception, what information should accompany it, and how it will be reviewed afterward. Colleagues should not have to choose between serving people and concealing a departure from the normal process.

In our example, the coordinator might need to arrange a replacement delivery promptly. A clear exception route allows the team to respond while preserving an account of what happened and who made the decision.

Give concerns a proper route

People need to know where to raise a question about a payment, a record, or an unusual request. That route should be appropriate to the concern and should not rely solely on approaching the person whose decision is in question.

Distinguish a request for clarification from an allegation. Investigations and reporting decisions belong with the responsible qualified people.

Staff training can use ordinary examples without implying that suspicion is the default relationship between colleagues. The purpose is to make it easier to notice, document, and address a problem before it becomes a larger one.

Protect participants from the organization’s paperwork

Good stewardship should support continuity and trust. It should not make participants prove the organization’s purchasing decisions or disclose unnecessary personal information to resolve an internal discrepancy.

Ask which records are actually needed and who should handle them. Keep service access questions separate from supplier and payment controls wherever the applicable arrangements allow.

People receiving support can still contribute observations about the service itself. A missing meal or changed delivery is relevant feedback. They should have a clear contact for that experience without being drawn into an organizational investigation.

The place for genus today

Configured genus care apps and care walls can share appropriate service updates and prepared program information with an audience. That can help people understand an interruption or find the correct contact.

genus is not an accounting system, a fraud-detection service, or evidence that funding requirements have been met. Financial controls and restricted records belong in the organization’s authorized processes.

Our interest is in the connection between dependable operations and dependable service. Clear communication cannot replace a financial control, but it can help keep the people affected informed while the responsible team does its work.

Check the arrangement when roles change. A dependable process should survive a colleague’s holiday or departure, with an authorized substitute who understands what they are being asked to approve.

A question for the next governance review

If a routine transaction does not go as expected, can each person explain their responsibility—and find an appropriate route to ask for help?