Main flow · 06
The project does not end at the peak moment. Many of the most valuable lessons are learned afterwards, and Sapluna helps capture them for future projects.
06 · Post Production
Post Production
Many projects focus almost entirely on the main event or delivery milestone.
In reality, however, a project does not end when the event takes place, the service is delivered, or the key objective is achieved. After the live phase comes post-production, whose purpose is to complete the project in a controlled manner, ensure the value of collected information, and create a foundation for future improvement.
In Sapluna's operating model, post-production is just as important as preparation and live production.
Typical post-production activities include invoicing, payment processing, reporting, feedback collection, feedback analysis, resource returns, maintenance activities, documentation and archiving.
During post-production, the project is packaged into a completed whole.
The project is considered fully completed only after post-production has been finalized.
Post-Production Follows the Same Logic
The Sapluna Roadmap contains dedicated Work Cards for post-production activities. Just like preparation and live production, post-production progresses through structured Work Cards.
This ensures that project closure does not depend on individual memory but follows a repeatable process.
Work Cards define:
Analyze Results and Learn from the Project
A significant amount of information is collected during preparation and live operations. Post-production provides the opportunity to analyze this information and transform it into useful insight.
These data points help create a comprehensive understanding of project performance.
Sapluna's AiLi AI Agent can assist by analyzing data, producing summaries, and generating project reports — accelerating learning and making valuable insights easier to identify.
Examples include:
Project Information Becomes Part of the Organization
Throughout the project, information is managed within the project database.
During post-production, organizations can decide what information should be transferred to the organization level and what should be integrated into core business systems. This happens according to the Sapluna Bridge philosophy.
Many organizations maintain official archives in separate systems. Sapluna can generate the necessary information package and transfer it to those platforms for long-term storage and governance.
Examples include:
Every Project Creates Benchmark Data
Even when a project ends, its information continues to provide value. Selected project information can be transferred to the organization level, where it contributes to broader analysis.
The more projects an organization completes, the more valuable this comparison data becomes.
Organizations can compare:
Progress Is Tracked Until Completion
Post-production activities are tracked using the same methods as preparation activities.
If work is delayed or at risk of delay, management can respond proactively, and Sapluna can also send automated reminders to users with unfinished tasks — keeping project closure under control and preventing important activities from being forgotten.
Tasks and Work Cards can include:
Automatic Project Closure
The default duration of the post-production period in Sapluna is 30 days. After the live phase ends, the project remains open for post-production activities for thirty days, and if the Project Admin does not manually close the project, Sapluna closes it automatically at the end of the period.
If additional time is needed, the Project Admin can reopen the project for another thirty-day period. Projects can remain active as long as required.
This helps prevent situations where:
What Happens When a Project Is Closed?
When a project is closed, user access to active project work ends.
Closing a project does not delete information. It simply ends active work within the project environment.
At the same time:
The Project Archive Becomes Organizational Memory
One of Sapluna's most valuable capabilities is the Project Archive. Organizations frequently need access to information from previous projects.
Traditionally, finding such information can be time-consuming and difficult. With Sapluna, all project-related information remains stored in one place.
Even projects completed years ago can be reviewed quickly and efficiently.
Historical information may be needed for:
The archive contains:
Continuous Learning Begins in Post-Production
The most important purpose of post-production is not project closure. Its most important purpose is learning.
When feedback, analytics, reports, and observations are processed systematically, they can be incorporated into operating models and project templates. As a result, future projects do not start from scratch — they start from better knowledge.
Every project generates knowledge about:
The Project Ends, but Knowledge Lives On
From Sapluna's perspective, the end of a project does not mean the end of its value. On the contrary.
The purpose of post-production is to ensure that the knowledge, analytics, information, and experience generated during the project remain available to the organization. When project information becomes part of the organization's shared knowledge base, every project increases organizational capability.
For this reason, post-production in Sapluna is not simply project clean-up. It is the stage where an individual project becomes shared learning, benchmark data, and a competitive advantage for future projects.
Other steps
01 · Organization Level
02 · Project Playbook
03 · People & Roles
04 · Processing Data
05 · Live Operations
