Audit Schedule: Keep the Gains Alive Long After Handover

The Audit Schedule tool does one job. In the product's own words, it schedules the recurring audits that sustain assurance over the improved process. You list each audit, say what type it is, how often it runs, who owns it and when it is next due. The tool puts them in date order and tells you what the set looks like as a whole.

That matters because the Sustain phase is where most improvement work quietly fails. The team is disbanded. The sponsor moves on. The new standard holds for a few weeks on goodwill, then drifts back. Audits are the mechanism that replaces goodwill with a routine. The schedule is the record of that routine.

Use the tool at handover, when you are agreeing what assurance stays in place after the project closes. Then use it again every quarter as a review artefact. The second use is the one people skip, and it is the one that tells you whether the plan is real.

Everything below uses the sample data that ships with the tool. It is a fictional case, included so you can see the calculation behave before you load your own audits. Treat the numbers as illustration, not as a benchmark.

The case is an accounts payable process that has been through an improvement cycle. Five audits are listed. A layered process audit run weekly by the AP Manager. A Kamishibai audit run weekly by the Supervisor. A 5S audit run monthly by the AP Clerk. An MSA revalidation run quarterly by the Black Belt. An SOP adherence audit run monthly by the AP Manager.

The mix is deliberate. Two audits check compliance with the standard. One rotates through a board of short checks. One looks at the physical workplace. One revalidates the measurement system that the whole improvement was judged on. Between them they cover behaviour, environment and data.

Three fields are mandatory, marked with an asterisk in the table. Audit, Owner and Status. The tool will not let you log an audit with no name or no owner, which is the correct constraint. An unowned audit is not scheduled, it is a wish.

Type and Frequency are free descriptors. In the sample they carry real meaning. Type is Compliance, Rotating, Workplace or Measurement. Frequency is Weekly, Monthly or Quarterly. Keep your vocabulary small and consistent so the cadence summary groups cleanly.

Next Date is the field that does the most work. It is not the date the audit was agreed. It is the date the next instance falls due. Every time an audit is completed, that date moves forward by one cycle. If nobody moves it, the tool starts to show you something useful, which the next section covers.

The tool returns six things. Five audits in total. The first audit due is the layered process audit on 2025-06-09. Four distinct owners. Two of the five run weekly or more often. And five are past their date.

The supporting line fills in the detail. Next dates run from 2025-06-09 to 2025-08-01. Cadence breaks down as Weekly 2, Monthly 2, Quarterly 1. Owners break down as AP Manager 2, Supervisor 1, AP Clerk 1, Black Belt 1. The tool also offers an AI review that explains the result in prose if you want a second reading.

Take the owner spread first. Five audits across four owners, with the AP Manager holding two. That is a reasonable load. If one name had held four of the five, the schedule would be a single point of failure dressed up as a system.

Then take the cadence. Two weekly, two monthly, one quarterly. The weekly pair are the frontline checks that catch drift early. The quarterly MSA revalidation is slower by design, because a measurement system does not degrade in a fortnight. A schedule with everything set to quarterly is not assurance, it is a calendar entry.

Five audits are past their date. All of them. Every status still reads Scheduled. Nothing has been marked complete and nothing has been rolled forward.

That combination is the tell. A healthy schedule has a rolling edge. Dates move forward as audits are completed, so at any moment only the imminent ones sit near today. When every next date is behind you and every status still says Scheduled, the schedule has stopped being maintained. The audits may or may not be happening in the workplace, but the assurance record is not being kept, and an assurance record that is not kept provides no assurance.

The date range reinforces it. Next dates run from 2025-06-09 to 2025-08-01. That is a spread of under two months across all five audits. Weekly audits should not still be sitting on a date from months back. One weekly audit left untouched produces many missed instances, not one.

So the first question the tool forces is not whether the process has drifted. It is whether anybody is still looking.

The first decision is reassignment. Four owners hold five audits. If one of those roles is vacant or overloaded, you move the audit rather than let it lapse. The tool makes the load visible in one line.

The second is cadence tuning. Two of five run weekly or more often. After a sustained period of clean results, you may reduce a weekly check to monthly. That decision should be made deliberately and recorded, not made by quietly skipping weeks.

The third is scope. The five audits in the sample cover compliance, rotating checks, workplace condition and measurement. If an audit type is missing for a risk you care about, the gap shows when you read the five rows together. Four audits of the same type is not coverage.

The fourth is escalation. Five past due is not a scheduling problem. It is a governance problem, and it belongs in front of the process owner with the schedule attached as evidence.

The most common mistake is loading the schedule once at handover and never touching it again. The tool then becomes a historical document rather than a live control. The sample data shows exactly what that looks like from the outside.

The second mistake is stacking audits onto one owner because that person is reliable. Reliability is not capacity. Spread the load across roles the way the sample does, with no owner holding more than two.

The third is over-scheduling. Weekly audits cost time. Two weekly audits out of five is a workable ratio. Set everything to weekly and the first thing to lapse will be the audit that mattered most.

The fourth is treating Status as decoration. Status is the field that separates a plan from a record. If every row reads Scheduled forever, nobody can tell a well-run process from an abandoned one.

The Audit Schedule tool records intent and timing. It does not record findings. Nothing in the five rows tells you whether the layered process audit found anything, how many non-conformances the 5S audit raised, or whether the MSA revalidation passed. You need a separate record for results.

It does not verify that an audit happened. A status can be changed by anyone with access. The tool reports what you typed. If the discipline to update it honestly is missing, the schedule will look tidy while the process drifts.

It does not judge whether your cadence is correct. Weekly 2, Monthly 2, Quarterly 1 is a description, not a recommendation. The right frequency depends on how fast your process degrades and how costly a failure is, and neither of those is in the data.

It will not tell you whether the improvement itself is still delivering. Audits confirm the standard is being followed. They do not confirm the standard still works. For that you need the measures from the Control phase, running alongside this schedule. Used together, the schedule tells you the checks are happening and the measures tell you they are worth doing.