Fatima Ladak // Competition Brief Precedents

In order to understand the structure and content required within competition briefs, I looked at the AIA Handbook of Architectural Design Competitions. This set out a structure of 3 sections:

1. Procedural Rules

2. The Project Program

3. Submission Requirements

I also looked at the two different competition briefs, one posted on a website (http://www.advancedarchitecturecontest.org/index.php) for a ‘Self Sufficient Habitat’ and the other for the ‘New Mosque & Museum of Triana Design’ (http://www.scribd.com/doc/82867108/Competition-Brief-New-Mosque-Museum-of-Tirana-and-Religious-Harmony-march-11) The first contains a very clear cut structure with vibrant and captivating graphics, clear instructions stating the timeline, jury members and rules. However, there were no images or maps pertaining to the project, intending the competitors to do their own research. This is in complete contrast to the ‘New Mosque & Museum of Triana Design’ competition brief which produces sufficient site maps and images which will enable the competitors to understand the site better. However, there is also a lot of what seems to be unnecessary text within this brief.

I have decided to follow the basic 3 section structure that the AIA suggests and aim to use captivating graphics and many images/maps to give as much information as possible to the potential competitors for them to fully understand the problems outlined.

Brief Precedent

– image screen shot of http://www.advancedarchitecturecontest.org/index.php

About Co.LAB Student

MArch FT5 Free city

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: