The code.
The context.
The reasoning.
Building-code research and analysis, connected to the project you are actually designing.
Ask a focused code question. Develop a code-information sheet from your project inputs. Keep the references and the basis of the answer in view.
Book a code-analysis walkthrough
A requirement needs
a place in the project.
LinkWave distinguishes the project information you supply from the code material used in the analysis. Start with the premises, then inspect the requirement.
- Project
- Address, use, occupancy group, and construction type
- Building
- Floors, area, and sprinkler status
- Spaces
- Functions and areas used in the occupant-load breakdown
- Sources
- Code references, authority layers, and available local context
Research a question.
Develop the analysis.
Code research
Use the code-lookup workflow to investigate a specific requirement within the selected scope. Read the answer with its references and the available jurisdiction context.
Keep the question precise: identify the building condition, use, and requirement you are investigating. Source coverage and local amendments matter; a model-code answer is not automatically the local rule.
Code-information sheet
Enter the project premises and generate a structured sheet. Review the criteria, required or allowed values, and code references together. Inspect the occupant-load breakdown rather than relying only on a total.
Correct a premise and regenerate the sheet when the project changes. Continue the conversation around the analysis, then export the sheet for further review.
Read across the row.
Not just down the numbers.
A code-information sheet is useful when its conclusions can be investigated. These are the kinds of information the LinkWave sheet keeps together—not a sample project result.
| Information | What it tells you | What to review |
|---|---|---|
| Criterion | The topic being evaluated | Does it describe the condition in this project? |
| Required / allowed | The reported requirement or calculated result | Which project inputs and code conditions support it? |
| Code reference | The cited provision and its authority layer | Open the source and read the conditions and exceptions. |
| Status & note | Whether the value was confirmed and what remains unresolved | Do not turn an unconfirmed entry into a determination. |
| Local context | Available amendment notes and local references | Confirm the applicable local requirements for the project. |
| Field | Example value | Reviewer question |
|---|---|---|
| Premise | Group R-2 over podium, sprinklered | Where is the sprinkler scope established? |
| Criterion | Allowable building height and number of stories | Which construction type and sprinkler condition apply? |
| Reference | 2024 IBC Tables 504.3 and 504.4 — example basis | Has the jurisdiction adopted this edition or amended these tables? |
| Status | Dependent on confirmation | What drawing or specification must resolve it? |
This format prevents a code answer from becoming a loose claim. The row carries the premise, source, status, and next action together. Inspect the example ICC source.
When a premise changes,
revisit the consequence.
A different occupancy, a revised area schedule, or a changed sprinkler assumption can affect the analysis. LinkWave keeps the project inputs editable so the sheet can be regenerated from the revised basis.
Export the analysis with its references, status, and notes. Review the output with the responsible design professionals before using it in a submittal.
From requirements
to drawing evidence.
Code Analysis helps establish the requirement. Design Compliance examines information in a PDF drawing set. Use each workflow for its own task, with professional review between the software output and the design decision.
Explore Design ComplianceRead the code-analysis guide