Meta introduced spaces in its Muse app on November 6, 2026. You describe a view you want, such as a hub for freelance projects, and Muse builds it. Meta says connected apps can supply updates in the background. If a client deadline changes in that view, the next step is to check what the client actually agreed to.

Conceptual illustration of a freelancer comparing two calendar cards; not a Muse interface.
Conceptual illustration of a freelancer comparing two calendar cards; not a Muse interface.

Give each deadline a meaning

A freelancer might track an internal review, a client review and final delivery for the same job. Three dates can all be correct when they refer to different milestones. Use a short label for each milestone so a date for feedback cannot silently replace a date for delivery.

Before building a hub, decide which record your team will consult for confirmed changes. For one project it might be a written client confirmation; for another it might be a shared project schedule the client maintains. Keep that choice in the project brief. A calendar reminder and an agreed milestone serve different purposes.

Try a fictional schedule change

Imagine a designer whose client confirms Thursday at 3 p.m. for final delivery. A teammate moves a calendar reminder to Wednesday at noon so the team has time to rehearse. The designer sees Wednesday in a planning view. Before notifying the client or shifting other work, the designer checks the event label and the client’s confirmation. Wednesday is the rehearsal; Thursday is still delivery.

If the client later confirms a Wednesday delivery, update the agreed schedule and check that the team can see the change. The example is fictional. It illustrates how to reconcile records; it does not describe how Muse chooses between conflicting dates.

For a related planning exercise, the Tana meeting-agent guide shows how to keep a proposed date separate from an agreed decision before sharing it.

Keep a short record of meaningful changes

  • Milestone: name the deliverable and the stage of work.
  • Confirmed time: include the date, time zone and source of confirmation.
  • New entry: note the different date shown and where it came from, if identifiable.
  • Action: record who will resolve the difference before anyone sends an update or moves dependent work.

Meta says you can edit spaces as you use them and choose where they appear in the app. Start with a low-risk project or fictional records to see whether the view helps you spot a change and trace it to its source. The announcement does not establish a refresh interval or a rule for resolving conflicting dates. Verify the important milestone in its original record before acting on it.

Check the project deadline

Primary source

Meta’s November 6 announcement: how spaces are built and updated