DoAssignment study guide

A5.3 · Plan preventive computer maintenance

Learn to plan preventive computer maintenance through clear examples and targeted practice.

Ontario Grade 10 Computer Science

Understanding Computers

A practical Grade 10 guide to keeping computers ready for use

A shared school laptop is used by many people. If its care is left until something goes wrong, a small concern may interrupt a class or make the device harder to use. Preventive computer maintenance means planning suitable care before a problem interrupts use. A plan cannot prevent every fault, but it can help people follow safe routines and report concerns promptly. A useful plan states what should be done, when, who is responsible, and what guidance to follow. The examples in this lesson are planning scenarios, not reports of actual maintenance or measurements.

What you will learn

Explain what preventive computer maintenance is and why it is planned ahead.
Create a practical maintenance plan with tasks, timing, responsibilities, and records.
Use school and manufacturer guidance to keep maintenance safe and appropriate.

1. Understand preventive maintenance

Preventive maintenance is planned care intended to reduce avoidable computer problems. It differs from responding only after a device stops working. For example, a class might have a regular routine to check that shared laptops are stored safely and that visible concerns are reported. Such checks do not guarantee that a laptop will never need repair; they help people notice and address concerns appropriately.

Start by considering the device and how it is used. A laptop carried between rooms may need different handling from a desktop that stays in one place. Do not assume that every computer needs the same task or schedule. Use school procedures and the manufacturer’s instructions to decide what care is suitable and how often it should be done.

A plan should be realistic and within the assigned person’s role. A student might be asked to report visible damage, while a designated staff member handles software changes or other work requiring permission. If instructions are unclear, ask the teacher or another authorized person rather than guessing.

Plan care before a problem interrupts use.
Choose tasks and timing to fit the device, its use, and applicable guidance.
Preventive care reduces avoidable risks but cannot guarantee that faults will not occur.

2. Make the plan specific and safe

A phrase such as “look after the laptops” is too general to guide a routine. Write tasks so that the person responsible knows what action is expected. For example: “At the classroom routine, check the laptop’s exterior for visible damage and tell the teacher about concerns.” The task is clear, and it does not ask the student to open or repair the device.

A plan should state the timing, responsibility, and way to record completion. Timing must come from applicable instructions or a school decision, not from an unsupported guess. The responsible person should also be clear: a student, teacher, or designated technology staff member may have different permissions.

Use only approved procedures and supplies. Do not spray liquid onto a computer, open its casing, disconnect internal parts, or install software unless an authorized person has directed you to do so. If an assigned check reveals damage or a problem, stop and report it according to school procedure.

A simple maintenance record can help people see what was checked and what still needs attention. Include only information needed for the task, such as a device identifier, date, brief task description, and status. Do not put passwords or personal file contents in the record.

State the task, timing, responsible person, and record method.
Follow school and manufacturer guidance; do not improvise cleaning or repair.
Keep maintenance records limited to information needed for the task.

3. Review and maintain the plan

A maintenance plan may need review when a device’s use, location, or applicable instructions change. For example, moving a laptop to a different setting is a reason to check whether the existing plan still fits. The change alone does not prove that a particular task or schedule is needed.

The person responsible should consult school procedures and the manufacturer’s instructions before changing a task or its timing. If the guidance supports a change, update the plan and identify who will carry it out. If the guidance does not support a change, keep the plan as it is and note the review if school procedure calls for a record.

Review also whether the plan is practical. Can the assigned person complete the task? Is the timing clear? Does the person know what to do if a concern appears? A plan that answers these questions is more useful than a vague reminder. If something is outside the assigned person’s role, the plan should direct them to stop and report it.

A change in use is a reason to review, not a reason to guess.
Change tasks or timing only when applicable guidance supports the change.
Make reporting steps clear for concerns beyond the assigned person’s role.

4. Practise planning for a shared computer

Imagine a classroom uses the same laptop each day. The teacher wants a routine that is safe for students and makes it clear who handles work requiring authorization. A simple plan could assign students a visual check of the exterior and ask them to report concerns. It could assign software maintenance to designated school staff under school procedures.

Before accepting the plan, check that each task is specific, its timing is stated, and its responsible person is named. Confirm that the procedures are supported by school or manufacturer guidance. Decide what record is needed, such as the date, task, and status. Do not include passwords or personal file information.

For practice, draft a plan for a computer used in your classroom. Include one routine task, one task for an authorized person, a suitable timing based on the guidance available, and a way to record completion or concerns. If you do not have the relevant guidance, write that it must be checked rather than inventing a schedule or procedure.

Separate routine observations and reporting from work requiring authorization.
Use guidance to set timing and procedures.
A good plan is clear, safe, practical, and recordable.

Example maintenance-plan outline

Task	When	Responsible person	Record
Check the exterior and report concerns	At the routine set by the teacher	Assigned student	Date and status, as required
Handle software maintenance	As directed by school procedures	Designated school staff	Date and status, as required
Review the plan after a change in use	When use or applicable instructions change	Teacher or designated staff	Review and any supported change

Worked example

Planning care for a shared classroom laptop

A class uses the same laptop regularly. Create a plan with one student routine and one task for authorized school staff.

Choose a student routine
Assign a task that is simple and within the student’s role: check the laptop’s exterior for visible concerns and tell the teacher if something appears wrong. The student does not open or repair the device.
Assign work requiring authorization
Assign software maintenance to designated school staff, who follow school procedures and the device’s instructions. Students should not install software or change settings without permission.
Make the plan usable
State when the routine occurs using the school’s chosen schedule, name the responsible people, and record the date, task, and status as school procedure requires.

Answer: Student routine: check the exterior during the teacher’s established class routine and report concerns. Authorized staff: handle software maintenance according to school procedures. Record the task, date, and status using the school’s required method.

Check: The plan names tasks and responsibilities without asking a student to perform unauthorized work.

Worked example

Reviewing a plan after a change in setting

A school laptop that is usually used in a classroom is sometimes taken to a workshop. Explain what the planner should do about the existing maintenance plan.

Recognize the change
The laptop’s setting has changed, so it is sensible to review whether the existing plan still fits. The change alone does not establish that a new cleaning task or schedule is required.
Consult applicable guidance
The responsible person checks school procedures and the manufacturer’s instructions. This avoids guessing about care methods or timing.
Update only when supported
If the guidance supports a different task, timing, or responsibility, revise the plan and record the review as required. Otherwise, keep the existing plan.

Answer: Review the plan, consult school and manufacturer guidance, and make a change only if that guidance supports it.

Check: A changed setting prompts a review, but it is not proof that any particular maintenance task is necessary.

Worked example

Responding to visible damage

During an assigned visual check, a student notices damage to a laptop’s casing. What should the student do, and what should the maintenance record include?

Stop the assigned check
Damage is a concern to report, not an invitation to open or repair the laptop. The student should stop and follow the school’s reporting procedure.
Notify the responsible person
Tell the teacher or designated staff member so an authorized person can decide what should happen next.
Record only useful maintenance details
Follow school procedure for recording the device identifier, date, and a brief description of the concern. Do not record passwords or personal file contents.

Answer: Stop, report the damage to the designated person, and record the required maintenance details according to school procedure.

Check: The student reports the concern instead of attempting an unauthorized repair.

Common mistakes and how to avoid them

Waiting until a computer stops working before thinking about care.

Correction: Plan suitable routines ahead of time, while remembering that preventive maintenance cannot prevent every fault.

Giving every computer the same tasks and timing.

Correction: Base the plan on the device, its use, and applicable school or manufacturer guidance.

Opening, cleaning inside, or changing software on a device without permission.

Correction: Stay within the assigned role, follow approved procedures, and report concerns to an authorized person.

Putting passwords or personal file contents in a maintenance record.

Correction: Record only the information needed to identify the task and its status, as school procedure requires.

Lesson summary

Preventive computer maintenance is planned care intended to reduce avoidable problems before they interrupt use.
A useful plan identifies the task, timing, responsible person, and record method.
Follow school and manufacturer guidance rather than guessing about procedures or schedules.
Stop and report concerns that are outside the assigned person’s role.

Check your understanding

Question 1

A student notices damage during a routine visual check. What is the best next step?

Open the laptop and attempt a repair.
Stop, report the concern to the designated person, and follow school procedure.
Ignore the damage unless the computer stops working.
correctIndex no need extra

Show answer and explanation

Stop, report the concern to the designated person, and follow school procedure.

The student should not attempt an unauthorized repair. Reporting the concern lets an authorized person decide what should happen.

Question 2

Which details make a maintenance plan most useful?

Task, timing, responsible person, and an appropriate record.
Device colour and the name of the last person who borrowed it.
Passwords and personal file contents.
correctIndex no need extra

Show answer and explanation

Task, timing, responsible person, and an appropriate record.

The task, timing, responsibility, and record make the plan usable. Passwords and personal file details do not belong in a maintenance record.

Question 3

A computer is moved to a different setting. What should the planner do first?

Assume more frequent cleaning is always required.
Review the plan using school and manufacturer guidance.
Stop all maintenance permanently.
correctIndex no need extra

Show answer and explanation

Review the plan using school and manufacturer guidance.

A change in use is a reason to review the plan, but the appropriate response should come from applicable guidance rather than a guess.

Key terms

Preventive computer maintenance: Planned care intended to reduce avoidable computer problems before they interrupt use.
Maintenance plan: A set of clear tasks, timings, responsibilities, and recording steps for caring for a computer.
Authorized person: Someone permitted by school procedures to carry out a particular maintenance task.

Continue through ICS2O

View the complete ICS2O Ontario Grade 10 Computer Science curriculum and lessons

Tutor support for A5.3 · Plan preventive computer maintenance

Working on A5.3 · Plan preventive computer maintenance in ICS2O? Bring the question and your own attempt. In a live session, you can trace a small example and find the first step where the output differs from what you expected. Ask about the first step that does not make sense, then try a similar question yourself.

Explore coding tutoring · Request an eligible free 30-minute introduction. Your request is matched by subject and language; a tutor must accept before a time is confirmed.

برای مبحث A5.3 · برنامه‌ریزی نگهداری پیشگیرانه رایانه در درس ICS2O، سؤال و تلاش خود را همراه بیاورید. در جلسه می‌توانید یک مثال کوچک را دنبال کنید و نخستین گامی را که خروجی با انتظار شما فرق دارد پیدا کنید. راهنمای معلم برنامه‌نویسی را ببینید یا جلسهٔ معارفهٔ رایگان ۳۰ دقیقه‌ای درخواست کنید. زمان جلسه پس از پذیرش معلم قطعی می‌شود.

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 10 Computer Science (ICS2O), expectation A5.3. It is a study resource, not an official curriculum publication.

Before publication, content is checked for structure, mathematical or chemical notation, calculations, course boundaries, and readability. Errors can still occur, so corrections are welcomed.

Official curriculum reference

Report a correction or ask a question