
You are leaving an architecture firm while a project you signed or sealed is still in construction. The resignation is a career decision; the project may continue to generate RFIs, revisions and site questions after your last day. Who answers them, who signs future documents and how are unresolved issues handed over? Those questions need a planned conversation with the firm. They cannot be settled by assuming that your name disappears from earlier work or that the next architect can automatically take over every responsibility.
Professional duties depend on jurisdiction, contract, employment arrangement and the status of the documents. This article is a handover checklist, not legal advice. In the United States, NCARB’s Model Rules of Conduct address signing and sealing work under responsible control; state rules govern actual practice. The AIA’s discussion of terminated agreements also shows that changing names or seals on documents can raise jurisdiction-specific issues. Ask the firm’s responsible principal, insurer, counsel or licensing board for advice on your case.
Identify what you actually signed
Make a private, authorised list of the relevant project, issue dates, document sets and your role. Was your seal on permit drawings, construction documents, a revision, a report or a consultant package? Did you sign as architect of record or in another capacity? Were later revisions issued by someone else? The answers affect the handover. Do not rely on memory or a generic “I signed the project.”
Keep the list within the firm’s systems unless you have permission to retain a record. Do not download client drawings to personal storage on your way out. Ask how you can document your professional history and access the information needed if a future question legitimately arises. Confidentiality and record-retention rules still apply after employment ends.
If you never signed or sealed documents, you still need to hand over open work. The process may be simpler, but unresolved decisions and consultant commitments do not vanish when you resign.
Build an open-issues register
List current RFIs, site observations, design changes, authority comments, consultant decisions and client commitments. For each, record the issue, latest document version, status, next action, due date and person with authority to decide. Highlight items affecting safety, code, imminent installation or work about to be concealed. A pile of emails is not a handover if the next architect cannot tell what remains open.
Add a “why it matters” sentence to difficult issues. For example: “The contractor requested a different façade anchor; structural review is pending, so no architectural instruction has been issued.” That is clearer than “façade RFI ongoing.” Name assumptions that have not been verified. The receiving architect should not have to discover them by comparing fifty attachments.
Do not resolve technical questions hastily to leave a clean list. A rushed approval can be worse than an explicitly open item with a named next action. Escalate critical matters through the firm’s process while you are still present.
Agree on future authority
Ask who will be the responsible architect for new submissions, revisions and site responses after your departure. Which documents will they review, and what will they need to understand before signing? A successor should have time and access to exercise the control required by the jurisdiction; a simple file transfer is not a substitute for professional review.
Clarify who communicates the change to the client, contractor, consultants and authorities where necessary. Do not independently announce a new architect of record if the firm has not completed the required process. The project team needs one clear channel for questions. If a contractor continues to email you personally after your last day, the agreed handover should tell you where to redirect the message.
Ask how your name and seal will be handled on prior documents and later versions. Do not remove a seal or instruct someone else to do so based on a generic online rule. AIA notes that some state boards restrict removal of signatures and seals once applied. The responsible firm and applicable authority should determine the proper treatment.
Review contract and insurance questions early
Your employment contract may describe notice, records, client contact and professional obligations. The firm’s project agreement may identify the architect of record or required services during construction. Professional liability coverage and notification duties may also matter. Raise these questions with the firm’s leadership and insurer before the last week. Do not assume that resignation ends all exposure or that your former employer’s coverage automatically resolves every issue.
If a dispute or claim already exists, seek appropriate independent advice. This article cannot tell you what to admit, sign or disclose. The important operational point is to make unresolved risk visible to people responsible for it while records and team members are available.
Keep your resignation letter separate from the technical handover. The letter can be short and professional. The project handover should be detailed enough for a successor to act. Combining them into one emotional document can obscure the practical decisions needed.
Plan a review meeting, not just a folder transfer
Schedule time with the receiving architect and project lead. Walk through the current issue set, key assumptions, high-risk details, consultant status and upcoming deadlines. Ask the successor to identify anything they cannot find or understand. Record decisions and remaining questions after the meeting. A second brief check near your last day can catch changes that happened during notice.
If the team is overloaded, prioritise. Safety- and schedule-critical issues go first, then active client and consultant commitments, then background project history. A well-structured ten-page handover can be more useful than a 200-page export with no index. The goal is continuity of professional judgement, not proof that you sent every file.
Do not make the successor responsible for reconstructing undocumented verbal promises. If you told a contractor or client that the team would review an option, record that. If you gave no approval, state that too. Precise status protects the project and everyone involved.
Keep a clean boundary after departure
Agree whether the firm may contact you for factual clarification and through which channel. You may be willing to answer a limited question, but you should not casually provide new professional services after employment ends. If post-departure consulting is expected, define scope, compensation, insurance and authority in an appropriate agreement. Do not answer an RFI from a personal email account just because you remember the detail.
If a former colleague asks you to “quickly sign” a revision after you have left, do not treat it as routine. Responsible control and jurisdictional rules still apply. Direct the matter to the firm’s current project lead and obtain advice before taking any action. Likewise, do not use confidential records from the former firm to support unrelated work.
Preserve professional relationships. A good handover is not a favour that erases your rights; it is a way to protect clients, colleagues and your own reputation while you move on. You can be clear about notice limits and still provide a structured transfer.
Questions for the final week
Ask the project lead to acknowledge the handover and name the receiving person. A shared file without a recipient is easy to miss during a busy construction week. The acknowledgement should record receipt and any open questions, not pretend that every professional responsibility has been transferred by an email. Keep the handover version dated so later changes can be distinguished from the information available on your last day.
Which signed sets exist? Which issues are open? Who owns each decision after your last day? How will the client and authorities be informed? What happens to your seal on prior and future documents? What records will be retained? Who handles a later claim or clarification? Which advice from the insurer or licensing board is still needed? Put the answers in a controlled project record.
Resigning from a role should not leave the project guessing. Hand over the decisions, the authority and the unresolved risks explicitly, then let the applicable professional rules guide any signature or responsibility that remains.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide to architecture burnout and career choices.




