Manuals and procedures · Lesson 25 · Approx. 7 minutes including practice
Maintenance schedules
Schedules link approved tasks to intervals and operating conditions. Keep the requirement source visible and distinguish calendar, running-hour and condition-based triggers. Resolve conflicts with the technical owner rather than choosing the longest interval.
Step 1: OEM source
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Preserve the source of each interval
A maintenance schedule links tasks to approved triggers such as elapsed time, operating hours, cycles or condition. Those triggers are not interchangeable. Record the source, applicable configuration and relevant operating conditions. Where multiple triggers apply, the technical owner should establish how they interact. Do not extend an interval because another machine uses a longer one, or infer maintenance requirements from a generic equipment category.
Prepare and check the work
Separate the task description from the interval, responsible role, required record and reference procedure. Check consistency with supplier information and resolve conflicts with the nominated authority. Distinguish planned tasks from completed maintenance evidence. A blank schedule row is a requirement to perform work, not proof that work occurred. Make revision and applicability visible so older schedules are not accidentally used for a modified machine.
Worked example · demonstration only
A supplier interval is stated in running hours, but the draft schedule labels it months. Correct the unit from the approved source and review other entries for the same transcription issue. Do not convert operating hours to calendar time using an assumed duty cycle.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Prepare a schedule template with task, source, interval, condition and record fields. Before starting, write down the question the finished record should answer and identify the source information you would need on a real job. Keep a separate list of missing inputs. Prepare a first draft, then compare it with the topic-specific checks above. Ask another person to follow your references without explaining them verbally. Record where they hesitate, what information they cannot locate and any different interpretation. Keep a brief review log with four columns: observation, proposed action, responsible reviewer and closure evidence. Revise the example and repeat the information-finding check. Your evidence of completion is the revised demonstration record plus that log, not simply time spent reading. Do not upload client information to the academy or practise on operating equipment.
What good completion looks like
A useful result can be understood by someone who did not prepare it. They can identify its purpose, applicable item, source and review status, and they can distinguish confirmed information from unresolved questions. Pay particular attention to this failure mode: Do not copy service intervals from superficially similar equipment. Check the output in the format the recipient will use. A native file, spreadsheet and exported PDF can expose different problems. Keep the source revision and the issued output linked, and record any limitations of the handover. On a real project, follow the customer's authorised checking and approval arrangements before the information is used. The knowledge check below tests understanding of this lesson; it does not assess practical competence or authorise regulated work.
Practical workflow
- Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
- Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
- Ask the nominated reviewer to check technical meaning. Capture the response, resolve comments and issue only under the agreed document-control process.
Review checklist
- Can another reader identify the source and applicable revision?
- Are assumptions and unresolved decisions clearly recorded?
- Is there evidence of the required review before issue?
Educational material and demonstration examples. Not accredited training, practical competency assessment or authority to perform regulated work. Use current approved sources and your responsible technical authority on real projects.