Find the written HPRB action for the same case before describing the review as approved. Compare its scope and conditions with later HPO review and any issued DOB permit. The HPRB meeting-record guide identifies the Board’s post-meeting Record of Actions; an agenda or staff recommendation cannot fill a missing decision.
What the pre-meeting packet can tell you
HPO publishes the agenda and staff report by the Friday before the meeting. Consent means HPO found consistency and no known opposition; Denial means HPO found inconsistency. HPRB acts on these cases by voice vote, so read the later Record of Actions.
The HPRB meeting calendar separately lists filing deadlines, regular meetings and possible continuation meetings. A filing deadline does not prove the case reached that meeting, and a continuation date is only a possibility until the case record confirms it. Use the calendar to choose which month's records to inspect, then read the corresponding action. No actual project, meeting packet or vote was checked for this guide.
Build one case line across the documents
When you have an application confirmation, keep its Project Case Number exactly as printed. The HPRB concept-review instructions say HPO sends that number after it receives and reviews a submission. If an older paper identifies an HPA reference, preserve that too; these pages do not establish a public HPA search field or a universal format. Match the case with the site address, project description, submitted drawing version, and meeting month. A shared address alone can join different phases by mistake.
Use a four-stage record card:
| Stage | What to save | What it establishes |
|---|---|---|
| Application and notice | Printed case reference, site, proposed work, drawings and noticed meeting. | The matter proposed for review, not its disposition. |
| Agenda, calendar and HPO report | Meeting date and HPO view. | Pre-vote packet. |
| Written Record of Actions | Case, Board scope and conditions. | Meeting action. |
| Later plan and permit trail | Revised plans, HPO response, DOB permit reference and issue date if one exists. | Whether a later authorization was actually issued; it does not rewrite the Board action. |
Leave an action cell blank until its matching written record is located. If the case was continued or revisions were requested, carry that result forward and inspect the later meeting record named by the file. A favorable decision for a concept also should not be copied onto a materially revised design without checking the later review.
In a wholly fictional file, the pre-meeting packet for “Case 24-EXAMPLE” concerns a rear addition. A later folder contains revised drawings but no written Board action. The meeting outcome remains unresolved. Find the action for that case, then compare its scope with the revisions. An action naming only the rear addition cannot settle a different front-facade proposal in the same property's folder.
Board concept approval is not the issued building permit
The Office of Planning's permit-and-design-review guide says preservation review is an added step in the ordinary DC building-permit process. HPO may clear some work administratively, so an historic-property permit file does not necessarily have an HPRB vote. When a project does go to HPRB for concept review, the Board's favorable action concerns a design stage, not a finished permit application.
The concept-review instructions say HPRB may approve a concept, seek revisions, or find it inconsistent with preservation standards. After concept approval, final review of changes and the later permit application is typically delegated to HPO; the applicant develops permit plans. Compare the Board's recorded scope with any revised plan and subsequent HPO review, then check the separately issued DOB permit if that is the question. The DC HPO raze-clearance guide addresses a different preservation path and illustrates why an HPO decision and a DOB permit must not be merged. Neither a concept approval nor a favorable staff report proves an issued building permit, completed work or a passed inspection.
When the action or older packet is missing
The Past HPRB Meetings page describes year-and-month meeting records in an external Box archive and labels a linked meeting collection 2009–present. The agendas-and-reports page separately says HPO maintains meeting actions dating to December 2005. Those statements describe different archive scopes; neither is a promise that every case packet or action is available online for every year. No Box folder, transcript, PDF or case result was opened in this review.
If a matching action is not visible, first check the meeting month, any continuation date actually recorded, and the exact case reference and site description. Then ask HPO or the Office of Planning for the named Record of Actions, or a transcript if that is the missing item. The current Office of Planning page lists (202) 442-7600 as its general phone. Give the project case number or printed HPA reference if available, address, approximate meeting date, work scope and the document you already have. The past-meetings page describes an email route for transcript inquiries, but the address was not legible in the served page; use its current contact link rather than guessing it. No contact or records request was made here.
An absent online packet does not prove that no HPRB review occurred or that a project was approved or denied. For property-identity conflicts, the DC square-and-lot guide helps keep a tax-lot clue separate from the record lot and address; it does not decide the Board action. The conclusion should say which document and meeting were found, what action the Board actually recorded, and which later plan or issued-permit record remains unresolved. HPRB records do not prove present safety or lawful occupancy.
Official Office of Planning and HPRB pages checked October 8, 2026 (UTC). Their documented archives and workflows were reviewed; no case search, Box file, meeting video, account, application, permit lookup or record request was completed.