Picture a campus team piloting a simple digital log of food left uneaten in a canteen. Students collect information, staff explore possible changes and the team prepares its final presentation. For this green and digital initiative, an important question remains: who will maintain the process after the student assignment ends? That question belongs in the project plan from the beginning.
Define the intended change, not only the output
A spreadsheet, dashboard or report is something a team can deliver. The intended benefit is the change that using it is meant to support.
In the canteen example, creating a digital log would be an output. Using reliable information to inform decisions about avoidable food waste would be an intended benefit. Demonstrating an actual improvement would require appropriate evidence; the existence of the log alone would not establish it.
Ask learners to state both parts clearly. What will they produce, and what should someone be able to do with it?
Then identify how the team would recognise progress. Which observations would be relevant? What starting information is available? Who could interpret the findings in the working context?
Keep the ambition proportionate. An educational pilot could test whether a recording process is usable without claiming to have solved the wider problem.
Make ownership part of the design
A plan for continued use needs more than the phrase “the institution will take over”.
For the hypothetical canteen project, a handover discussion could identify the person or team responsible for keeping records, reviewing them and deciding whether to change the process. Those responsibilities should be discussed with the people concerned, not assigned to them at the end.
Ask what would make the routine manageable. Could it fit existing work? What instructions would be needed? What would happen when the usual person is unavailable?
Also clarify who will maintain any shared files or digital tools and how an incoming team could understand the records. Avoid leaving essential knowledge with one student who knows how the spreadsheet works.
The resulting arrangement might be modest: a named contact, a short guide and an agreed review point. What matters is whether the people expected to continue the activity understand and accept the responsibility.
Plan for review, including the option to stop
Continued use should not become a goal regardless of usefulness. A pilot may reveal that the original approach requires too much effort, collects the wrong information or duplicates an existing process.
Build a review into the plan. Ask the people using the proposed system what helps them and what creates unnecessary work. Compare that feedback with the original purpose.
For the canteen scenario, the team might discover that a detailed recording form is impractical during a busy service period. A sensible response would be to reconsider the approach with staff rather than assume that more reminders will solve the problem.
Document what changed and why. Keep observations separate from interpretations, and avoid treating a short trial as proof of a lasting result.
A responsible final recommendation could be to continue, adapt or stop. Each option should be connected to the evidence and to what the organisation can realistically maintain.
Make project delivery a learning outcome
These questions turn project management into something learners can practise: defining a purpose, identifying responsibilities, considering constraints and planning how work will be used.
Sustainable project management is among the areas included in GreenTech Horizons’ project design. Its second work package (WP2) connects learning with a wider competency-oriented approach combining green, digital and business knowledge.
An educator could apply that connection by asking student teams to submit a short continuation brief alongside their final presentation. The brief would identify the intended user, the work needed after completion, the agreed responsibilities and the next review decision.
Students could also explain which parts remain proposals and which have been discussed with the relevant people. A suggested arrangement is not the same as an accepted commitment.
For us at European Academy, that distinction is important. A convincing plan should make the conditions for continued use visible rather than promise that a good idea will sustain itself.
Ask the handover question early
A green pilot should leave behind more than a demonstration. It should make clear what was learned, what remains uncertain and what would be needed for useful continuation.
Before starting your next student or workplace project, ask: “Who could use this after we finish, and what would they need from us?” Put that conversation into the plan. The answer may change what you decide to build in the first place.
Hashtags: #GreenTechHorizons #EuropeanAcademy #SustainableProjectManagement #CapacityBuilding
Alexia Voutsina, Project & Business Development Manager, European Academy
Alexia Voutsina is a Project and Business Development Manager at European Academy, working at the intersection of EU-funded projects, professional training and international cooperation. She holds an MBA from European University Cyprus, complementing her academic background in Educational Sciences and Special Education. Her work focuses on translating ideas into practical learning experiences that strengthen skills, promote sustainability and support meaningful professional growth.
