Why SLA Reports Need the Policy That Applied at the Time
Snapshot the SLA policy on each ticket so later reports explain performance against the commitment that actually applied.
Read Why SLA Reports Need the Policy That Applied at the Time →← Back to blogTag Archive
Auditability
Browse 23 articles tagged Auditability across approvals, auditability, plugins, and controlled AI operations.
Browse tags
Operations30Auditability23approvals11Case Management10ai-triage9finance-controls9Field Service8action-providers7ai-governance7ticketing7Reporting6SLA5Workflow5workflow-orchestration5evidence4Guides4maker-checker4plugins4Product Updates4risk-controls4security4triage4ai3audit-trail3compliance3kyc3queue-management3reconciliation3Access Control2architecture2Attachments2authentication2authorization2change-management2email2eu-ai-act2extensibility2governance2integrations2iso-420012nist-ai-rmf2platform-architecture2status-management2ai-assistance1api1api-design1assets1auth1brute-force-protection1customer-operations1customer-support1Dashboards1Data Management1decisioning1defense-in-depth1developers1engineering1exception-handling1exceptions1implementation1ingestion1integration1legal-discovery1logging1mcp1metrics1Mobile1mobile-operations1monitoring1multi-tenant1oidc1Operations Management1Performance1platform1Policy Management1product-update1Public Forms1refunds1Reliability1reopen1reprocessing1runtime-control1saas1Search1segregation-of-duties1service-history1Sites1support1support-operations1technical-communication1ticket-routing1tickets1tutorials1unified-triage1workflow-design1
Immutable Payment Audit Trails Need Workflow Context
An immutable payment file is not enough for legal discovery. What workflow context an audit trail has to carry alongside it.
Read Immutable Payment Audit Trails Need Workflow Context →Four-Eyes Principle, Maker-Checker, and Segregation of Duties: What Actually Differs
Four-eyes, maker-checker, dual control, and segregation of duties are related but distinct. What changes in workflow design for each.
Read Four-Eyes Principle, Maker-Checker, and Segregation of Duties: What Actually Differs →Governance, Rollback, and the Implementation Order That Works for KYC and Reconciliation
Governance, rollback, and the implementation order that works when adding AI to KYC and reconciliation case handling.
Read Governance, Rollback, and the Implementation Order That Works for KYC and Reconciliation →Architecture, Monitoring, and Where Self-Tuning Belongs in KYC and Reconciliation
How to architect and monitor AI case management for KYC and reconciliation, including where self-tuning belongs and where it does not.
Read Architecture, Monitoring, and Where Self-Tuning Belongs in KYC and Reconciliation →AI Case Management for KYC and Reconciliation Starts With the Case, Not the Model
AI case management for KYC and reconciliation starts with the workflow, not the model. What to fix before adding intelligence.
Read AI Case Management for KYC and Reconciliation Starts With the Case, Not the Model →Audit Logging for Compliance Operations
What compliance operations teams should record in an audit log so a reviewer can reconstruct a decision without asking anyone.
Read Audit Logging for Compliance Operations →What Is New in Latch: April and May 2026
A customer-facing product update on recent Latch improvements across ticket queues, SLA visibility, ticket filtering, governed API access, and operational ti...
Read What Is New in Latch: April and May 2026 →Authorization Logic Audits for Case Management
Case management authorization should support flexible rules, numeric thresholds, and audit-ready evidence on every sensitive action.
Read Authorization Logic Audits for Case Management →What Is a Plugin Action?
A plugin action runs on an external system from inside the ticket with role checks, governed approvals, and immutable audit logging.
Read What Is a Plugin Action? →How Four AI Governance Frameworks Handle Approval vs. Runtime Evidence
How the EU AI Act, ISO 42001, and NIST AI RMF treat approval evidence, and where runtime evidence fills the gap they leave.
Read How Four AI Governance Frameworks Handle Approval vs. Runtime Evidence →Governance-First Approval Systems for AI: What They Prove, What They Miss, and Where Runtime Evidence Fills the Gap
What governance-first approval systems for AI prove, what they miss, and where runtime evidence closes the remaining gap.
Read Governance-First Approval Systems for AI: What They Prove, What They Miss, and Where Runtime Evidence Fills the Gap →The Runtime Control Layer: What This Category of Software Is and Why It Exists
Ticket workflows need a control layer between the suggestion and the action. What that layer does, and why existing tools leave it out.
Read The Runtime Control Layer: What This Category of Software Is and Why It Exists →AI Raises the Value of Control-First Software
AI increases the value of control-first case platforms that combine governed execution, immutable audit logs, and cross-system integration.
Read AI Raises the Value of Control-First Software →Why Approval, Auth, and Audit Logic Must Stay in the Core
Why approval, authentication, and audit logic belong in the platform core rather than in plugins that can be swapped or misconfigured.
Read Why Approval, Auth, and Audit Logic Must Stay in the Core →Using ChatGPT Safely for Refunds and Customer Offers
How to use ChatGPT for refunds and customer offers without handing it the ability to act. Where the approval gate has to sit.
Read Using ChatGPT Safely for Refunds and Customer Offers →How to Run Four-Eyes Control Without Inbox Approvals
Replace forwarded-email approvals with case-centric four-eyes control that keeps role boundaries, denied attempts, and execution outcomes visible.
Read How to Run Four-Eyes Control Without Inbox Approvals →What Auditors Need to See in a High-Risk Approval Workflow
High-risk approval workflows need origin, authority, denied paths, outcomes, and case-linked evidence in one immutable audit log.
Read What Auditors Need to See in a High-Risk Approval Workflow →AI Triage Needs a Control Plane, Not Just Better Prompts
AI ticket triage is not a prompt problem. What a queue needs around it, ticket routing, approval gates, execution records, and a model you host yourself.
Read AI Triage Needs a Control Plane, Not Just Better Prompts →Case Records Should Be Systems of Action, Not Just Systems of Record
A case record that only stores notes is a record store. What changes when it can also initiate work and prove execution.
Read Case Records Should Be Systems of Action, Not Just Systems of Record →Audit Trails That Answer the Real Questions
An immutable audit log is only useful if it answers real questions. What to record so reconstructing a decision does not depend on memory.
Read Audit Trails That Answer the Real Questions →Finance Exception Handling Needs Four-Eyes Control
Why finance exception handling needs four-eyes control, structured evidence, and audit-ready review before unauthorized actions slip through.
Read Finance Exception Handling Needs Four-Eyes Control →What to Log When Operators Trigger External Actions
What to record when an operator triggers an external action, so the audit trail still answers the question months later.
Read What to Log When Operators Trigger External Actions →