Project dossier
kept together
Example project · refurbishment
- Project details
- Location, timeframe, scope
- Documents
- Drawings, model, room schedule
- Responsibility
- Project lead
- Open question
- Check the existing on site
- Next step
- Arrange the site visit
Digital architectural studio
STUDIO BY ANGERMAYER
Less manual work.Better digital workflows.
ANGERMAYER Studio develops digital systems together with architecture, planning and engineering practices.
The Studio systems
Digital systems for situations an office meets again and again.
The starting point is the work itself: where does repetition happen, where does information get lost, and where is the same material prepared by hand again and again? Every system grows out of how an office actually works and is adapted to the project, the team and the tools already in use. The Studio does not push ready-made software onto the work.
Everything that belongs to a projectcomes together in one place.
Project Intake System
The inquiry, the drawings, the model, the spreadsheets, the open questions and the responsibility rarely arrive together. The system files them against one project as they come in.
Arriving
- Email Inquiry from the client
- PDF Drawings attached
- IFC Model from the design
- Spreadsheet Room schedule separately
- Note Open question from the phone call
The details are an example. The system works just as well for projects without an IFC model.
Why this helps your office: You no longer search through several places before you can answer the next question.
View system details: Project Intake System
System details
Project Intake System
Everything that belongs to a project comes together in one place.
Blue stands for what has been sorted and filed. Violet stands for the one question still open.
Why it matters: Before the first meeting, everything that belongs to the project sits together.
How it runs today
The inquiry arrives by mail, the drawings as attachments, the model separately, the confirmation by phone. It has all arrived, but nobody can see it together.
What arrives, and where it lands
- Email with the inquiry Project details
- PDF drawings attached Documents
- IFC model from the design Documents
- Room schedule as a spreadsheet Documents
- Note from the phone call Open question
What changes day to day
Before the first meeting, what would otherwise have to be chased is already there. Who reviewed the documents is recorded on the project, not in an inbox.
Example result
A project record with location, timeframe and scope, the filed documents, a named project lead, one open question and the next step.
Typical framework
An intake form or mail entry point, the filing structure, the assignment rules and the handover to the tools you already use. Scope and timeframe are agreed together once the starting position is clear.
Not included
- No architecture, engineering or approval services
- No professional review of drawing content
- No forced change to the filing you already have
Update a project once.Show the current status everywhere.
Portfolio & Website System
The project description, the images, the key facts and the status are kept in one place. The website, the portfolio and presentations all use the same released status.
Your firm
released
Project
Residential refurbishment
- Description
- on file
- Images
- selected
- Key facts
- recorded
- Status
- in progress released
Used in
Residential refurbishment
released
WebsiteProject page
Residential refurbishment
released
PortfolioDouble spread
PresentationSlide
One change where the project is kept reaches every intended output.
Why this helps your office: A change is made once, instead of being carried over in several places afterwards.
View system details: Portfolio & Website System
System details
Portfolio & Website System
Update a project once. Show the current status everywhere.
Blue stands for the released status. Violet stands for the change currently going through.
Why it matters: No project is left showing an older status somewhere.
How it runs today
The same project is written separately for the website, the portfolio and the presentation. After a few changes the details differ, and somebody has to remember every place that still needs updating.
The same details, three uses
- Website Project page with the current status
- Portfolio Double spread with the same details
- Presentation Slide with the same status
What changes day to day
One change where the project is kept reaches every intended output. No outdated project texts, no double upkeep, no hunting for the latest version.
Example result
A project is updated once and then reads with the same status on the website, in the portfolio and in the presentation.
Typical framework
The place the project is kept, the output paths, the website or portfolio connection and the introduction for your team. Scope and timeframe are agreed together once the starting position is clear.
Not included
- No advertising campaigns and no ongoing social media management
- No guarantees about search engine placement
- No photography or copywriting production for your projects
Everyone can seewhat happens next.
Workflow System
What has arrived, who reviews it, where a decision is needed, who hands it over and what follows stays visible to everyone.
-
01 · done
Intake
Inquiry arrives
ResponsibleOffice administration
-
02 · done
Review
Documents reviewed
ResponsibleProject lead
-
03 · done
Decision
Approval given
ResponsiblePractice lead
-
NOW
Handover
Next step named
ResponsibleProject lead
Why this helps your office: Fewer questions, clear responsibility and a documented handover.
View system details: Workflow System
System details
Workflow System
Everyone can see what happens next.
Blue stands for the stages that are done. Violet stands for the stage being worked on now.
Why it matters: Nobody has to ask in order to know who acts next.
How it runs today
A case is passed on by voice or by mail. Where it sits and who acts next is only clear once somebody asks. During holidays or illness it is left waiting.
Four stages, four owners
- 01 Intake Office administration
- 02 Review Project lead
- 03 Decision Practice lead
- 04 Handover Project lead
What changes day to day
Everyone can see where a case stands, who is responsible and what follows. The handover is a recorded state, not a reminder.
Example result
A case stands visibly at the review stage, with a named owner, a named next step and a documented handover.
Typical framework
Capturing how the work actually runs, the system itself, the connection to your tools and the introduction for your team. Scope and timeframe are agreed together once the starting position is clear.
Not included
- No prescription of how your office should work
- No performance or time tracking of staff
- No replacement for your project management
Your system stays usable,even as your office changes.
Digital Care
Processes, responsibilities and requirements change. Digital Care records what was adjusted, why it was changed and when the system is looked at together again.
System care
actively looked after
Open point
The handover no longer fits the process
Documented change
- Change
- Project handover adjusted
- Reason
- New internal responsibility
- Changed
- Handover step
- Documented by
- Project lead
- Status
- in place
History
- Review agreed
- Change reviewed and documented
- Next review scheduled
Why this helps your office: Changes stay traceable, responsibility stays clear and the next date is fixed.
View system details: Digital Care
System details
Digital Care
Your system stays usable, even as your office changes.
Blue stands for what has been recorded. Violet stands for the point that is currently open.
Why it matters: A system that is looked after does not quietly go stale.
How it runs today
The system runs, but the office has moved on: a responsibility is new, a step no longer fits. It gets adjusted on the side, and later nobody knows what was changed or why.
From an open point to a recorded change
- Open point The handover no longer fits the process
- Reviewed together Looked at within the agreed framework
- Recorded Handover step adjusted, with reason and date
- Next review Date agreed
What changes day to day
What was adjusted and why is on record. There is a person who is responsible, and a date when it is looked at together again.
Example result
An entry in the operations record: handover step adjusted, reason a new internal responsibility, documented by the project lead, next review agreed.
Typical framework
An agreed rhythm, one entry per review and a defined framework for smaller adjustments. Scope and timeframe are agreed together once the starting position is clear.
Not included
- No unlimited support and no on-call availability
- No undefined development engagements
- No care of third-party software without prior agreement
Why ANGERMAYER?
Five disciplines. One capability: making digital systems understandable and usable for architecture.
-
Architecture
We know the context in which planning and building happen.
-
BIM and IFC
We work with models and open data formats.
-
Software
We build the systems ourselves.
-
AI
We use it where it noticeably makes a task easier.
-
Systems thinking
We consider process, data and responsibility together.
One capability
-
Understand context
Read the architectural and planning context.
-
Create structure
Organise information, process and responsibility.
-
Build systems
Implement the digital system technically.
-
Hand over clearly
Deliver it usable, understandable and documented.
How we work
First understand the work. Then build the right system.
The route
-
Understand
See how the work actually runs today.
-
Frame
Agree the scope, information and responsibility.
-
Build
Create the system and connect it to what already exists.
-
Hand over
Deliver it usable, documented and clearly owned.
Result
A usable digital system your office can continue working with.
Collaboration Models
| Model | Pilot | System Project | Digital Care |
|---|---|---|---|
| Suitable for | One clearly bounded first problem. | A process that needs a complete digital system. | An existing system that has to stay reliable. |
| Result | A working first solution and a validated direction. | A designed, built and documented system. | Agreed care and controlled improvements. |
| Engagement | One time, short and bounded. | A defined project with an agreed scope. | Recurring within an agreed framework. |
| Investment | Based on the agreed scope | Agreed per project | Within the agreed care framework |
| Next step | Request a pilot | Request a system project | Request Digital Care |
Pilot
- Suitable for
- One clearly bounded first problem.
- Result
- A working first solution and a validated direction.
- Engagement
- One time, short and bounded.
- Investment
- Based on the agreed scope
System Project
- Suitable for
- A process that needs a complete digital system.
- Result
- A designed, built and documented system.
- Engagement
- A defined project with an agreed scope.
- Investment
- Agreed per project
Digital Care
- Suitable for
- An existing system that has to stay reliable.
- Result
- Agreed care and controlled improvements.
- Engagement
- Recurring within an agreed framework.
- Investment
- Within the agreed care framework
Which form fits is something we work out in conversation. Every inquiry leads to a conversation first, not to a quote.
Not part of the collaboration
- No architecture, engineering or approval services
- No legal, tax or data protection advice
- No undefined development engagements and no unlimited support
- No advertising campaigns, no ongoing social media management, no ranking guarantees
A product by ANGERMAYER
An independent product
ArchOS is an independent ANGERMAYER product.
It came out of the same combination of architecture, BIM and IFC, software and systems thinking that shapes the work of the Studio.
A good digital system makes work easier to understand, without making it more complicated.