Diggy Geotechnical Toolkit – Free Access to 9 Calculators

Diggy Geotechnical Toolkit – Free Access to 9 Calculators

Diggy Geotechnical Toolkit is a free, browser-based suite of nine geotechnical calculators that run locally in your browser to consolidate AGS, SPT and core recovery workflows. It accelerates geotechnical calculations to improve accuracy and save time—claiming roughly 6 hours saved per project—and is available now for $149 value but free to use.

What is Diggy Geotechnical Toolkit – Free Access to 9 Calculators?

Diggy is a practical collection of execution tools: calculators, a VS Code extension, and lightweight workflows that replace ad hoc spreadsheets and PDFs. It includes AGS processors, SPT correction tools, core recovery and fracture frequency calculators, file reducers and an editor extension—templates, checks and UI features built for on-device, offline use.

Why Diggy Geotechnical Toolkit – Free Access to 9 Calculators matters for Geotechnical engineers performing AGS, SPT, and core recovery tasks seeking faster, more accurate calculations.,Site technicians and drillers who need reliable offline tools to process data on the go.,QA/QC leads and project managers who require standardized workflows and rapid validation of site data.

Operational workflows are inefficient when calculations are scattered; Diggy centralises repetitive tasks so teams produce consistent, auditable outputs fast.

• Reduce manual transfer errors that slow field teams and QA/QC leads; aligns with the primary outcome of accelerating calculations.
• Supports Product Managers and Project Managers by standardising deliverables and integrating into existing playbook marketplaces.
• Requires intermediate effort—2–3 hours setup—and skills in data analysis and workflow optimisation to onboard properly.
• Enables site technicians and drillers to work offline without exposing project data, improving turnaround and traceability.
• Fits curated playbook expectations: small, repeatable systems that scale across projects and teams.

Core execution frameworks inside Diggy Geotechnical Toolkit – Free Access to 9 Calculators

AGS File Intake and Validation

What it is: A standard intake flow to import AGS files, run quick validations and produce a summary that highlights missing fields and group mismatches.

When to use: At project start and after every file transfer from contractors or labs.

How to apply: Upload AGS, review the summary, apply AGS Reducer to strip irrelevant groups, then export a validated subset for analysis.

Why it works: It enforces a repeatable gate before downstream calculations, reducing rework and manual column checks.

SPT Correction Chain

What it is: A sequential framework for overburden and energy corrections leading to a standardised N-value and φ estimate.

When to use: When raw SPT records arrive from field logs and before geotechnical interpretation.

How to apply: Run overburden correction, then energy correction, then N-value calculator; save presets for typical rigs.

Why it works: Chaining corrections reduces operator error and produces consistent inputs for design calculations.

Core Recovery and Fracture Frequency Routine

What it is: A compact workflow for logging core recovery, calculating RQD-like metrics and fracture frequency from field notes.

When to use: During sample processing, lab handover and final reporting.

How to apply: Enter core lengths, mark recovered intervals, run recovery and fracture frequency calculators, archive results to project folder.

Why it works: It ensures lab and site numbers align and produces defensible metrics for reports and tender responses.

Pattern-copying for AGS workflows (VS Code supported)

What it is: A template-and-pattern approach leveraging the AGS VS Code extension for consistent file structure, syntax highlighting and repeatable edits.

When to use: When teams handle multiple AGS files or onboard new data sources frequently.

How to apply: Apply the VS Code extension to enforce column schemas, use hover tooltips and table view to copy established file patterns to new projects.

Why it works: Copying verified patterns reduces onboarding friction, removes column-counting errors and scales proven file structure across projects.

Local-first Data Governance

What it is: A governance pattern that keeps all calculations and sensitive data on-device while enabling optional saved favourites for convenience.

When to use: For projects with privacy concerns or limited connectivity in the field.

How to apply: Use the browser-hosted tools offline, store templates locally, require explicit export for any sharing.

Why it works: Minimises data exposure risk and preserves auditable chains of custody for sample and site data.

Implementation roadmap

Start small, validate outputs, then expand tool use across teams. The baseline setup takes 2–3 hours for a single user and requires intermediate data and project management skills.

Follow this step sequence to operationalise across a project.

1. Project kickoff
   Inputs: sample list, AGS files, SPT logs
   Actions: nominate an owner and run initial AGS Summary
   Outputs: validated file list and priority fixes
2. Local install and permissions
   Inputs: browsers on field devices
   Actions: confirm offline availability and local storage settings
   Outputs: devices ready for on-site use
3. Baseline validation
   Inputs: one representative AGS file and one SPT log
   Actions: run reducer, corrections and compare against expected values
   Outputs: acceptance checklist completed
4. Preset creation
   Inputs: common rig and lab parameters
   Actions: save correction presets and templates in the extension
   Outputs: reusable project presets
5. Rule-of-thumb QA
   Inputs: processed dataset
   Actions: sample-check 5% of rows or a minimum of 20 rows
   Outputs: QA pass/fail and notes
6. Decision heuristic
   Inputs: error rate, sample count
   Actions: apply heuristic: if (errors ÷ total_samples) > 0.03 then escalate to QA lead
   Outputs: triage decision
7. Team roll-out
   Inputs: onboarding doc, 1-hour workshop
   Actions: train site technicians and engineers on workflows
   Outputs: users able to run core calculators
8. Project cadence
   Inputs: weekly data drops
   Actions: integrate a weekly gate to re-run summaries and corrections
   Outputs: stable, auditable dataset
9. Integration and archive
   Inputs: final validated dataset
   Actions: export standardised reports and archive raw AGS with notes
   Outputs: project archive and lessons log

Common execution mistakes

These are real operator failures that slow projects; each has a clear fix to keep the system lightweight and reliable.

• Mistake: Skipping AGS validation and editing files manually.
  Fix: Always run AGS Summary first and use AGS Reducer to create a trimmed canonical file before edits.
• Mistake: Applying corrections without documenting presets.
  Fix: Save correction presets per rig and include them in project notes to maintain reproducibility.
• Mistake: Centralising sensitive data into cloud services by default.
  Fix: Use local-first mode and require explicit export for shared files.
• Mistake: Relying on a single user’s memory for workflow steps.
  Fix: Create a short checklist and include it in onboarding to reduce single-point failures.
• Mistake: Treating the toolkit as a one-off tool rather than an OS-level pattern.
  Fix: Embed calculators into weekly cadences and PM systems so they’re part of normal delivery.
• Mistake: Not sampling outputs for QA, trusting bulk outputs blindly.
  Fix: Use the rule-of-thumb sampling (5% or 20 rows) on each export for spot checks.

Who this is built for

Positioned for teams that manage ground investigation data and need consistent, offline-capable calculations across field, lab and project management roles.

• "Product Managers at scale who want standardised calculation workflows."
• "Geotechnical Engineers in design who want faster, auditable inputs."
• "Project Managers running site packages who want consistent deliverables."
• "Site technicians and drillers in the field who want reliable offline tools."
• "QA/QC leads who want reproducible checks and simplified validation."
• "Lab technicians processing samples who want fewer manual transcriptions."

How to operationalize this system

Turn the toolkit into a living operating system by integrating it with existing tooling, cadences and version controls.

• Dashboards: Export standardised summaries to your project dashboard for visibility on validation status.
• PM systems: Attach validation artifacts and presets to tickets in your PM tool for traceability.
• Onboarding: Create a 1-hour runbook session and a one-page checklist for new users.
• Cadences: Add a weekly data-gate where team runs AGS summary and SPT chains before reporting.
• Automation: Use local scripts or the VS Code extension to apply presets to batches of AGS files.
• Version control: Store template presets and example AGS files in a repo; version changes to presets and workflows.
• Escalation: Define a simple threshold heuristic for when QA leads must review processed outputs.
• Retention: Archive validated exports alongside raw AGS to preserve the audit trail for future reviews.

Internal context and ecosystem

This playbook was created by Diggy and sits in a curated library of Product playbooks for field and lab workflows. The toolkit complements internal standards by providing execution-level tools and integration patterns rather than prescriptive policy.

Reference the live playbook and downloads at https://playbooks.rohansingh.io/playbook/diggy-geotech-toolkit-free-access for templates, and treat the tools as components you can copy into your project OS.

Frequently Asked Questions

What is the Diggy Geotechnical Toolkit and what does it include?

It is a free, local-first browser toolkit containing nine calculators and a VS Code extension for AGS handling, SPT corrections, core recovery and fracture frequency. The package includes processors, presets, and an editor to standardise file structure and speed routine geotechnical computations without sending project data off device.

How do I implement the Diggy Geotechnical Toolkit in a live project?

Start by running an AGS Summary on a representative file, save correction presets, and validate outputs using the 5% sampling rule. Train one operator (2–3 hours) to run the intake, then add the workflow to weekly cadences and attach exports to your PM tickets for traceability.

Is Diggy ready-made or does it require heavy configuration?

It’s ready to use out of the box with sensible defaults and presets, but benefits from light configuration: saving rig-specific correction presets and a short onboarding session. This balances plug-and-play accessibility with the ability to tailor outputs to your project standards.

How is Diggy different from generic calculation templates?

Diggy focuses on domain-specific execution: AGS-aware processing, SPT correction chains and a VS Code pattern-copying extension. Unlike generic templates, it enforces file schemas, preserves local data privacy, and standardises repeatable workflows rather than offering one-off spreadsheet cells.

Who should own the toolkit inside a company?

Ownership usually sits with a QA/QC lead or a geotechnical team lead who defines presets and validation checks. Product or project managers can govern rollout and cadences, while site technicians and lab staff operate the tools under that ownership model.

How do I measure results after adopting Diggy?

Measure time saved per project, reduction in transcription or calculation errors, and the number of validated datasets delivered on schedule. Track these through your PM tool and a weekly dashboard; initial targets can be set as minutes saved per routine task and a decline in QA escalations.

Can I use Diggy offline and keep sensitive project data local?

Yes. All calculations run in the browser and can operate offline, so project data remains on the device. Exports and saved favourites require explicit actions, preserving local-first governance and reducing the need for cloud transfers.

Can I request new calculators or add custom workflows?

Yes. The toolkit accepts feedback and prioritises calculators used routinely by site professionals. In the meantime you can adapt presets and pattern templates in the VS Code extension to create reproducible local workflows that match your team’s needs.