generate-closure-report

To generate a project closure report, provide the charter, plan-fact report, and lessons learned as inputs. The system aggregates these sources to produce a structured closure document with deviations, risks, and recommendations.

An automated project closure post-mortem summary includes sections for Project Results, Plan-Fact Deviations, Realized Risks, and Lessons Learned. These sections are populated directly from your provided charter, risk register, and plan-fact data.

Yes, you can create a formal project closure document in multiple languages. The system supports language-specific templates with RU and EN triggers, allowing multilingual teams to generate the post-mortem summary in their chosen language.

A risk register is optional when automating lessons learned capture. While providing it enriches the Realized Risks section, the core requirement is the charter, plan-fact report, and user-provided lessons to generate the closure documentation.

The best way to compile plan-fact deviations and realized risks is to input the plan-fact report and risk register together. The system automatically extracts and structures these deviations into the formal closure-report template.

Generating a project closure report without a formal charter limits the context for project results and deviations. The charter provides baseline objectives, so omitting it may result in a less comprehensive post-mortem summary and lessons learned analysis.