The JFDI Planner Suite

Resource Planner is the fifth product in the JFDI Planner Suite, a family of focused SharePoint apps that share an SPFx packaging, a per-user licensing model, an in-tenant data philosophy, and a coordinated release rhythm. Calendar Planner shipped first; Process Planner, Decision Planner, and Booking Planner are at production or in active pilot; Resource Planner is in MVP build; Content Planner is the next product after this one.

Calendar Planner

Calendar Planner

Six views (Year, Month, Week, Grid, Timeline, Gantt) over native SharePoint events. The calendar SharePoint should have shipped with.

Process Planner

Process Planner

A kanban board for any multi-stage process. 30+ business templates, multi-source unified board, drag-and-drop, offline-capable.

Decision Planner

Decision Planner

Capture decisions, owners, options, and outcomes against the work they affect. Built-in revisit cycle and Quality Dashboard.

Booking Planner

Booking Planner

Meeting room, desk, and resource booking on top of SharePoint. Floor-plan first, admin-friendly, QR check-in.

Resource Planner

Resource Planner

Forward demand and capacity planning on a quarterly board. Traffic-light cells, audit trail, links into Decision Planner.

Content Planner

Content Planner

Coming soon

Editorial calendars and content workflows for marketing, comms, and internal teams.

What ties the suite together

The Planner products share their plumbing. All of them are SPFx web parts; all of them store data in SharePoint lists inside your tenant; all of them authenticate through Entra. The design system is shared, the licensing is identical (per user, per month, through the Microsoft commercial marketplace), and the release rhythm is coordinated so customers running more than one product can plan rollouts in step.

Where Resource Planner stands apart in the family is its closer pairing with Decision Planner. The two products read each other’s SharePoint lists: a demand item can reference the decision that triggered it, and a capacity gap can prompt a decision to be recorded against it. The integration is through shared schema rather than hard dependencies, so each product still works on its own.

Want to be notified when the next product ships?

Tell us which Planners are most useful and we’ll let you know as they go live.