# Operational Procedures and Professionalism

> Chapter 15 of the Courseiva A-PLUS-220-1202 curriculum — https://courseiva.com/learn/a-plus-220-1202/operational-procedures-and-professionalism

**Official objective:** 4.1 — Given a scenario, apply appropriate operational procedures and professional communication.

## Introduction

If you don't follow proper procedures or communicate poorly on the job, you could lose data, break expensive equipment, or — worst case — cause a security breach that costs your company thousands. Operational procedures and professionalism are the rules and habits that keep an IT environment stable, secure, and respectful. For your 220-1202 exam, this means knowing how to escalate issues, document work, handle sensitive data, and treat customers and colleagues with respect.

## The Restaurant Kitchen Manager Analogy

A restaurant kitchen manager runs the back of house during a busy Saturday night. They coordinate the chefs, ensure food safety by checking fridge temps, and maintain equipment so nothing catches fire. When a complaint comes in about a cold steak, they don't scream at the line cooks. Instead, they document the issue, speak calmly to the chef, and follow up with the customer. Their job includes ticking off a cleaning checklist before close and locking the walk-in freezer at the end of the night. This mirrors operational procedures: you follow documented steps to keep systems running, secure, and safe. Professionalism means you communicate respectfully, even when someone spills coffee on a server. Just as the manager logs maintenance on the deep fryer, an IT pro logs changes to a network switch. When the manager explains to the owner why the oven broke, they use clear language — no blaming, just facts. That's exactly how you handle a ticket about a crashed hard drive: explain what happened, what you did, and what comes next. The kitchen manager also writes an incident report if a knife gets left in the sink. You write one if a virus infects a laptop. Both roles rely on procedure, not panic, to keep everyone safe and the business running.

## Core explanation

Operational procedures and professionalism cover the 'soft skills' and structured processes that make IT support effective. Think of it as the rulebook for how you act at work. The exam splits this into several key areas: communication, documentation, safety, environmental controls, prohibited content, scripting basics, and change management.

First, communication. This is about how you talk to users, manage expectations, and resolve conflict. You must use clear, jargon-free language. If a user says 'my computer is slow', you don't rattle off technical specs. You ask clarifying questions like 'when did it start?' or 'is it slow in one program or everything?' Active listening means you repeat back what the user says to confirm understanding: 'So you're saying the email attachment won't open — correct?' You also need to set and manage expectations. Don't promise a fix in ten minutes if it might take two hours. Instead, say 'I'll start diagnostics and update you in thirty minutes.' Professionalism includes being punctual, dressing appropriately, and maintaining a positive attitude even when a user is frustrated.

Documentation is another pillar. Every interaction gets logged in a ticketing system. A ticket contains: the user's name and contact info, a description of the problem, steps you tried, the outcome, and any relevant hardware/software details. Documentation is not optional. If you fix a printer jam without creating a ticket, there's no record. That means if the same printer jams again, the next technician wastes time repeating your work. Change management is the formal process for making changes to an IT environment. You never just update a server or install software without approval. A change request details what will change, why, the potential impact, and a rollback plan if it goes wrong. Typically, changes go through a change advisory board (CAB) that reviews and approves them.

Safety and environmental controls refer to physical safety around equipment. You need to know how to handle a fire with the correct extinguisher type (Class C for electrical fires, never water). You must manage cable runs safely to avoid trip hazards. Tools like power strips and uninterruptible power supplies (UPS) protect against surges. You also need to manage computer components safely: use an antistatic wrist strap or mat when handling internal parts to avoid electrostatic discharge (ESD) that can fry a motherboard.

Prohibited content and activity covers what you must report. If you see illegal content (like child exploitation material), you report it immediately to management — never investigate or share it. You also do not install unlicensed software or access data you're not authorised to see.

Scripting basics appear in this section because IT pros use scripting to automate repetitive tasks. You might write a simple batch script to delete temp files on multiple machines. Understanding variables (containers for data), functions (reusable blocks of code), and basic logic (if/then statements) helps you script more efficiently.

Finally, professional behaviour includes respecting diversity, avoiding gossip, maintaining confidentiality, and knowing when to escalate a problem to a senior technician or manager. Escalation is not failure — it's a sign you understand your limits and want the best outcome for the user.

## Real-world context

You work as a junior IT support technician for a mid-sized accounting firm. A senior partner calls because her laptop won't boot. She's panicking because she has a client meeting in two hours. Here's what you actually do:

First, you stay calm and listen. You ask: 'When did this start? Did you install anything recently? Did you spill anything?' She says it froze after installing an update last night. You acknowledge the issue: 'I understand this is urgent. Let me take a look.' You create a ticket in your helpdesk system, noting the laptop model, OS version, and the user's description.

Next, you try to boot into safe mode. It works. You check for recent updates under Windows Update history. You see a failed cumulative update. You roll back the update and the laptop boots normally. Before handing it back, you run a disk check to ensure no corruption. You also update the ticket with every step you took.

Now, critical professional moment: you tell the partner the laptop is ready. But instead of leaving her to struggle, you explain in plain English: 'I removed a recent update that caused a conflict. Your files are all here. If you see a similar freeze again, give me a call immediately.' You don't use terms like 'cumulative rollback' or 'Safe Mode'. You keep it simple.

You also need to manage the timeline. The fix took forty minutes. You promised an update in thirty, so you gave one at twenty-five minutes saying 'still working on it, looks promising'. That's setting expectations.

Another scenario: you're asked to dispose of old hard drives. You cannot just throw them in the bin. Client data is on them. You follow the company's data destruction policy. You use a degausser to wipe magnetic drives or physically destroy them with a drill. Then you document the serial numbers and destruction method in a disposal log. That log is auditable.

If a colleague shows you illegal content on their screen during lunch, you stop looking immediately. You tell your supervisor privately: 'I was shown something I believe is illegal. I need to report it.' You do not copy, share, or discuss it. You let management handle it from there.

Finally, you encounter a user who keeps installing unauthorised software. You don't shout at them. You explain the company policy politely, remind them of security risks, and escalate to their manager if it continues. Professionalism wins every time.

## Exam focus

The 220-1202 exam tests operational procedures and professionalism heavily — expect around 10-15% of your score here. The questions are scenario-based. You get a short story about a problem or interaction, and you must choose the BEST response.

Key exam topics include:
- Best communication practices. The correct answer usually involves clarifying the issue without interrupting the user. Traps: answers where you 'tell the user they are wrong' or 'fix it without asking questions' are wrong.
- Change management process. The exam loves asking: 'What should you do before making a change?' The answer is always 'submit a change request and get approval from the CAB.' Traps: 'just do it' or 'backup first but skip approval' are incorrect.
- Incident documentation. You'll be asked what to include in a ticket. Required: date/time, steps taken, outcome, user info. Traps: including personal opinions ('user was rude') is wrong.
- Safety procedures. Know the fire extinguisher classes: A (ordinary combustibles), B (flammable liquids), C (electrical), D (metals). For a server room fire, use Class C carbon dioxide extinguishers. Traps: water extinguisher on electrical fire — instant fail.
- ESD prevention. Always use an antistatic wrist strap when working inside a computer. Traps: 'touch the computer case' is wrong because the case could be painted (non-conductive) or not grounded.
- Prohibited content. If you encounter illegal content, report to management immediately. Traps: 'investigate further' or 'notify the user it's illegal' are wrong.
- Professional behaviour. Respect cultural differences, avoid offence, and use inclusive language. Traps: telling a joke to lighten the mood when someone is upset — that can backfire and be unprofessional.
- Data destruction. Know the difference between magnetic degaussing, physical destruction, and overwriting. For SSDs, degaussing may not work; physical destruction is required.
- Scripting concepts. You won't write code, but you must recognise terms like variable, loop (repeating code), function (named block of code), and conditional (if-then-else). Trap: they'll ask 'What construct allows code to run only when a condition is true?' Answer: conditional or if statement.

Trap patterns: The exam often gives you two good-looking answers. One is technically correct but rude. The other is slightly less efficient but polite and professional. The professional answer wins. Example: 'User reports error message. Should you: A) remote in, fix it, close ticket. B) acknowledge the issue, ask for the exact message, then fix it.' Answer is B because you verify the problem first.

Key definitions to memorise: escalation (handing off to higher level), ticket (record of incident), change advisory board (CAB), rollback plan, uninterruptible power supply (UPS), electrostatic discharge (ESD), Material Safety Data Sheet (MSDS).

## Step by step

1. **Greet and Listen Actively** — When a user reports an issue, start by saying hello and asking what's happening. Let them describe the problem fully without interrupting. This builds trust and helps you gather all the symptoms before you start troubleshooting.
2. **Document Initial Details** — Open a ticket in your helpdesk system immediately. Record the user's name, contact method, device details, the reported issue in their own words, and the time of the report. This creates a permanent record so nothing gets lost.
3. **Set Expectations Clearly** — Tell the user what you will do next and a realistic timeframe for an update. For example: 'I'll run some tests now and get back to you within thirty minutes.' Managing expectations prevents frustration and shows professionalism.
4. **Diagnose and Fix** — Follow documented troubleshooting steps — check for common causes, test solutions in a safe order, and verify the fix works. If the fix involves a system change that could affect others, check whether change management approval is needed first.
5. **Inform the User and Verify** — Contact the user to confirm the issue is resolved. Explain what the problem was in simple language. Ask them to test it themselves. Do not close the ticket until the user agrees the issue is fixed.
6. **Complete Documentation and Close** — Update the ticket with every step you took, the solution applied, and any follow-up actions needed. Close the ticket with a clear resolution summary. Good documentation helps future troubleshooting and compliance.

## Comparisons

### Ticket vs Change Request

**Ticket:**
- Records an incident or service request
- Typically shorter and less formal
- Does not require approval before creation

**Change Request:**
- Formal proposal to alter infrastructure
- Requires impact analysis and rollback plan
- Must be approved by change advisory board

### Active Listening vs Passive Listening

**Active Listening:**
- You repeat back what the user says to confirm understanding
- You ask clarifying questions
- You take notes during the conversation

**Passive Listening:**
- You just nod without verifying
- You don't ask for more details
- You assume you understand the problem

### Electrostatic Discharge (ESD) Wrist Strap vs Antistatic Mat

**Electrostatic Discharge (ESD) Wrist Strap:**
- Worn on wrist
- Must be clipped to grounded metal
- Protects the component you are holding

**Antistatic Mat:**
- Placed on work surface
- You place components on it
- Protects items resting on the mat

### Degaussing vs Physical Destruction

**Degaussing:**
- Uses a strong magnetic field to wipe data
- Works on magnetic media (HDDs)
- Leaves the drive shell intact

**Physical Destruction:**
- Shreds, drills, or crushes the drive
- Works on all drive types including SSDs
- Drive is unusable afterwards

## Diagram

_Flowchart of the typical IT support process from user report to ticket closure, including the change management decision point._

```mermaid
flowchart TD
    A[User Reports Issue] --> B[Ticket Created]
    B --> C{Diagnose Problem}
    C --> D[Simple Fix?]
    D -- Yes --> E[Fix and Document]
    D -- No --> F[Escalate to Senior Tech]
    E --> G[Inform User and Verify]
    F --> G
    G --> H[Update Ticket and Close]
    C --> I{Involves System Change?}
    I -- Yes --> J[Submit Change Request]
    J --> K[CAB Approval?]
    K -- Yes --> E
    K -- No --> L[Do Not Proceed]
    L --> B
```

## Common misconceptions

- **Misconception:** If a user is angry, I should ignore their emotions and just fix the computer fast. **Reality:** You must acknowledge their frustration and stay calm before starting the technical fix. Emotional validation builds trust. (Beginners think IT is only about machines, but the exam tests people skills. Ignoring emotions is unprofessional and often escalates conflict.)
- **Misconception:** Change management means I need permission to do any work at all, like swapping a dead power supply. **Reality:** Change management applies to changes that could affect users or system stability. Emergency fixes for critical outages can be done with verbal approval and documented later. (Learners over-interpret the rule. The exam tests when formal approval is needed versus when a quick fix is acceptable.)
- **Misconception:** When disposing of hard drives, just deleting files and formatting is enough to protect data. **Reality:** Deleting or formatting only removes the file pointers, not the actual data. You must overwrite, degauss, or physically destroy the drive to prevent data recovery. (People assume 'delete' means gone. The exam wants you to know that data remains recoverable until securely erased.)
- **Misconception:** If I see a colleague viewing inappropriate content, I should ignore it unless it's illegal. **Reality:** Even non-illegal prohibited content (like violent or pornographic material) violates company policy and must be reported to management. (Beginners think only illegal content matters. The exam covers enforcing all prohibited-content policies, not just legal boundaries.)
- **Misconception:** For ESD protection, touching the metal part of the computer case is good enough. **Reality:** Some cases are painted or otherwise non-conductive. You must use a proper antistatic wrist strap clamped to a grounded metal object. (This is a specific exam trap. Touching the case is a myth unless you know it's bare, unpainted metal grounded to earth.)

## Key takeaways

- Always clarify the problem with open-ended questions before starting any fix — jumping to a solution wastes time and risks the wrong repair.
- Every IT interaction must be documented in a ticket with the issue, steps taken, outcome, and user details.
- Changes to a production system require a formal change request approved by a change advisory board unless it is an emergency fix.
- Use a Class C fire extinguisher on electrical fires in a server room — never use water or foam.
- When handling internal computer components, always wear an antistatic wrist strap properly grounded to prevent electrostatic discharge damage.
- If you encounter illegal content on a user's machine, report it to your manager immediately and do not investigate, copy, or share it.
- Professional communication means using plain language, confirming understanding, and setting realistic expectations about resolution time.
- Data destruction requires overwriting, degaussing, or physical destruction — simple formatting or file deletion is not sufficient.
- A script's 'if' statement is a conditional that runs code only when a specified condition is true.
- When a problem exceeds your skill level, escalate it to a senior technician promptly — this is responsible, not admitting failure.

## FAQ

**Do I really need to create a ticket for every single interaction?**

Yes. Every support interaction must be logged in a ticketing system. This provides an audit trail, helps track recurring issues, and ensures accountability.

**What happens if I change a server setting without using change management?**

You could cause an outage, lose data, or violate company policy. The exam expects you to always submit a change request unless it's an authorised emergency fix logged after the fact.

**How do I handle a user who yells at me on the phone?**

Stay calm, do not raise your voice, and acknowledge their frustration. Use phrases like 'I understand you're upset, let me help you with this.' If they continue, offer to transfer them to a supervisor.

**Is formatting a hard drive enough to destroy data before recycling?**

No. Formatting only removes the file system pointers. Data remains on the drive and can be recovered with simple tools. You must overwrite, degauss, or physically destroy the drive.

**What's the difference between a ticket and a change request?**

A ticket records an incident or service request. A change request is a formal proposal to alter IT infrastructure, requiring documentation of impact, rollback plan, and approval from a change advisory board.

**Can I wear an antistatic wrist strap without grounding it?**

No. A wrist strap must be clipped to a grounded metal object (like the computer chassis or a grounding mat) to safely drain static. Wearing it unconnected does nothing.

## Check your understanding

1. **A user reports that their computer is slow. What is the first thing you should do?**

   Answer: Ask open-ended questions to clarify the issue, such as when the slowness started and which applications are affected.

2. **Before making a non-emergency change to a server, what must you do first?**

   Answer: Submit a change request and obtain approval from the change advisory board (CAB).

3. **What type of fire extinguisher should you use on an electrical fire in a server room?**

   Answer: A Class C carbon dioxide (CO2) extinguisher.

4. **You are disposing of old hard drives containing client data. What is the minimum step required to make the data unrecoverable?**

   Answer: Physically destroy the drives (shred, drill, or crush) or degauss them if they are magnetic.

5. **While working, a colleague shows you an image on their screen that appears to be illegal. What should you do?**

   Answer: Report it to your manager immediately without investigating, copying, or discussing it further.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/a-plus-220-1202/operational-procedures-and-professionalism