A promise is made in a meeting, becomes a task in your tracker, closes when the tracker closes it, and lands on a record your team can open. Rooms, Ledger, People and Accounts are the four places that happens. Workspaces and Spaces are the structure they sit inside
Four surfaces, and one thing travelling through them
1 / 5Rooms
Launch readiness reviewJul 15, 09:30
The team walked the remaining launch blockers and agreed the announcement waits on legal rather than on the product. Privacy and DPA copy were the two items holding the date, and both were taken on with names against them. Pricing and the security page were pushed past launch deliberately, and everything still unresolved was moved onto one open-questions list instead of being carried in the meeting.
4 commitments were made
1 is kept and 1 is still in flight; the other 2 need someone
4 commitments were made. 1 is kept and 1 is still in flight; the other 2 need someone.
A room holds the meeting after the meeting is over
It captures the call as it runs and ends holding the individual promises inside it, each in the words it was made in, with the person who made it and the moment they did.
In flightWrite the support handover notesto Emma RossCustomer rollout1d
In flightFinish the launch analytics specto Priya NairLaunch analytics spec1d
In flightCirculate the launch-readiness briefto Tom BeckerLaunch-readiness brief for Thursday2d
KeptFinal privacy-page copy to legalto Tom BeckerLaunch readiness review2d
KeptClose the outstanding design-review decisionsto Elias NovakDesign review3d
StatusCommitmentCounterpartySourceAge
AwaitingApprove the privacy-page copyfrom Jon BellRe: Final privacy-page copy1d
In flightSend the enterprise capacity forecastfrom Ana SilvaRevenue review2d
StalledOwn the security page through launch weekfrom Sofia RossiLaunch readiness review2d
DisputedApprove the implementation scopefrom Owen PriceCustomer delivery3d
KeptSend the launch runbookfrom Emma RossLaunch runbook, with rollback steps3d
Every promise your team makes, and what happened to it
Each one becomes a task in the tracker you already run, and the same authorization reads its status back, so a receipt closes because the tracker closed it, not because somebody said so.
Your record, in contextWhat the register below cannot show you
Not yet a name3
Voices with no person
Claim yours
People you work with
9 people
Shared work first, alphabetically. A rate shows only for you and the people you manage.
PersonEmailOwed to youYou owe
Tom Beckertom.becker@northwind.exampleOwed to you—You owe1
Priya Nairpriya.nair@northwind.exampleOwed to you—You owe1
Jon Belljon.bell@northwind.exampleOwed to you—You owe1
Emma Rossemma.ross@northwind.exampleOwed to you—You owe1
Ana Silvaana.silva@northwind.exampleOwed to you1You owe—
Marc Duboismarc.dubois@northwind.exampleOwed to you1You owe—
Owen Priceowen.price@northwind.exampleOwed to you1You owe—
Elias Novakelias.novak@northwind.exampleOwed to you—You owe—
Who owes what, and how it usually goes
The work each person has open, and what is still owed between them and you. A record belongs to the person it is about, which is why nobody is ranked against anybody here.
Bring work signals and source context into Unifies
Launch readinessForward a thread here
capture+northwind.launch-readiness@in.unifies.aiThe address is reserved for this space
GoogleCalendar and Meet authorization
1 account connected, 1 unusedBrings scheduled meetings into Unifies
Task delivery
Inherited from workspace setup and read-only on this page
LinearTask delivery authorization
1 account connectedInherited when you created or joined Northwind
Workspace managed
Connect what your team already runs, once
Your tracker stays the source of truth, and every authorization is yours rather than the workspace’s. You can hold two accounts for the same tool and give a Space the one that belongs there.
A workspace carries the team, access and delivery defaults; each selected tracker project becomes a Space that inherits them. An owner sets the rules once, and everyone else joins the ready structure.