Microsoft has confirmed that Planner will finally support local custom fields and columns, with a worldwide rollout targeted for October 2026. The feature, now listed on the Microsoft 365 Roadmap, allows plan owners to add text, number, date, yes/no, and choice fields that can be sorted, filtered, grouped, and bulk-edited across web, desktop, and Mac clients. For anyone who has ever resorted to a separate spreadsheet just to track a ‘priority level’ or ‘department’ field, this update eliminates a long-standing friction point.

What’s Actually Landing

The roadmap item – ID 566867, posted on July 1, 2026 – describes local custom fields for Microsoft Planner, a capability that has been absent from the core experience since the tool’s debut. Here are the concrete details:

  • Field types: Text, Number, Date, Yes/No, and Choice (dropdown). These cover the most common lightweight tracking needs that usually send teams to Excel.
  • Surfaces: The fields will appear in Board view, Grid view, and the Task details pane. This means you can see and interact with them whether you’re dragging cards or scanning a list.
  • Interactivity: Microsoft promises sorting, filtering, and grouping based on custom fields, plus the ability to bulk edit multiple tasks at once. This last point is crucial – without it, custom metadata becomes a maintenance headache.
  • Scope: The word “local” means these fields belong to a specific plan, not a tenant-wide schema. Each plan can have its own set of columns, defined by the team that uses them.

What’s notably absent from the roadmap entry is any mention of mobile support or the Teams app integration. Historically, Planner features can lag on those clients, so watch for updates.

What This Means for You

The impact of custom fields varies widely depending on your role. Here’s how it breaks down.

For Team Leads and Everyday Users

If you’ve ever had to maintain a side spreadsheet to track information that Planner couldn’t hold, this is your escape hatch. A marketing team can now add a “Campaign Stage” dropdown and group their board by it. An IT help desk can track “Change Window” as a date field and filter tasks within a release window. Facilities teams can capture “Vendor” as a text field and “Compliance Flag” as a yes/no toggle. The feature moves Planner from a generic task board to a tool that can mirror your team’s real vocabulary. Bulk editing will save hours of clicking when you need to update a dozen tasks at once.

For IT Administrators

The new flexibility comes with governance challenges. Because fields are local – plan by plan – there’s no built-in consistency mechanism. Two teams could invent three different “Priority” fields with incompatible values. Reporting across plans becomes messy unless you enforce naming conventions early. Treat this feature like a tool that needs guardrails: set up templates, establish a shared dictionary of field names, and communicate expectations before the rollout.

Licensing is a major unresolved question. Until now, custom fields have been a premium‑only capability, bundled with Planner premium plans (formerly Project for the web features). The roadmap entry lists only “Planner” as the product and “General Availability” as the release ring, without clarifying whether the feature will appear in standard plans or remain premium. If you’re managing a tenant, you should check your license mix and prepare for two scenarios: either every plan gets custom fields, or only premium plans do. Either way, users will notice the difference and ask questions.

Data sensitivity also shifts. A task titled “Review renewal” is vague; a plan with a custom “Customer Name” or “Contract Value” field holds more business context. Before users start filling those fields, confirm that the data is covered by your existing eDiscovery, retention, and compliance policies. Planner data stored in group‑backed plans generally falls under SharePoint governance, but fields added here might not automatically inherit the same controls. Run a quick test with your Purview team.

For Developers and Automation Builders

A custom field is only as useful as the automation that touches it. If you use Power Automate to create tasks or update statuses, you’ll need to know whether custom fields are exposed through Microsoft Graph. Historically, Planner UI features have arrived before their API endpoints, and premium capabilities sometimes lag behind the standard REST surface. For now, assume that the October release will provide a UI‑only experience, and plan fallbacks accordingly. Keep an eye on the Microsoft Graph changelog for Planner updates; when a fields property shows up under plannerTask, that’s your signal to build.

How We Got Here

Planner launched in 2016 with a deliberately simple data model: title, description, dates, checklist, labels, and a board. That simplicity made it accessible but also created a ceiling. Teams that needed just one extra column would export data to Excel, move to Microsoft Lists, or adopt third‑party tools like Trello or Asana. Over the years, Microsoft added more complex capabilities – premium plans, timeline views, dependencies – but custom metadata remained absent from the base experience.

The 2024 rebrand to “the new Microsoft Planner” merged the old Planner with Project for the web, signaling a more ambitious roadmap. Microsoft’s own tech community blog showed a preview of custom fields in 2025, but that feature was tied to premium licenses. The July 2026 roadmap entry suggests a broader launch, though as noted, licensing details are still opaque.

This evolution reflects a larger bet: if Planner can handle everyday structured work, it reduces the number of apps a team needs to open. That keeps users inside the Microsoft 365 ecosystem and cuts down on information silos. For Microsoft, the competitor isn’t just Asana or Monday.com – it’s also Excel and Lists, which have been the workaround of choice for years.

What to Do Now

October 2026 may feel distant, but a few steps now will save you from a messy cleanup later.

  • Identify your high‑value fields. Survey the teams that use Planner the most. What missing column forces them to switch tools? Pick 3–5 fields that deliver the most immediate value.
  • Standardize names and values. If two teams need a “Priority” field, agree on the same name and the same choice list (e.g., High/Medium/Low). Document these in a shared wiki or Teams channel. This small act of discipline makes cross‑plan reporting possible later.
  • Audit current workarounds. Look for plans that already have ad‑hoc fields in the task title or checklist. For example, “[High] Review contract” tasks suggest a real need for a “Priority” field. Target those plans for early migration.
  • Review your Planner licensing. Log into the Microsoft 365 admin center and check how many premium Planner licenses you have. If custom fields remain premium, you’ll need a strategy for who gets them. If they become universal, your communication just needs to cover usage guidelines.
  • Talk to compliance. Ask your security team whether they want to restrict certain data types from Planner custom fields. If you’re in a regulated industry, this conversation is non‑negotiable.
  • Prepare a rollout message. Once the feature appears in your tenant, users will start experimenting. Send a brief email or Teams post with the do’s and don’ts before they build a tangle of inconsistent columns.

What to Watch Next

The roadmap date is a target, not a guarantee. Features can shift by weeks or months, so watch for messages in the Microsoft 365 admin center and the Planner Tech Community blog. Pay particular attention to:

  • Licensing clarity – Will this be standard or premium? The answer shapes your budget and governance.
  • API support – As soon as Graph enables custom fields, automation and reporting can follow. That’s when the feature becomes truly powerful.
  • Cross‑client parity – If fields work on web but break on mobile or in Teams, users will be frustrated. Monitor early feedback.
  • Field‑level permissions or formulas – These aren’t announced, but if Microsoft adds them later, they could change how you structure plans.

Custom fields may sound like plumbing, but in practice they can turn Planner from a simple task tracker into a genuine work‑management hub. With a little preparation, your teams can hit the ground running in October – not stumble into a governance mess.