Internal controls

Keep a delegation of authority record current for the following cycle

A delegation record that names the authority, the limit, the delegate, and the review date Revisit the rule with one current example before the following cycle.

Keep a delegation of authority record current for the following cycle workflow illustration

Keep a delegation of authority record current for the following cycle

How to approach: Keep a delegation of authority record current for the following cycle

The following cycle is a good moment to test Keep a delegation of authority record current for the following cycle against one real case before changing the template. Start with the authority, the limit, the delegate, and the review date. A delegation that is only mentioned in a meeting is not a delegation. Set a review date now so the following cycle has a real checkpoint.

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. A reviewer should not have to search three systems to confirm the authority. Test the revised rule on one live case and record what the team learned. Record the owner and the date beside the action.

Record the authority and the limit

Treat Keep a delegation of authority record current for the following cycle as a control question: what would a reviewer need to repeat the check without asking? A general authority to approve is too broad to audit. The limit should be specific to the decision and the period. Separate what the team observed from what it assumed before publishing the result.

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. A condition that is not recorded will be missed. The delegate should know the condition before acting. Set a review date now so the following cycle has a real checkpoint.

Record the delegate and the acceptance

Treat Keep a delegation of authority record current for the following cycle as a control question: what would a reviewer need to repeat the check without asking? Record that the delegate accepted the authority and understands the limit. An accepted delegation is stronger than an assumed one. Leave the exception and the approver in the record instead of relying on memory.

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. A later review may need to see who granted the authority and when. A delegation without a start date is ambiguous. Test the revised rule on one live case and record what the team learned.

Set the review and the expiry

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. A delegation that never expires may outlive the role. The expiry should be tied to the role or the period. Ask a reviewer who did not prepare the item to restate the conclusion from the evidence.

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. A review without an owner will slip. The review should confirm the limit and the evidence. Separate what the team observed from what it assumed before publishing the result.

Review the record quarterly

Before the next review, write down what Keep a delegation of authority record current for the following cycle is meant to prevent and how the team would notice a gap. Remove the delegations that are no longer active. A record that grows without review becomes a risk. Keep the note with the record so the next reviewer can compare the change.

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.