4 IT Documentation and Knowledge Management Free Online FlashCards

What is the purpose of an IT ticket?

A ticket records a specific request, fault, task, or incident, including its status and work performed.

What impact and scope details belong in a ticket?

Include who or what is affected, the severity, and when the issue began, if known.

What makes a runbook usable by a trained colleague?

State the purpose and scope, prerequisites, risks and approvals, ordered actions, checkpoints, recovery steps, verification criteria, and document ownership and review details.

What should a change record contain before implementation?

Record its purpose, affected systems, risk or impact, testing, approvals, implementation window, responsible people, validation, and rollback or recovery plan.

What is the safety limit of operational documentation?

Documentation does not replace training or authorization. Hazardous work must be referred to qualified people, and stop-work or escalation conditions should be clear.

How do a runbook and a procedure differ?

A runbook guides diagnosis or response to a specific operational condition; a procedure gives an approved, repeatable sequence for a task.

What is a knowledge article for?

A knowledge article provides a reusable explanation or solution for a defined audience, such as users or support staff.

Why link a ticket to a runbook instead of copying its instructions?

A ticket can link to a maintained runbook or procedure, while recording the work and outcome for its specific case.

How should a ticket distinguish facts from hypotheses?

Separate observed facts from hypotheses. Report what happened without presenting an unverified cause as certain.

When should a ticket be closed?

Close it only after required checks and communication are complete.

How should documentation handle secrets?

Never include passwords, access tokens, private keys, or other secrets. Use approved secure storage and reference it appropriately.

When should operational documentation be reviewed?

Review it when systems, owners, risks, or workflows change, and periodically according to organizational policy.