Architecture school teaches you to make and defend a design. In an office, you also have to make your work usable by someone who was not in your studio at 2 a.m. That transition is less about knowing every detail and more about finding the right question, recording the answer and handing off a reliable piece of work.
The debate about a “practice gap” is real, but it is not a verdict on every school or graduate. An Archinect discussion started by a practice owner drew strong disagreement about what universities should teach. The useful question for a new employee is narrower: what can I do in week one that reduces uncertainty for my team?
Learn the project’s source of truth
Before editing a drawing, ask where the team keeps the latest model, issued drawings, consultant files, meeting decisions and unresolved questions. A beautiful update in the wrong file is invisible work. Write down the naming rule and who approves an issue. If a colleague says “use the latest plan,” ask for the exact file or issue date.
Make a one-page project map: project phase, client, lead architect, your reviewer, drawing set location, model location, consultant list and next issue. This is for your own use. Check it with your manager rather than assuming an old folder is current.
Separate a drawing change from a design decision
Suppose a door moves 200 mm on a plan. You can move a symbol in minutes. But the decision may affect clearances, hardware, fire strategy, structure, furniture or another discipline’s drawing. Ask: Who requested this? What problem does it solve? Which other documents describe the same door? Who can approve the change?
A good first-week contribution is a tiny change log with four columns: item, source of request, affected documents and decision owner. The point is not bureaucracy. It is to stop an unapproved edit becoming an apparent instruction to the rest of the team.
Treat redlines as questions with an owner
Never silently guess what an ambiguous redline means. Mark it “clarify” and ask one focused question: “Does this note change the stair width, or only the annotation?” After the answer, record the decision where your team expects it. If you discover a conflict between a redline and a consultant drawing, show both rather than choosing the version that looks easier.
Build a basic review loop
Before sending work back, check three things:
- Completeness: did you address every marked item, including notes that need a reply rather than a drawing edit?
- Consistency: did the plan, section, schedule and model remain aligned where this change touches them?
- Traceability: can your reviewer see what changed and which questions remain open?
Then send a short handoff: “Updated A101 and door schedule for items 1–4; item 5 needs a decision on fire rating; model version dated X is ready for review.” Replace X with the actual date, not a guessed one.
Ask for feedback on the workflow, not just the drawing
At the end of week one, ask your reviewer which error created the most rework and which check would have caught it earlier. A graduate can improve quickly by learning the team’s failure points. Design judgement matters; so do file hygiene, coordination and the ability to say “I need an answer before I issue this.”
Courses do teach professional practice in different ways. For example, Liverpool’s professional practice module covers clients, procurement, project management, regulations and cost control. Your first office will still have its own systems. Learn those systems before trying to look fast.
A five-day practice plan
On day one, ask where the live model, drawing register and decisions log live. Write down the naming convention and who approves a change. On day two, take one small marked-up item and trace it backwards: which client request, consultant input or regulation produced it? On day three, trace it forwards: which views, details, schedules and notes need the same update? On day four, ask a colleague to review your handoff before you call the item complete. On day five, note the three errors you nearly made and the check that caught each one.
This plan is intentionally modest. A new hire does not need to understand an entire building in a week. They do need to make one bounded piece of work safer for the next person. For example, moving a door on a plan is not finished when the symbol moves. Its clear opening, hardware set, room data, accessibility assumptions and related elevations may need checking. Record which of these you checked, which are outside your assignment and who owns the remaining decisions.
Save this as a first-week checklist: locate the source files; identify the decision owner; log change impacts; close redlines with evidence; send a clear handoff. The strongest new hire is the one whose work the next person can trust.
What to say when you are stuck
New employees often wait too long to ask because they want to appear capable. Try a question that shows the work you have already done: “I checked the issued plan and the current model. They show different door positions. Which one governs this revision, and should I flag the conflict to the consultant?” That gives a reviewer a decision to make instead of asking them to rediscover the problem.
Keep a short list of open questions with an owner and deadline. Separate items that stop the drawing from items that can wait until a scheduled review. When a colleague answers verbally, confirm the decision in the project’s usual record. This protects the team when another person picks up the file tomorrow. It also shows that you understand the real first-week skill: moving work forward without quietly converting an assumption into a project instruction.
Browse current architecture jobs on Jobs.archi and read our guide for recent architecture graduates for a related next step.
The post Your First Week in an Architecture Office Tests Skills Studio Never Graded first appeared on jobs.archi.