For Architects, Engineers and Design Teams
Verify the complete code requirement before it becomes redesign.
LocalCode brings dimensional standards, definitions, exceptions, measurement rules, referenced manuals, and ordinance history into one connected research path. Design teams can establish the documented code basis earlier and preserve the source record behind important design assumptions.
A number in a table is rarely the entire requirement.
A height limit may depend on where measurement begins. A setback may change because of adjacency or an overlay. A parking requirement may contain exceptions elsewhere in the code. An engineering standard may be incorporated through a separate criteria manual. LocalCode helps you follow the complete reference chain before advancing the design.
Dimensional standards as a table, not as prose
Lot area, width, depth, setbacks, height, coverage, and open space, stored per district as typed rows with the section each one came from. Where a standard does not apply to a district, that is recorded explicitly rather than left blank for you to interpret.
LocalCode dimensional standards matrix showing standards by row and zoning district by column
Dimensional standards by district, each row carrying its source section.
Figures are part of the code
Setback diagrams, frontage figures, and dimensional illustrations carry regulatory content that the text alone does not. They are stored against the section they belong to, not as decoration on a page.
LocalCode section view showing a dimensional figure attached to its code section
A figure resolved to the section that governs it.
Verbatim, or nothing
LocalCode does not paraphrase a standard. What you see is the ordinance text with its citation, or an explicit statement that the record does not answer the question. Nothing in the middle, because a plausible number on a Z-sheet is worse than no number.
The work between design and submittal
The zoning analysis sheet, every project
Required against provided, line by line, with a citation on each line. Setbacks, height, lot coverage, density, parking, loading, landscape buffer widths, screening, open space. Assembling it means opening the UDC article by article and transcribing, and it is the first sheet a reviewer opens.
The standards for a district come back as structured rows with their source sections, so the sheet starts from the code rather than from a previous project's template.
Comment cycles
A reviewer cites a section number. Determining whether the comment is correct means finding that section, reading it in context, and checking whether the provision it relies on has been amended. Each round is calendar time against a construction start date.
A cited section resolves in one step, in context, with its cross-references and its adopting ordinance.
A different city every project
Fate, Rockwall, Royse City, Forney, Princeton. Different code, different parking ratios, different masonry and screening requirements. The standard you remember from the last city is the one most likely to end up wrong on a sheet with your seal on it.
Every jurisdiction LocalCode holds is normalized to the same representation and the same field names, so the lookup does not change shape when the city does.
Which jurisdictions
We build a jurisdiction to depth rather than scraping fifty to the surface. Coverage today is City of Fate, Texas as the reference build, and an Austin feasibility pilot. Tell us which cities your firm submits in most and we will tell you honestly whether we can be useful on your schedule.
Tell us your jurisdictionsWhat the code said on the date you filed
Under Chapter 245, the regulations in effect when the first permit application was filed generally govern the project. Answering that requires the amendment chain behind a section, not just its current text. We hold the adopting ordinances and we are building the chain that connects them to prior section text. It is not finished and we are not going to imply otherwise.
Join the waitlistDesign from the complete rule—not the first table you find.
LocalCode supports code research and professional verification. It does not replace the architect, engineer, plan reviewer, or legal counsel responsible for the final determination.
Explore the Code Library