Home/Blog/How to Decode a Home Energy Bill from a Pasted Statement
Blog

How to Decode a Home Energy Bill from a Pasted Statement

P
promptstudio
How to Decode a Home Energy Bill from a Pasted Statement

Bill decoders invent kWh rates. Quote line items only. Leave USAGE NOT IN STATEMENT when blank.

The matching generator is the Home Energy Bill Decoder from a Pasted Statement prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Print not-financial-advice banner first

Decode a pasted home energy bill into plain-language line items. Never invent rates, fees, or usage totals. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Pasted statement text (de-identify account numbers): [Statement]
Utility name I allow (or UNKNOWN): [Utility]
Service address city I allow (or UNKNOWN): [City]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Banner I require: [Banner or Not financial advice]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Table only charges present in the paste

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: Statement nouns, Utility, City, Banner, Lang.
  2. Banner and de-identify reminder (mask account numbers if present).
  3. Bill header: Utility or UTILITY UNKNOWN; City or CITY UNKNOWN; billing period only if present.
  4. Line-item table: each charge/credit named in Statement with amount only if present; else AMOUNT NOT IN STATEMENT.
  5. Usage section: kWh/therms only if Statement includes them; else USAGE NOT IN STATEMENT. Never invent rates.
  6. Plain-language summary: what the household is paying for, only from named lines.
  7. Refuse: inventing rates, inventing rival utility quotes, inventing carbon scores, inventing account balances not shown.
  8. Compliance pass: Banned and Never. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Skip usage when kWh is missing

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Decoder from Statement only. No invented rates.
  • Never invent fees, taxes, or usage totals.
  • Keep Banner visible.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Refuse invented rates and rival quotes

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (home energy bill decoder, utility statement plain language, energy bill no invented rates) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.