How do I check driven pile logs against the pile schedule and flag tip elevations, criteria and odd driving records with AI?
On a driven pile job the inspector's logs come in as handwritten or scanned sheets, one pile per page, and the questions in the trailer each morning are always the same: which piles are done, which stopped short of or well past the estimated tip, which met the driving criteria at a stroke outside the approved range, and which logs mention an obstruction, a splice or damage that nobody has looked at yet. Have Claude or ChatGPT read each log into rows and have Copilot in Excel or Gemini in Google Sheets compare them with the pile schedule and the criteria you typed from the approved driving plan. Whether a pile is acceptable, needs a restrike or needs testing stays with the geotechnical engineer of record.
Geotechnical Engineer · Geotechnical · Claude · ChatGPT · Microsoft Excel · Microsoft Copilot · Google Sheets
Content updated · Tool links listed below; vendor features and pricing change, so confirm with the vendor
Short answer
Use Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads scanned pile driving logs into rows; Copilot or Gemini matches them to the pile schedule and flags missing logs, tip elevations outside your tolerance, final blows below your typed criteria, strokes outside your range and remarks about obstructions, damage or splices. On a driven pile job the inspector's logs come in as handwritten or scanned sheets, one pile per page, and the questions in the trailer each morning are always the same: which piles are done, which stopped short of or well past the estimated tip, which met the driving criteria at a stroke outside the approved range, and which logs mention an obstruction, a splice or damage that nobody has looked at yet. Have Claude or ChatGPT read each log into rows and have Copilot in Excel or Gemini in Google Sheets compare them with the pile schedule and the criteria you typed from the approved driving plan. Whether a pile is acceptable, needs a restrike or needs testing stays with the geotechnical engineer of record. A person still checks: every flagged pile and every acceptance, restrike or test decision with the geotechnical engineer of record.
AI tie-in
Tool: Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets
Claude or ChatGPT reads scanned pile driving logs into rows; Copilot or Gemini matches them to the pile schedule and flags missing logs, tip elevations outside your tolerance, final blows below your typed criteria, strokes outside your range and remarks about obstructions, damage or splices.
Prompt 1
Read these pile driving logs [upload]. Build a table with one row per pile: pile ID, date, hammer as written, ground elevation, final tip elevation, blows and stroke for the last three intervals, cutoff, pay length, splice noted and remarks copied exactly. Write UNREADABLE instead of guessing. Do not estimate capacity or judge acceptance.
Prompt 2
Here are the headers and a few sample rows of my Schedule and Logs tabs [paste] and the driving criteria I typed from my approved driving plan [paste]. Write Excel formulas (or a step-by-step Copilot plan) that list piles with no log, flag tips above the minimum or outside my tolerance, final blows below my criteria, strokes outside my range and remarks with obstruction, refusal, damage, heave or splice, and summarize installed versus scheduled by cap. Use only my data.
Human check: Every flagged pile and every acceptance, restrike or test decision with the geotechnical engineer of record.
The problem
Check driven pile logs against the pile schedule and flag tip elevations, criteria and odd driving records with AI. This is a common, time-consuming task for a geotechnical engineer.
What this workflow does
On a driven pile job the inspector's logs come in as handwritten or scanned sheets, one pile per page, and the questions in the trailer each morning are always the same: which piles are done, which stopped short of or well past the estimated tip, which met the driving criteria at a stroke outside the approved range, and which logs mention an obstruction, a splice or damage that nobody has looked at yet. Have Claude or ChatGPT read each log into rows and have Copilot in Excel or Gemini in Google Sheets compare them with the pile schedule and the criteria you typed from the approved driving plan. Whether a pile is acceptable, needs a restrike or needs testing stays with the geotechnical engineer of record.
How it works: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
Your checkpoint: The workbook only compares what the logs say with what the schedule and your typed criteria say. It does not estimate capacity, interpret blow counts, set refusal or decide whether a pile is acceptable. Every flag goes to the geotechnical engineer of record, and restrikes, dynamic testing and added piles are their call.
Before you start
- Access to the named tool; confirm license, version and cost with the vendor.
- A small, non-confidential sample to try the workflow on first.
- A qualified person to review the output before it is used.
Tools and access
Follow the steps
- On a Schedule tab, list every pile from the foundation plan: pile ID, cap or bent, pile type, estimated tip elevation, minimum tip elevation if one is specified, cutoff elevation and required order length. On a Criteria tab, type the driving criteria, approved stroke or energy range and tip tolerance from your own approved driving plan and wave equation results. Don't take values from the AI or from memory.
- Scan or photograph each day's pile driving logs. Use an AI account your firm allows for project records.
- Have Claude or ChatGPT read each log into a Logs tab: pile ID, date, hammer as written, ground elevation, final tip elevation, blows per interval for the last few intervals with the stroke recorded, cutoff and pay length, splice noted, and remarks copied exactly. It writes UNREADABLE instead of guessing.
- Have Copilot in Excel or Gemini in Google Sheets match logs to the schedule and flag: piles with no log, tip above the minimum or more than your tolerance from the estimate, final blows below your typed criteria, strokes outside your typed range, and any remark containing words like obstruction, refusal, damage, heave, relaxation or splice.
- Build the morning summary: piles installed against the schedule by cap or bent, open flags oldest first, and the order length used against driven length so the next pile order isn't a guess.
- Send every flagged pile to the geotechnical engineer with the log page, and record their disposition (accept, restrike, test, add pile) back in the log.
Try a small example
Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet.
Sample input
Fill in the bracketed [fields] in the text below with your project data.
Starter prompt
Here are the headers and a few sample rows of my Schedule tab [paste: pile ID, cap, type, estimated tip, minimum tip, cutoff, order length], my Logs tab [paste: pile ID, date, ground elev, final tip elev, last intervals blows and stroke, remarks] and the criteria I typed from my approved driving plan [paste: required final blows, stroke range, tip tolerance]. Write Excel formulas (or a step-by-step Copilot plan) that match logs to the schedule, list piles with no log, flag tips above the minimum or outside my tolerance, final blows below my criteria, strokes outside my range and remarks containing obstruction, refusal, damage, heave or splice, and summarize installed versus scheduled by cap. Use only my data; do not estimate capacity or decide acceptance.
Expected output
Not published yet. Treat any output as a draft and check it against the source documents.
Check the result
- Every value, citation or quantity traces back to a source document.
- Missing information is marked as missing, not filled in.
Limits and recovery
- The workbook only compares what the logs say with what the schedule and your typed criteria say. It does not estimate capacity, interpret blow counts, set refusal or decide whether a pile is acceptable. Every flag goes to the geotechnical engineer of record, and restrikes, dynamic testing and added piles are their call.
- Check your organization’s data policy before sharing project files with third-party tools.
Stop or switch when: The source cannot be verified, permissions are missing, or the result contains unsupported facts.
Frequently asked questions
How does AI help with this?
Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads scanned pile driving logs into rows; Copilot or Gemini matches them to the pile schedule and flags missing logs, tip elevations outside your tolerance, final blows below your typed criteria, strokes outside your range and remarks about obstructions, damage or splices. A person still checks: Every flagged pile and every acceptance, restrike or test decision with the geotechnical engineer of record.
How do I how do I check driven pile logs against the pile schedule and flag tip elevations, criteria and odd driving records with AI??
On a Schedule tab, list every pile from the foundation plan: pile ID, cap or bent, pile type, estimated tip elevation, minimum tip elevation if one is specified, cutoff elevation and required order length. On a Criteria tab, type the driving criteria, approved stroke or energy range and tip tolerance from your own approved driving plan and wave equation results. Don't take values from the AI or from memory. Scan or photograph each day's pile driving logs. Use an AI account your firm allows for project records. Have Claude or ChatGPT read each log into a Logs tab: pile ID, date, hammer as written, ground elevation, final tip elevation, blows per interval for the last few intervals with the stroke recorded, cutoff and pay length, splice noted, and remarks copied exactly. It writes UNREADABLE instead of guessing. The full step list is above.
Does this use an AI agent or regular software?
It is labeled AI assists: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
What tools do I need?
Claude, ChatGPT, Microsoft Excel, Microsoft Copilot, Google Sheets. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first.
Has this workflow been tested?
Workflow guide · not independently tested. Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.
Evidence and maintenance
Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.