16 August 2026
Updated 16 August 2026 · Beech Product Education Team
Project code, category, sequence, and -R1 revisions — why the number never changes, and how to jump to a sheet with search.
Intent: Explain how drawing numbers work 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.
Beech assigns every drawing a stable number when you create it. Use that number in search, reports, reviews, and conversation. It does not reshuffle when you reorder the list.
The format
{PROJECT CODE} – {CATEGORY ABBREVIATION} – {SEQUENCE}
RV01-FLP-003 is the third drawing in the Floor Plans section (FLP) on project RV01. Revisions append -R1, -R2, and so on. General tasks use TSK instead of a section code. Site visits and meetings have their own prefixes (MOM-, MTG-).
Why the code matters
The project code is chosen when you create the project. Keep it short, unique, and uppercase. It becomes part of every number on that job, so changing it later is painful.
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
- 1Troubleshooting step 1
If a control is missing, verify your role has permission for the action.
- 2Troubleshooting step 2
If results look wrong, check filters and refresh to confirm latest synced data.
Full reference: Drawings in the user guide
Related guides: Drawing tasks vs general tasks · Why a drawing is Blocked · Getting a drawing to Done