Internal controls

Build an approval matrix the team can apply

An approval matrix that maps the amount, the decision, the approver, and the evidence.

Build an approval matrix the team can apply workflow illustration

Build an approval matrix the team can apply

How to approach: Build an approval matrix the team can apply

An approval matrix should tell the team who can approve what, at which amount, and with which evidence. Start with the decision type, the threshold, and the approver. A matrix that only lists job titles does not resolve a real approval. Keep the evidence with the record rather than in a separate log.

Keep the matrix to one page. A complex matrix with overlapping bands will be interpreted differently by each reviewer. Simplicity is part of the control. Review the first few notes together before the process expands.

Define the decision and the threshold

Write the decision in plain language, such as release a payment or sign a contract. Record the threshold and the currency. A threshold without a currency is ambiguous. Use the same format for every handover so the next reader can scan it.

Record the conditions, such as a budget check or a second quote. A condition that is not written will be applied inconsistently. The matrix should name the evidence for each condition. Record the exception and the person who approved it.

Name the approver and the backup

Record the role that approves and the backup role. A named person is easier to audit than a title. The backup should have the same authority and the same evidence requirement. Keep the boundary visible in the place where the work is assigned.

Record the escalation for anything above the top band. A decision that is too large for the matrix should not sit. Name the person and the time frame. Ask whether a new reviewer could act on the record without a conversation.

Record the approval

Write the approval in the system that holds the transaction. An approval that lives only in a chat is hard to find later. Record the approver, the date, and the evidence. Separate what was observed from what was assumed.

Record the exception and the person who approved it. An exception without a record looks like a bypass. The matrix should say who can grant an exception. Ask whether a new reviewer could act on the record without a conversation.

Review the matrix annually

Review the thresholds and the approvers with the finance and operations leads. A role change or a new contract may make the matrix stale. Record the review date. Name the owner in the same line as the action.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.