How we work
Planned. Precise. Documented.
A blast you can sleep on the night before isn't luck — it's a sequence. The same five steps, in the same order, on every job: assess, recommend, plan, coordinate, execute. Built to reduce surprises and to document the work.
FIVE STEPS, SAME ORDER.
Each step exists to answer a question before it becomes a problem: Is this feasible? What method? What's the plan? Who needs to know? What happened?
01
Site assessment
On-site evaluation of rock, depth, access, and proximity to structures, wells, and utilities. An honest read on feasibility — including when blasting isn't the answer.
02
Method recommendation
Controlled blasting, mechanical removal, or a hybrid — compared against volume, restrictions, schedule, and authority requirements before anything is recommended.
03
Engineered plan
Charge design, drill pattern, sequencing, burden, stemming, and delay intervals matched to the site.
04
Coordination
Permit path, abutter notifications, utility locates, and fire-department communication according to local and project requirements. Requirements vary; the path is identified during review.
05
Execution & documentation
Controlled execution with seismograph monitoring where required or appropriate, post-blast inspection, and the project records handed over.
WHAT THE PROJECT FILE MAY INCLUDE.
Scope and jurisdiction set the exact list — documentation is the standard on every job, because records protect everyone involved.
Engineered plan
Site-specific assumptions, method, constraints, sequencing, and controls.
Pre-blast survey
Existing visible conditions at nearby structures, documented before blasting begins — where required.
Monitoring records
Seismograph vibration and airblast documentation where required or appropriate.
Completion records
Shot logs, post-blast inspection notes, and clearance documentation as applicable.
WHAT CAN CHANGE THE TIMING — NAMED UP FRONT.
A schedule built on named assumptions beats one built on optimism.
Approvals
Permit requirements and timelines vary by state, municipality, fire department, utility owner, and project type — confirmed per project, not assumed.
The rock itself
Bedrock depth, fractures, and groundwater don't always match the surface. The plan names its assumptions.
Site conditions
Weather, access, and the rhythm of an active site can shift the sequence. Decision points agreed in advance.
FAQ
Process questions. Answered.
Straight answers on timing, documents, schedule changes, and when blasting isn't the right call.
How long does the whole process take?
It depends on the site, the method, and approvals. The review names the sequence. It does not promise a clock.
What can change the schedule?
Approvals, the rock itself, and site conditions. Those variables are named up front so changes are decisions, not surprises.
What documents will I actually receive?
Scope and jurisdiction set the list. The file may include the engineered plan, a pre-blast survey, monitoring records, and completion records as applicable.
What if blasting isn't the right call for my site?
The review can come back as a shot, a ram, a mix, or a request for more information. Asking does not lock the method.
Ready for a site read?
See this process applied to your site.
Step one is a no-obligation site review. A blaster reads the site and responds with a method fit or more information.
Requesting a review does not commit the project to a particular removal method.