For Engineers

Technical support for
engineers specifying repair
and stabilization systems

Get the technical information, documentation, and project support needed to evaluate failure conditions, compare repair methods, and specify the right system with more confidence.

Specification support

Technical documentation

Project-specific guidance

The problem

Why repair decisions
get challenged

Engineers are often expected to diagnose the condition, justify the repair method, and document the recommendation at the same time. When those elements are weak, the result can be delay, redesign, rejected submittals, or a repair method that does not hold up in the field.

Diagnosis Before Method™

The difference between a repair that lasts and one that fails. 

Identify what's actually failing below the surface before selecting a repair method.
These four steps are how that decision gets made. 

Diagnosis

01

Identify the visible symptom

The crack, settlement, water entry, or movement you can actually see.

02

Understand what changed below

The water, soil, void, or loss of bearing driving it beneath the surface.

Then select the method

03

Match the method to what failed below

Choose the repair that addresses the cause, not just the visible symptom.

04

Confirm the correction holds

Verify the repair is backed by conditions stable enough to last.

From uncertainty to logic

Move from visible
conditions to method
logic more quickly

Most projects begin with a visible condition, a report, or a field observation that still needs interpretation. This page helps engineers move from that uncertainty toward a more disciplined evaluation.

Stronger technical backing

Support the
recommendation
with stronger
technical backing

Alchatek helps engineers evaluate likely mechanisms, compare system options, review technical resources, and strengthen recommendations before they move into specification, review, or construction.

Where to go next

Find the resources
that match the
engineering question

Use problem pages when the main question is still what is happening.


Use Engineering Resources and its Downloads page for specifications, details, drawings, data, certificates, and case studies.

Use solution pages when the main question is which method family fits.


Use Technical Services when the project has unusual constraints, higher consequence, active water, sequencing concerns, or a recommendation that needs deeper review.

Condition to specification

A disciplined process for moving
from condition to specification

  1. Identify the likely failure mechanism 
behind the visible condition.

  2. Narrow the repair method to the most appropriate solution family.

  3. Review the supporting documents, details, and performance considerations.

  4. Bring in project-specific support when design constraints, sequencing, approvals, unusual exposures, or site conditions require deeper input.

Diagram of the engineer path: diagnosis to solution family, documentation (specs, drawings, QA/QC) and technical support

Need a defensible recommendation
before the project moves further?

When the method is not yet clear, site constraints are unusual, or the documentation burden is heavy,
bring in Technical Services before the recommendation moves deeper into design, review, or construction.

Frequently Asked Questions

Yes. Alchatek can help engineers evaluate the failure condition, compare repair directions, and determine which system is most defensible for the project constraints and performance objective.

Yes. Engineers should be able to request editable specification content so the right version, supporting files, and revision status stay aligned.

Yes. Engineering Resources should support CSI-style specifications, details, drawings, data, and other files used in design, review, and coordination.

Yes. Soil information, field observations, and project constraints can be translated into better method selection and planning guidance.

Yes. Conceptual support can help engineers think through treatment zones, sequencing, and method logic before a project moves deeper into design or review.

Yes. The support structure should accommodate both, depending on project requirements and the role the system is expected to play.

Yes. Engineers should be able to access or request documentation that supports submittal review, QA/QC expectations, and technical decision quality.

That is the point where Technical Services should be involved. Unusual constraints usually need deeper review before the recommendation is carried further.

Start with the relevant problem page or the Knowledge Center first, then move into solution pages, Engineering Resources, or Technical Services as the recommendation becomes clearer.

Proof & Verification

Named Project

CVS Pharmacy Soil Stabilization

Muck under a new Orlando CVS Pharmacy threatened the parking lot until AP Lift 475 replaced costly excavation and passed every stability test.

Case Study

Credential or Proof Point

Our contractor called Alchatek. Alchatek scoped the fix.

Diagnose the condition, compare the method, and specify with stronger technical backing,
with project-specific review when the stakes are high.