TOOL 5 OF 6

Check before release

Bring the checks together before the system is put into use.

No system named yetVersion not recorded · Owner not recorded

Edit system details

System nameVersion / configurationOwner or responsible role

Review the intended use and GxP answers

You can start here. Check system use when you are ready to connect the work to a system assessment.

Bring the checks together

Items remain before the release decision

Review the open items below. A completed checklist cannot override a failed, missing or outdated test result.

0functions

0 / 0test entries complete

23open items

Why are these items carried forward?

The release decision depends on the stated use, reviewed requirements, suitable supplier information, actual test results and resolved problems. Missing references and results from a changed plan need review.

What still needs attention 23

These items stay open until you record the answer or supporting evidence.

Record the system name and what it does.Complete or review the system assessment.
Record the version or configuration being released.Complete or review the system assessment.
Name the responsible owner or role.Complete or review the system assessment.
Confirm whether the use is GxP.Complete or review the system assessment.
Confirm electronic record requirements.Complete or review the system assessment.
Confirm the software type.Complete or review the system assessment.
Confirm whether regulated electronic signatures are used.Complete or review the system assessment.
Name the supplier or service.Record the provider for this system.

Show 15 more items

Confirm who supplies the software.Choose supplier or internal development.
Has your team reviewed the supplier?Not yet confirmed.
Are software development and change controls suitable?Not yet confirmed.
Do you have the actual test results?Not yet confirmed.
Do those results cover your functions, version and setup?Not yet confirmed.
Have known problems and local differences been reviewed?Not yet confirmed.
Are support, changes and record responsibilities agreed?Not yet confirmed.
Identify the important functions.Add at least one function before planning tests.
Has the system use and scope been reviewed?Not yet confirmed.
Have the requirements, risks and testing been reviewed?Not yet confirmed.
Have failed tests and remaining problems been resolved?Not yet confirmed.
Are access, record history, retention and recovery checks complete?Not yet confirmed.
Are procedures, training and support ready?Not yet confirmed.
Has the summary of testing been reviewed?Not yet confirmed.
Is the release decision recorded in your controlled process?Not yet confirmed.

Release review

Has the system use and scope been reviewed?

Include the system version, GxP decision, required records and excluded work.

Have the requirements, risks and testing been reviewed?

Reference the approved plan and requirement / test links.

Have failed tests and remaining problems been resolved?

Record corrections and retests. Any remaining risk needs a separate documented decision.

Are access, record history, retention and recovery checks complete?

Include signatures and interfaces where used.

Are procedures, training and support ready?

Confirm who will use and support the system, including incident handling.

Has the summary of testing been reviewed?

Reference results, deviations, limits of use and the conclusion.

Is the release decision recorded in your controlled process?

Enter the approval reference. This website does not sign or approve release.

Keep a copy of your work

Download a PDF for review. Save the working file to continue another day or on another device.

Open working file