Instructions for Submitting a Request for Repair of ICT Equipment
Reliable computers, printers, projectors, network devices, and other digital tools are essential to daily work in Ozamiz City schools. When equipment stops working, a clear and complete repair request helps the responsible personnel assess the problem, assign the right technician, and restore service with less delay.
Schools should document each issue through the proper administrative channel rather than relying only on verbal reports or informal messages. A written request creates a record for monitoring, supports accountability, and helps the Division of Ozamiz City identify recurring equipment and infrastructure needs.
Verify The Equipment And Problem
Begin by identifying the affected device. Record the school name, office or classroom, equipment type, brand, model, property number, and any available inventory or asset tag. If several devices are affected, list each unit separately so the service team can evaluate them accurately.
Describe the fault in plain, specific language. Explain what happens when the device is switched on, when the problem began, and whether the issue is constant or intermittent. “The printer produces blank pages after the first sheet” is more useful than “printer is broken.” Include error messages, unusual sounds, recent changes, and basic troubleshooting already completed.
Prepare The Repair Request
Use the school or division-approved request form when one is available. The request should identify the requesting teacher, school head, office representative, or designated ICT coordinator, together with a reachable phone number or official email address. Add the date of submission and indicate whether the equipment is needed for instruction, administration, assessment, communication, or another essential function.
Attach photographs of the device, cables, ports, display messages, or visible damage when appropriate. For software problems, include screenshots and the application name. Do not send passwords, confidential learner information, or other sensitive files unless an authorized ICT personnel specifically requires them through a secure channel.
Include The Information That Speeds Assessment
A repair team can respond more efficiently when the request includes enough technical and operational detail. The following information should appear in the form or its attachments:
| Information | What to provide |
|---|---|
| Equipment identity | Type, brand, model, asset tag, and serial number |
| Location | School, building, room, and assigned office |
| Reported fault | Clear description of symptoms and error messages |
| Timing | Date discovered and frequency of the problem |
| Impact | Classes, records, services, or activities affected |
| Troubleshooting | Safe checks already performed |
| Supporting files | Photos, screenshots, inspection notes, or quotations if required |
| Requester details | Name, position, contact number, and approval details |
Avoid opening sealed components, altering electrical connections, or installing unapproved software to solve the issue. Such actions may worsen the damage and can affect warranty or accountability records. If there is smoke, a burning smell, exposed wiring, water intrusion, or electrical sparking, disconnect the equipment only when it is safe to do so and report the hazard immediately.
Submit Through The Proper Channel
Send the completed request to the designated school ICT coordinator, property custodian, administrative officer, or division office identified in current DepEd Ozamiz procedures. Follow the required file format, naming convention, signature process, and submission method. Keep a copy of the signed form and all attachments for school records.
Requests involving urgent safety concerns, widespread connectivity failure, or systems that affect examinations and critical reporting should be marked clearly according to local procedures. Disaster-related incidents may require additional reporting, so review the division’s DRRM updates when equipment damage is connected to flooding, severe weather, fire, or another emergency.
Track The Request And Support Inspection
After submission, record the reference number, date received, assigned personnel, and current status. A simple monitoring log can show whether a request is pending assessment, awaiting parts, under repair, ready for testing, or completed. Follow up through official channels if the stated response period has passed, attaching the original reference rather than creating duplicate requests.
Make the equipment available for inspection and provide access to relevant users who can explain the fault. Before accepting the repair, test the device using the tasks it normally performs. Check printing, display output, internet access, audio, file saving, or other functions that relate to the original complaint.
Keep Asset And Service Records Current
When the repair is completed, update the equipment history with the work performed, parts replaced, service date, technician or vendor, and final condition. Record whether the device was repaired, replaced, transferred, or recommended for disposal. These details support inventory reconciliation, procurement planning, warranty claims, and future budgeting.
ICT equipment should be considered alongside broader school facility needs. Updates about projects such as the new classroom construction can help school leaders coordinate room assignments, network points, electrical requirements, and equipment deployment before a facility becomes operational.
Use This Submission Checklist
- Identify the device with its asset tag, model, serial number, and exact location.
- Describe the fault, date observed, operational impact, and troubleshooting performed.
- Attach clear photos, screenshots, inspection notes, and required approvals.
- Submit through the authorized school or division channel and retain the reference number.
- Test the equipment after service and update its maintenance record.
A complete repair request turns an equipment problem into a traceable service action. School personnel should prepare the documentation promptly, submit it through the recognized DepEd Ozamiz process, and maintain records from initial report through final testing. This practice protects public assets while helping teachers, administrators, and learners regain dependable access to ICT resources.