Truth Computing

The pre-submittal layer

Catch the red lines before the city does.

We automate the pre-submittal plan-check process to eliminate plan-review correction loops — checking building designs for code compliance before they go to the jurisdiction, and telling designers exactly how to fix each issue.

Flagship In development

PreCheck

Pre-Submittal Compliance Engine · V1 vertical: ADA

“We don’t find out what’s wrong until the city red-lines us — weeks later.”

Upload your construction documents (PDF, drawings, or BIM). The engine checks the design against the codes for that specific jurisdiction and returns a pre-submittal corrections list. Unlike a city plan checker — who tells you only what is wrong — it is built to tell you how to fix each issue before you ever submit.

For: architects and designers, and the developer PM offices who carry the cost of every cycle.

  • IBC
  • CBC
  • CRC
  • Title 24
  • ADA
  • CALGreen

How it works

  1. Upload
    Drop in your CDs — PDF, drawings, or BIM.
  2. Check
    We run the design against the codes for that jurisdiction.
  3. Fix-it list
    Get a corrections list with how to resolve each issue — before you submit.

The suite

A deliberately sequenced set of tools, all sitting in the pre-submittal layer. Each is designed to remove one reason a project gets stuck in plan check.

CodeBase

Inland Empire Jurisdiction Code Library
On the roadmap

“The code library everyone uses has no real Inland Empire coverage, so we hire consultants.”

Deep, maintained code pages for Riverside, San Bernardino, Fontana, Ontario, Eastvale, Chino, and Tracy — including the local amendments and infrastructure-sequencing rules generic libraries don’t document.

For anyone doing code research for IE projects.

RedLine IQ

Correction Intelligence · the data moat
On the roadmap

“Cities enforce changes that aren’t published anywhere until you get dinged for them.”

Every correction your team uploads is designed to train the engine and surface unwritten or newly-enforced code changes — so the next project doesn’t lose a cycle to the same surprise. This is how the platform is built to compound and stay current.

For repeat submitters who feel the same rejections twice.

FastLane

Completeness & Express/OTC Qualifier
Exploratory

“We never know if we’ll land in the fast pile or the slow pile.”

Checks submittal completeness against the jurisdiction’s requirements and is designed to tell you whether the package qualifies for Express or over-the-counter (OTC) review — and exactly what’s missing if it doesn’t.

For developers and expediters optimizing time-to-approval.

AHJ Map

Multi-Jurisdiction Coordinator
Exploratory

“One project touches the building department, the fire marshal, and environmental health — and nobody reconciles them.”

Aggregates and reconciles requirements across every Authority Having Jurisdiction on a project into one view, so conflicting or overlapping requirements are designed to surface before submission.

For complex, multi-AHJ projects.

CarryClock

Carrying-Cost ROI
On the roadmap

“Every week stuck in plan check is full carrying cost for nothing.”

Translates correction rounds avoided into days and dollars saved against the project’s daily carrying cost, so the value is legible to whoever signs the check.

For the economic buyer — corporate PM and finance.

One layer, sequenced on purpose: PreCheck finds the issues, CodeBase grounds them in local code, and RedLine IQ makes the whole system smarter every time a correction comes back.

Where we fit in your workflow

  1. Stage 1 Design
  2. Stage 2 Code Research
  3. Stage 3 Compliance Check ← This is us
  4. Stage 4 Permit Submission
  5. Stage 5 Tracking

We own Stage 3. We sit upstream of the tools that submit and track permits — and complement the code-reference libraries used in research — by feeding clean, corrected designs into the rest of your stack rather than competing with it.

15–18 days
per residential plan-check cycle — and multiple cycles commonly stretch to 4–6 months.
~29%
of manual plan checks contain errors or inconsistencies.
$10K–$50K/day
carrying costs while a mid-sized IE development sits idle.

Figures from industry research, cited where applicable. Not a guarantee of results.

We’re building this with our first design partners.

If you carry the cost of every plan-check cycle — as a developer PM office, architect, or expediter — we want to build PreCheck around your real submittals.

Become a design partner Or reach us directly at singularityintelligence4@gmail.com