U dont need to bother for it, simply a Validation Summary Report provides an overview of what was accomplished and concludes the documentation. Yes as advised above Results of execution,Deviations and observation noted should be covered, and on the basis of this the action plan is decided by validation team.
Addis Pharmaceutical Factory SC. Ethiopia
Validation Summary Reports provide an overview of the entire validation project. When regulatory auditors review validation projects, they typically begin by reviewing the summary report. The validation summary report should include:
A description of the validation project
All test cases performed, including if those test cases passed without issue
All deviations reported, including how those deviations were resolved
Summary reports should be signed by the System Owner and Quality Assurance. Once the summary report is signed, the validation project is considered to be complete.
The collection of documents produced during a validation project is called a Validation Package. Once the validation project is complete, all validation package should be stored according to your site document rules.
on the first, pls..do not make the same mistake like many of your colleagues from Val. Dept.!!!!
First of all, you need to spend some time into production area, to see what happen there, to work toogether with other people, to see, recognize and learn all about process there, machines, devices, enviroment, legislatives..etc, etc..
Once when you get a lot of expiriences, you could start validation.You need to KNOW how to do, also you need to FEEL.
It is not like just seat and write procedure. Much experiences, much learning...after that..writing.