How should a workaround be documented?

• A. It must be fully documented, including justification and time limits.
• B. It should be noted in the daily log only.
• C. It should be documented with justification, time limits, and tracked for permanent resolution.
• D. It requires a formal risk assessment and budget impact.

Answer: (C)

A workaround is a temporary fix that keeps operations safe while a permanent solution is developed, so it must be documented with why it’s needed, how long it will be in place, and how the issue will be resolved permanently. Recording the justification communicates the risk being mitigated and the reasoning for the temporary approach. Including a time limit ensures the workaround isn’t used indefinitely and prompts timely re-evaluation and escalation. Tracking for permanent resolution creates accountability and a clear path to replace the workaround with a proper fix, preventing the issue from being forgotten or left unresolved. A daily log alone doesn’t provide the full context or a defined duration, and while a formal risk assessment and budget impact can be relevant in some cases, they’re not the core elements required to document a standard workaround.