Skip to content
Daniel TorresConnect

Case study 02 · Weekly control status tracker

DRIFT

What moved since last Monday, measured and briefed in one run.

v6.1 · runs the Monday progress report

Film shows DRIFT running on two weeks of synthetic exports for a sample system.

01Program challenge

During a Rev. 4 to Rev. 5 transition, progress is reported every Monday. That meant comparing an earmarked planned-control baseline against fresh eMASS exports by hand, and rebuilding the totals since the transition began each week.

Leadership needed two numbers every week, progress since last Monday and progress since the start, with the controls behind them named. A recount from scratch each week invited errors and ate the morning.

02Leadership decision

Requirements
Defined the exact signals to track for each export: Planned to Implemented for controls, compliance changes at the assessment-procedure level, and POA&Ms opened and closed in transition scope.
Stakeholders
Program leadership receives the Monday brief; the authorization team uses the changelog and report to work the gaps.
Trade-off
Kept the planned-control baseline as the core of the tool and layered procedure and POA&M tracking on top, rather than broadening it into a general dashboard.

Key decisions

A snapshot chain instead of re-uploading history

Each week’s file carries the ledger forward, so one file gives both the week-over-week delta and the total since the start.

Avoid counting the same progress twice

Test results drive assessment-procedure progress under controls that are still planned, rather than repeating the Planned to Implemented signal.

Data quality rules built in

Estimated completion date requirements depend on implementation status, and a date on a Not Applicable control is flagged as an error to correct.

Name the controls, not just the count

The one-slide report lists the controls that newly entered Planned, so leaders can act on it.

03Engineering solution

  • Five sources: the planned-control baseline, the Implementation Plan export, test results, the POA&M export and last week’s snapshot.
  • A Monday wizard that walks the run step by step.
  • A snapshot chain that carries the running ledger forward, so only the current exports are uploaded each week.
  • Outputs: a one-slide PowerPoint brief, an Excel changelog and an HTML delta report.
  1. Step 1

    Load this week’s exports and last week’s snapshot

  2. Step 2

    Review posture, movement, currency and POA&M flow

  3. Step 3

    Check regressions first

  4. Step 4

    Build the slide and save this week’s snapshot

04Operational impact

Compliance posture, net movement, 12-month assessment currency, reassessments coming due in 30, 60 and 90 days, and POA&Ms past due, opened and closed, from one run.

Regressions surface at the top of the control list so they are addressed before anything else.

Planned control tracking is DRIFT’s primary use, and the weekly snapshot makes each Monday a repeat of the same short process.