Skip to main content
Beech

Reports you can send a client or principal

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

Portfolio Excel/PDF, team-member sheets, sprint printouts, and the drawing-list PDF — who can download which.

Intent: Explain reports you can send a client or principal in a way that a new team member can follow without prior Beech context.

Who this helps: Architecture studio admins, managers, and contributors who need a repeatable operational workflow.

Reports are live at download time. More → Reports has Project Portfolio and Team Member side by side, plus an in-app digest. Period can be Week, Month, or Sprint (most recently completed sprint).

Portfolio

All tasks (or one project): references, assignees, reviewers, sprint, dates, blocked/on-hold reasons, vendors, days overdue. Excel opens on a Summary “what’s on fire” sheet. PDF is for scanning — status pills and a cover with progress bars. Admins see all projects; Managers see accessible ones; Contributors cannot download this one.

Team member and sprint prints

Team Member is one person in a period. Contributors can download only themselves; Managers any Contributor; Admins anyone. Sprint PDFs: retrospective (with notes space), planning sheet (blank assignee/date columns), and final review (done, pending, spillover). From a project Work tab, Print drawings is the sectioned drawing list for handover.

Print the retrospective before the end-of-sprint meeting. The planning sheet is for writing in the room, not for duplicating Schedule.

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.

Full reference: Reports in the user guide

Related guides: Roles and permissions playbook · Security controls for admins · Exporting data for audit or handover

Next: explore related feature workflows.