Preconstruction Regulatory Intelligence

Know every code
before you break ground.

Brand identity for a platform that turns weeks of manual compliance research into hours. Multi-jurisdictional mapping, proactive monitoring, automated feasibility.

Codesite

Dual meaning: "code" (regulatory building codes) + "site" (construction site). Short, modern, developer-tool energy. Works across every vertical.

"We use Codesite to map compliance across jurisdictions before breaking ground."

codesite.ai codesite.io codesite.com getcodesite.com

Setline

SET-line

From "setback line" -- the legal boundary on a survey that dictates where you can build. Evokes the line between cleared and blocked. Also reads as "set the line" for compliance boundaries. Clean, surveying vocabulary.

"Pull the Setline report before we submit -- I need to see what Cook County changed."

setline.ai setline.io setline.dev setline.com

Planbrace

PLAN-brace

"Plan" (preconstruction planning) + "brace" (structural reinforcement, and to prepare/brace for). Implies strengthening your plans against regulatory risk before they fail. Feels solid, engineering-native.

"We use Planbrace to stress-test feasibility against every applicable code."

planbrace.ai planbrace.io planbrace.com

Preclr

pre-CLEAR

Shorthand for "pre-clearance" -- the regulatory approval you need before construction. Reads as "pre-clear" which is exactly what the platform does: clear regulatory hurdles before they become problems. Vowel-dropped like a dev tool (flickr, tumblr era, but still current).

"Preclr flagged three zoning conflicts before we even submitted the permit application."

preclr.ai preclr.io preclr.dev preclr.com

Benchline

BENCH-line

From "benchmark" (a surveyor's reference point) + "line" (regulatory boundary). Benchmarks are the fixed reference points surveyors use to measure everything else against -- like codes are the fixed reference your project must measure against.

"We ran it through Benchline -- 47 requirements across four jurisdictions, mapped in twenty minutes."

benchline.ai benchline.io benchline.com getbenchline.com

Clearspec

CLEAR-spec

"Clear" (regulatory clearance, clarity) + "spec" (specification, the language of construction). Your spec, cleared. Double meaning: clear specifications and cleared for construction. Professional, precise.

"Clearspec generated the compliance matrix before the bid meeting even started."

clearspec.ai clearspec.io clearspec.com clearspec.dev

Forebuild

FOR-build

"Fore" (foresight, before, looking ahead) + "build." The preconstruction angle made literal. Also echoes "forewarn" -- seeing what is coming before it arrives. Simple, direct, says exactly what it does.

"We use Forebuild to see regulatory risk before it costs us money."

forebuild.ai forebuild.io forebuild.com forebuild.dev

Stratum

STRAY-tum

A real English word meaning "a layer or level." In construction: the layers of soil, rock, or material a foundation sits on. In regulation: the layers of jurisdiction (federal, state, local, industry) that stack on top of each other. The platform reveals every stratum of compliance.

"Stratum mapped the full regulatory stack -- federal through local -- in one report."

stratum.ai stratum.com stratum.io usestratum.com

Gridsight

GRID-site

"Grid" (the structural grid in construction drawings, also the regulatory grid of overlapping codes) + "sight" (visibility, foresight, oversight). Your regulatory grid, visible. Also near-homophone with "gridsite" which echoes the construction site angle.

"Gridsight caught the egress conflict between the fire code and the TSA barrier spec."

gridsight.ai gridsight.io gridsight.dev gridsight.com

Codemark

CODE-mark

"Code" (building codes) + "mark" (a benchmark, a mark of compliance, to mark/annotate). Like Codesite, plays on the dual meaning of "code" but with "mark" implying precision, annotation, and the benchmark your project must hit. Also reads as "the codemark" -- a stamp of regulatory readiness.

"We ran Codemark on the RFP and flagged six requirements the GC missed entirely."

codemark.ai codemark.io codemark.com codemark.dev

Color

Indigo + Copper is the primary direction. Deep institutional indigo grounds the interface. Copper accents signal earned authority.

Deep indigo backgrounds create institutional depth -- the kind of gravity you feel opening a regulatory reference. Copper accents are deliberate: not gold (too flashy), not orange (too casual), but copper -- a material that earns its patina through use. The combination says: this tool has weight, and it has been here before.

Secondary indigo/periwinkle accents provide contrast for code citations and secondary actions. Status colors (compliant, warning, violation) are universal across all palettes for consistency.

Root #07091a

Surface #0b0f22

Elevated #10152b

Copper subtle #3a1f14

Copper muted #5a3020

Copper #d4845e

Indigo subtle #1c1a4e

Indigo muted #2e2c80

Indigo #8690f8

Compliant

#34d399

Warning

#fbbf24

Violation

#f87171

Neutral

#586380

Info

#60a5fa

Teal + Violet

Regulatory precision meets modern intelligence. Teal for compliance trust, violet for analytical insight. Lighter, more contemporary feel.

Slate + Amber

Blueprint-grade tools for the built world. Pure zinc backgrounds with amber signal accents. Industrial, utilitarian, construction-site native.

Typography

Two faces. Inter for everything the user reads and clicks. JetBrains Mono for everything the regulations say.

Inter

UI / Headings / Body

Used for all interface text, headings, navigation, buttons, and body copy. Weight range 300-900. Size contrast is dramatic by design: display headings at 48-60px, body at 14px. This tension creates editorial hierarchy.

48 / 800 Compliance

24 / 700 Multi-Jurisdictional Analysis

18 / 600 Regulatory Change Monitoring

14 / 400 This feasibility report maps applicable building codes across federal, state, and local jurisdictions for the proposed healthcare facility in Harris County, Texas.

13 / 500 Navigation item · Button label · Table header

12 / 400 Caption · Metadata · Timestamp

JetBrains Mono

Codes / Citations / Data

Every code reference, regulation citation, data value, and machine-generated output uses JetBrains Mono. This creates an instant visual signal: "this text comes from a regulatory source" vs. "this text is our interface speaking."

16 / 700 IBC 2024 Section 903.2.1

13 / 600 NFPA 72 §17.7.3.2.1

13 / 400 Automatic sprinkler systems shall be provided throughout all buildings with a Group A occupancy fire area exceeding 12,000 sq ft.

11 / 500 COMPLIANT · 2026-02-26T14:32:00Z · CONFIDENCE: 0.97

Interface

Real regulatory content. Real compliance scenarios. Switch palettes above to see every component adapt.

Codesite

Workspace

Dashboard

Compliance Matrix

Jurisdictions

Code Library

Intelligence

Monitoring 3

Feasibility

Reports

Code	Requirement	Jurisdiction	Status
IBC 2024 §903.2.1	Automatic sprinkler system required for Group A occupancy exceeding 12,000 sq ft	Federal / IBC	Compliant
NFPA 72 §17.7.3	Initiating devices for fire alarm systems in high-rise buildings shall include manual pull stations at each exit	Federal / NFPA	Compliant
FAA AC 150/5360	Terminal planning guidelines for passenger processing capacity and level of service	Federal / FAA	Review
TSA 49 CFR §1542	Airport security program requirements for sterile area design and access controls	Federal / TSA	Violation
TX HSC §755.007	Texas Health and Safety Code requirements for commercial building fire alarm systems	State / Texas	Pending

IBC 2024 §903.2.1.1

Group A-1 Occupancies — Sprinkler Requirements

Effective: 2024-05-01

          An automatic sprinkler system shall be provided for Group A-1 occupancies where one of the following conditions exists: (1) The fire area exceeds 12,000 square feet; (2) The fire area has an occupant load of 300 or more; (3) The fire area is located on a floor other than a level of exit discharge serving such occupancies.
        

Fire Protection Sprinkler Systems Group A Occupancy IBC Chapter 9

Code conflict detected

TSA sterile area barrier requirement (§1542.201) conflicts with IBC emergency egress path width in Terminal C Gate B12-B18 corridor.

12m

Regulatory change pending

Cook County fire code amendment (Ord. 2026-0341) modifies egress requirements for assembly occupancies. Effective March 15. 2 projects affected.

Compliance verified

IBC 2024 automatic sprinkler requirements confirmed for all Group A occupancy areas in Terminal C.

Voice

Five attributes that define how the product speaks. No exclamation marks. No emoji. Our users make million-dollar decisions.

Precise

Code sections, not "the code." Dates, not "recently." Percentages, not "a lot." Ambiguity costs money in this domain.

Authoritative

We cite sources. We show confidence levels. We distinguish "required" from "recommended." We never guess.

Pragmatic

No academic abstractions. Actions are verbs: "Generate matrix." "Export report." "Track change."

Proactive

We surface what matters before it becomes a crisis. What changed, what it affects, what to do next.

Understated

The product's competence speaks through its precision, not its enthusiasm. We sound like a senior compliance consultant with twenty years of experience handing you the relevant code section, pre-highlighted.

In-app notification

"3 code conflicts detected in Harris County zoning overlay. Review required."

"Uh oh! We found some issues you might want to look at."

Marketing

"Map applicable building codes across 50+ jurisdictions in minutes, not weeks."

"The AI-powered game-changer revolutionizing construction compliance!"

Error state

"Unable to retrieve IBC 2024 §903. Source unavailable. Retry or use cached version (last synced Feb 24)."

"Oops! Something went wrong. Please try again later."

Empty state

"No compliance matrix generated. Start by entering a project address or uploading an RFP."

"It's empty in here! Let's get started by adding your first project."

Accessibility

WCAG AA minimum. Most combinations exceed AAA. Designed for tablet use on construction sites in bright ambient light.

Combination	Colors	Ratio	Grade
Primary text on root	#e6ebf5 on #07091a	15.4:1	AAA
Secondary text on root	#8892b0 on #07091a	7.2:1	AAA
Muted text on root	#586380 on #07091a	4.6:1	AA
Copper accent on root	#d4845e on #07091a	6.8:1	AA / near AAA
Indigo accent on root	#8690f8 on #07091a	7.0:1	AAA
Compliant badge	#6ee7b7 on #04261a	8.3:1	AAA
Violation badge	#fca5a5 on #2d0808	7.6:1	AAA

Touch targets: 56px minimum throughout. Status badge colors tested for bright ambient light (tablet on construction site). Contrast ratios shown for Indigo + Copper dark theme -- other palettes verified separately.