What Should an Architecture CV Show That a Portfolio Cannot?
You have probably reached this point before: the portfolio is looking good, the plans are finally aligned, the renders are behaving themselves, and then you open your CV and realise you are about to describe the same projects all over again.
That is the awkward part.
Your portfolio already shows the building. It shows the concept, drawings, models, diagrams and visual development. So what can the CV possibly add without becoming a watered-down version of the portfolio?
Quite a lot, if you look at it differently. The portfolio shows what you produced. The CV helps explain what you actually did, what you have learned, what you can contribute and how your experience has developed.
That distinction becomes especially useful for architecture students approaching placements, Part 1 opportunities, internships and graduate roles. You do not need to make your CV sound as though you have spent ten years in practice. You need to make the experience you genuinely have easier to understand.
Understanding the Topic
An architecture CV is often treated as the less interesting document because the portfolio carries all the visual impact. Yet the CV can answer questions that the portfolio cannot.
Imagine a second-year student has completed a community centre project with three other people. The portfolio might show the final plans, sections, physical model and rendered views. A reviewer can see the outcome, but they may not know who carried out the site research, who developed the model or who prepared the final drawings.
The CV provides that missing context.
It might explain that the student analysed pedestrian movement around the site, developed the physical massing model and prepared presentation drawings for the final review. Suddenly, the same project says much more about the individual.
This is particularly relevant at university because academic work often involves repeated cycles of designing, receiving feedback and changing direction. Those processes may be visible in a portfolio, but the CV can make the individual’s responsibilities and developing skills much easier to identify.
The expected balance also changes with experience. A Part 1 student will naturally have more academic material and less professional history than someone who has already worked in practice. Requirements vary between employers and applications, so there is no single perfect structure.
The principle, however, remains useful: do not make the CV repeat information the portfolio already communicates well.
Common Problems or Concerns
The first problem usually appears when students start writing project descriptions.
They know they need to mention their university work, so they write something like: “Designed a sustainable community centre focused on social interaction and public space.”
Nothing is technically wrong with that sentence.
The trouble is that it tells the reader very little about you.
If the portfolio already contains several pages showing the concept, site strategy and final proposal, repeating the project idea on the CV adds little value. A better description might explain that you carried out site analysis, explored circulation through physical modelling and developed the final presentation drawings.
That is the difference between describing a project and describing your involvement in it.
Another concern is the feeling that a student CV looks too empty.
This happens frequently before a first placement application. You compare your one-page CV with somebody who has worked in three practices, completed a placement year and contributed to built projects. Suddenly, every empty centimetre of your own page looks like a problem.
It is not.
A student who has completed a strong degree project, taken part in a competition, developed useful software skills and worked part-time may already have plenty to discuss. The challenge is selecting and explaining it properly rather than manufacturing experience.
Software is another area where students can accidentally make the CV less convincing. Listing ten programmes can look impressive until the reader wonders how confidently each one can actually be used.
There is a meaningful difference between having opened Grasshopper for a university workshop and being comfortable using it independently for design development.
Key Theories or Concepts to Know
There is no universal formula for an architecture CV, but several ideas help explain why some information carries more weight than other information.
Show evidence, not just qualities
“Creative”, “hardworking” and “passionate about architecture” are easy statements to make.
They are much harder for a reader to evaluate.
Compare that with saying that you developed several design iterations after receiving studio criticism, or that you presented your proposal during weekly reviews and adapted the design in response to feedback.
The second approach gives the reader something observable.
This is not about making every sentence longer. It is about connecting a claim to an action. If you say you are organised, show where that organisation appeared. If you say you can collaborate, explain what you contributed to a group project.
Understand the difference between activity and ability
Completing a task does not automatically demonstrate advanced competence.
A student might have used AutoCAD for one module but use it regularly for detailed drawings. Those experiences are not equivalent.
The same reasoning applies to model-making, rendering, visualisation, research and presentation. The useful question is not simply, “Have I done this?”
Ask:
- How much experience do I actually have with it?
- What did I produce using that skill?
- Could I explain my process if someone asked about it?
That last question is particularly useful because a CV creates expectations. Anything you claim may become part of a later conversation.
Separate the outcome from the contribution
Architecture is often collaborative, even within university.
A final project may look like one complete piece of work, but the individual contributions can be very different. Being clear about your role does not make your contribution look smaller. It makes it more credible.
Key Factors to Consider
The strongest CVs usually begin with relevance rather than trying to impress the reader with sheer volume.
Education needs to establish where you are in your architectural training. Your degree, institution and dates provide the basic context. Additional information can be useful when it helps explain a particular academic direction, achievement or area of interest.
Software should receive similar attention. If you have developed a substantial amount of work in Revit, Rhino or Adobe Creative Cloud, explain the kind of work you have used them for where appropriate. That gives a more useful picture than simply producing a long software list.
Project descriptions should then concentrate on responsibilities. If the portfolio already explains the design concept, there is little reason for the CV to spend another paragraph explaining it.
Instead, it could identify:
- site research and analysis you personally completed;
- drawings, models or visualisations you produced;
- technical or digital tools used during development;
- your role within collaborative studio work;
- presentations, critiques or reviews in which you contributed.
This is also where discussions of the best architecture CV writing service in UK can become less useful if the emphasis shifts towards making an applicant sound impressive rather than helping them communicate accurately. Good wording can clarify experience, but it cannot create experience that was never there.
Professional work deserves the same level of precision. “Assisted with architectural projects” is vague. If you helped prepare drawings, organise project information, develop models or produce presentation material under supervision, those activities can be explained more clearly, provided they reflect what you actually did.
Competitions, exhibitions and workshops can also strengthen the picture when they have genuine relevance. Their value comes from what they reveal about your skills and development, not from simply adding more headings.
Practical Guidance
A useful starting point is surprisingly simple: put the portfolio away for ten minutes.
Look only at your experience and ask what someone would need to know about you before opening the portfolio.
Write down the answers without worrying about formatting.
Perhaps you have completed a placement but never mentioned what you actually did. Perhaps you worked on a group project where you handled most of the physical modelling. Perhaps you became confident producing drawings in Revit or learned how to present a design proposal clearly during studio reviews.
Now bring the portfolio back.
For each major project, check whether the CV is repeating information that the portfolio already proves. If it is, change the emphasis.
For example, imagine your portfolio shows a housing project with beautiful renders and detailed plans. Your CV does not need to explain the housing concept again. It could instead say that you carried out site analysis, developed massing studies, worked within a four-person group and produced the final presentation drawings.
The project has not changed.
What the reader learns about you has.
It is also worth checking the CV against the job or placement description. You do not need to copy its language, but notice which abilities are genuinely relevant. If the opportunity involves drawing production, digital modelling and collaborative work, make sure genuine experience in those areas is not buried beneath unrelated information.
Before submitting, read the CV as though you know nothing about the person.
Can you tell what stage of architectural education they are at? Can you distinguish academic work from professional experience? Can you understand their individual contribution? Can you tell which software they genuinely know?
If the answer is yes, the document is doing its job.
Mistakes to Avoid
Repeating the portfolio.
A CV filled with project summaries leaves less room for information that cannot be seen in the portfolio. Focus on your role, process and experience.
Trying to look more experienced than you are.
There is nothing embarrassing about being a student. Calling a university exercise professional experience can create more questions than it answers.
Treating software names as proof of competence.
A list of programmes does not explain what you can actually produce. Give context where it matters and be honest about your level.
Claiming everything from a group project.
If four people worked on the project, the CV should not quietly turn four contributions into one person’s achievement. Explain your part.
Deleting useful non-architectural experience.
A retail job may not demonstrate architectural design, but it can show that you dealt with customers, managed responsibility and worked with other people. That may be worth mentioning if it supports the application.
Adding information because the page looks empty.
A clean, focused CV is not automatically a weak CV. Relevance matters more than filling every available line.
Using impressive words without evidence.
If a sentence could describe almost any architecture student, it probably needs to become more specific.
Bringing the Main Lessons Together
The CV and portfolio work best when they behave like two parts of the same application rather than two versions of the same document.
The portfolio allows the reader to examine your architectural thinking. It shows the drawings, models, visualisations, research and development that make your work tangible.
The CV gives those visuals a person behind them.
It explains what you studied, what responsibilities you took on, which skills you have developed, where your professional exposure has come from and what you contributed when the work was collaborative.
For a student without years of practice experience, that distinction can make a real difference. You do not need to hide the fact that much of your experience comes from university. You need to understand what that experience actually demonstrates.
A second-year housing project might show that you can analyse a site, develop an idea through several iterations, work with others and communicate a proposal. A workshop might show practical curiosity. A placement might introduce professional processes. A part-time job might demonstrate responsibility that studio work alone does not reveal.
None of those experiences needs to be inflated.
The most convincing architecture CV is usually not the one packed with the biggest claims. It is the one that allows a reader to understand, quickly and honestly, where you are, what you have done, what you can contribute and how your architectural skills are developing.
Once that becomes the purpose of the CV, the blank page becomes much less intimidating. You are no longer trying to find more things to say.
You are deciding which parts of your experience are actually worth saying.