CPD ยท Telecommunications and IT
Documenting a change
Writing a change request that others can approve and reverse.
about this course
What you will be able to do
Writing a change request that others can approve and reverse.
- Describe a change, given a scenario, with reason, scope and impact.
- Plan a back-out, given the change, with clear steps and a time limit.
- Record approval, given a template, with name, date and decision.
- Review a change after the fact, given outcome notes, stating what to keep or fix.
Task, condition and standard
Task
Write a change record with reason, risk and rollback, test the change with a checklist, record the approval and result, and review a risky change to choose a safer time
Condition
Given change scenarios such as a mail server update and a firewall rule change, a record template and a test checklist, in a 2-hour practical session
Standard
Complete a record with reason, risk, rollback, test plan, named approver and result, stop and record when a test fails, and choose a safer time for a risky change
These courses teach process, communication and recording. They give no clinical, legal, tax, financial or engineering sign-off. A named subject expert must review every line, and you must check your own professional body's current CPD rules, before you rely on a certificate.
sessions
8 modules
Module 1 Why changes need records 15 min
- A record lets others approve, reverse and learn from a change.
- Emergency changes are recorded afterwards with a reason.
- No record means no proof of what changed.
Practise: Practise with a case card or template for "why changes need records": describe a change, given a scenario, with reason, scope and impact.
Standard to meet. Explain why a change needs a record, so that others can approve it, reverse it and learn from it, including emergency changes recorded afterwards with a reason.
Module 2 Reason, risk, rollback 25 min
- Reason: why the change is needed.
- Risk: what could go wrong and for how long.
- Rollback: clear steps to undo the change.
Practise: Practise with a case card or template for "reason, risk, rollback": plan a back-out, given the change, with clear steps and a time limit.
Standard to meet. Write the reason, risk and rollback for a change, given a scenario such as a mail server update, with the rollback as clear steps that undo the change.
Module 3 Testing with a checklist 25 min
- Write the test list before the change.
- Test that the service works and nothing else broke.
- If a test fails, stop and record it.
Practise: Practise with a case card or template for "testing with a checklist": record approval, given a template, with name, date and decision.
Standard to meet. Test a change with a checklist, confirming that the service works and nothing else broke, and stop and record the result if a test fails.
Module 4 Approval and result 20 min
- Record the named approver, date, time and decision.
- Record the outcome after the change.
- Keep the record for later review.
Practise: Practise with a case card or template for "approval and result": review a change after the fact, given outcome notes, stating what to keep or fix.
Standard to meet. Record approval and the result, given a template, with the named approver, date, time and decision, and the outcome noted for later review.
Module 5 Practice 10 min
- Fill every field of the template.
- Keep the wording short and exact.
- Check the rollback is possible.
Practise: Run one full practice round for "documenting a change" on a case card or template: work through each outcome in turn (describe a change; plan a back-out; record approval; review a change after the fact).
Standard to meet. Complete a change record for a firewall rule change, given a scenario, with reason, risk, rollback, test plan and approver all filled in.
Module 6 Check 5 min
- Check the record for six fields.
- Judge whether the timing is safe.
- Choose a better time if the risk is high.
Practise: Take the end check for "documenting a change": show that you can review a change after the fact, given outcome notes, stating what to keep or fix, and meet every outcome standard above.
Standard to meet. Review a risky change, such as a mail server upgrade on a Friday evening, and choose a safer time, with the record complete and consistent.
Module 7 Second worked case: a Friday evening upgrade 10 min
- Add the time for the change, the tests, the rollback and a margin.
- Choose a window when few people are affected.
- Rewrite the record with the new time.
Practise: Practise with a case card or template for "second worked case: a Friday evening upgrade": review a change after the fact, given outcome notes, stating what to keep or fix. Use a new case this time (round 2).
Standard to meet. Review a risky upgrade planned for a busy time, calculate the time needed including rollback, and choose a safer window with the record rewritten.
Module 8 Teach-back and peer check 10 min
- Swap records with a partner.
- Check the six fields one by one.
- Name any field that is blank or unclear.
Practise: Practise with a case card or template for "teach-back and peer check": review a change after the fact, given outcome notes, stating what to keep or fix. Use a new case this time (round 2).
Standard to meet. Evaluate a partner's change record against the six required fields, find any blank or unclear field, and decide whether to approve or return it.
practice
Worked example and case cards
Worked example
Change: update mail server. Reason: security fix. Risk: 30-minute outage. Rollback: restore snapshot. Test: send/receive test. Approver and time recorded.
Case card
a firewall rule change.
Case card 2
Upgrade a mail server on a Friday evening. Learners write reason, risk, rollback and choose a better time.
checks
10 check questions with model answers
Why a rollback plan?
Model answer: To recover if it fails. (Covered in module 2: Reason, risk, rollback. To pass that module: Write the reason, risk and rollback for a change, given a scenario such as a mail server update, with the rollback as clear steps that undo the change.)
Who approves?
Model answer: The named approver, per policy. (Covered in module 4: Approval and result. To pass that module: Record approval and the result, given a template, with the named approver, date, time and decision, and the outcome noted for later review.)
What is tested?
Model answer: That the service works and nothing else broke. (Covered in module 3: Testing with a checklist. To pass that module: Test a change with a checklist, confirming that the service works and nothing else broke, and stop and record the result if a test fails.)
Record the result?
Model answer: Yes, with time. (Covered in module 4: Approval and result. To pass that module: Record approval and the result, given a template, with the named approver, date, time and decision, and the outcome noted for later review.)
What is rollback?
Model answer: The steps to undo the change. (Covered in module 2: Reason, risk, rollback. To pass that module: Write the reason, risk and rollback for a change, given a scenario such as a mail server update, with the rollback as clear steps that undo the change.)
Who approves?
Model answer: The named approver. (Covered in module 4: Approval and result. To pass that module: Record approval and the result, given a template, with the named approver, date, time and decision, and the outcome noted for later review.)
What if the test fails?
Model answer: Do not proceed; record the result. (Covered in module 3: Testing with a checklist. To pass that module: Test a change with a checklist, confirming that the service works and nothing else broke, and stop and record the result if a test fails.)
Why record the result?
Model answer: For later learning and audit. (Covered in module 4: Approval and result. To pass that module: Record approval and the result, given a template, with the named approver, date, time and decision, and the outcome noted for later review.)
Emergency change?
Model answer: Same record, written after, with reason. (Covered in module 1: Why changes need records. To pass that module: Explain why a change needs a record, so that others can approve it, reverse it and learn from it, including emergency changes recorded afterwards with a reason.)
A change takes 30 minutes, testing 15 and rollback 20, in a 60-minute window. Does it fit?
Model answer: No: 30 + 15 + 20 = 65 minutes, which is over 60; ask for a longer window or choose another time. (Covered in module 7: Second worked case: a Friday evening upgrade. To pass that module: Review a risky upgrade planned for a busy time, calculate the time needed including rollback, and choose a safer window with the record rewritten.)
glossary
Words used in this course
change, rollback, risk, approval, test plan.
marking
How the practice and assessment are marked
| Level | Meaning | Marks of 4 |
|---|---|---|
| Secure | Meets the standard in the outcome every time, no prompts | 4 |
| Meeting | Meets the standard with one small slip, corrected when prompted | 3 |
| Developing | Meets part of the standard; needs a re-attempt | 2 |
| Not yet | Standard not met | 1 |
Pass = average 3 or more, and no outcome at 1. You may re-attempt after feedback. The subject expert sets any stricter pass mark.
where next
Ladder L1 to L7, slide by slide with notes
This course sits at L4 Practitioner. Credits stack; aligned with, not accredited by, any framework.
jobs this leads to
Where this takes you
- IT support technician
- Systems administrator
- Change coordinator
- Service desk analyst
- Network technician
assessment and certificate
How you are checked
Each outcome is checked against its standard with a checklist or a short test. A digital CPD record shows the hours. Keep evidence in My page. Aligned with common CPD practice; not accredited. Learners check their own body's rules.
ten locations and global
Your place
Use your own body's forms, units and currency. Local professional bodies set the rules for CPD hours; check them first.
India (Bengaluru)
Language: English, Hindi, Kannada. Personal data: Digital Personal Data Protection Act 2023. Credit and levels: National Skills Qualifications Framework (NSQF) and the national credit framework.
Netherlands (Eindhoven area)
Language: Dutch, English. Personal data: EU GDPR (Dutch: AVG), supervised by the Autoriteit Persoonsgegevens. Credit and levels: the Dutch qualification framework (NLQF) linked to the European Qualifications Framework.
UAE (Dubai and Abu Dhabi)
Language: Arabic, English. Personal data: Federal Decree-Law No. 45 of 2021 (personal data protection). Credit and levels: the emirate education and training regulators (for example KHDA in Dubai) and the national qualifications framework.
Brazil (Sao Paulo)
Language: Portuguese (Spanish and English support). Personal data: LGPD (Lei Geral de Protecao de Dados). Credit and levels: the national technical-education catalogue and the national S-system training bodies.
Canada (Toronto)
Language: English, French. Personal data: PIPEDA, with provincial rules where they apply. Credit and levels: the provincial colleges framework and the national credential-recognition guidance.
United States
Language: English, Spanish. Personal data: state privacy laws (for example California), and COPPA for children under 13. Credit and levels: state and community-college credit systems.
Singapore
Language: English, Mandarin, Malay, Tamil. Personal data: Personal Data Protection Act (PDPA). Credit and levels: the Singapore national skills frameworks and the national credit system.
Australia
Language: English. Personal data: the Privacy Act 1988 and the Australian Privacy Principles. Credit and levels: the Australian Qualifications Framework (AQF) levels.
Hong Kong (Eastern Asia)
Language: Chinese (Cantonese, Mandarin), English. Personal data: the Personal Data (Privacy) Ordinance. Credit and levels: the Hong Kong Qualifications Framework.
Georgia and Israel (Western Asia)
Language: Georgian, Hebrew, Arabic, English. Personal data: the personal data law of the country where the learner lives. Credit and levels: the national qualifications framework of that country.
Cayman Islands (Caribbean)
Language: English. Personal data: the Data Protection Act. Credit and levels: the local education and training framework.
Mexico
Language: Spanish, English. Personal data: the federal law on personal data held by private parties. Credit and levels: the national competency certification system and the education ministry levels.
next
Draft
Draft CPD course. It opens only after final checks. No fee is shown.