Skip to content

Who FedMS is for

FedMS is a deliberately opinionated platform. It is at its best when the unit of work in your organization is a structured engagement with a defined group of people over a defined window of time, repeated many times a year, often involving more than one organization.

This page describes the audiences for which the platform was built and a few scenarios where the design pays off particularly well.

Primary audiences

Training companies

Organizations like Amplius Partners that deliver professional training to corporate clients are the canonical FedMS customer.

A typical training company:

  • runs dozens to hundreds of workshops per year,
  • each workshop has 5–50 delegates from a single client organization,
  • each workshop involves at least one trainer/speaker and one moderator,
  • pre-workshop, mid-workshop, and post-workshop deliverables (briefs, pre-reads, slides, recordings, feedback forms, certificates) need to reach the right people at the right time,
  • the client needs visibility into what is happening, what they owe the trainer, and what their delegates are getting.

FedMS lets the training company run a tenant site for itself, and offers its corporate clients their own federated instance so that the client has full visibility into its own engagement — without having to log in to the trainer's back office.

Event agencies

Agencies that organize events on behalf of business clients — conferences, summits, internal away-days, partner events — face many of the same problems as training companies, but with two twists:

  • the client is much more involved on the agenda side and often wants editorial control over the public-facing content,
  • service providers (venues, AV companies, caterers, translators) need to be brought into the workflow without giving them access to the whole event.

FedMS' role-based group permissions and the Service Provider role are designed for exactly this.

Professional bodies running CPD programs

Bodies that certify continuing professional development for their members need to track which member attended which session, what evidence was captured, and what certificate to issue. FedMS' task patterns and the attachment entity (which can carry signed forms, recordings, and evaluation results) are a natural fit.

In-house learning-and-development teams

L&D teams in large organizations often run a parallel calendar of internal training, onboarding programs, and leadership programs. They need many of the same primitives — events, sessions, delegates, tasks — but with their own users instead of external clients. Running FedMS as a single-tenant instance gives them a structured platform without the overhead of building one in-house.

Scenarios where FedMS pays off particularly well

Multi-org events

The same event involves people from multiple organizations who all need the right view of the same reality. FedMS' federation is designed for this from the ground up.

Repeating event templates

You run the same workshop format ten times a year for different clients. Defining the workflow once as an event type + task patterns, and instantiating it per client, is faster, more reliable, and less error-prone than copying spreadsheets.

Workflows that change with role

What a Delegate sees, what a Speaker sees, and what a Manager sees about the same event are very different things. FedMS' role-based visibility and task assignment let you express that difference cleanly.

Compliance-sensitive engagements

You need an audit trail — who was invited, who attended, what they received, what they returned. Because every task in FedMS is a tracked content entity with revisions, and because membership changes are soft-deleted rather than erased, FedMS produces this audit trail by default.

Federations of organizations

Trade associations, networks of consultants, alliances of training companies — anywhere multiple organizations need to coordinate but remain independent — are a natural fit for the federated model.

Scenarios where FedMS is not the right fit

To be honest about the boundary:

  • Pure broadcast platforms — if you sell on-demand video courses to anonymous customers, a pure LMS / video platform is a better fit.
  • One-off events — if you run a single annual conference, the overhead of installing and configuring a tenant FedMS instance may exceed the value.
  • Lightweight scheduling — if you just need a calendar, a polling tool will be cheaper.
  • Real-time collaboration — FedMS is structured-workflow software, not a chat or whiteboard product.

Next steps