4.1 Given a scenario, implement best practices associated with documentation and support systems information management.
📘CompTIA A+ Core 2 (220-1202)
In IT support, keeping proper documentation is critical. Documentation helps IT teams track problems, standardize processes, train new employees, and measure performance. Below are the main types of documents you need to know:
1. Incident Reports
- Purpose: To record problems (incidents) when something goes wrong in the IT environment.
- Contents of an incident report:
- User information (who reported the issue)
- Device or system affected
- Time and date of the incident
- Description of the problem
- Steps taken to fix it
- Outcome/resolution
- Example in IT environment:
- A user reports that their email is not working. The technician logs it, checks the mail server, and resolves the issue. The incident report records all these details for future reference.
Why it matters: Incident reports help IT track recurring problems and identify weak points in systems.
2. Standard Operating Procedures (SOPs)
- Purpose: SOPs are step-by-step instructions to perform routine IT tasks consistently.
- Why use SOPs: Ensures tasks are done correctly, reduces errors, and helps new staff follow procedures.
Example: Software Installation SOP
- Steps to install a company-approved software package:
- Verify license availability
- Download installer from trusted source
- Follow installation prompts
- Configure company-specific settings
- Document completion in ticketing system
Other uses in IT:
- Backup procedures
- Network configuration
- Printer setup
3. New User / Onboarding Setup Checklist
- Purpose: Ensure all IT tasks for a new employee are completed.
- Typical items on the checklist:
- Create user account in Active Directory
- Assign email and access permissions
- Install necessary software
- Provide device (laptop/PC) and accessories
- Configure network access
- Provide IT policies and guidelines
Why it matters: Ensures every new employee has the tools they need and avoids missing steps.
4. User Off-boarding Checklist
- Purpose: Ensure IT properly deactivates access when an employee leaves.
- Typical items on the checklist:
- Disable user accounts
- Remove access to email and cloud services
- Collect company devices (laptops, phones)
- Transfer files and data as needed
- Update documentation
Why it matters: Protects sensitive data and prevents unauthorized access.
5. Service-Level Agreements (SLAs)
- Purpose: SLAs define the level of service expected between IT teams and users or third parties.
- Types of SLAs:
- Internal: Between IT team and company departments
- Example: IT promises to respond to critical issues within 30 minutes.
- External/Third-party: Between the company and outside vendors
- Example: Internet service provider guarantees 99.9% uptime per month.
- Internal: Between IT team and company departments
Why it matters: SLAs set clear expectations and help measure IT performance.
6. Knowledge Base / Articles
- Purpose: A knowledge base is a library of IT articles, guides, and FAQs that help users or technicians solve common problems.
- Examples in IT:
- How to reset a company email password
- Troubleshooting VPN connection issues
- Installing a printer on Windows or Mac
- Benefits:
- Reduces repeated questions
- Speeds up problem resolution
- Provides self-help options for users
Key Takeaways for Exam
- Incident reports = track problems and resolutions.
- SOPs = standardize IT tasks to prevent errors.
- Onboarding checklists = ensure new employees have everything set up correctly.
- Off-boarding checklists = secure accounts and retrieve company assets.
- SLAs = define service expectations (internal and external).
- Knowledge base/articles = central resource for solving problems efficiently.
💡 Tip for remembering: Think of these as “Record, Standardize, Onboard, Offboard, Promise, Guide”: each type of document serves one of these functions in IT.
