Unshelled

    From Manual Controls to Control by Design

    Sep 1, 2026

    6 mins read
    From Manual Controls to Control by Design

    In complex businesses, controls are essential.

    Approvals need to happen. Transactions need to be validated. Activities need to be recorded. Access needs to be restricted. Auditors need evidence.

    Traditionally, many of these controls have depended heavily on procedures and people.

    Software gives organisations another option:

    Build the control directly into the way the system works.

    This is what we call control by design.

    From procedure to product behaviour

    Consider a transaction that requires approval.

    In a manual environment, the process might depend on an employee remembering the approval procedure, checking the relevant information and documenting the decision.

    A digital system can make the approval requirement part of the transaction itself.

    The transaction cannot proceed until the appropriate approval happens.

    The system records who performed the action.

    The activity becomes auditable.

    The control isn't simply documented.

    It is embedded.

    The AltTill approach

    This principle was central to AltTill, an in-branch operations management system designed to digitise cash services while embedding existing controls directly into system workflows.

    The platform digitises deposits, withdrawals, transfers and vault movements while incorporating Maker-Checker approval flows, automated validations, real-time audit trails and reporting.

    The system isn't simply recording what happened.

    It is helping determine how the work happens.

    Why this matters

    Embedding controls into software can help organisations:

    • reduce operational errors;
    • improve consistency;
    • strengthen auditability;
    • identify exceptions earlier;
    • improve accountability; and
    • create better visibility for managers.

    AltTill was designed to provide real-time visibility rather than relying solely on end-of-day reconciliation.

    That changes the information available to leadership.

    Compliance should be part of the architecture

    This principle extends beyond branch operations.

    In financial technology, compliance requirements can affect customer onboarding, transactions, reporting, access and monitoring.

    SeaBaas Lite incorporates CBN-aligned regulatory reporting, AML controls and KYC workflows into its platform.

    The point is not to add compliance at the end.

    It is to consider it during product and system design.

    The Omnichannel CRM similarly includes configurable SLAs, compliance tracking, role-based access and audit/activity tracking.

    Good controls shouldn't create unnecessary friction

    There is an important balance.

    A control is only useful if people can follow it consistently.

    Poorly designed controls can create bottlenecks, encourage workarounds and make systems difficult to use.

    That is why control design and user experience need to happen together.

    The objective isn't to add more approvals.

    It is to make the necessary controls clear, consistent and natural within the workflow.

    Control by design is a product philosophy

    When controls are designed into a product, the system becomes part of the organisation's operating model.

    It can enforce rules.

    It can record decisions.

    It can provide evidence.

    It can surface exceptions.

    And it can give management better visibility.

    The best business software doesn't just help people complete work.

    It helps organisations complete that work consistently, safely and intelligently.

    Build technology that works for your business.

    Talk to Unshelled about your next product or digital transformation project.