An ArchiBrain is a simple idea: one useful place to organise the architecture knowledge you keep collecting. For students, that might mean precedents, project briefs, tutorials, feedback, software notes, portfolio evidence and career ideas.
The danger is turning Notion into another design project. The point is not to build the prettiest dashboard. The point is to make your work easier to retrieve, explain and improve.
Watch: get organised as an architecture student
This Architecture Social video is useful if your notes, files and job-search evidence feel scattered. Organisation should reduce friction, not become another project.
Why architecture students need a better system
Architecture school creates a lot of loose material. You might have screenshots, lecture notes, precedent studies, sketches, models, crit feedback and job-search notes scattered across folders and apps.
- Precedents disappear when you need them for a design argument.
- Crit feedback gets forgotten before it changes the project.
- Software notes are hard to find when the same problem happens again.
- Portfolio evidence is rebuilt from scratch at the end of the year.
Listen: building an ArchiBrain with Sana Tabassum
This related episode with Sana Tabassum goes deeper into the ArchiBrain idea, :scale and how architecture students can organise knowledge more intentionally.
What to keep in your ArchiBrain
Start with a small system. If it takes more time to maintain than it saves, it will not survive the semester.
- Project briefs and deadlines.
- Precedents with a short note on why they matter.
- Tutorial and crit feedback, grouped by project.
- Software fixes you had to search for more than once.
- Portfolio-ready images, drawings and captions.
- Job-search evidence, including project roles, teamwork and skills.
How it helps your CV and portfolio
A good student system gives you language as well as files. When you can find the brief, your response and the feedback quickly, it becomes easier to explain the project in a portfolio or interview.
- Use the portfolio guide to decide what belongs in a sample portfolio.
- Use the CV guide to turn project and society evidence into clean application language.
- Use Part I job listings to check what practices are asking for.
Build a simple ArchiBrain starter system
Start with five sections. You can make it more sophisticated later, but only if the basic version is genuinely useful.
- Projects: brief, concept, drawings, final outcome.
- Feedback: tutor notes, crit comments and changes made.
- Precedents: image, source, lesson and project relevance.
- Skills: software notes and repeated fixes.
- Career evidence: CV bullets, portfolio captions and interview examples.
Common mistakes
- Spending more time designing the Notion dashboard than using it.
- Saving images without writing why they matter.
- Keeping feedback but not recording what changed afterwards.
- Separating university work from career evidence until it is too late.
Architecture Social view
Stephen’s view is that organisation should make you more employable, not just more tidy. If your system helps you explain your work faster and apply with better evidence, it is doing its job.
Next step
Build a small ArchiBrain around your current project, then use the CV guide and portfolio guide to turn that evidence into stronger applications.
Add a comment