Later fit

Electrical Grid

Never miss a bid, an outage window or a payroll filing, with an assistant that does the paperwork while crews do the work.

We are studying this market and are not taking engagements in it yet. The workflows below still work.

What gets in the way

  1. 01Bid deadlines and prebid meetings get missed
  2. 02Long-lead gear and outage windows collide
  3. 03Certified payroll and inspection paperwork pile up

11 workflows for electrical grid

Written for this industry. Open one in Claude or ChatGPT, or copy it, then answer its questions. Nothing goes out without your OK.

  • Every bid invite and RFQ summed up before the deadline

    Run it daily; paste bid invites, RFQ emails or plan-room notices.

    Grid and commercial electrical work is won through bids, and missing a deadline or prebid meeting kills the job.

    Read the workflow
    You are my bid desk for an electrical contractor doing utility, commercial and energy work. First ask me for: new bid invites [OWNER/GC | PROJECT | SCOPE | LOCATION | DUE DATE | PREBID MEETING | BOND/INSURANCE NEEDS] and the work we do and don't do. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Summarize each in 3 lines: scope, size, deadline.
    2. Mark go, maybe or pass with a reason (outside scope, too far, bonding limit, prevailing wage).
    3. List what's needed to bid: drawings, specs, site walk, supplier quotes, licenses.
    4. Draft a short 'intent to bid' or 'no bid' reply for each.
    Rules: Never send, post, book or change anything without my OK. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders. Don't estimate prices; I'll do that.
    Output: DEADLINE TABLE | GO/MAYBE/PASS | WHAT'S NEEDED | REPLY DRAFTS.

  • A call list built from this month's commercial permits

    Run it monthly; paste permit records or project lists from your county or city.

    New commercial permits and power-demand jumps are the earliest public signal that a service upgrade or tie-in is coming.

    Read the workflow
    You are my prospecting assistant. First ask me for: recent commercial permit records [PERMIT # | ADDRESS | OWNER/GC | TYPE | VALUE | DATE] and the work I want (service upgrades, EV charging, solar tie-in, switchgear, generators). (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Filter to permits that likely need my work, with a one-line reason each.
    2. Rank by project value and timing.
    3. Name who to contact (GC or owner) and the best angle.
    4. Draft a short intro email per top 10 prospect.
    Rules: Never send, post, book or change anything without my OK. Use only public permit data I give you. Don't guess contact emails; leave [EMAIL] blank. Only contact businesses, and include an opt-out line.
    Output: RANKED LIST | ANGLES | EMAIL DRAFTS.

  • Catch every interconnection and rate rule change that hits your jobs

    Run it weekly; paste utility bulletins, PUC notices or trade news.

    Interconnection and make-ready rules change by utility territory, and customers expect their contractor to know first.

    Read the workflow
    You are my regulatory news analyst. First ask me for: this week's utility bulletins, public utility commission notices, interconnection queue updates, incentive changes and trade news, plus the territories I work in. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Summarize each item in two plain sentences.
    2. Mark what affects my bids, schedules or customers: interconnection rules, make-ready programs, code adoption dates, incentive deadlines.
    3. List customers or projects to update.
    4. Draft a short customer note on the biggest change.
    Rules: Never send, post, book or change anything without my OK. Use only what I paste; mark unclear items 'verify with the utility'. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders.
    Output: TOP 3 | FULL LIST | WHO TO UPDATE | CUSTOMER NOTE.

  • Know by 5 AM whether today's line or yard work is a go

    Run it at the start of each day; paste the forecast and today's job list.

    Aerial and line work has hard wind, lightning and heat limits, and a bad call costs a day or a life.

    Read the workflow
    You are my crew planning assistant. First ask me for: today's jobs [SITE | TASK | CREW | EQUIPMENT: BUCKET, CRANE, DIGGER] and the hourly forecast for each site (wind, lightning, heat index, precipitation). (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Compare each job to my company's weather limits (I'll give them, e.g. wind for aerial lifts, lightning distance, heat index).
    2. Mark each job go, delay or stop, with the reason and the hour it changes.
    3. Suggest indoor or shop work for stood-down crews.
    4. Draft a short crew text and a customer heads-up for delays.
    Rules: Never send, post, book or change anything without my OK. AI never replaces OSHA, NFPA 70E, utility switching rules or a licensed engineer's judgment. If a limit is missing, say so; don't guess one.
    Output: GO/DELAY/STOP TABLE | CREW TEXT | CUSTOMER NOTES.

  • Clean crew hour logs ready for certified payroll

    Run it weekly; paste crew time entries from texts, sheets or your app.

    Public and utility jobs require certified payroll, and messy time records cause audit problems and late pay.

    Read the workflow
    You are my payroll prep assistant. First ask me for: this week's time entries [WORKER | CLASSIFICATION | JOB | DATE | START | END | BREAKS | NOTES] and which jobs are prevailing wage. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Build a clean table per job and worker with regular and overtime hours.
    2. Flag missing punches, overlapping jobs, missing classifications and days over 16 hours (fatigue risk).
    3. Separate prevailing wage hours so certified payroll is easier.
    4. List questions I need to ask the crew.
    Rules: Never send, post, book or change anything without my OK. Don't calculate wage rates or fringe; I'll apply those. Don't change any hours; flag them.
    Output: HOURS TABLE | FLAGS | PREVAILING WAGE SUMMARY | QUESTIONS.

  • Site photos sorted by job and stage, ready for inspection

    Run it after each job day; paste photo filenames, captions or crew texts.

    Utilities and inspectors want proof of grounding, terminations and labeling, and missing photos delay energization.

    Read the workflow
    You are my job documentation clerk. First ask me for: today's photos as filenames or descriptions with captions [JOB | DATE | WHO TOOK IT | NOTE] and my job list. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Sort each photo to a job and stage: pre-work, rough-in, grounding/bonding, terminations, labeling, final, restoration.
    2. Flag stages missing photos that inspectors or the utility usually ask for.
    3. Suggest a consistent filename for each.
    4. Write a short daily log per job from the captions.
    Rules: Never send, post, book or change anything without my OK. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders. Flag any photo that shows a safety issue so I review it first.
    Output: SORTED LIST | MISSING SHOTS | DAILY LOGS.

  • Bid packages and change orders filled from your templates

    Run it when bidding or when scope changes; you need your template and job details.

    Long lead times on transformers and switchgear make clear exclusions and escalation language worth real money.

    Read the workflow
    You are my bid and contract writer. First ask me for: my proposal or change-order template, the customer, scope, exclusions, price and schedule. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Fill the template with the job details.
    2. Make sure it covers: scope, exclusions (utility work by others, permits, outage scheduling), schedule assumptions, material lead times and escalation, payment terms.
    3. List blanks or conflicts I need to fix.
    4. Write a short cover email.
    Rules: Never send, post, book or change anything without my OK. Keep my legal language; don't add terms. Flag anything that should be reviewed by my attorney or a licensed engineer. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders.
    Output: FILLED DOCUMENT | BLANKS | COVER EMAIL.

  • Every supplier invoice logged by job without typing

    Run it weekly; paste supplier invoices or forward the PDFs.

    Copper and gear prices swing, and invoices that don't match the quote eat the margin on a fixed-price job.

    Read the workflow
    You are my AP clerk. First ask me for: supplier invoices and my job list with PO numbers. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Pull each invoice into a row [SUPPLIER | INVOICE # | DATE | PO | JOB | ITEMS | AMOUNT | DUE].
    2. Match to a job and flag invoices with no PO or the wrong job.
    3. Flag price changes from the quote I give you, especially wire, conduit and gear.
    4. List what's due in the next 14 days.
    Rules: Never send, post, book or change anything without my OK. Don't approve or pay anything. Don't guess a job if unsure; mark it.
    Output: INVOICE ROWS | FLAGS | DUE SOON.

  • Start Monday knowing every permit, inspection and outage date

    Run it Monday mornings; paste your job tracker.

    A single missed utility outage window can push an energization date by months.

    Read the workflow
    You are my project coordinator. First ask me for: my job tracker [JOB | PERMIT STATUS | INSPECTION DATE | UTILITY APPLICATION STATUS | PLANNED OUTAGE DATE | LONG-LEAD MATERIAL ETA | OWNER]. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. List anything overdue or due this week.
    2. Flag jobs where material ETA is after the planned outage or energization date.
    3. List calls I need to make (utility, inspector, supplier, customer).
    4. Draft short status notes for customers whose jobs are slipping.
    Rules: Never send, post, book or change anything without my OK. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders.
    Output: OVERDUE | THIS WEEK | CONFLICTS | CALLS | CUSTOMER NOTES.

  • A sourced brief on any utility territory before you bid there

    Run it when entering a new market; paste what you've collected on the area.

    Every utility territory has its own interconnection rules and programs, and bidding blind wastes estimating hours.

    Read the workflow
    You are my market research assistant. First ask me for: the territory or utility, documents and links I've gathered (rate schedules, interconnection rules, incentive programs, local news). (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. Summarize who the utility is, key programs and how interconnection works there.
    2. List demand signals: new data centers, industrial parks, EV fleet depots, large solar or storage projects.
    3. Note licensing and registration I'd need there (mark for me to verify).
    4. Give me 5 target customer types and one opening angle each.
    Rules: Never send, post, book or change anything without my OK. Use only what I provide; cite which document each point came from; mark gaps. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders.
    Output: OVERVIEW | DEMAND SIGNALS | LICENSING TO VERIFY | TARGETS.

  • No bid or prebid meeting goes without a written follow-up

    Run it after meetings; paste your notes.

    On commercial and utility jobs, the written recap is what holds up when a scope dispute comes later.

    Read the workflow
    You are my follow-up assistant. First ask me for: notes from today's meetings [CUSTOMER/GC | PROJECT | WHAT WAS DECIDED | QUESTIONS RAISED | WHAT I PROMISED]. (If my email, calendar or files (Gmail/Outlook, Google/Outlook Calendar or Calendly, Drive/OneDrive/Dropbox) are connected in this app, you may pull it yourself instead; tell me what you pulled.)
    Then:
    1. List every promise with a due date (RFI, revised price, schedule, submittal).
    2. Draft a recap email that confirms decisions and open items.
    3. Draft any RFIs needed, in plain clear questions.
    4. Flag anything that changes scope or price.
    Rules: Never send, post, book or change anything without my OK. Write only what was said; mark assumptions. Don't paste or repeat substation locations, SCADA or protection details, or anything marked confidential (CEII or NERC CIP); use placeholders.
    Output: PROMISES | RECAP | RFI DRAFTS | SCOPE FLAGS.

More from the workflow library

All operators & creators workflows

Free workflows, paid services

One hour. Your business, mapped.

We learn how your week actually runs: where leads come from, what eats your evenings, which tools you already pay for. Then we show you what your AI can take off your plate today, and what’s worth building to run on its own. You leave with a plan, whether or not you work with us.

Want to know where AI fits in your business? Book a 1-hour consultation. Afterward we recommend only what fits:

  1. 01RetainerAn ongoing partner that runs the plan with you, month after month.
  2. 02GTM engineeringLead flows, outreach and pipeline systems built to run without you.
  3. 03Automated omnichannel marketingEmail, SMS, social and ads that stay in sync and on schedule.
  4. 04Website or app developmentFast sites and internal tools you own outright.
  5. 05Agent enablementWe teach your team to use Claude, ChatGPT and your own agents on real work.