Skip to main content

Implement Level 2 control in Tenacy

Updated over 3 months ago

In highly regulated environments—particularly in the banking sector—rigorous oversight of internal controls is essential. Implementing Level 2 control through Tenacy provides a structured approach to ensuring traceability, independence, and regulatory compliance in operational processes.

Why Implement Level 2 Control?

Level 2 control addresses a regulatory requirement: to ensure that primary controls (Level 1) have been properly executed, thoroughly documented, and reviewed by an independent party—often for internal audit or supervisory purposes.

Level 1: Execution

  • A team member carries out a recurring task (RT), such as a user access review.

  • A second individual approves or rejects the task within Tenacy.

  • This process ensures that the control was performed on time and that the correct information was provided.

Level 2: Independent Review

A second control layer is added through a new dedicated recurring task assigned to an independent reviewer.

  • This task is scheduled 1 to 2 weeks after the original RT to allow for proper oversight.

  • Typically performed by a CISO or member of the internal control team, the review includes:

    • Verifying that the Level 1 control was properly completed,

    • Approving, commenting on, or escalating as needed,

    • Ensuring full traceability within the platform.

Simplified Oversight with Tenacy

Tenacy allows for planning, documenting, and tracking both levels of control in a unified environment:

  • Staggered task scheduling,

  • Clear role separation,

  • Archived validations and comments,

  • Centralized dashboards for audit readiness.

✅ Best Practices

  • Clearly name recurring tasks to reflect their level (e.g., "Level 2 Review – Access Control").

  • Maintain traceability through comments (via the “Activity Feed” tab) in the Level 2 RT.

  • Use automated reminders if the Level 1 task has not been completed on time.

Did this answer your question?