What is a change log?
A change log is an organized record of change requests and their progress.
Study 4 Change Logs and Audit Trails with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What is a change log?
A change log is an organized record of change requests and their progress.
What does an audit trail preserve?
An audit trail preserves the sequence of events for a request, including who acted, when, and what decision or update they made.
How should each change request be identified and recorded?
Give each request a unique identifier and maintain one authoritative record for it.
Which core details belong in a change request record?
Record its title, description, requester, submission date, and affected project, service, product, or configuration item.
What assessment references should a change record include?
Include references to impact analysis, risk assessment, estimates, and supporting documents or related requests.
What information makes a change decision traceable?
Record the outcome, decision date, decision-maker or approver, rationale, and any conditions or follow-up actions.
What must accompany an important status transition?
Record each important transition with a timestamp and the responsible person or workflow; a status label alone is not a complete history.
How does an approval decision differ from current request status?
Approval is the decision; implementation and verification describe the request’s current progress. A request can be approved but not implemented yet.
What should be retained when a change needs multiple approvals?
Retain each approval or rejection, including its actor, comments, and time, rather than recording only the final result.
Why should a rejected change request include a rationale?
State the rationale so the requester and later reviewers can understand the outcome.
What evidence helps reviewers reconstruct a request’s path?
Preserve the original request, impact-analysis material, approvals and comments, status transitions, implementation evidence, and closure record.
How should an error in a change record be corrected?
Preserve the prior entry or system history, then record the correction’s author, date, and reason.
Learn how project governance assigns decision authority, sets boundaries, escalates issues, and records decisions.
A 14-question quiz on project governance, decision authority, escalation, and decision records.
Learn how project governance assigns decision-making authority, accountability, delivery duties, oversight, and escalation paths.
Learn how project governance assigns decision authority, accountability, delivery responsibilities, oversight, and escalation across project roles.
Learn how to assess stakeholders, select tools for comparing them, and keep judgments evidence-based, validated, and current.
Learn how to classify project matters, set escalation routes and thresholds, and make escalations actionable.
A medium-difficulty quiz on applying escalation routes, decision rights, thresholds, and response practices in project issue resolution.
Learn how to distinguish project risks, issues, conflicts, and decisions, then design and use escalation routes that support timely, accountable resolution.
Learn how to plan stakeholder engagement, choose appropriate participation methods, build trust, address disagreement, and adapt a project’s approach as needs and circumstances change.
A medium-difficulty quiz on applying project oversight, performance monitoring, stage-gate decisions, change control, escalation, and corrective action.
Learn how project teams monitor performance, make formal decisions at stage gates, control changes, and respond to issues through corrective action and escalation.
Apply core quality-planning and delivery practices to project scenarios, including acceptance criteria, assurance and control, defect response, and evidence-based improvement.