Using BeeBo for live work

BeeBo sits in the bottom-right (or open /beebo). It reads live firm data and can propose changes — but nothing writes until you tap Confirm on a plan card.

BeeBo vs Beech Assistant

• BeeBo — live projects, tasks, sprints, vendors, Vault, hours; Confirm-gated writes.
• Beech Assistant (Help Centre) — how Beech works, navigation tips, support tickets. No task moves.

Ask, then Confirm

Ask in plain language (“what’s blocked on RV01?”, “add these three tasks to the sprint”). For writes, BeeBo shows a plan card. Review the steps, then Confirm or Deny. Typing “yes” in chat is not enough.

Credits

Usage draws on firm BeeBo credits. Admins manage packs under Firm settings → BeeBo. When credits run out, pause until an Admin adds a pack or the period resets.

Prerequisites

• Confirm you can access the project and the page referenced in this workflow.
• Collect any drawing references, due dates, and ownership details before you start.

Expected outcome

By the end of this workflow, your team has one visible, repeatable process and cleaner handovers.

Common mistakes and prevention

• ✓

  Mistake 1: Skipping context fields (owner, due date, status notes), which makes follow-up harder.

• ✓

  Mistake 2: Treating chat updates as source of truth instead of recording the update in Beech.

Troubleshooting checklist

1. 1
   Troubleshooting step 1

   If a control is missing, verify your role has permission for the action.

2. 2
   Troubleshooting step 2

   If results look wrong, check filters and refresh to confirm latest synced data.