Moving Forward: Why eMS v3 Is the Next Step

There comes a point in every long-term project where you have to stop asking, “How much more can we add to this?” and start asking, “What would this become if we built it the way we know it should work now?”

That is where we are with eFed Management Suite.

For the last year, eMS v2 has grown into something far bigger than what it originally started as. What began as a tool to help manage an e-fed has become a full management system with characters, events, results, promos, applications, media, rankings, contracts, achievements, finances, and so much more. Every update has added something useful. Every new version has pushed the system further.

But with that growth comes reality.

At some point, continuing to stack new features onto the same foundation becomes harder than stepping back and building the next version the right way from the ground up.

That is why the primary focus of eMS development is shifting to eMS v3.

To be clear, this does not mean eMS v2 is being abandoned overnight. The current v2 roadmap through 2.10.0 to 2.10.3 is still planned to be completed. Those updates will finish out the major items already laid out for the current generation of the software. After that, there will still be a period of smaller fixes, polish, and maintenance updates for v2.

But the future of active development is now focused on the next generation.

And honestly? It needs to be.

Why Build eMS v3?

The simplest answer is control.

eMS v3 is being built around the idea that your fed should work the way you need it to work. Not the way a default install says it has to work. Not the way another fed does it. Not the way older versions of eMS assumed things should be structured.

Your fed. Your rules. Your setup.

One of the biggest changes in v3 is the move toward much more granular permissions. In v2, giving someone access to certain areas could sometimes feel like opening the flood gates. You may want someone to help manage one small part of the site, but not want them anywhere near the rest of the admin tools.

eMS v3 is being designed to fix that.

You will be able to grant non-admin users access to very specific tools and actions without making them full admins. That means more flexibility, safer delegation, and a better experience for fed heads who want help without giving up control of the entire system.

A Better Public Site System

Another major reason for the rebuild is the new public site builder.

In v2, custom functions helped make pages more dynamic, but they also came with limitations. In v3, those are being replaced with a much more flexible module-based system.

You will be able to add your own HTML, CSS, and JavaScript templates, then create pages and drop in pre-built modules where you need them. The goal is to let you build a fed site that actually feels like yours, without needing to fight the core system every time you want to change a layout.

Even better, main content layouts can be set on a per-page basis.

That means one page can have a certain structure, another page can have something completely different, and you are not locked into one rigid layout across the entire site.

One of the biggest frustrations with any system like this is when a core update accidentally breaks a fed’s custom design. With eMS v3, the user-facing pages are being built in a way that separates the core functionality from your layout much more cleanly. The goal is simple: updates to core pages should no longer wreck your fed’s design.

That alone is a massive step forward.

Features, Features, and More Features

Everything currently available in eMS v2 is being rebuilt for v3.

This is not a stripped-down replacement. This is not starting over with fewer tools and hoping to catch up later. The goal is to rebuild the existing feature set with a stronger foundation, better organization, and more flexibility.

But v3 is not just a rebuild.

It is also where the next era of eMS begins.

Two of the first major new features already make the switch worth paying attention to: multi-fed support and multi-brand support.

For larger communities, networks, or promotions with multiple shows, divisions, or brands, this is a huge deal. Instead of trying to force everything into one structure, eMS v3 is being built to support more complex setups from the start.

That opens the door for more realistic promotion management, better organization, and more freedom for fed heads who want to grow beyond a single-brand format.

Customize What Used to Be Default

Another major difference in v3 is that more of the system can be turned off, adjusted, or completely customized.

In v2, certain things were treated as standard. Genders. Alignments. Public pages. Application fields. Bio fields. The system gave you options, but there were still parts that assumed a certain way of doing things.

eMS v3 is taking a different approach.

Don’t use alignments? Turn them off.

Want to customize genders? You can.

Need to temporarily disable the public-facing side of your fed while you work on setup or maintenance? Click a button.

Want character bios to show fields that matter to your fed, instead of being locked into what eMS thinks should be there? That is exactly the point.

Why should the software tell you what your roster pages need to display?

Why should applications be forced into a structure that does not match how your fed accepts characters?

eMS v3 is being designed so you can add the fields you need. Bios and applications should reflect your fed’s style, rules, and expectations. Not someone else’s.

A Better Booking Flow

The booking process is also getting a major overhaul.

In v2, getting a show together could sometimes mean bouncing between five or six different pages. You might start in one area, jump to another to adjust matches, go somewhere else for segments, then another page for results, then another for publishing.

It worked, but it was not always as friendly as it could be.

With v3, the goal is to make booking more natural and less scattered. The system should help you build a show, not make you hunt through the admin panel just to finish one.

That means better flow, better organization, and fewer unnecessary clicks.

There will always be a lot of information involved in running an e-fed. Matches, segments, writers, results, titles, statuses, publishing, and more all matter. But managing those pieces should feel smoother than it has in the past.

That is one of the biggest goals of v3: make powerful tools easier to actually use.

Documentation From the Start

One of the most important improvements in eMS v3 is not just a feature for running your fed.

It is a feature for understanding the system itself.

eMS v3 includes an internal documentation database. As new parts of v3 are built, documentation is being added along with them. That means the docs are not being treated as an afterthought or something to maybe write later.

They are part of the development process.

The goal is to create a living, breathing information center inside eMS that explains how each part of the system works. Whether you are managing templates, pages, modules, characters, booking, settings, or permissions, the documentation area will grow alongside the platform.

That matters because eMS has become a large system. A powerful system is only useful if people can understand how to use it.

What About Existing v2 Users?

If you are already using eMS v2, the obvious question is: what happens to my data?

The answer is that an importer is planned.

Will it be possible to port absolutely everything perfectly from v2 to v3? Probably not. The systems are different enough that some things may not translate one-to-one. That is part of the reality of rebuilding something properly instead of forcing the new version to carry every old limitation forward.

But the important data will be the focus.

Users. Characters. Character information. Results. Promos. Event history. Core fed content. The pieces that matter most will be part of the upgrade path.

The goal is to make the move to eMS v3 as practical as possible for existing users, while still allowing v3 to be the clean rebuild it needs to be.

Because the entire point of v3 is not to recreate every old limitation.

The point is to move forward.

The Next Generation of eMS

eMS v2 has done a lot.

It has grown, changed, expanded, and supported more features than originally imagined. But v3 is the opportunity to take everything learned from building v2 and use it to create something stronger, cleaner, and more flexible.

This is not just another update.

This is the next generation of eFed Management Suite.

More control. Better permissions. A stronger public site builder. Custom fields. Multi-fed support. Multi-brand support. Improved booking. Internal documentation. Cleaner updates. More flexibility over what your fed shows, hides, uses, and ignores.

That is the future of eMS.

We will finish the v2 roadmap we committed to. We will continue to support it with fixes and smaller updates for a period of time. But the main development focus is now where it needs to be:

Building eMS v3.

From the ground up.

For the way e-feds actually run.

Learn more about the eFed Management Suite at https://efedmanagementsuite.com

Have suggestions, feedback, or want to be in line for an early sneak peek? join our Discord: https://discord.com/invite/jZVpQBkE2B

*All images displayed in this article are real, and from the in-development eMS v3. Some features and designs may change between now and release.