40 Free AI Prompts for Oil and Gas Leaders: The Field Library

How to Use This Field Prompt Library

These forty oil and gas leadership AI prompts are organized by the jobs a shift leader actually does: walk the daily loop, build the talk, hold the handover, correct without burning trust, lead contractors, learn from incidents, manage fatigue, and scale the whole system across a turnaround. Every prompt assigns the AI a role, injects your context through [BRACKETED PLACEHOLDERS], and demands an artifact, a script, a log, a one-page plan, rather than a summary you would have to rewrite anyway.

Two disciplines make the library work. The confidentiality rule: every prompt runs on roles and conditions instead of names, so nothing you would not write in an open log goes into a consumer tool. The rehearsal rule: prompts that draft your opening are half the job, and the role-play prompts that push back in character are where the preparation hardens, run the coach prompts against a real observation this week, not a hypothetical one.

The Daily Loop, Prompts 1 to 8

The loop prompts install the daily engine: presence with a route, a rhythm, and a log instead of a poster. The Walk Designer turns your site geography and shift pattern into a two-week rotating route with a theme question per day; the Say-It-Kindly Coach role-plays the naming conversation and scores your specificity, kindness, and handover; the Barrier Removal Tracker builds the one-tab log with the seven-day overdue flag that catches the loop's most common death. The remaining prompts handle adoption, the announcement, the failure diagnostic, the night-shift walk plan, and the daily crew question.

• Daily Loop Walk Designer, route, rhythm, and theme question from your site map and shift pattern
• Say-It-Kindly Coach, role-plays the naming conversation, then rewrites your best attempt
• Barrier Removal Tracker, one-tab log with owners, dates, and the overdue flag
• Loop Adoption Announcement, 150 words for the next huddle, no corporate tone
• Loop Failure Diagnostic, which beat collapsed first and the targeted fix
• Night-Shift Walk Plan, the same loop adapted to fatigue and lighting realities

Toolbox Talks and Handovers, Prompts 9 to 18

The talk prompts compress preparation from hours to minutes without making the talks generic: the Talk Builder turns tomorrow's job package into a Hook-Hazard-Habit-Heart-check script using today's real hazard, the Story Finder converts a site event into a sixty-second blame-free story, and the Hook Practice Room gives you ten first sentences and tells you which two survive a crew that has heard everything. For the framework behind these, our toolbox talk guide walks the four beats in full.

The handover prompts attack the seam where supervision is thinnest. The Handover Log Builder creates your four-section one-pager, Status, Risks, Pending, People, with structured prompts per section; the Shift Note Compressor turns twelve messy hours into five clean lines and flags anything missing an owner or a time; the Quality Audit scores last week's logs and names the single edit that improves each one most. The shift handover protocol guide pairs with these and explains why the read-back is non-negotiable.

• Talk Builder, full Hook-Hazard-Habit-Heart script from the real job package
• Story Finder, a site event converted into a sixty-second blame-free story
• Hook Practice Room, ten first sentences, ranked for a skeptical crew
• Handover Log Builder, the four-section one-pager with five prompts per section
• Shift Note Compressor, twelve hours compressed to five lines, gaps flagged
• Handover Quality Audit, last week's logs scored 1-5 with the highest-leverage edit

Accountability, Contractors, and Learning, Prompts 19 to 28

The accountability prompts rehearse the ninety-second conversation before it matters: the planner builds your observe-ask-agree-follow script for both the first lapse and the repeat, the coach role-plays a defensive crew member so your calm gets tested before the crew tests it, and the Expectation Reset Memo drafts the toolbox talk version that owns your part of the drift honestly. Rehearsal is what keeps correction from becoming confrontation, which is why these prompts come before the contractor set.

The contractor prompts run the lifecycle: the Charter Builder produces the one-pager with the two-way escalation path, the Day-One Induction Walk script makes mobilization count, the Standards Gap Conversation rehearses correcting through the contractor's supervision instead of around it, and the Closeout Learning Memo captures what most sites delete at demobilization. The learning prompts complete the set: the Debrief Agenda Builder with the two banned questions printed at the door, the Five-Why Facilitator that reframes every why that tempts a name, and the Report-Back Composer that turns one closed report into the reason the next five get reported.

Fatigue, Turnarounds, and the Capstone, Prompts 29 to 40

The fatigue prompts bring structure to a conversation most leaders wing: the Rota Reality Check audits actual hours, callouts, swap chains, eaten recovery days, against the roster the spreadsheet claims exists; the Fatigue Risk Conversation rehearses the dignity-intact approach; the Critical Decision Protocol compresses the rules that keep the 03:00 decision as good as the 09:00 one onto a pocket card. None of these diagnose anyone; all of them price the risk before the incident prices it for you.

The turnaround prompts scale the system: the Task Packager structures scope sheets into verifiable task lists, the What-If Analyst stress-tests the schedule for the physical and crew conflicts no Gantt chart shows, and the Standup Summarizer compresses twelve shift reports into the five-line morning picture, with the contradiction line that catches handover failures on day two. The capstone prompts close the library: the Plan Assembler, the Objection Pre-Answerer that attacks your plan before the room does, and the 90-Day Commitment Card that turns the work into three practices, two metrics, and one date.

The Library Map: Which Prompt for Which Job

When time is short, route by job rather than by number. The map below shows where each prompt family sits, what you feed it, and what you get back, and it doubles as the table of contents for the fifteen-day program that houses the full vault.

Why the Manager Numbers Should Shape Your Prompt Habit

Prompt libraries are cheap to collect and easy to abandon, so it helps to be clear about what the practice is actually for. Gallup's manager research attributes roughly 70% of the variance in team engagement to the manager, reports that about half of employees have left a job to get away from one, and finds that 52% of exiting employees say their manager or organization could have done something to prevent the exit. On a plant or rig, every one of those percentages is a recruiting bill and a competency gap you did not plan for.

The prompts attack the mechanism behind those numbers, not the mood. A designed loop makes presence checkable; a rehearsed naming conversation makes standards enforceable without drama; a held handover makes the night shift inherit decisions instead of surprises. Run the library as a rhythm and the manager effect starts working for your crew instead of against it, which is the entire point of installing structure before inspiration.

What Engagement Returns to a Site

Engagement earns its place on an operations dashboard when you read it as a leading indicator rather than a mood survey. Gallup's Q12 meta-analysis across more than 112,000 business units finds top-quartile engagement teams deliver 64% fewer safety incidents, 81% lower absenteeism, and 23% higher profitability than bottom-quartile teams. Those three numbers are the business case for the daily loop, the talk framework, and the handover protocol, they are the mechanisms engagement is made of.

Use the numbers honestly, though. The meta-analysis shows association at the business-unit level, not a guarantee per site, and the figure you should actually watch is your own: near-miss reporting rate, handover exceptions, loop log completion. The prompts exist to move your local numbers; the published research exists to tell you it is worth trying. Our oil and gas safety statistics roundup collects the industry-level figures with their caveats.

Adapting the Library to Your Site

Adaptation is encouraged; dilution is not. When you edit a prompt, keep the three ingredients that make it work, the role, the placeholder-forced context, and the required artifact, and change only the domain specifics. If a prompt produces mush, the cause is almost always a thin input line: add the constraint you are most worried about, the history the model cannot know, and the personality it will meet. One honest sentence of context is worth more than any template.

Version control matters too. Keep a shared notes page with the prompts your team actually uses, named by job rather than by date, and delete what stopped producing, forty living prompts beat a graveyard of two hundred. Review the library quarterly with your supervisor team, and let the artifacts argue: if a prompt has not produced a usable output in a month, it is decoration, and decoration is how libraries die.

Your 30-60-90 Rollout Plan

The library compounds only if it meets a rhythm, so plan the rollout the way you would plan any operating change: small, scheduled, and verified. The calendar below is the one we teach in the Oil & Gas Operations Leadership program, and it assumes ten minutes a day, not a two-hour retreat. For workshop delivery, field leadership case studies books and coaching toolkits, the store versions of these prompts and frameworks run offline with printed cards.

Ninety days in, the test is simple: is the loop log alive, are the talks scripted and verified, and did the rehearsal prompts change what happens in real conversations? If yes, the library has become an operating system. If no, shrink it, three prompts run daily beat forty prompts admired, and rebuild the rhythm before adding anything back.

Frequently asked questions