Your best project may have twenty contributors. The firm won the commission, a design director set the concept, an engineer resolved the structure and you developed the drawing package that made the design coherent. A portfolio page that says only “we designed” hides your value. A page that claims the whole project as yours risks losing trust in the first interview. Precise attribution solves both problems.
Architecture hiring managers need to know what you can do next. They cannot infer that from a beautiful image of a building unless you explain your own decisions, the stage of the work and the people who reviewed it. Clear credit is especially important for graduates and mid-career candidates whose work was produced inside large teams. It also helps you handle confidential material responsibly.
Separate project ownership from your contribution
Begin each project with a compact fact box: project type, location at a safe level, stage, dates, firm or team, your title, and your work. If the project is public, link to the official project page where appropriate. If it is confidential, use an anonymised description and check what your agreement permits. A client’s permission to publish a building photograph may not include permission to publish internal drawings or cost information.
Use verbs that describe actions. “Prepared a series of accessibility option plans,” “coordinated architectural comments with MEP,” or “developed the planning presentation diagrams” gives a clearer picture than “assisted on a mixed-use project.” The verb should also match your authority. “Proposed” is different from “approved.” “Coordinated” is different from “designed.” None of these distinctions make your work smaller; they let a reviewer trust it.
If you supervised others, identify the team size and what you reviewed. If a principal made the final decision, say so. For example: “I led the two-person façade package, developed three module options and presented the comparison to the project architect, who selected the final arrangement.” That sentence shows leadership, technical work and the decision chain.
Make a contribution map
For a complex project, build a small matrix for yourself before designing the page. Columns might be concept, planning, technical documentation, consultant coordination, site work and visual communication. In each, list what you personally did, what the team did and what you cannot share. This private map helps you decide which images support a truthful claim.
Suppose a competition entry shows a striking render. You designed the circulation concept, a colleague modelled the façade and an external studio produced the final visual. You can still use the image if permissions allow. Caption it: “Team competition entry; my contribution: circulation strategy and option diagrams. Final visualisation: external studio.” Then place your circulation sketch beside it. The render provides context; your diagram provides evidence.
Do not assume the reviewer will read a long disclaimer at the back. Put attribution near the work it explains. If a page has several images with different authorship, label each or add a clear legend. The AIA’s advice to architecture job seekers emphasises making the candidate’s work and range understandable. Local, specific credits do that better than a global “all projects were collaborative.”
Check rights before collecting images
Your employment contract, client agreement and jurisdiction may limit use of drawings, photographs, models and unpublished project facts. Ask the firm what you may include in a private application and what you may publish openly. A permitted, password-protected interview PDF and a public website portfolio may have different rules. Do not assume that because you drew a sheet, you own the right to distribute it.
If permission is denied, consider a case study that uses your own text and recreated, non-identifying diagrams, provided that this also respects your obligations. Describe a generic decision process without disclosing a client’s confidential data or copying protected documents. Label a recreated example as such. You can talk about the scale, stage and type of work without naming a private client. When uncertain, ask the employer or obtain advice under the applicable agreement.
Never remove a title block from a confidential drawing and assume it is now safe to publish. Geometry, site context or annotations may still reveal the project. Likewise, a site photograph may show people or restricted areas. The right level of disclosure depends on the project and your permissions, not on how easy it is to crop an image.
Show impact without claiming the team’s entire outcome
“The project received planning approval” is a project fact. “I secured planning approval” is a personal claim. If your role was preparing the drawing package and responses under review, say that. You can still show why it mattered: your diagrams clarified the access strategy or your drawing comparison resolved a comment. Where the effect cannot be measured, describe the decision made and the deliverable produced. Do not invent cost savings or performance results.
Use the interview to explain how your work entered the team’s process. What input did you receive? What options did you test? Who reviewed the recommendation? What happened afterward? An applicant who can answer those questions is more convincing than one who repeats “we collaborated” without a sequence.
If you joined a project late, do not imply you shaped the original design. Technical completion is significant work. “I inherited the scheme at developed design and coordinated the curtain-wall junctions for tender” tells a hiring team exactly where you can contribute. If you only worked on one floor, show that floor and say why it was challenging.
Use a short speaking formula
Try: “The team was working on [project problem]. My responsibility was [specific scope]. I produced [evidence] and brought [decision] to [reviewer or team]. The resulting direction was [outcome or current status].” This is easier to remember than a defensive list of caveats. It also gives the interviewer a place to ask deeper questions.
For a student team project, adapt the formula: “Four of us developed the master plan; I led the public-space sequence and made the section diagrams. The structural concept was developed by another teammate.” Academic collaboration deserves the same clarity as professional collaboration. An interviewer may be testing whether you can work in a design team, not only whether you can draw.
Do not downplay your contribution with “just.” Preparing a reliable coordination log, checking dimensions across packages or revising a detail after consultant feedback can be substantial work. Describe what made it difficult and how you handled it. Precision makes a modest task legible.
Make the project page readable at a glance
A simple structure works: one context image, one or two images showing your actual contribution, a role box and a brief decision story. If you need three paragraphs to explain which parts were yours, the page may be trying to carry too many tasks. Split it or choose a sharper example. A portfolio is evidence selection, not a complete project archive.
Use consistent labels across all projects: “Individual,” “Team of four,” “Professional work at [firm],” “My role,” “Project status.” Do not use “lead designer” for one project and “supported design” for another if the underlying scope was similar. Consistent attribution makes your career progression visible.
Ask a colleague who knows the project to review your claims if you can do so safely. Could they recognise your contribution? Would they object to your description of the decision process? This is an ethical check and a practical one: architecture networks are small, and references may include people from the same team.
Confidence through accuracy
Attribution is not a footnote to impressive images. It is the bridge between the team’s work and your next employer’s question: “What can this person do here?” When you specify scope, evidence and decision authority, you do not surrender credit to everyone else. You show what you actually made possible. The strongest collaborative portfolio says exactly where your work begins and why that part mattered.
Browse current architecture jobs on Jobs.archi and compare your next step with our architecture portfolio and interview guide.
The post How to Credit Team Projects in an Architecture Portfolio Without Underselling Yourself first appeared on jobs.archi.