An architect interested in code consulting may know how to look up a regulation but have little evidence of giving independent advice. A code consultant’s value lies in framing the question, locating the adopted rule, understanding the project facts, identifying uncertainty and communicating an answer the design team can act on. A short, carefully bounded case file can show those skills to an employer more clearly than a CV line that says “strong code knowledge.”
This article is about a work sample for a career transition, not a guide to becoming licensed or authorised to practise in a specific jurisdiction. The International Code Council’s discussion of moving into code consulting highlights the need to build expertise and client trust. Use current local codes and qualified review for real decisions. A portfolio exercise should be labelled as a study unless it was part of authorised professional work.
Choose a question with a clear boundary
Pick a narrow issue: the occupancy classification of a proposed space, the route of an accessible entrance, the basis for a fire separation or the effect of changing a room’s use. Avoid trying to “review the whole building” in one sample. A bounded question lets the reader see your source selection and reasoning. It also makes it easier to state what facts are missing.
If you use a real project, obtain permission and remove confidential details. If not, create a hypothetical building with explicit assumptions. For example: “Two-storey community building in [jurisdiction], proposed ground-floor assembly room, construction type and occupant load to be confirmed.” Do not choose assumptions merely to force a preferred answer. The case should test your method, including what you would do when a fact is uncertain.
State the jurisdiction and adopted code edition before quoting a section. Codes change and local amendments matter. A section from the wrong edition can be persuasive and wrong. If you cannot verify the adopted basis, make that the first unresolved item in the case file rather than pretending it is settled.
Use a five-part structure
Page one can contain: project question; known facts and missing facts; applicable sources; interpretation options; and recommended next action. A diagram may show the space or route. Page two, if needed, can show the source trail and decision log. Keep the conclusion proportionate to the evidence. “This appears to require review under X provision once occupant load is confirmed” may be the correct interim answer.
Separate a rule’s text from your interpretation. Use a short paraphrase with a precise citation rather than pasting pages of copyrighted code. Identify the authority that will confirm a disputed interpretation. A consultant can advise, but a local authority may make a final decision in a permit process. Your sample should show that you understand the difference.
If two plausible interpretations exist, lay out their consequences and the fact that would decide between them. Employers value this more than a confident answer that hides ambiguity. A good code note reduces the design team’s uncertainty without overstating authority.
Show how the answer changes a design decision
A code case file should not end at “Section X applies.” Explain the project implication: a corridor may need to widen, a door may need a different rating, a route may need another access point or a programme assumption may need review. Identify who would act and what drawing or schedule would change. Code advice becomes valuable when it connects the rule to an implementable project action.
Do not redesign the entire project in a code note. A narrow recommendation can say, “Architect to test two entrance options; access consultant to review; authority meeting required before design freeze.” The action should respect each person’s scope and decision authority.
If there is a cost or programme impact, flag it as a matter to estimate rather than inventing a number. The design team or cost consultant can assess options. Your role is to make the implication visible early enough to matter.
Document your source trail
List the official code edition, local amendments, relevant guidance and any authority correspondence used. Record the date checked. If the code text is not freely available, do not cite an unverified secondary summary as though it were the law. A work sample can state that a licensed source was consulted without reproducing protected text.
Use a table: fact, source, interpretation, open question and owner. For a real project, include only material you have permission to share. If your employer’s internal note is confidential, recreate a synthetic example using public sources and label it. The ability to protect client information is part of the professional skill.
Do not use AI-generated code citations without checking them. A model may invent a plausible section number or omit an exception. If you used AI to locate candidate provisions, say so and show the independent verification. The reviewer should be able to follow your reasoning even if the tool disappears.
Ask for a critique from a qualified person
Before showing the case to employers, have a code specialist, registered architect or experienced plan reviewer examine it. Ask: Did I identify the right governing edition? Did I omit a key fact? Did I overstate a conclusion? Would my recommended next action be safe? Record the feedback and revise. Do not present a self-reviewed hypothetical as an official opinion.
If you cannot obtain a specialist review, label the sample as an analytical exercise and focus on questions and method. An employer may still value it. They should not mistake it for a certified interpretation. Honesty about review status increases credibility.
Keep a version history. If the code basis changes, your case may need updating. A date on the work sample prevents a future interviewer from assuming it reflects today’s rules without review.
Translate architecture experience into consulting evidence
You may already have relevant stories: spotting a conflict before submission, coordinating an accessibility review, answering an authority comment or explaining a code issue to a client. Show your own part. Did you research the provision, draft a question, compare options or make the final recommendation under a senior’s review? These are different contributions. Use the most precise description.
In an interview, describe how you handled a disagreement. Did an architect prefer an option that you thought conflicted with a requirement? How did you present evidence without turning the conversation into a contest? Code consulting often depends on clear communication under commercial pressure. A case file that records both the design objective and the compliance concern can show that skill.
Ask the employer what kind of work it does: early concept advice, permit responses, independent review, expert reports or ongoing project support. Your sample should match the role’s actual tasks. A firm focused on authority negotiations may need different evidence from one focused on document QA.
A two-page sample checklist
The strongest answer may be a request for facts
Suppose the client asks whether a room can become an assembly space. Before giving a categorical answer, the consultant may need occupant load, existing exits, use of adjacent rooms, construction type and the authority’s adopted code. In your sample, show the questions in priority order and explain which answers could change the conclusion. This is not evasive. It is how you prevent an attractive preliminary interpretation from becoming an unsafe design assumption. A hiring manager can see that you know when the evidence is insufficient and how to obtain it efficiently.
Before sending: narrow question, jurisdiction, current adopted edition, facts and gaps, source citations, options, consequences, decision owner, review status and confidentiality check. Make the title clear: “Code analysis study” if hypothetical, “Redacted project note” if authorised. Add your name and exact role.
The purpose is not to prove that you have memorised a codebook. Show that you can move from a project’s uncertain facts to a traceable interpretation and an appropriately reviewed next action. That is the work a code consultancy can build on.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide to architecture burnout and career choices.
The post Architect to Code Consultant: Build a Case File That Shows Your Reasoning first appeared on jobs.archi.