Week 16: Operational Procedures and Professional IT Support

210 instructional minutes | five 42-minute lessons

Technical skill is not enough if the technician loses the ticket history, changes production without approval, destroys recoverable data, ignores safety, exposes private information, or leaves the customer confused.

This week is about how professional IT work is controlled and documented.

Lesson sequence

1. Documentation, Assets, and Change Management
2. Backup, Safety, and Environmental Controls
3. Privacy, Licensing, Policy, and Incident Evidence
4. Professional Communication and Remote Support
5. Scripting and AI Operations Practical

Evidence you will produce

• ticket, asset, SOP/SLA, and change-management record;
• backup/recovery plus safety/environment decision plan;
• privacy/licensing/policy and incident-evidence record;
• professional remote-support scenario;
• scripting/AI operations practical integrating the week.

A+ alignment

Primary coverage: Core 2 Operational Procedures objectives 4.1 through 4.10.

The Version 4.0 objective set includes documentation/support systems, change management, workstation backup/recovery, safety, environmental controls, privacy/licensing/policy, professional communication, scripting, remote access, and basic AI concepts.

Boundaries

This is not a programming week. Script files are recognized and evaluated as technician automation tools.

Remote-access work uses fictional/supplied state only. No real credentials or external endpoints are used.

Incident-evidence work focuses on preservation, documentation, chain-of-custody concepts, and appropriate escalation. AI exercises use fictional/non-sensitive information and require accuracy/privacy/source evaluation.

What good work looks like

A professional technician can answer:

What was requested?
What system/asset is affected?
What am I authorized to change?
What could go wrong?
What is the rollback/recovery path?
What safety/privacy/policy rules apply?
How will I communicate status?
How will I verify and document the result?

Week 17 removes the objective labels and asks you to solve mixed technician incidents across the entire course.