Lesson 5: Service Record and Technical Briefing

Core path: 42 minutes

The work is not complete until another person can understand what happened, what changed, what was verified, and what still needs attention.

Today you assemble the final Technician Service Challenge service packet for Harborview Community Learning Lab and defend it.

Part 1: build the service packet

Your packet must contain all of the following.

Client intake

• client goals;
• asset inventory;
• user/workload requirements;
• service constraints;
• safety/privacy/authorization boundaries.

Baseline

• expected functions;
• observed starting state;
• known-good boundaries;
• important last-known changes;
• unresolved questions from intake.

Configuration/service plan

• workstation role decisions;
• network/service plan;
• OS/application target state;
• printer/mobile support plan;
• security controls;
• VM/cloud responsibility notes;
• backup/recovery plan;
• documentation/change plan.

Incident records

Include at least three completed seeded-fault records.

For each one show:

symptom and scope
strongest evidence
theory
rejected alternative
controlled action
rollback/recovery
verification
customer explanation
documentation/escalation

Security and recovery review

Include:

• least-privilege/account review;
• MFA/session/security-control state;
• endpoint/firewall/update status;
• wireless/client-security review;
• mobile/printer/data-handling check;
• backup and restore-verification record.

Final verification

Show the final checklist for the client workflows.

Do not write "everything works" without evidence.

Remaining risks

List anything not fully resolved and identify the correct next owner/action.

Part 2: prepare the technical briefing

Your briefing is short. The evidence packet is the main artifact.

Use this order:

1. What did Harborview need?
2. What did the baseline show?
3. What were your most important service/configuration decisions?
4. Which incidents did you diagnose?
5. What evidence mattered most?
6. What did you change?
7. What rollback/recovery path existed?
8. What security/privacy/safety decisions mattered?
9. How did you verify the final state?
10. What remains unresolved or escalated?

Presentation software is optional.

Part 3: client language

Choose one technical incident and explain it twice.

Technician version

Use precise technical language appropriate for the service record.

Client version

Explain the same issue in plain language without removing the important truth.

Example:

Technician version:

Endpoint had valid addressing and gateway reachability, but hostname resolution failed while direct IP reachability succeeded. DNS configuration/service path was corrected and verified by successful hostname lookup and portal access.

Client version:

The computer could reach the network, but it could not translate the portal name into the address it needed. We corrected that setting and verified the portal opens normally now.

Part 4: final defense questions

Be prepared for questions such as:

• Which decision had the greatest effect on reliability?
• Which fault had the strongest competing theory?
• What evidence prevented you from choosing a destructive fix?
• What user data was at risk during your work?
• Which change required the clearest rollback plan?
• Which security control would you refuse to bypass for convenience?
• What would you escalate instead of attempting yourself?
• What would you monitor or re-check after handoff?
• Where could AI help a technician in this case, and what still requires human verification?
• What is one thing you would change if the client budget or requirements changed?

Final reflection

Answer in one paragraph:

At the beginning of the course, what did you think computer support was? What do you think it is now? Use one specific piece of evidence from your capstone.

Capstone rubric

A strong final submission demonstrates:

• accurate system understanding;
• evidence-first diagnosis;
• compatible and requirement-driven decisions;
• safe handling of hardware/data/security boundaries;
• controlled change and rollback thinking;
• functional verification;
• clear documentation;
• professional client communication;
• honest escalation of unresolved risk.

Course completion checkpoint

You have completed the course when you can take a support problem through this entire chain:

client requirement
→ baseline
→ system/service decision
→ evidence
→ diagnosis
→ controlled correction
→ rollback/recovery
→ security/privacy review
→ verification
→ service record
→ client communication

That is technician work.