--- title: "Architecture studio SOPs in Notion: onboarding and standards" url: https://notionforarchitecture.com/blog/architecture-studio-sops-notion-onboarding-standards updated: 2026-10-27 author: Notion for Architecture --- # Architecture studio SOPs in Notion: onboarding and standards Architecture studio SOPs in Notion work best as a database of short procedures, each with a purpose, owner, steps, last-reviewed date and links to templates. Start with four: onboarding a new starter, setting up a project, issuing drawings and closing a project. Review each yearly and keep every SOP to one page. ## Key takeaways - An SOP is a short, owned, dated procedure, not a manual. - Begin with onboarding, project setup, drawing issue and project close. - Store SOPs in a database with owner and review date. - Link SOPs to the templates and checklists they use. ## What is an SOP in an architecture studio? A standard operating procedure is a short, step-by-step description of how the studio does a recurring task. It answers 'how do we do this here?' for new staff and for the principal at 6pm on a Friday. In practice, SOPs cover things like setting up a project folder, naming files, issuing drawings and reviewing before issue. Notion suits SOPs because they are linked, searchable, and can sit next to the databases they govern. ## Which SOPs should you write first? | SOP | Trigger | Output | | --- | --- | --- | | New starter onboarding | Someone joins | Accounts, access, reading, first tasks | | Project setup | Appointment signed | Folder structure, Notion project, stages, team | | Drawing issue | Before every issue | Checked set, register updated, issue recorded | | Design review | End of each stage | Signed-off stage checklist | | Project close | Practical completion or handover | Archive, lessons learned, final invoice | ## How do you structure the SOP database? - Title (verb first: 'Issue drawings') - Area (select: Projects, Drawings, Admin, People, Finance) - Owner (person) - Status (Draft, Active, Under review) - Last reviewed (date) - Next review (formula: last reviewed plus 365 days) - Related (relation to templates, other SOPs) Put the steps in the page body as a numbered list or checklist. Include a 'Why this matters' sentence at the top; people follow procedures they understand. ## What goes in an onboarding checklist? Group it by when it happens, and assign each item to a person: 1. Before day one: accounts, hardware, software licences, desk, welcome message. 2. Day one: studio tour, who is who, safety and security basics, where the Notion workspace is. 3. Week one: read the rulebook, CAD or BIM standards, file naming, drawing issue SOP; shadow a project setup. 4. Month one: first owned task on a live project, a check-in with their line manager, feedback on the SOPs themselves. Statutory induction, health and safety, and employment requirements vary by country; check yours and add them to the list. ## How do you write standards that people follow? - Use the verb-first title and steps of five to ten lines. - Show a screenshot or example file, linked, not described. - State the standard and the exception: 'Use 1:100 for plans; use 1:50 for details.' - Say who to ask when it does not fit. If you work to a published standard, name it and link it rather than paraphrasing it. ## How do you keep SOPs from going stale? Use the Next review field and a view of SOPs due for review this quarter. Put it on the weekly review of the studio. After each project closes, ask 'which SOP did we break or find missing?' and update accordingly. Retire what nobody uses; a short set that is followed beats a long one that is not. ## What does a worked SOP look like? Here is a sample 'Issue drawings' SOP, invented to show the level of detail: 1. Purpose: everyone receives the same, checked set and we know what was sent. 2. Check sheet numbers, titles and revision codes against the drawing register. 3. Confirm status matches the purpose of the issue (information, coordination, approval, tender or construction). 4. Run the second-person check and record the checker's initials in the register. 5. Export PDFs using the studio naming rule and save them to the project's issued folder. 6. Send the transmittal and record the issue: date, recipients, sheets and purpose. 7. Update the stage checklist if the issue completes a stage. Seven lines, one owner, one review date. Anyone new can follow it; anyone experienced can see what is missing. Add your own checks, such as consultant coordination sign-off. ## Where ArchitectOS fits ArchitectOS (we make it, $79) includes a Template Vault, a place to keep reusable pages. You can store SOP pages and checklists there or build a separate SOP database as above. It does not include pre-written SOPs; the procedures must reflect your studio. - See what's inside ArchitectOS: https://notionforarchitecture.com/#templates - ArchitectOS pricing: https://notionforarchitecture.com/#pricing ## FAQ ### What is an SOP for an architecture firm? A short documented procedure for a recurring task, such as setting up a project or issuing drawings, so that work is done consistently regardless of who does it. ### How long should an SOP be? One page where possible. If it needs more, split it into linked procedures. Long manuals are rarely read. ### How often should SOPs be reviewed? A yearly review is a common default, plus an update whenever you find the procedure no longer matches reality. Track a next-review date in the database. ### Do small practices need SOPs? Even a two-person studio benefits, mainly for onboarding and for tasks done rarely. Start with three or four and add as gaps appear. ### Can SOPs replace quality management certification? No. SOPs support consistent work, but formal quality management systems have their own requirements. Check the relevant standard if you pursue certification. ## Sources - [Notion guide: manage client work in a flexible project tracker](https://www.notion.com/help/guides/manage-client-work-in-a-flexible-project-tracker) - [Notion guide: manage client work in a flexible project tracker](https://www.notion.com/help/guides/manage-client-work-in-a-flexible-project-tracker)