- Community planning
- Development applications
- Historic preservation
- Info counter
- About us
- Related sites
ePlans allows property owners to submit development proposals and regulatory agencies to review applications electronically. The system helps manage critical project information and provides the opportunity for agencies and individuals who review and comment on new development plans to organize their comments as one voice to applicants and the public. Users at all technical skill levels communicate throughout the review process, and all project information is visible and accessible, allowing multiple reviewers to access information simultaneously.
ePlans is a major step toward streamlining the Planning Department’s development review process and provides real benefits, including cost savings, time savings, eliminating paper, greater coordination, and greater accuracy.
Below are new user guides for uploading files to ePlans for Preliminary and Site Plan applications. A summary of the changes follows:
The sort code is the two-digit number at the beginning of the ePlans filenames that ensures the files appear in a logical and consistent order in the ePlans folders. Whereas the original Preliminary and Site Plan guides had different sort codes for the same files, depending on which type of plan you were submitting, the new guides use the same sort code for each type of file, regardless of plan type.
The descriptor is the abbreviation in the filename after the sort code that identifies the file contents. These descriptors are important because a script on our Development Applications Information Center (DAIC) website converts these descriptors into full document type descriptions when displaying the file listing.
There are a few files that are typically required for either of these application types that only get reviewed in one of the two projects in ePlans. For these files, you will upload a placeholder document for the required file in the project where the file will not be reviewed pointing to the project where that file will be reviewed. This placeholder document is an 8 ½ x 11 PDF stating which plan to see for that exhibit. Many of the required items still need to be uploaded to both the Preliminary and Site Plan projects in ePlans, so make sure you have the correct plan number in the filename depending on which project you are uploading to.
See the bottom of the page for a note about sheet numbers.
Our ePlans supporting documents will guide you through submitting a complete application. We encourage your input on their usefulness. Please send us your comments.
As part of the on-going effort to improve and streamline the Local Area Transportation Review and Transportation Policy Area Review (LATR & TPAR) Guidelines, M-NCPPC staff has developed a traffic study scoping form. The purpose of this form is to simplify and standardize the traffic analysis component of the Adequate Public Facilities (APF)/Local Area Transportation Review test.
For applications requiring a traffic study or exemption statement, please fill out the form and send it to the appropriate transportation planner for Area 1, 2, or 3, as noted below. The Area transportation planner will review the submitted Agreement Form and contact you to refine specific details of the traffic study scope, as needed.
Please use this form for all new traffic study/exemption statement scoping requests. If you have any questions, please feel free to contact one of the Montgomery County Planning Department’s Area Transportation Planners:
|Click here to get started||Add drawings and documents|
The following is an example of the typical preliminary or site plan review process through ePlans:
The following is an example of the typical record plat review process through ePlans:
One thing that perhaps needs clarification is the sheet number part of the filename. In the submission guides, many of the drawing types show “-00X” at the end of the filename. While it was originally envisioned that the sheet numbers on the plan drawings would start with 1 and go up from there, leading to filenames ending in “-001”, “-002”, etc., in practice many applications are submitted with very different sheet-naming conventions.
The sheet number in the filename serves two purposes:
Someone looking at the sheet index on the cover sheet of the drawing set should be able to ascertain which file to open to see that sheet. If you use something very straightforward like “S-1” for the first site plan drawing, “L-1” for the first landscape drawing, and “A-1” for the first architectural drawing, it is fine to use “-001” at the end of the filename for each of these. However, if your drawing set contains “S 1.3”, “LL-2.1”, “LT-1.0”, and “A5.2”, you need to make sure your filename ends with these sheet numbers to make it easy for someone looking at the index find the correct file. In this example, your filenames could end in “-S1.3”, “-LL2.1”, “-LT1.0”, and “A5.2” or “-S-1.3”, “-LL-2.1”, “-LT-1.0”, and “A-5.2”.
If your drawing has sheets that begin with “10” or more, insert a zero in front of the sheet number for sheets before 10 to ensure the files will sort correctly in ePlans. So, for example, if you have sheets “S 9” and “S 10”, the filenames should end in “S-09” and “S-10” or “-009” and “-010”. If you have multiple iterations of a sheet beginning with the same sheet number, such as sheets “2 A”, “2 B”, and “2 C”, add the letter to the end of the filename, giving you something like “-002A”, “-002B”, “-002C”.
Last updated: October 7, 2015