Features

There are three things a decision register has to do well. Capture the call with enough context that someone else can read it back later. Lock it down once the team commits, so the record is defensible. Review it on a deliberate cadence, so the outcome lands while the rationale is still readable. Decision Planner is built around those three jobs; the views, dashboards, templates, and customisation surfaces are downstream of them, not the point.

Capture in minutes, find for ever

A complete entry takes a few minutes to record and outlives every other artefact of the meeting.

One form, two halves

The top half holds the structured metadata: title, summary (capped at 500 characters), status, category, department, team, the date taken, the revisit date, the people involved (Entra account pickers, not free text), the options considered, and the rationale. The bottom half holds the outcome rating, the date reviewed, outcome notes, and the lineage (what this decision supersedes and any related decisions). Top half gets filled at capture; bottom half at revisit.

Five ways to read the same register

The same decisions, looked at five different ways. Switching never costs you anything because the underlying data is the same SharePoint list. Every view sits above the same Revisit Radar and Quality Dashboard, so the context is consistent and only the bottom half of the page changes shape when you pivot. Click any image below to zoom into the detail.

List view

The searchable, sortable register. The day-to-day surface. Title, status pill, category, date taken, decision-makers, revisit indicator, sign-off state. Virtualised so a register of thousands of records stays responsive. The default view on every install.

Timeline view

Quarterly bands across the year. See at a glance what was decided when, and where the activity clusters. Each decision card shows the status, the category, the title, the summary, and the date taken. Useful for post-quarter reviews and “what did we even do last quarter?” conversations.

Matrix view

Category on one axis, status on the other. Spot where the activity (or the backlog) lives at a glance. The Proposed column tells you what’s in flight; the In Effect column shows what’s been delivered; clicking a cell pivots the list view to that exact slice.

Heatmap view

Quarter against category, shaded by volume. See where the team has been spending decision energy and where it has not. Useful for spotting category drought (you haven’t made a Compliance decision in two quarters: should you have?) or hotspots (every decision this quarter was Technology).

Lineage view

Supersession chains drawn as a graph. Follow how a decision evolved through revision and replacement. The leftmost node is the original; arrows point to its replacement. Click any node to open the detail panel. Essential when an external party asks “why did you change your mind in 2024?” and you need to show the chain, not just the latest entry.

Strategic Overview report

A one-click multi-section breakdown of the register. By category, by status, quarterly trend across the last eight quarters, and the top decision-makers. The headline numbers you need for a board pack or a programme review, generated from your live register, without setting foot in Excel.

Accountability you can defend

A decision register is only useful if the people responsible are tied to the decisions they made, and only credible if outcomes get recorded against the original rationale.

• Sign-off and lock records who signed and locks the record from edits, with a confirmation dialog so the action is deliberate
• Revisit cycle with a Pending Review queue, a Revisit Radar surfacing overdue and due-this-month decisions, and a Mark-as-revisited closing entry that captures the actual outcome
• Outcome ratings (Successful, Mixed, Unsuccessful, Too early) feed the success-rate metric, so the Quality Dashboard reflects what actually happened, not what was planned
• Decision-makers and stakeholders are people-picker fields, so the audit trail names real Entra accounts rather than free-text names
• SharePoint version history carries every edit before lock-in: the audit chain is the one your tenant already trusts

Insight, derived from outcomes you actually recorded

The Quality Dashboard is the headline metric. A success-rate gauge derived from outcomes captured at revisit (not from sentiment, not from “what we hoped”), broken down into Successful, Mixed, Unsuccessful, and Too early. The “Too early” bucket is deliberate: a decision pending its revisit window stays out of the success number until the team has actually formed a view.

Templates that suit different teams

Template	What it captures well
Strategic decision	Long-horizon calls with named owners and a clear “we are committed” moment
Technology choice	Vendor or stack selection with options considered, costs, and trade-offs
Vendor selection	Procurement-style records with evaluation criteria and shortlists
Hiring decision	Panel calls with rationale, dissent, and outcomes after a review window
Policy change	Internal policy or process changes with the reason and the affected stakeholders
Blank	A clean form when none of the above fit

Enterprise customers can add their own templates and category lists, without writing code, so a regulated team can adopt a register that matches their internal audit language on day one.

Lives where your team already works

Designed for governance from day one

Real teams have permission boundaries, retention rules, and audit requirements. Decision Planner reads and writes a normal SharePoint list, so all of that just works.

• Existing permissions apply. A user only sees the decisions they can see in SharePoint
• Retention policies carry through. Records aren’t deleted independently; they expire the way your tenant says they should
• Version history is preserved. Every edit before sign-off is in the SharePoint version chain
• Cross-site list selection (Enterprise) lets a programme office point at any list on any site they have access to, without copying data
• Custom categories and templates (Enterprise) are configured by admins, not engineers

Compatibility and accessibility

The features we won’t build

A decision register works because it is the boring, reliable record everyone goes back to. Add too much and it stops being that. The list below is the running record of asks we have turned down, with the reason in each case. Some of these stay closed permanently; one or two might open if the product moves into territory we haven’t tested yet.

No workflow approval engine

If a decision needs to route to a specific approver before sign-off, that is Power Automate’s territory. Decision Planner exposes status changes as events your flows can react to. Sign-off itself stays in the hands of the named decision-maker.

No discussion thread on a decision

That turns a register into a project tool with its own storage and notification model. SharePoint modern list comments already exist on every item and stay in the source of truth.

No real-time collaborative editing

A SharePoint web part has no SignalR layer. Building real-time would require infrastructure outside your tenant. Edits are saved as they happen; conflict detection catches collisions when two people edit the same record.

No external integrations beyond M365 + JFDI suite

Customers asked for Jira, Confluence, ServiceNow, and Salesforce links. We are deliberately keeping the surface to Microsoft 365 + JFDI products at first, because that is where the data already lives and the permission story is coherent.

No private decisions hidden from the audit log

Every decision is in the list; visibility is controlled by SharePoint permissions on that list. We will not ship a private-mode that bypasses the audit trail, because the whole product depends on the audit trail being trustworthy.

No client-side export of the register

SharePoint lists already export to Excel natively, and that export is more trustworthy than anything we could generate client-side from a filtered view.

A register earns its keep by being trustworthy across years, not by being feature-rich in any given quarter. The boundary above is part of how we keep that trust.

Licensing tiers

Decision Planner is available in three tiers. All tiers include capture, sign-off, and the List view; higher tiers unlock additional views, dashboards, and customisation.

Free is enough to capture and sign off decisions with the List view, on a SharePoint page.

Standard adds the revisit cycle, search, the Quality Dashboard, four more views, and Teams / Outlook / M365 home surfaces.

Enterprise adds Heatmap, Lineage, the Strategic Overview report, admin-defined categories and templates, cross-site list selection, and the integration surface for the rest of the JFDI suite.

Tier enforcement is rolled out progressively as the licensing flow lights up. Heatmap and Lineage are gated today; the remaining gates land alongside the Microsoft Marketplace listing. A 30-day Enterprise trial is included with every install once we ship.

Ready to make decisions you can defend?

Decision Planner is coming to the Microsoft commercial marketplace. Pilot today with the full Enterprise surface; install on your tenant when the listing goes live.

Join the pilotSee pricing