A Website Change Log: 6 Details Worth Recording After an Update
Can you tell what changed before a website problem started? A short change record helps connect updates with later investigations.
1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.
Prefer YouTube? Watch this video on our YouTube channel (opens in a new tab).
The six points in the video
This is a silent video. The headings, explanations and labels below reproduce the information on screen.
-
Step 1: Record when it changed
Use a date and time that others can interpret clearly.
On-screen labels: Update date; Update time; Relevant time zone.
-
Step 2: Describe what changed
Name the affected page, component or service.
On-screen labels: Affected area; Brief description; Related task.
-
Step 3: Explain the reason
Record the problem or customer need behind the update.
On-screen labels: Customer need; Issue addressed; Expected outcome.
-
Step 4: Name the person responsible
Include the owner or team who can answer follow-up questions.
On-screen labels: Change owner; Support contact; Related approval.
-
Step 5: Record the checks performed
Note the important pages and tasks tested after release.
On-screen labels: Actual checks; Observed result; Known limitations.
-
Step 6: Link the project reference
Version history or a release reference can identify the exact change.
On-screen labels: Release reference; Version history; Useful investigation trail.
A practical check for your business
Record the purpose of a meaningful change alongside its date and responsible person. Include enough context to help explain a later issue and identify the release that needs investigation.
Sources and further detail
Common questions
Can you tell what changed before a website problem started?
A short change record helps connect updates with later investigations. Keep a clear record alongside the actual project history.
Go further
More video tips
All 205 videos →
How to Report a Website Problem: 6 Details That Help Support
Help support reproduce the issue.
Git vs GitHub: Version Control and Collaboration Explained
Version control and collaboration.