Edit a deal

Deals should be updated throughout their lifecycle. Editing a deal keeps execution visible and ensures the rest of the team can rely on the record.

When to edit a deal

You should edit a deal when:

• status changes
• priority changes
• whitelist numbers change
• obligations become clearer
• deadlines move
• proof links become available
• follow-up timing changes
• the summary needs better context

Common updates inside a deal

Typical deal edits include:

• changing status
• updating requested, approved, or delivered WL
• refining deal terms
• updating what your side owes
• updating what the other side owes
• adding a deadline
• adding proof, AlphaBot, or form links
• updating the next follow-up date

Why editing matters

An outdated deal record causes confusion. That affects:

• execution quality
• reporting accuracy
• team visibility
• handoffs
• accountability

Good editing habits

Update a deal after:

• important conversations
• approvals
• delivery events
• internal decisions
• deadline changes
• new proof becoming available

💡Best practices

• edit the deal as soon as the new information is known
• keep summaries short and clear
• use proof links when useful
• do not rely on memory for active execution details

Update deal status

Updating deal status quickly helps your team keep the deal pipeline accurate. This is especially useful when status can be changed directly from the deal card or deal page.

Why quick status updates matter

Quick updates help your team:

• keep the board accurate
• reduce stale data
• reflect real deal movement
• improve accountability
• make reporting more trustworthy

When to update deal status

Change a deal status when:

• the deal moves from planning into active work
• the other side responds and changes the state
• your team completes delivery
• the deal becomes blocked
• the deal is cancelled
• the deal is fully complete

What status updates should do

A status update should help the next person understand the reality of the deal instantly. That means the status should answer:

• is this active?
• are we waiting?
• is work done?
• is this no longer moving?

💡Best practices

• update status immediately after major movement
• align status with next follow-up timing
• review deals that have not changed status in a long time
• avoid leaving completed or cancelled deals in active states

Deal deadlines and follow-ups

Deadlines and follow-ups help your team avoid dropped execution, missed delivery windows, and forgotten next steps. They are essential for keeping deals alive and properly managed.

Deal deadlines

A deadline is the hard date tied to an actual requirement. This could include:

• content delivery date
• whitelist fulfillment deadline
• partner submission deadline
• campaign timing
• launch timing

Deadlines represent time-sensitive execution.

Deal follow-ups

A follow-up is the next action checkpoint for the team. This could include:

• check for partner reply
• send updated offer
• confirm approval numbers
• review pending delivery
• revisit the deal next week

Follow-ups represent operational timing.

Difference between the two

Deadline

A real required date tied to execution.

Follow-up

The next internal moment the team should revisit or act on the deal. You often need both.

Why they matter

Deadlines and follow-ups help your team:

• stay proactive
• prevent stale deals
• keep momentum
• avoid missed obligations
• manage execution with more discipline

Good examples

Deadline examples

• whitelist list due Friday
• campaign assets due tomorrow
• partner confirmation needed before launch day

Follow-up examples

• check reply in two days
• review with lead next week
• confirm final WL allocation tomorrow

💡Best practices

• always set a deadline when there is a real delivery requirement
• always set a follow-up when the deal is waiting on action
• update both when timing changes
• use them together to keep deals moving instead of going cold

Team

Team overview

The Team section is where you manage the people inside your workspace. It gives you visibility into who has access, what role they hold, and how responsibility is distributed across the workspace.

What the Team section includes

The Team section can help you manage:

• active workspace members
• invited members
• member roles
• removals
• leave-workspace actions
• team performance visibility

Why the Team section matters

Collab workflows break down when ownership is unclear. The Team section helps solve that by making it easier to see:

• who is in the workspace
• who can do what
• who is responsible for execution
• who should still have access
• how the team is performing

What a healthy team setup looks like

A healthy workspace team usually has:

• clear ownership
• a limited number of admins
• managers assigned to active work
• viewers only where visibility is needed
• inactive or removed members cleaned up properly

When to use the Team section

You will use the Team section when:

• inviting new members
• reviewing member roles
• removing members
• leaving a workspace
• checking who is responsible for work
• reviewing performance and accountability

💡Best practices

• review team membership regularly
• keep roles intentional
• avoid giving too much access too widely
• remove or disable access when someon