Clear Path Solutions is a demonstration workspace, open to anyone and read-only. The documents behind it are a real consulting engagement; the states, conflicts and supersessions are what OIDA derived from them.Create your own workspace

← All sources
Source

Observation 003 — audit workflow

Ingested 57 min ago by yuki.tanaka@meridian-labs.com. The text submitted to this workspace, kept exactly as it arrived.
Typeobservation-noteAuthority0.70Referenceclearpath-observation-003Locator02-subject/observation-003-audit-workflow.mdEvent date2 Oct 2025Ingested23 Oct 2026Records supported6Length4276 charactersContent hashsha256:1eff2816d810…PermalinkNot recorded
# Observation 003: Audit Workflow Review **Date:** October 2, 2025 **Observer:** Marcus Webb (Lead Consultant, Meridian Labs LLC) **Location:** ClearPath Solutions Inc., Florence, Italy **Duration:** 3 hours 45 minutes **Present:** David Park (CTO), Marco Fiore (Audit Team Lead), two junior auditors --- ## Context This observation focused on the audit and quality assurance (QA) workflow that underpins ClearPath's core deliverable production. The audit workflow is positioned as a critical gate before client reports are finalized and signed off. Understanding this process is essential to identifying bottlenecks in the overall engagement cycle. ## Overview of the Workflow The audit workflow consists of five sequential stages: 1. **Initial Submission**: Completed report drafted by consultant and submitted to audit queue 2. **Assignment**: Audit team lead (typically Marco Fiore or Laura Galli) reviews and assigns to available auditor 3. **Review & Markup**: Auditor checks for compliance gaps, formatting, and completeness 4. **Revision & Resubmission**: Consultant incorporates feedback and resubmits 5. **Final Sign-off**: CTO (David Park) provides final approval before client delivery ## Key Observations ### Queue Depth At the time of observation, there were 14 deliverables waiting for David Park's final sign-off. Of these, 8 had been in the queue for more than 5 business days. David acknowledged the backlog but attributed it to concurrent product roadmap work. He indicated that sign-off typically requires 20–40 minutes per deliverable, depending on complexity. ### Data Collection Gaps A significant challenge emerged early in the observation: **it was not possible to measure the actual time spent at each stage of the audit queue**. ClearPath does not track this at a granular level. When asked how long the average report spends in the audit phase before reaching his desk, responses varied sharply: - Marco Fiore estimated: 3–4 business days - Laura Galli estimated: 6–8 business days - One junior auditor estimated: 2–3 days This represents a factor-of-3 variation with no objective data to reconcile the discrepancy. David Park noted that they have discussed implementing audit metrics in previous years but "never quite got to it." ### Workflow Interruptions During the observation period, three instances of re-work were noted: 1. A report submitted for sign-off was returned for minor formatting corrections (1 hour rework) 2. An auditor realized mid-review that a compliance standard referenced in the report had been updated in Q3 2025, requiring the consultant to verify applicability (2.5 hours rework) 3. A consultant resubmitted a report that had been rejected, but the comments from the initial audit were not accessible via shared drive — the auditor had to recreate feedback from memory ### Positive Aspects The audit team demonstrated competence and attention to detail. No compliance errors slipped through during the observation period. The feedback provided was specific and actionable, and consultants appeared to respond quickly to revision requests. David Park's final sign-offs were thorough and appeared to catch edge cases. ## Frustrations and Informal Feedback During a brief aside with David, he mentioned: "The backlog is frustrating, but so is not knowing where things actually are in the pipeline. I know there are problems, but I can't quantify them." Marco Fiore echoed similar sentiment: "We do good work, but we're flying blind on timing. If I could measure turnaround accurately, I'd know where to hire or where to streamline." ## Preliminary Observations 1. The audit workflow has no real-time visibility into cycle time or WIP (work-in-progress) 2. Team leaders estimate cycle times very differently, suggesting either inconsistent execution or inconsistent understanding of the process 3. Rework is occurring, at least in part, due to external changes (standard updates) that are not being tracked systematically 4. The process is functional and produces quality output, but lacks transparency for process improvement --- **Next Steps:** Recommend gathering time-tracking data for a 2-week period to establish baseline metrics.

What was taken from it

Show all
“At the time of observation, there were 14 deliverables waiting for David Park's final sign-off.”✓ Verified · Characters 1270–1365, found at the stored offsetsHighlight this oneAssertedFourteen deliverables were waiting for the CTO’s final sign-off, eight of them for more than five business days.
“it was not possible to measure the actual time spent at each stage of the audit queue”✓ Verified · Characters 1707–1792, found at the stored offsetsAssertedThe time a deliverable spends at each stage of the audit queue cannot be measured: ClearPath does not track it.
“- Marco Fiore estimated: 3–4 business days”✓ Verified · Characters 1967–2009, found at the stored offsetsHighlight this oneAssertedThe audit team lead estimates the audit phase at three to four business days.
“- Laura Galli estimated: 6–8 business days”✓ Verified · Characters 2011–2053, found at the stored offsetsHighlight this oneAssertedThe controls assessment lead estimates the same audit phase at six to eight business days.
“- One junior auditor estimated: 2–3 days”✓ Verified · Characters 2055–2095, found at the stored offsetsHighlight this oneAssertedA junior auditor estimates the same audit phase at two to three days.
“An auditor realized mid-review that a compliance standard referenced in the report had been updated in Q3 2025, requiring the consultant to verify applicability (2.5 hours rework)”✓ Verified · Characters 2513–2692, found at the stored offsetsHighlight this oneAssertedNothing tracks changes to external compliance standards, so a mid-review update caused two and a half hours of rework.