Consistency
Every project opens with the same ten pillars and the same phase logic, so anyone can find a drawing, a submission or a certificate without asking.
Avci Architects · Architecture practice manual
The working manual of Avci Architects.
An architecture practice runs on repetition: the same project structure, the same drawing standards, the same quality gates on every job. This site is where we keep that knowledge, so a project does not depend on who happens to remember it.
- live guides
- 1
- in preparation
- 5
- project pillars
- 10
- template folders
- 443
Why this manual
Three reasons the firm keeps it
The manual is not a style guide on a shelf. It is the operating layer that lets a project move between teams, phases and consultants without losing its structure.
Efficiency
We stop rebuilding folder trees, naming schemes and checklists per project. The template is the starting point, not a discussion.
Quality control
Each stage has a defined gate, a defined record and a defined owner. The guide library is where those checks live and are versioned.
Guide library
How we structure, produce and check the work
Live guides open. Planned guides are listed now so the coverage of the manual is visible; they are not links until the page exists.
Folder Template
The ten-pillar project structure, generated from disk, with canonical phase codes and the known exceptions kept visible.
Drawing & naming standards
Sheet numbering, title blocks, revision codes and issue naming, so a drawing can be identified from its filename alone.
Stage-gate QC checklists
The checks, records and sign-offs required before each issue leaves the office, from pre-concept through executive design.
Automation & workflow
Repeatable scripts and batch workflows for plotting, renaming, model handover and the other manual steps that slow delivery.
Onboarding
What a new team member needs in week one: tools, access, standards, first tasks and the people to ask.
Project close-out
Archiving, handover and lessons learned when a project reaches completion, so the next one starts better informed.
Using the manual
Three rules that keep it useful
- 01
Start from the guide
Use the published structure as the first move. If a project genuinely needs a new folder pattern, change the template before the project, not after it.
- 02
Keep the canonical codes
Phase logic uses P0–P4, independent of the numeric prefixes on disk. Prefixes are display-only and stay verbatim; cross-pillar references use the canonical phase.
- 03
Propose, do not fork
If a guide is wrong or incomplete, raise it with the owner instead of maintaining a private variant. A manual with two versions is no manual.
The folder template is the normative example: codes are kept verbatim, phases are canonical, and known exceptions are left visible rather than quietly normalised. See the full tree.
Ownership
Maintained, not crowdsourced
Every guide has an owner and a last-updated date. The folder template is generated from the real directory rather than drawn by hand, so the published tree cannot drift from the working template.
Last updated · Folder Template