Start with the job you need done
Give the next person a useful answer.
Recognize a work problem, compare possible responses, then leave with an editable report, decision request or receiving brief.
These 20 improved guides use invented situations and manual drafts. They do not read your workspace or send messages. TeamBoost access and enabled functions need confirmation.
Request TeamBoostAI access Browse all 229 guides →
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Reporting people can use
Fix a stale AI status report before it sends the team backwards
When an AI summary repeats an old blocker, I want to reconcile it with current task evidence so people act on the work that still needs help.
Leave with: a useful update
Report partial progress without promising a finished outcome
When visible screens are finished but the full workflow is not, I want to explain the accepted slice so stakeholders can decide without assuming delivery.
Leave with: a useful update
Share a report people can interpret without the original meeting
When a report leaves the dashboard where it was created, I want its meaning to travel with it so another reader can use the figures correctly.
Leave with: a useful update
Tell a customer you are investigating without promising a fix
When a customer reads investigating as a delivery promise, I want to describe the next evidence checkpoint so expectations match the work actually authorized.
Leave with: a useful update
Replace repetitive customer check-ins with useful review checkpoints
When daily meetings repeat the same progress, I want a shared update and specific review gates so customer time is used for the decisions that matter.
Leave with: a useful update
Decisions that move work
Route a blocker request to someone who can actually answer
When a blocker alert reaches people who cannot decide, I want an acknowledged route to the accepting owner so a specific answer returns instead of another broadcast.
Leave with: a decision request
Keep an approval moving when the decision owner is away
When the approver is unavailable, I want to identify a valid decision route so the team can move without inventing authority.
Leave with: a decision request
Defer a decision without losing the reason to revisit it
When a choice is postponed for learning, I want a return condition and decision owner so later evidence can change the plan rather than disappear.
Leave with: a decision request
Give the next prospect meeting a decision worth attending
When the prospect’s reviewer has not answered, I want the next contact to resolve a real comparison so we do not use another demo as a substitute for evidence.
Leave with: a decision request
Handoffs without guessing
Pass the business receiving check after the technical tests pass
When technical tests pass but the business meaning remains unclear, I want the receiving expert to check specific examples so the implementation owner gets a bounded correction rather than a vague approval request.
Leave with: a business receiving check
Stop a done handoff from becoming the next team’s surprise
When a sender says done but the receiver has not tried the result, I want the completion boundary stated so the next team knows what it can safely use.
Leave with: a receiving brief
Let two contributors help without creating two competing final versions
When two people change the same artifact independently, I want clear contribution boundaries and one integration owner so the receiver gets one coherent result.
Leave with: a receiving brief
Make the evidence usable before asking someone to approve the work
When a reviewer can open the task but not its evidence, I want an approved access route so their verdict is based on what they can actually inspect.
Leave with: a receiving brief
Leave the next shift a handoff they can act on without waking you
When the next owner starts after I log off, I want a usable action boundary so they can progress without guessing or waiting for a meeting.
Leave with: a receiving brief
Start routine support without losing the unfinished onboarding promise
When support can start but one training topic remains, I want both responsibilities visible so the customer gets help without losing the unfinished learning work.
Leave with: a receiving brief
Acknowledge a supplier delivery while keeping missing review evidence open
When a supplier delivers files without the agreed demonstration, I want to acknowledge receipt and name the acceptance gap so correction stays focused.
Leave with: a receiving brief
Requests into owned action
Turn meeting notes into actions without losing what was decided
When meeting notes mix agreements and actions, I want the decision traceable and the next work owned so no one executes a slogan or reopens a settled choice.
Leave with: a next-action brief
Find out whether a missed decision is a report problem or a routing problem
When a decision request is missed, I want to test whether readers cannot find it or do not know it belongs to them so we choose the right intervention.
Leave with: an observation protocol
Turn “the report is wrong” into an investigation someone can start
When a complaint has no reproducible example, I want the smallest relevant comparison so we can investigate the mismatch without guessing a fix.
Leave with: a next-action brief
Give a prospect a one-page comparison their internal reviewer can use
When a prospect needs to brief a reviewer who missed the call, I want a bounded comparison packet so the recipient can make the actual evaluation decision.
Leave with: a next-action brief