An LPA schedule needs to answer five questions: which process will be checked, by whom, at which layer, on which shift, and when? A calendar full of assignments is only useful if the work can be completed and gaps are easy to see.
Set frequency from the process risk and applicable requirements, then check the workload against the people and time available. Choose the scheduling tool by the coordination you need, not the number of employees you have.
If you are still choosing the scope, questions and responsibilities, use How to set up an LPA program. This guide starts with those decisions in place and turns them into a working schedule.
1. Gather the inputs before assigning dates
Use one agreed list of processes, layers and people. Otherwise, different versions of the plan can leave a shift uncovered or assign someone who is unavailable.
| Input | What to record |
|---|---|
| Processes and locations | The lines, work areas and process checks included in the program |
| Audit layers | Which organizational levels need to participate |
| Required frequency | The agreed cadence and the requirement or risk decision behind it |
| Operating calendar | Working days, shifts, shutdowns and planned changes |
| Auditors | Eligible people, their shifts and known availability |
| Time per audit | Time to reach the area, complete the checks and record evidence |
| Schedule owner | The person who reviews conflicts, absences and overdue work |
Keep the schedule tied to the approved checklist. If the checklist changes substantially, measure the time again before adding more assignments.
2. Set frequency by requirement and risk
There is no single daily, weekly and monthly pattern that fits every LPA program. Start with the requirements that apply to your operation and customers. Then consider process changes, the consequence of a missed control and the history of repeat findings.
A recently changed process may need closer attention than an established process with consistent results. That decision should be recorded and reviewed by the program owner. Reducing frequency should be a considered decision, not a way to make an overloaded calendar look manageable.
The schedule should make participation across layers visible. It should also cover the shifts on which the process runs. Strong day-shift completion does not tell you whether the night shift has been checked.
3. Check the workload before publishing the schedule
Count the assignments, not just the checklists. One short audit repeated across several lines and shifts can create a substantial workload.
For each group of assignments:
Weekly audit time = number of assignments × minutes per audit.
Here is an illustrative calculation for one line operating two shifts over five days. The frequencies are assumptions for this example, not a recommended standard.
| Example assignment | Audits per week | Minutes per audit | Weekly time |
|---|---|---|---|
| One check on each shift each working day | 10 | 10 | 100 minutes |
| Two supervisor checks during the week | 2 | 15 | 30 minutes |
| One manager check during the week | 1 | 20 | 20 minutes |
| Total | 13 | 150 minutes |
That is 2.5 hours of audit work. Allow additional time for travel, discussing findings and follow-up. If one person receives most of those assignments, the total alone can hide a capacity problem. Check the distribution by person, layer and shift.
4. Resolve coverage and availability gaps
Before releasing the schedule, look for these problems:
- An assignment falls outside the auditor's working hours.
- A process is scheduled for a check while it is shut down.
- Several audits fall on one person on the same day.
- One shift or layer has no planned coverage.
- Leave or training removes the only eligible auditor for an area.
- A recurring assignment keeps checking the same area while another is missed.
Agree who can reassign work and how the change will be recorded. Choose auditors who understand the process and the checks they are performing. Apply the role and independence rules required by your program; do not assume that supervisors must always be excluded from auditing their own areas.
5. Agree what happens when an audit is missed
A missed audit needs a visible status and a decision. Quietly moving its date can hide the original gap.
The schedule owner should review the reason, decide whether reassignment or rescheduling is appropriate, and retain a record of the change. Follow the site's response process when the missed coverage creates an immediate concern.
Keep two types of overdue work separate:
- An overdue audit: the planned check has not been completed.
- An unresolved finding: the audit took place, but a failed check still needs action.
Reassigning an audit does not resolve a finding. Both need an owner and follow-through.
6. Choose the tool by the work it needs to manage
Choose the scheduling tool by the coordination your program needs. A small manufacturer with multiple shifts, frequent checks and recurring findings may have demanding scheduling needs. Employee count does not capture that work.
A spreadsheet can document a schedule. Keeping assignments, availability, evidence and follow-up aligned still takes coordination, whether that is handled manually or through other connected tools.
When evaluating software, test whether it makes these tasks easier:
- Set recurring rules for the relevant layers, locations and shifts.
- See the projected workload before releasing assignments.
- Find coverage gaps and review conflicts.
- Keep completed audit records and their supporting evidence accessible.
- Review unresolved findings without rebuilding a separate tracking sheet.
Compare the subscription and setup cost with the coordination effort in your current process. Use your own volumes and timings rather than a promised savings figure.
How Audera supports schedule planning
Audera supports calendars, shifts, locations, audit levels and scheduling rules. The schedule simulator lets you inspect projected audit volume and coverage before committing the schedule. Review the plan by calendar, layer or auditor, then adjust the rules where needed.
After execution, recorded answers and attachments support the audit record. Unresolved failed checks can be reviewed with responsible contacts, days open and configured escalation. Those findings remain a separate follow-up responsibility after the scheduled audit is complete.
For a useful demonstration, bring one line's shift pattern, the layers involved and the frequency you want to test. Ask to see how the proposed workload is distributed and how gaps are identified.
Review the first schedule before expanding it
Run the plan through a complete operating cycle that includes the shifts you intend to cover. Compare planned work with completed work by layer and shift, and ask auditors where the plan was difficult to follow.
Review actual time per audit, late assignments, uncovered areas and repeated reassignments. Adjust the rules and capacity before extending the schedule to more lines.
For the broader decisions about questions, ownership and rollout, return to the LPA program setup guide.
