Maryland’s state adoption and a jurisdiction’s implementation date are separate checkpoints. Capture both, and identify whether the building falls under a special code category before setting up the reference comparison.
Groundbook can review your drawings against the state and local code PDFs you upload. Add the adopted code books and amendments that apply to your project, then review potential issues with links to the supporting sources.
Add your references
Upload the applicable code PDFs alongside the drawing set. Include the edition, local amendments, and project requirements.
Choose each file’s role
Set code PDFs to Code and Use as reference. Mark the drawings you want reviewed as Check this file.
Review the findings
Follow the linked drawing and reference, check applicability, and have the responsible professional verify the issue.
California code PDFs shown as an example. Upload the references that apply to your project.Try with your code PDFs
State and local references
Code references for Maryland
Examples of references you can bring into Groundbook. Confirm the adopted edition, effective date, and project scope with the reviewing authority, then upload the applicable PDFs.
Include the applicable accessibility and existing-building references alongside the local submission requirements.
Code names link to official agency or publisher resources. Reviewed September 9, 2026. The reference set comes from the files you supply.
Maryland reference guide
Establish who reviews what
Confirm local implementation
Maryland Labor describes a two-step adoption process, with local jurisdictions given time after state adoption to implement the new codes. It directs applicants to the specific local jurisdiction for its adoption status.
The state’s code matrix distinguishes project types, including modular and state-owned or state-used buildings under the Model Performance Code. The Building Performance Standards also have limits on local changes to energy and accessibility requirements.
Sources reviewed September 9, 2026. Confirm current requirements and project applicability with the reviewing authority.
Prepare a useful review
What to bring for Maryland
Use this preparation list for Groundbook alongside the official permit checklist.
Local adoption record
Supply the local effective date, code editions, permitted amendments, and submission checklist. State the application date being used.
Building-category confirmation
Identify whether the project is site-built, modular, state-owned, or state-used and include the authority’s determination of the governing standards.
Energy/accessibility coordination
Add the applicable energy and accessibility references, reports, schedules, and plans. Compare common values and design assumptions across discipline documents.
A current drawing register
Identify which files are being checked, which are references, and which revisions are superseded. Include reviewer comments and responses where they explain an unresolved decision.
Does Maryland state adoption immediately establish every local submission’s code basis?
Confirm the local implementation date. Maryland Labor describes a state-adoption step followed by local implementation and directs applicants to the local jurisdiction for its current status.
Which documents should I supply for a Maryland AI plan review?
Supply the current drawing set and schedules, relevant specifications and reports, the applicable code and amendment PDFs, and the reviewing authority’s checklist. Identify the edition, project scope, and permit stage. Groundbook reviews the supplied evidence; do not assume every local requirement is already available.
Does Groundbook approve a permit or certify compliance?
No. Groundbook surfaces potential conflicts and omissions with links to source documents for professional verification. It does not issue permits, certify compliance, provide permit-expediting services, or replace the authority having jurisdiction.