SF Permits MCP Server

{ "metadata": { "title": "SF DBI Electronic Plan Review (EPR) Requirements", "source": "SF DBI EPR Guidelines (Exhibit F) + Bluebeam Usage Guide", "source_urls": [ "https://www.sf.gov/information--how-create-pdfs-your-plans-or-addenda", "https://www.sf.gov/information--how-use-bluebeam", "https://www.sf.gov/resource--2021--electronic-plan-review-epr-resources" ], "compiled_from": [ "SF DBI EPR Guidelines (Exhibit F)", "SF DBI Bluebeam Usage Guide", "tier3/AB-004.txt (Priority Permit Processing Guidelines, Dec 15, 2022)", "tier1/completeness-checklist.json (plan format requirements)", "decision-tree-draft.json step_5 (plan format requirements)" ], "effective_date": "2024-01-01", "last_verified": "2026-02-14", "confidence": "high", "context": "DBI transitioned to 100% Electronic Plan Review for In-House Review projects. All plans reviewed in Bluebeam. Non-compliant submissions will be delayed or rejected." }, "epr_mandate": { "regulatory_basis": "Administrative Bulletin AB-004, Section on Concurrent Review", "quote": "The applicant of a priority project shall be required to submit plans for electronic plan review (EPR) to avail of concurrent plan review.", "current_status": "As of January 1, 2024, ALL plan submissions to DBI must be electronic — EPR is no longer limited to priority projects" }, "submission_platform": { "name": "Bluebeam Studio", "access": "Via DBI PermitSF portal", "note": "All in-house review plans are reviewed in Bluebeam Studio sessions" }, "requirements": { "drawing_production": [ { "id": "EPR-001", "rule": "Vector-based lines required", "detail": "Plan drawings created in CAD programs must use vector-based lines. Must line up when overlaid electronically. Scanned/raster drawings are not acceptable for plan review.", "severity": "reject", "common_violation": "Architects scanning hand-drawn markups instead of CAD output" }, { "id": "EPR-002", "rule": "TrueType or OpenType fonts required", "detail": "Use TrueType or OpenType fonts to create searchable text within the document. SHX fonts (AutoCAD default) are allowed only if you run batch OCR on the drawing set with Bluebeam eXtreme afterward.", "severity": "warning", "common_violation": "AutoCAD SHX fonts creating non-searchable text — plan checkers can't search for code references" }, { "id": "EPR-003", "rule": "Submit drawings as single PDF", "detail": "All drawing sheets must be in one consolidated PDF file per document type. Do not submit individual sheet PDFs.", "severity": "reject", "common_violation": "Submitting separate PDFs for each sheet" }, { "id": "EPR-004", "rule": "Full 1:1 scale output", "detail": "Plot or print drawing sheets at full 1:1 scale from authoring software. Also called 100% or 'to scale' output. Do NOT use 'scale to fit' printing.", "severity": "reject", "common_violation": "Printing to letter-size PDF instead of arch-size — makes dimensions unreadable in Bluebeam" }, { "id": "EPR-005", "rule": "Minimum sheet size 22\" x 34\"", "detail": "Drawing sheets must be at least 22\" x 34\" (ANSI D or Arch D). Larger sheets accepted. Exception: signage permits accept 11\" x 17\". Supplemental forms/documents at 8.5\" x 11\".", "severity": "reject", "exceptions": ["signage_permits_accept_11x17", "supplemental_docs_accept_8.5x11"], "common_violation": "Entire set printed at 11x17 — too small for plan review markup" }, { "id": "EPR-006", "rule": "File size under 250MB per upload", "detail": "Each uploaded file must be less than 250MB. For site permit addenda, limit is 350MB.", "severity": "reject", "common_violation": "High-resolution raster images embedded in plan set inflating file size" } ], "pdf_metadata_and_navigation": [ { "id": "EPR-007", "rule": "Bookmarks with page number and sheet name", "detail": "Add bookmarks for each sheet with format: 'A0.0 - COVER SHEET'. Calculations do not need bookmarks. DBI says 'We do not require bookmarks' but 'Reviewers can work faster if you add them.'", "severity": "recommendation", "common_violation": "No bookmarks — plan checkers have to scroll through 50+ pages manually" }, { "id": "EPR-008", "rule": "Page labels in Thumbnails tab", "detail": "Drawings shall have page labels in the Thumbnail tab containing sheet number and name. Labels must match bookmark labels.", "severity": "recommendation", "common_violation": "Default numeric page labels instead of sheet numbers" }, { "id": "EPR-009", "rule": "PDF must be unlocked and editable", "detail": "Do not submit locked, password-protected, encrypted, or 'restricted' documents. Bluebeam needs to add markup, comments, and stamps.", "severity": "reject", "common_violation": "PDF exported with security restrictions from Adobe Acrobat" }, { "id": "EPR-010", "rule": "No certificate-type digital signatures", "detail": "Do not use certificate-type digital signatures. This will lock the file and delay permit approval. Use scanned graphic signatures instead.", "severity": "reject", "common_violation": "Engineer using Adobe Sign or DocuSign certificate signature — locks the PDF for Bluebeam" } ], "cover_sheet": [ { "id": "EPR-011", "rule": "Total page count on cover sheet", "detail": "Cover sheets must have a total page count that matches the actual PDF page count.", "severity": "warning", "common_violation": "Cover says '12 sheets' but PDF has 14 pages" }, { "id": "EPR-012", "rule": "8.5\" x 11\" blank area on cover sheet", "detail": "Cover sheets must contain a blank area that is 8.5\" wide x 11\" tall for DBI stamping and permit information.", "severity": "warning", "common_violation": "Cover sheet completely filled with project info — no room for DBI permit stamp" } ], "title_block": [ { "id": "EPR-013", "rule": "Project address on every sheet", "detail": "Title blocks must have the project address on every sheet in the entire set.", "severity": "reject", "common_violation": "Address on cover but missing from individual drawing sheets" }, { "id": "EPR-014", "rule": "Sheet number on every sheet", "detail": "Title blocks must have the sheet number on every sheet.", "severity": "reject", "common_violation": "Unnumbered supplemental pages mixed into drawing set" }, { "id": "EPR-015", "rule": "Sheet name on every sheet", "detail": "Title blocks must have the sheet name (description) on every sheet.", "severity": "warning", "common_violation": "Sheet numbers present but no descriptive names" }, { "id": "EPR-016", "rule": "2\" x 2\" blank area on every sheet title block", "detail": "A blank area at least 2\" wide x 2\" tall must appear in the same location on every sheet's title block. Used for reviewer stamps and approval marks.", "severity": "warning", "common_violation": "Title block completely filled — reviewer has to stamp over existing content" }, { "id": "EPR-017", "rule": "3 consistent items across entire set", "detail": "Title blocks must have 3 consistent items on every sheet in the entire set (typically: project address, firm name/logo, and sheet numbering format).", "severity": "warning", "common_violation": "Mixed title block formats when structural engineer uses different template than architect" } ], "signatures_and_stamps": [ { "id": "EPR-018", "rule": "Design professional signature and stamp on every sheet", "detail": "Every sheet must have your signature and stamp. Use a scanned graphic signature with a PDF stamp. Scan a .PNG file with transparent background for best results.", "severity": "reject", "common_violation": "Unsigned sheets — especially supplemental calculation pages" }, { "id": "EPR-019", "rule": "Flatten PDF after adding graphic signatures", "detail": "If you add a graphic stamp or signature after creating the PDF, flatten the PDF to embed the images. Unflattened stamps can be moved or deleted in Bluebeam.", "severity": "warning", "common_violation": "Stamp added as Bluebeam annotation instead of flattened into page" } ], "file_naming": [ { "id": "EPR-020", "rule": "Document naming convention", "detail": "Format: [Number Prefix]-[Document type]-[Revision Number] [Street address]_[Type/Count of Addenda]. If no application number yet, use street address. 6 accepted document types with number prefixes.", "severity": "warning", "common_violation": "Files named 'plans_final_v3.pdf' instead of following convention" } ], "bluebeam_specific": [ { "id": "EPR-021", "rule": "Back Check page required", "detail": "You must add DBI's Back Check page PDF to submit plans in Bluebeam. This is a standardized page for tracking review comments and responses.", "severity": "warning", "common_violation": "Forgetting to append the back check page template" }, { "id": "EPR-022", "rule": "Dense hatching may cause rendering issues", "detail": "Not an official DBI rule, but dense cross-hatching patterns cause slow rendering and lag in Bluebeam Studio sessions. Plan checkers may request simplified hatching.", "severity": "recommendation", "common_violation": "Dense material hatching patterns causing Bluebeam to freeze during markup" } ] }, "exhibit_f_supplementary": { "source": "EPR Exhibit F — PDF Creation Guidelines (original source document for EPR-001 through EPR-022)", "bookmark_hierarchy": { "id": "EPR-007-DETAIL", "description": "Recommended bookmark structure for plan sets. Not strictly required but significantly speeds review.", "format": "Sheet Number - Sheet Name (e.g., 'A1.0 - FLOOR PLAN')", "hierarchy_example": [ "G0.0 - COVER SHEET", "G0.1 - SHEET INDEX / GENERAL NOTES", "A1.0 - FLOOR PLAN - EXISTING", "A1.1 - FLOOR PLAN - PROPOSED", "A2.0 - ELEVATIONS", "A3.0 - BUILDING SECTIONS", "A4.0 - DETAILS", "S1.0 - STRUCTURAL FOUNDATION PLAN", "S2.0 - STRUCTURAL FRAMING", "M1.0 - MECHANICAL PLAN", "E1.0 - ELECTRICAL PLAN", "P1.0 - PLUMBING PLAN" ], "note": "Bookmarks help plan checkers navigate directly to specific sheets. DBI reviews 500+ plan sets per month — fast navigation = faster review." }, "sheet_numbering_convention": { "description": "Standard discipline-based sheet numbering used by DBI reviewers. Consistent numbering across all projects helps reviewers find information quickly.", "prefixes": [ {"prefix": "G", "discipline": "General", "examples": ["G0.0 Cover Sheet", "G0.1 Sheet Index", "G0.2 General Notes"]}, {"prefix": "A", "discipline": "Architectural", "examples": ["A1.0 Floor Plans", "A2.0 Elevations", "A3.0 Sections", "A4.0 Details"]}, {"prefix": "S", "discipline": "Structural", "examples": ["S1.0 Foundation Plan", "S2.0 Framing Plans", "S3.0 Structural Details"]}, {"prefix": "M", "discipline": "Mechanical", "examples": ["M1.0 HVAC Plan", "M2.0 Mechanical Details", "M3.0 Mechanical Schedules"]}, {"prefix": "E", "discipline": "Electrical", "examples": ["E1.0 Electrical Plan", "E2.0 Panel Schedules", "E3.0 Lighting Plan"]}, {"prefix": "P", "discipline": "Plumbing", "examples": ["P1.0 Plumbing Plan", "P2.0 Plumbing Details", "P3.0 Fixture Schedules"]}, {"prefix": "T", "discipline": "Title-24 Energy", "examples": ["T1.0 Energy Compliance Forms", "T2.0 Energy Calculations"]}, {"prefix": "L", "discipline": "Landscape (if applicable)", "examples": ["L1.0 Landscape Plan"]} ] }, "file_size_guidance": { "maximum_per_upload": "250MB (standard), 350MB (site permit addenda)", "recommended_split": "Split plan sets at 50MB for faster upload and download", "common_causes_of_large_files": [ "High-resolution raster images embedded in drawings", "Unoptimized photos of existing conditions", "Embedded 3D model data from Revit exports", "Dense hatching patterns rendered as raster" ], "reduction_tips": [ "Downsample images to 150-200 DPI (sufficient for plan review)", "Remove embedded 3D model data before PDF export", "Use vector hatching instead of raster patterns", "Run PDF optimizer in Bluebeam or Acrobat before upload" ] }, "pdf_security_requirements": { "id": "EPR-009-DETAIL", "must_not_have": [ "Password protection (open password or permissions password)", "Print restrictions", "Copy/edit restrictions", "Certificate-based encryption", "DocuSign or Adobe Sign certificate signatures (locks PDF)" ], "must_allow": [ "Bluebeam markup and annotation", "Text search (searchable fonts required — EPR-002)", "Page extraction and reordering by reviewers", "Stamp placement by DBI for approval" ], "note": "Plan checkers cannot review locked PDFs in Bluebeam. A locked submission will be returned without review." }, "batch_ocr_instructions": { "id": "EPR-002-DETAIL", "context": "AutoCAD SHX fonts create non-searchable text in PDF. Plan checkers need to search for code references (e.g., 'CBC 11B', 'NFPA 13').", "steps": [ "Open plan set in Bluebeam Revu", "Go to Document > OCR > Run OCR on entire document", "Select 'Searchable (Exact)' option for best accuracy", "Save and verify text is searchable by using Ctrl+F" ], "alternative": "Use TrueType or OpenType fonts in AutoCAD (set TEXTFONT system variable) to avoid needing OCR entirely" }, "back_check_page": { "source": "DBI EPR Back Check Page PDF (Updated 01/19/2021)", "id": "EPR-021-DETAIL", "description": "A standardized Bluebeam-formatted page that must be appended as the LAST page of every plan set PDF. Contains the backcheck menu that DBI plan reviewers need to complete plan review.", "instructions": [ "Complete your plans", "Export a PDF file of your plans", "Add the Back Check Page as the last page of the PDF file", "Save the PDF" ], "format": "Bluebeam-formatted PDF — contains embedded Bluebeam form fields for reviewer use", "common_mistake": "Forgetting to add this page, or adding it in the middle of the plan set instead of at the end" }, "exhibit_c_project_folder_structure": { "source": "CCSF EPR Exhibit C — Bluebeam Studio Project Layout & Folder Structure (2/10/2020)", "description": "Defines the standard folder structure within Bluebeam Studio Projects used for DBI electronic plan review. Understanding this structure helps applicants know where their documents will be organized.", "project_naming": "Format: [Year]-[Application Number] [Street Address] (e.g., '2019-1126-1234 49 S. Van Ness')", "folder_structure": { "root": "CCSF EPR", "folders": [ { "folder": "A. PRE-SCREENING & PERMIT SUBMITTAL", "subfolders": [ {"name": "1. PERMIT FORMS", "contents": "Building permit application forms (Form 1/2, 3/8, etc.)"}, {"name": "2. ROUTING FORMS", "contents": "Agency routing forms for Planning, DPH, SFFD, etc."}, {"name": "3. DOCUMENTS FOR REVIEW", "contents": "Plan sets, calculations, reports — the actual construction documents for review"} ] }, { "folder": "B. APPROVED DOCUMENTS", "subfolders": [ {"name": "1. BUILDING PERMIT DOCUMENTS", "contents": "Final approved and stamped plan sets after all agencies approve"} ] } ] }, "applicant_note": "Applicants upload to folder A. DBI moves approved documents to folder B after permit issuance." }, "exhibit_e_studio_session_layout": { "source": "CCSF EPR Exhibit E — Bluebeam Studio Session Layout (2/10/2020)", "description": "Visual reference for how Bluebeam Studio Sessions are configured for DBI plan review. Sessions are where real-time multi-agency review and markup happens.", "session_naming": "Format: [Application Number] [Street Address] REVIEW - [Session Number] (e.g., '2019-1126-1234 49 S. Van Ness REVIEW - 95')", "session_components": { "studio_menu": "Studio tab must be selected (not Projects) to access the active review session", "studio_connection": "Green cloud icon indicates connected to Studio — required for real-time collaboration", "attendees_panel": "Shows all reviewers currently in the session (DBI BLDG, DBI MECH, FIRE, etc.) with online/offline status", "documents_panel": "Shows the plan set PDF(s) uploaded to the session", "bookmarks_panel": "Pull up from bottom — shows sheet navigation bookmarks (why EPR-007 bookmark format matters)", "tool_chest": "DBI-specific markup tools: Callout, Text Box, Cloud+, Dimensional Note, Highlighter, Length Measurement, Area Measurement", "markups_list": "Bottom panel showing all review comments with Date, Page Label, Author, Color, Comments, and Status columns" }, "markup_status_workflow": { "description": "When a reviewer adds a correction comment, applicant must respond using the status menu (double-click to respond)", "applicant_response_statuses": [ {"status": "INCORPORATED (per reply as needed)", "meaning": "Applicant has addressed the comment and made the correction in revised plans"}, {"status": "NOT INCORPORATED (per reply)", "meaning": "Applicant has not made the change — must include explanation in reply"} ], "reviewer_back_check_statuses": [ {"status": "CLOSED", "meaning": "Reviewer has verified the correction was properly made — comment is resolved"}, {"status": "OPEN", "meaning": "Reviewer has NOT accepted the response — correction still needed or response inadequate"} ], "workflow_sequence": "Reviewer comments → Applicant responds (INCORPORATED/NOT INCORPORATED) → Reviewer back-checks (CLOSED/OPEN) → Repeat until all CLOSED" }, "color_coding_note": "Different agencies use different markup colors to distinguish their comments. DBI BLDG, DBI MECH, FIRE, and other reviewers each have assigned colors visible in the Markups List." } }, "severity_levels": { "reject": "DBI will not process the submission. Must fix before filing.", "warning": "DBI may accept but will likely issue a correction letter. Fix to avoid delays.", "recommendation": "Not required but significantly improves review speed and reduces friction." }, "pre_submission_checks": [ "Vector-based lines (no scanned/raster drawings) [EPR-001]", "TrueType/OpenType fonts for searchable text [EPR-002]", "All sheets in single consolidated PDF [EPR-003]", "Full 1:1 scale output (not 'scale to fit') [EPR-004]", "Minimum sheet size 22\" x 34\" for drawings [EPR-005]", "File size under 250MB per upload [EPR-006]", "Bookmarks for each sheet (recommended) [EPR-007]", "PDF unlocked — no encryption or passwords [EPR-009]", "No certificate-type digital signatures [EPR-010]", "8.5\" x 11\" blank area on cover sheet [EPR-012]", "Project address on every sheet [EPR-013]", "Sheet numbers on every sheet [EPR-014]", "Design professional signature/stamp on every sheet [EPR-018]", "Flatten PDF after adding graphic signatures [EPR-019]", "Back Check page appended [EPR-021]" ], "format_requirements": { "confidence": "high — sourced from official DBI EPR Guidelines (Exhibit F)", "requirements": [ {"requirement": "Vector-based PDF required", "details": "CAD-produced vector lines, not scanned images. Non-compliant = rejection.", "epr_id": "EPR-001"}, {"requirement": "TrueType/OpenType fonts", "details": "Searchable text required. SHX fonts need OCR post-processing.", "epr_id": "EPR-002"}, {"requirement": "Single consolidated PDF", "details": "One PDF per document type. No individual sheet files.", "epr_id": "EPR-003"}, {"requirement": "Full 1:1 scale", "details": "Print at 100% scale from authoring software.", "epr_id": "EPR-004"}, {"requirement": "Minimum 22\" x 34\" sheets", "details": "ANSI D or Arch D minimum. Signage permits: 11x17. Supplements: 8.5x11.", "epr_id": "EPR-005"}, {"requirement": "File size < 250MB", "details": "Per upload. Site permit addenda: 350MB limit.", "epr_id": "EPR-006"}, {"requirement": "PDF unlocked", "details": "No encryption, passwords, or security restrictions.", "epr_id": "EPR-009"}, {"requirement": "No digital certificate signatures", "details": "Use scanned graphic signatures. DocuSign/Adobe Sign certificates lock the PDF.", "epr_id": "EPR-010"}, {"requirement": "Back Check page", "details": "DBI standardized Back Check page appended to plan set.", "epr_id": "EPR-021"} ] }, "plan_content_requirements": { "source": "completeness-checklist.json + EPR Guidelines", "cover_sheet": [ "Property address and block/lot", "Project scope description matching permit application", "Code references (Building Code edition, Fire Code, Accessibility)", "Table of contents / sheet index", "Total page count matching actual PDF pages [EPR-011]", "8.5\" x 11\" blank area for DBI stamping [EPR-012]", "Licensed professional stamp and signature [EPR-018]" ], "title_block_every_sheet": [ "Project address [EPR-013]", "Sheet number [EPR-014]", "Sheet name/description [EPR-015]", "2\" x 2\" blank area for reviewer stamps [EPR-016]", "3 consistent items across entire set [EPR-017]" ], "architectural_plans": [ "Existing and proposed floor plans", "Existing and proposed elevations", "Sections showing existing and proposed conditions", "Site plan / plot plan", "Demolition plan (if applicable)" ], "structural_plans": [ "Structural calculations (if structural work)", "Foundation plans", "Framing plans", "Seismic analysis (if applicable)" ], "mep_plans": [ "Mechanical plans and schedules", "Electrical plans and panel schedules", "Plumbing plans and fixture schedules" ] }, "submission_copies": { "otc_review": "Submit via PermitSF portal — electronic only as of Jan 2024", "in_house_review": "Submit via PermitSF portal for electronic plan review in Bluebeam", "note": "Physical paper plans are no longer accepted for initial submission" }, "correction_response_workflow": { "source": "CCSF EPR Applicant Procedure Guide (2024), pages 21-49", "overview": "When plan checkers identify issues during review, they add Bluebeam markup comments directly on the plans. The applicant must respond to ALL comments before resubmittal.", "steps": [ { "id": "EPR-023", "step": "Download marked-up plans from Bluebeam Studio session", "detail": "Plan checker comments appear as Bluebeam markup annotations on specific sheets. Download the full annotated set to review all comments across all reviewers.", "common_mistake": "Only reviewing comments from one reviewer — multiple agencies comment simultaneously" }, { "id": "EPR-024", "step": "Address ALL plan check comments", "detail": "Every comment from every reviewing agency must be addressed. Use Bluebeam's markup reply feature to respond to each comment, or create a correction response letter referencing each comment by reviewer and sheet number.", "common_mistake": "Missing comments from agencies that review later in the cycle (e.g., DPH, SFFD)" }, { "id": "EPR-025", "step": "Add revision clouds on ALL changed items", "detail": "Every change between submission rounds must be enclosed in a revision cloud. Include revision delta markers (triangle with revision number). Revision clouds must be on the drawing layer, not as Bluebeam annotations.", "common_mistake": "Submitting corrected sheets without revision clouds — reviewer cannot find what changed" }, { "id": "EPR-026", "step": "Upload only changed sheets for corrections", "detail": "For plan check corrections, upload only the sheets that were modified — not the entire plan set. Use the same file naming convention with incremented revision number. Full set re-upload is only for addenda (new scope).", "common_mistake": "Uploading the full plan set for a correction response — slows review and confuses version tracking" }, { "id": "EPR-027", "step": "Update sheet index and page count", "detail": "If sheets were added or removed, update the cover sheet's table of contents and total page count to match the revised set.", "common_mistake": "Cover sheet still shows original page count after adding sheets" }, { "id": "EPR-028", "step": "Notify reviewer of resubmittal", "detail": "After uploading corrected sheets, notify the reviewer through the Bluebeam Studio session or PermitSF portal. Do not assume reviewers are automatically notified of uploads.", "common_mistake": "Uploading corrections but not notifying reviewer — plans sit in queue unreviewed" } ], "addenda_vs_corrections": { "correction": "Response to plan check comments. Upload only changed sheets with revision clouds. Uses same application number and review session.", "addendum": "Additional scope added to an approved or in-review permit. Requires new document upload with full addenda set. Format: [Number Prefix]-[Document type]-[Revision Number] [Street address]_[Type/Count of Addenda]. File size limit for site permit addenda is 350MB (vs 250MB standard)." } }, "document_type_numbering": { "source": "CCSF EPR Applicant Procedure Guide", "prefixes": [ {"prefix": "1-", "type": "Plans/Drawings", "example": "1-Plans-R0 123 Main St"}, {"prefix": "2-", "type": "Calculations", "example": "2-Calculations-R0 123 Main St"}, {"prefix": "3-", "type": "Reports/Studies", "example": "3-Reports-R0 123 Main St"}, {"prefix": "4-", "type": "Specifications", "example": "4-Specifications-R0 123 Main St"}, {"prefix": "5-", "type": "Other Documents", "example": "5-Other-R0 123 Main St"}, {"prefix": "6-", "type": "Addenda", "example": "6-Addenda-R1 123 Main St_Addendum1"} ], "naming_format": "[Number Prefix]-[Document type]-[Revision Number] [Street address]_[Type/Count of Addenda]", "note": "If no application number yet, use street address. Revision numbers increment: R0, R1, R2, etc." }, "review_statuses": { "source": "CCSF EPR Applicant Procedure Guide", "statuses": [ { "status": "Approved", "meaning": "Plans meet all code requirements. No changes needed.", "action": "Proceed to fee payment and permit issuance." }, { "status": "Approved as Noted", "meaning": "Plans are approved with minor notations. Changes may be required to be shown on job-site set but do not require resubmittal.", "action": "Review all notations. Incorporate notes into construction documents. Proceed to fee payment." }, { "status": "Corrections Required", "meaning": "Plans have deficiencies that must be corrected and resubmitted for another review round.", "action": "Follow correction response workflow (EPR-023 through EPR-028). Upload corrected sheets with revision clouds." }, { "status": "Not Approved", "meaning": "Plans have fundamental deficiencies. May require significant redesign.", "action": "Schedule pre-submittal meeting with plan checker. Address all comments. May need to restart review cycle." } ] }, "multi_agency_review": { "source": "CCSF EPR Applicant Procedure Guide", "overview": "In-house review projects are reviewed by multiple agencies simultaneously in the same Bluebeam Studio session. Each agency adds their own color-coded markups.", "typical_reviewers": [ "DBI Building (structural, architectural)", "DBI Mechanical/Electrical", "Planning Department", "SFFD (Fire Department)", "DPH (Public Health — food facilities)", "SFPUC (water/sewer)", "DPW/BSM (public right-of-way)" ], "coordination_tips": [ "Review ALL agency comments — not just DBI Building", "Agency comments may conflict — flag conflicting requirements to plan checker", "Agencies review on different schedules — some comments may arrive later than others", "Request a consolidated review meeting if comments from multiple agencies are contradictory" ] }, "permit_issuance_process": { "source": "CCSF EPR Applicant Procedure Guide", "steps_after_approval": [ "All reviewing agencies must show 'Approved' or 'Approved as Noted' status", "Pay all permit fees via PermitSF portal", "Verify contractor insurance and license (if applicable)", "DBI issues permit electronically through PermitSF", "Download approved stamped plans for job site" ], "note": "Permit is not issued until ALL agencies approve and ALL fees are paid. One 'Corrections Required' from any agency holds up the entire permit." }, "decision_tree_integration": { "step_5_connection": "EPR format requirements apply to ALL documents listed in decision tree Step 5", "otc_implications": "Some OTC 'no plans' permits (Form 8) do not require plan drawings but still use electronic submission", "in_house_implications": "In-house review plans must be EPR-formatted for multi-agency concurrent review in Bluebeam Studio" } }