WEBVTT

00:00:00.000 --> 00:00:06.000
Can you tell what changed before a website problem started?

00:00:06.000 --> 00:00:13.000
A short change record helps connect updates with later investigations.

00:00:13.000 --> 00:00:18.000
Write down the useful details.
6 change-log entries.

00:00:18.000 --> 00:00:30.000
Record when it changed
Use a date and time that others can interpret clearly.
Update date · Update time · Relevant time zone

00:00:30.000 --> 00:00:42.000
Describe what changed
Name the affected page, component or service.
Affected area · Brief description · Related task

00:00:42.000 --> 00:00:54.000
Explain the reason
Record the problem or customer need behind the update.
Customer need · Issue addressed · Expected outcome

00:00:54.000 --> 00:01:06.000
Name the person responsible
Include the owner or team who can answer follow-up questions.
Change owner · Support contact · Related approval

00:01:06.000 --> 00:01:18.000
Record the checks performed
Note the important pages and tasks tested after release.
Actual checks · Observed result · Known limitations

00:01:18.000 --> 00:01:30.000
Link the project reference
Version history or a release reference can identify the exact change.
Release reference · Version history · Useful investigation trail

00:01:30.000 --> 00:01:39.000
Your checklist
Record when it changed · Describe what changed · Explain the reason · Name the person responsible · Record the checks performed · Link the project reference

00:01:39.000 --> 00:01:47.000
Keep a clear record alongside the actual project history.
jerseyweb.je