Internal controls

How current is the delegation of authority record?

A proposed protocol for measuring whether delegations have a limit, an acceptance, and a review date.

This research is general operational information, not legal, tax, accounting, employment, benefits, privacy, cybersecurity, insurance, or financial advice.

How current is the delegation of authority record? evidence review illustration

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks how current the delegation of authority record is. The result would describe the record, not the delegate. Record the exception and the person who approved it.

The protocol does not measure whether the delegation was useful. It measures whether the authority was documented and reviewed. Record the exception and the person who approved it. Keep the original note beside the corrected version.

Population and unit of analysis

Define the population as delegations active during a stated period. The unit is one delegation, with the authority, the limit, the delegate, the acceptance, and the review date recorded. Update the template when the same question appears twice. A short note with four fields is easier to use than a long narrative.

Link the delegation to the role so the same delegation is not counted twice. A delegation that covers several roles should be recorded per role. Ask whether a new reviewer could act on the record without a conversation. Update the template when the same question appears twice.

Definitions and measures

Define currency as a review within the policy window and an expiry in the future. Define completeness as the presence of the limit and the acceptance. A control that depends on memory is not yet a control. Test the rule on one real transaction before applying it to the run.

Report currency and completeness separately. A current delegation can still be incomplete. Name the owner in the same line as the action. A short note with four fields is easier to use than a long narrative.

Evidence standard

Use the delegation record and the approval matrix. A record without the limit is weak. The reviewer should be able to state the authority in one sentence. Record the exception and the person who approved it.

Record the date and the reviewer. A later review may need to see what was checked. Keep the boundary visible in the place where the work is assigned. Test the rule on one real transaction before applying it to the run.

Sampling and collection

Use a census of the delegations. If sampling is necessary, stratify by role. A sample that excludes the senior roles may miss the biggest exposure. Ask whether a new reviewer could act on the record without a conversation.

Pilot the review on a few records and compare the reviewers. Clarify how a temporary delegation is treated. Ask whether a new reviewer could act on the record without a conversation. Write the deadline as a date and a local time.

Analysis and reporting

Report currency and completeness by role. Show the delegations without a review date. Present the results as a description of the record, not a judgment about the delegate. Use the same format for every handover so the next reader can scan it.

Limits and sources of error

The delegation may be recorded in a different system. State the systems included. The role may have changed without the record being updated. Test the rule on one real transaction before applying it to the run.

Review cadence

Repeat the review after a role change or at the same interval each quarter. Compare the same roles. Assign the follow-up to the controller and set a date. Write the deadline as a date and a local time.

Useful internal handoffs

Sources