Yes. Ideally your description for the project should be no more than about 3 sentences. People with an architecture school background typically include the title of the project, what course or studio it was done for (i.e. "Sophomore Studio, spring 2001), the name(s) of the professor(s), and often the timeframe for the project ("2-day charrette", "3-week studio project", etc.) Since an architecture studio-type project may be anywhere from a 2 to 6 page spread with various images, often each image is labeled or keyed to a list of titles ("Preliminary sketch", "study model", "traffic analysis diagram", "competition board", etc.)
If you worked with anyone else on the project you MUST include their names and specify your role in any pieces you include.
Occasionally there may be other things you'd want to tell them - for instance if the work has been published somewhere, if it won an award,

I'd keep it very simple. A few sentences are enough for each project, plus a title, which semester would be good, or just "Fall 2002". Maybe the length, but only if you have some really short things, otherwise it doesn't really matter that much.
You could label some drawings, but I don't think it's necessary (I didn't label any drawings). I would NOT list the professors name and if it's a group project, I'd only say 'group', if anything at all (you don't want to list someone's name esp. if they are applying also to the same school).

thanks, that helps

maybe this would help
http://www.theportfolio.org.uk/

I've always noticed that when I look at a project on a wall the presentation/explanation makes a huge difference so i can't make sense of it without the spiel, especially when the work is more abstract (and i'm sure everyone will have one or two projects like this).

so, i'm including a little essay at the beginning at each project.
what do you do if you have a thesis? isn't text an important part of it?

A very, very short paragraph is good, but remember that anyone looking at it will have stacks of them to go through. I would guess that no one reads a word until the last few, if even then.
Personally, I know if I'll like a project within seconds of seeing images. I've yet to change my mind based on an explanation (although I have gained more appreciation after learning more). For me, if the visuals don't sell me, the words can only be an idea that wasn't explored or a missed opportunity.

Purely subjective, of course, but that's how it plays out in the real world. If I like something formally and spatially, I'll want to learn more. Generally, this is how most people work, not the other way around.

When I showed my thesis to prospective employers, they didn't care for more than a two sentence answer, but they looked at the images for a while and asked questions pertaining to what they were interested in. I have no text in any portfolios now, but I do list the awards and publications.

If you're writing paragraphs about each project, you should use it mostly as a graphic tool. The text should read as a graphic element on the page. Who's going to read every word, especially admissions people. Make the project text meaningful, but realize it will be quickly scanned at most. The images will really draw the eye.

It's just suggestions. I don't read much text about projects unless I am really impressed. It's a cautionary note not to spend too much time on it and sacrifice the images or layout. Sure, you want both, but the images are 95% of what will be noticed.

I think it's significantly easier to write a good paragraph than make a good layout and certainly easier than making good projects. My assumptions are if a project is visually compelling, then there is either a brilliant intuition, which is great, or some great ideas, great again. Eitherway, the project is nice.

Words cannot make up for any lack of presentation or quality - just don't get caught up in something that will be overlooked, that's all.

What about the statement of purpose? Is that read concurrently with the viewing of the portfolio? Are the two considered together and judged at all by the amount in which they correspond?

thanks

One more thing - for those who have sat in portfolio reveiws. Speaking of the short attention spans of reviewers, does that mean it is "dangerous" to save the best images for last in each project? I have begun each project with less impressive sketches and models from the early development and ended with finished renderings. Is there a risk they won't even get to the renderings or will become bored or dissatisfied and make a judgement early on?

Don't EVER show anything that is less than your best.

For loose, dirty concept sketches or models (which are admittedly not polished), all that means is that they clearly show the idea quickly.

It is better to show ONE good image over a series of almost-good images.

The only time to put those lesser quality images is if you risk showing close to nothing.

The reviewers WANT to see good things, and they'll remember that over the amount of images or projects.

The procedures vary from school to school, but often the situation is that only 1 or 2 of the people on the committee read your statement, and it isn't reviewed concurrently with the portfolio. The schools often divide portfolios into small groups, which each reviewer takes home for a few days, and then they switch. The portfolios are often the only material that makes it to the table at the committee meetings with the full group.

i don't know about that, aluminate.
i guess it depends on the school.
i just came back from visiting east coast and at princeton they said the statement is one of the most important things along with the portfolio, of course. and, mind you,don't spend time on any "unusual packaging that is likely to get damaged" (from their site)

but, point is, we all agree they look on images first, but they will ocasionally read some of the text, too, if the images look intriguing.
but if you can't say it in a few crystal clear paragraphs, it might do more damage than good.

i'm also making the portfolio as a record for myself, now that i still remember what the heck i was thinking when i did those projects.
plus, some schools (upenn, i think) require a sample or two of writing.
i wonder what that could be.

One thing to always consider, and this goes for studios, is your 'thesis' statement. You should be able to give the meaning of the project in a sentence or two. From there you can express a quick way in which you tackled the problem.

cki: I said nothing about the importance of the statement. The statement can be very important. What I said is that - at least in schools with which I'm familiar - it isn't necessarily reviewed in conjunction with the portfolio by the whole committee. A typical scenario is for each member of the committee to take a small number of applicant's materials at any given time and review them on their own time. In between meetings of the committee these materials may be reviewed by 1 to 3 of the committee members. When the committee gets together, those who've reviewed a particular student tend to "champion" the ones they like - by directing attention to elements of their portfolio and sometimes by explaining the work a bit - if they feel they've got some understanding of it. Most schools' committees meet on a number of occasions over a few weeks. There are usually a few "cuts" to narrow down the field. If you make it to the very end all your materials will most likely have circulated among all of the committee members, whereas if you're eliminated earlier your statement may have only been read by one or two members of the committee (but again, schools vary. Some committees have only 3 or 4 people in the first place. Others have 10 or 12. Some meet only once or twice, others many more times. Some have marathon deliberations, others don't.)
I feel it's very helpful to include names of professors for whom you did the work in your portfolio. Architecture is a small world, and even if the reviewers don't have any direct personal connection to your profs (and it's not all that unlikely that they do) they may be familiar with their leanings... This can do as much to "explain" your work as your text might.

what's a good size of font for titles and descriptions?

I'd be careful about listing your professors. To me, it'll either come of as bragging or they won't know who the person is and won't care, in which case it'll look better with nothing.
When I show people work from portfolio I'll add 'and this was done under the guidance of Thom Mayne', but I won't put it in the print.

Kai - the graphics are a subjective aspect of the portfolio and you shouldn't take advice here. It depends on a ton of things, being able to read it being an important one. Go to Borders and look at some graphics books on typography. Treat this like a design class, not a question and answer project.