Architecture practices
Coordinate the people and decisions around the design.
Keep client contacts, meeting notes, project tasks and reviewed documents connected while specialist design and formal project systems stay in place.
- 01Set up the relationship
- 02Prepare discussion
- 03Record decisions
- 04Share deliberately
A drawing does not carry the entire conversation.
Architecture involves clients, consultants and internal teams making decisions at different moments. Tsumira can organize the business relationship and coordination work around a project. It is not a CAD application, BIM model platform or formal construction document environment. Decide which information belongs in each system before moving active work.
A concrete workflow
Set up the relationship
Record the client, project contacts and decision responsibilities.
Prepare discussion
Collect questions and assign preparation for the next design meeting.
Record decisions
Capture the actual outcome and give follow-up tasks clear owners.
Share deliberately
Send the reviewed reference material and identify its intended use.
Keep project participants identifiable.
Use company and contact records for the client and other participants. Record site discussions, meeting notes and decisions with the relevant customer relationship. Identify the person who can answer an outstanding question; a meeting attendee is not automatically authorized to approve a design change.
- Client contacts and meeting activities
Coordinate milestones and review work.
Plan tasks for preparation, internal review and client discussions with named owners. Keep time records to understand where the team's effort goes. Use the project plan for office coordination while statutory stages, fee calculations and construction obligations remain subject to your professional processes.
- Owned tasks and project time records
Distinguish review copies from authoritative plans.
Drive can store and share files, including version-specific external links. That does not create BIM coordination or formal plan approval. Keep the authoritative design record in the agreed specialist environment and tell recipients exactly what a shared document represents before they act on it.
- Version-specific file sharing
An illustrative working example
Illustrative scenario: a small commercial refurbishment
An office prepares a client review for a refurbishment. Tsumira holds the participants, discussion notes and preparation tasks. A reviewed reference PDF is shared through Drive, while models and authoritative plans remain in specialist software. A change request becomes a documented decision and assigned office task. A client changes the intended use of one room during review. The office records the request, assigns clarification and keeps the reference PDF distinct from the authoritative design. Before sending material, the responsible person checks its purpose and status. The pilot focuses on whether a colleague can follow the discussion and remaining actions while technical models, formal approvals and contractual documentation stay in the established project environment.
Questions about this topic
Is Tsumira a CAD or BIM tool?
No. It supports office and client coordination around specialist design work, not model authoring or technical coordination.
Can it manage formal drawing approvals?
Do not treat file sharing as a formal approval process. Check contractual and project requirements in the designated specialist system.
Can we record office time by project?
Time entries support effort records. They do not calculate regulated professional fees or validate contractual entitlements.
Where should we start?
Try one client review cycle: participants, preparation tasks, meeting notes and follow-up, while retaining the established design environment.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
