Creating Chapter Legacy Projects That Outlast Officer Terms

As Indiana HOSA’s largest annual conference, the State Leadership Conference, quickly approaches, chapter officers should be thinking about the lasting impact or legacy they leave behind as they prepare to leave office. Every active HOSA chapter already runs events. Some of these events may have been traditions within the chapter for years, while others may be brand new. The difference between planning events and structuring systems is crucial to creating a legacy project that has a meaningful impact beyond current HOSA members. Think about the initiatives your chapter remembers most and that your members absolutely love: they’re rarely one-time events. Banquets, bake sales, holiday service projects, field trips, etc. are the programs, partnerships, and traditions that give each chapter its history. One truth exists about creating impact that can last decades: it doesn’t happen accidentally. This blog guides you through a practical framework for creating projects that remain incredibly effective, engaging, and relevant well beyond a single officer team or HOSA year.

The first step in creating a legacy project is identifying an actual problem that needs a solution in a community. If a chapter starts with the issue and brainstorms solutions, creating a novel event becomes much easier. The challenge lies in identifying a pressing issue that remains unresolved. By conducting a simple needs assessment using input from members, advisors, community members, and partners, a chapter can clearly identify two things: what people care about and what has not been addressed. Perhaps new members struggle to stay involved, clinical exposure opportunities are few and far between, or a certain population in the community is struggling to make ends meet or find entertainment. When a project addresses a problem that reappears every year, it remains relevant regardless of who the chapter leadership team is. For instance, a chapter might recognize that freshmen lack mentorship, feel disconnected, and make the same mistakes that upperclassmen did. Subsequently, a team might create a structured peer mentorship program with a defined board and roles, meeting schedules, and training materials that can be shared and improved upon across multiple years. The program then becomes a permanent solution to a recurring problem rather than a temporary fix. 

The second step is one of the most crucial points of this process. Often, projects fade away or collect the so-called “cobwebs” because their success depends on the memory or energy of a single leadership team. If the officer-elect team lacks either of these fundamental aspects (memory, meaning the infrastructure of guides, notes, feedback, etc. from previous years, and energy, meaning the passion for fighting the issue), then systems fall apart. Instead, you can simply keep systems consistent by sharing folders, templates, checklists, etc., which is more sustainable than relying exclusively on passed-down knowledge that might get filtered in translation. Ever heard of the telephone game? That is exactly what will happen if your team doesn’t keep cumulative records. Having the president, secretary, and committee heads collect and compile information allows future teams to focus on making improvements to previous systems instead of trying to reinvent the wheel. I suggest making three core documents by the end of the event/year: a one-page overview describing the purpose of the event and its goals, an operations guide outlining procedures step by step, and a timeline highlighting key milestones and checkpoints. Of course, this system is subject to change based on the chapter and a wide variety of other factors. 

The third step is building ownership beyond the officer team. When the entire chapter is passionate about the project, then it becomes long-lasting and extremely powerful. Establish committees so that underclassmen naturally gain the knowledge and skills to lead these events in the future instead of scrambling to teach them once they become elected. Get your advisor involved, speak with your administrators, and maybe even request funding to ensure institutional support for the initiative. Create partnerships with external organizations in the community and build personal relationships to ensure that these organizations continue to support your chapter as it demonstrates sustained progress. Feature them at kickoff meetings and even invite individuals to award ceremonies to recognize them for their impactful contributions! This will intertwine both organizations, HOSA and the partner, in a way that fosters long-term mutualistic benefit.

The fourth step is measuring impact. As with any goal, event planning requires quantifiable metrics that show value. For instance, service hours, participation numbers, funds raised, or community outcomes like screenings completed or educational sessions delivered are needed to truly see the change. Moreover, when it inevitably comes time to share the success of your HOSA chapter with the world, it will be impressive for others to see the specific, measurable, positive benefits the community receives. This in turn may allow for additional support in following years to expand upon, scale, and improve the initiative. At the end of each year, compile a brief impact summary, which serves as a record to help future officers make decisions about where to allocate time and resources. 

The fifth step is formalizing the transition process. Leadership transitions should involve more than one ceremony where the officers and officer-elects do not get to have a conversation. There should be a transition meeting where outgoing leaders meet with incoming officers to exchange contact information and review documents, timelines, and lessons learned before the school year ends. This structured transition allows knowledge to be passed down, which contributes to the effectiveness and longevity of legacy projects.

Several common pitfalls can undermine even the most well-intentioned efforts. Projects that are overly complex or resource-intensive often struggle to persist when enthusiasm fades. Initiatives that lack advisor awareness and support constantly battle with logistics. Without documentation of the entire process, crucial details are lost. Finally, projects driven by short-term recognition rather than genuine need usually fail over longer periods of time. Each of these risks can be mitigated by focusing on efficiency, alignment with chapter priorities, and consistent record-keeping.

At its core, legacy building reframes leadership as stewardship. The most meaningful contribution an officer team can make is not to host one-time events but to leave behind systems that empower future health professionals to go further. When a project continues to serve students and communities years later, it extends the influence of a single group of revolutionary leaders across multiple generations. Chapters that focus on sustainability take isolated efforts and morph them into lasting impact, ensuring that a single innovative idea, program, or event snowballs into a legacy project that is extraordinary.

Yonathan Bezza

President

2026