Field SOP
Field SOP

Stop Typing Tables: Three Sentences, One Excel Sheet

A practical SOP for generating and processing spreadsheets (Excel / Sheets) with AI: a five-step workflow, three copyable prompt templates (headers and sample data, complex formulas with XLOOKUP / SUMIFS / INDEX-MATCH, VBA or Python batch), a six-tool strength comparison, and the five most common pitfalls including hallucinated columns and permission leaks.

Published November 1, 20269 min read
<!-- ai-spreadsheet-sop | sop | Stop Typing Tables: Three Sentences, One Excel Sheet -->

This "Hands-on SOP" covers one thing: using AI to generate and process spreadsheets (Excel / Google Sheets) from scratch. We do not go deep into data analysis methods or visualization tricks. If you later want pivot tables, charts, or statistical modeling, the site has separate data analysis and data cleaning topics you can link to. What this article gives you is a workflow you can copy directly, plus three prompt templates, to turn a plain sentence into a clean, usable table.

The five-step workflow: from one sentence to one table

Building a table fails most when you jump straight to "make me a table". The AI does not know what columns, types, or calculations you need. Break it into five steps, each with key actions and easy-to-miss points, and you will rarely crash.

Step 1: Describe the need (let the AI state what it will build before you ask for the result)

Key action: Do not rush the deliverable. First ask the model to describe the data structure it understands in plain language — column names, each column's type (text / number / date / dropdown), and a few sample rows. This surfaces ambiguity: you will immediately see whether "sales" means pre-tax or post-tax, whether "status" should be a dropdown.

Easy-to-miss: The request is too short, so the AI imagines fields for you and ends up with columns you never wanted. Write the business scenario, what each row represents, and key definitions (currency unit, date format) — that matters more than writing a long formula. Have the model describe the structure before producing the result, so you avoid asking for data it cannot deliver and keep the analysis from drifting.

Step 2: Pick the tool (embedded vs file-and-code)

Key action: If you are already inside an Excel / WPS workbook and want to tweak format and formulas in place, use the embedded type (Excel native Copilot, WPS AI). If you have a file to clean, batch-process, or want a downloadable xlsx, use the file-and-code type (ChatGPT Advanced Data Analysis, Claude). Sheets users go straight to Gemini.

Easy-to-miss: Using a file-and-code tool to "iteratively tweak format inside a workbook" is awkward, and conversely using the embedded type for "batch cleaning of tens of thousands of rows" cannot run. Decide first whether you want to "edit this table" or "process a batch of files", then pick a side.

Step 3: Generate (headers / formulas / data, step by step)

Key action: Generate headers, formulas, and data separately; do not dump everything into the AI at once. When asking for a formula, always state three things: absolute or relative references, whether the separator is comma or semicolon (Chinese-region Excel often uses semicolon), and the target Excel version. XLOOKUP and dynamic arrays need Microsoft 365 / Excel 2021 or later, or you get #NAME?.

Easy-to-miss: You ask for a formula without stating the version, so it defaults to XLOOKUP, which will not run on your machine; you forget the separator, so every drag-down is wrong once pasted locally. Ask the model to give the final formula first, then explain it parameter by parameter, and list two most error-prone boundaries.

Step 4: Verify (small-sample diff, then production)

Key action: Run the formula and code on a 10 to 20 row small sample first, and compare against two or three results you know are correct. Focus on boundaries: empty cells, zeros, text mixed into number columns, leading/trailing spaces. For finance, compliance, or data going to stakeholders, a human must review the logic before it goes live.

Easy-to-miss: Running the full thousands of rows at once hides errors. Small-sample diffing is cheap and saves lives. Run a small representative sample first, then scale up; check boundaries like nulls, zeros, and text leaking into number columns.

Step 5: Deliver (move the result back into your workflow)

Key action: ChatGPT / Claude will not automatically hand you a formatted report. Once the table is done, either download the xlsx (Claude supports Artifacts and saving to Google Drive) or paste the result back into a document. Confirm file name, sheet name, and column order match your downstream system.

Easy-to-miss: What the AI gives you is "a table in the chat", not "the format your system wants". Align field names and order before delivery, or the downstream step reworks it. Moving the table or chart back into a document or downloading the file is a manual step the model will not finish for you.

Three reusable prompt templates

The three templates below can be copied directly. Replace the placeholders with your real content; the bracketed examples can be deleted. Every template asks the model to "explain first, then give the result" so you can verify.

Template 1: Natural language to Excel headers + sample data

text
Based on the business need below, help me design the [headers (column names)] for an Excel table and generate [5 to 10 rows] of sample data.

Business scenario (replace with your need): [e.g. a small team's content publishing calendar that tracks topic, owner, platform, planned publish date, status, and read-count goal]

Requirements:
1. Give clear column names (one plain sentence per column stating what it is and whether the type is text / number / date / dropdown).
2. Mark which are "required" and which fit a dropdown (e.g. status: draft / writing / published / reviewed).
3. Generate 5 to 10 rows of realistic sample data (no empty columns, no made-up fields that do not exist).
4. End with a plain-language note: which formula suits this table for summarization (e.g. use COUNTIF to count each status).
5. Do not invent Excel functions or fields that do not exist; if unsure, write "(to confirm)" explicitly.

Template 2: Natural language to complex formulas (XLOOKUP / SUMIFS / INDEX-MATCH)

text
I want to write one formula in an Excel workbook. Use [XLOOKUP / SUMIFS / INDEX+MATCH] (replace with your need, pick one or specify) to achieve it.

My data structure (replace with your need):
- Main sheet Sheet1: column A = order id, B = customer name, C = region, D = amount, data from row 2 to row [N].
- Lookup sheet Sheet2: column A = customer name, B = account manager.

What I want:
[ e.g. look up the account manager from Sheet2 by customer name in Sheet1's column B, exact match; and sum orders where region = East and amount > 1000. ]

Hard requirements (must follow to avoid failure):
1. Use [absolute references $] for ranges (I will drag down to fill).
2. Use [comma ,] as the argument separator (if your Excel is Chinese-region it may use semicolon ;, change per my region).
3. Target Excel version is [Microsoft 365 / Excel 2021 / other]; if XLOOKUP or dynamic arrays are used, confirm that version supports them first.
4. Write the final formula first, then explain each part in plain language parameter by parameter.
5. List 2 most error-prone boundaries (blanks, text-formatted numbers, leading/trailing spaces, #N/A causes) and how to debug them.

Template 3: Natural language to VBA macro / Python script for batch processing

text
Help me write a [VBA macro / Python script (openpyxl or pandas)] (replace with your need) to batch-process an Excel file.

Task (replace with your need):
[ e.g. split the "full name" column into "last name" and "first name"; delete fully empty rows; convert text-formatted numbers in the amount column to real numbers; add filters to row 1 of every worksheet. ]

Input/output contract:
- Input file: [path or "uploaded file"], worksheet name = [Sheet1].
- Output: for VBA give code I can paste into a module; for Python give a runnable script that reads input.xlsx and writes output.xlsx.
- About [N] rows; consider performance (avoid cell-by-cell loops, prefer vectorized / batch writes).

Safety and verification requirements (required):
1. Code must run on a [copy], never overwrite the original (Python writes to a new file name).
2. Give a "before running" checklist (e.g. VBA must save as .xlsm, enable macros via File > Options > Trust Center).
3. Clear comments; explain key steps in plain language; do not let code call any external URL or hardcode a password.
4. End with 3 "how to eyeball-check the result is correct" checks after running.

Tool comparison: who is good at what

The following is a qualitative strength map, not an official ranking, based on each tool's public capability descriptions.

  • ChatGPT (Advanced Data Analysis / Code Interpreter): Strong at running real Python on uploaded files — reading, cleaning, statistics, pivoting, and format conversion are actual computation, not the model guessing numbers. The environment is temporary; files and variables clear after the chat ends or goes idle, so re-upload. It accepts .xlsx / .xls / .csv / .json / .pdf and more; above roughly 30 to 50MB parsing slows, times out, or returns incomplete output. Official guidance says upload structured data with descriptive header rows, one record per row, and plain-language column names, avoiding multiple unrelated tables, empty rows, and empty columns in one sheet.
  • Claude: Can create and download .xlsx files directly, and upload CSV / TSV to do data analysis and visualization in Python, outputting PNG charts. Single-file limit is 30MB (both upload and download), up to 20 files per chat; larger needs splitting. It offers a sandbox code environment that installs dependencies from approved package managers.
  • Gemini (inside Google Sheets): A side panel builds tables, formulas, and summarizes data; shortcut Ctrl+Alt+G on Windows / ChromeOS. "Help me organize" is summoned with @ to generate project plans and trackers in natural language, with "Export to Sheets" saving chat results as a new sheet. Example formula prompt: "Create a formula that divides goals by games"; when a cell errors, click Fix to have Gemini review the formula and diagnose it. It can generate charts into a new tab, but note those charts do not auto-update with the source data. Unstable above a few hundred rows.
  • Excel native Copilot: Embedded in the workbook for in-place iteration, like an Excel expert beside you; can add filters, split text, apply formula-based conditional formatting, ask for insights in natural language, and generate charts and pivot tables. It already supports complex formulas like XLOOKUP and SUMIF (and the SUMIFS family), shows step-by-step explanations, and previews before applying. Copilot in Excel with Python is in public preview, while Python in Excel itself is generally available.
  • WPS AI: Embedded in WPS Sheets; supports natural-language writing of SUM, AVERAGE, VLOOKUP, IF, COUNTIF, SUMIF, INDEX-MATCH and nested formulas, with a "formula explainer" that decodes nested layers in plain language. It also offers AI conditional formatting (e.g. "highlight sales above 100k in red"), AI data analysis (conversational insight / forecast / correlation), and AI chart generation. In natural language it can one-click generate a professional table structure with formulas and templates, auto-clean (detect duplicates / entry errors), auto-complete VLOOKUP-style cross-sheet matching, and auto-flag sensitive fields (ID card / bank card) with desensitization suggested.
  • Google Sheets AI (Help me organize / formula suggestions): See the Gemini item; it is the same capability exposed through two entry points inside Sheets.

One-line pick: for in-place table editing use Excel Copilot / WPS AI; for uploading files to run Python cleaning and batch jobs use ChatGPT / Claude; Sheets users use Gemini. This is an editorial summary based on public capability descriptions, not an official ranking.

Common pitfalls: the five places AI-made tables most often crash

  1. Hallucinated columns / fields: AI invents Excel functions that do not exist, or applies another tool's syntax (SQL / Sheets) to Excel, looking right but unrunnable. After getting a result, first check whether the function name truly exists in your Excel version; if unsure, ask it to mark "(to confirm)" rather than copy blindly.
  2. Wrong formula logic: Complex formulas crash at boundaries — empty cells, inconsistent date formats, argument separators (comma vs semicolon by region), and broken nested logic once the structure changes. Ask the model to list boundary cases and diff them yourself; note that older Excel raises #NAME? with XLOOKUP.
  3. Wrong data types: "001" as text is not the number 1; leading/trailing spaces and text-formatted numbers make XLOOKUP return #N/A and SUMIFS totals disagree with hand math. When cleaning, explicitly convert types, trim spaces, and pad zeros; decide early whether "001"-style codes stay as text.
  4. Permission leak red line: Do not paste company-sensitive data into public models. External files can be injected with instructions to leak sensitive data, so monitor usage. Desensitize before upload; prefer local processing for ID card / bank card fields; when cloud is truly needed, use an enterprise edition or a service under a signed NDA.
  5. Oversized file limits: ChatGPT is unstable above roughly 30 to 50MB, Claude caps a single file at 30MB, and Sheets is unstable above a few hundred rows. For huge files, split, sample, or move to a local script first; you can also send only the headers and a few sample rows so the AI writes the logic, then run that logic locally on the full set.

S4 question-style titles (SEO candidates)

When writing or building on-site search landing, use question-style titles to catch traffic:

  • How do I use AI to generate an Excel table in one click?
  • I cannot write functions; how do I get AI to write VLOOKUP / XLOOKUP for me?
  • For AI table-making, which tool is best: ChatGPT, Copilot, or WPS AI?
  • AI-generated Excel formulas keep failing? Avoid these 5 pitfalls
  • How do I let AI automatically clean a messy table?
  • Is it safe to use AI to write VBA macros for batch Excel processing?
  • How does Gemini in Google Sheets help me build tables and analyze?
  • Can I feed company data to AI for table-making? Where is the privacy red line?

Related reading

FAQ

Q1: For AI table-making, which tool is best? A1: There is no absolute best; it depends on the scenario. For tweaking format and formulas inside a workbook in place, Excel native Copilot and WPS AI are smoothest. For uploading files to run Python cleaning, batch processing, and generating downloadable xlsx, ChatGPT Advanced Data Analysis and Claude are stronger. Google Sheets users should use Gemini directly. Decide first whether you want to "edit this table" or "process a batch of files".

Q2: The formula the AI gave me is wrong. What do I do? A2: First test the formula's boundary cases alone: empty cells, zeros, text mixed into number columns, leading/trailing spaces, argument separators (comma or semicolon). Ask the model to write the final formula first, then explain it parameter by parameter, and list the most error-prone boundaries with debugging steps. Diff two or three known-correct results on a small sample, confirm the logic, then run the full set. On older Excel, XLOOKUP raises #NAME?; confirm version support.

Q3: Is it safe to paste company data into AI for table-making? A3: The red line is not feeding company-sensitive data to public models. External files can also be injected with instructions to leak data, so monitor. The safe move is to desensitize first — remove or mask fields like ID cards, bank cards, and client lists; prefer local scripts for sensitive data. When cloud is truly needed, use an enterprise edition, private deployment, or a service under a signed NDA, and monitor inputs and outputs.

Q4: The file is too big for AI to handle. What now? A4: ChatGPT slows and times out above roughly 30 to 50MB, Claude caps a single file at 30MB, and Sheets is unstable above a few hundred rows. For huge files, split, sample, or move to a local Python script; you can also send only the headers and a few sample rows so the AI writes the logic, then run that logic locally on the full set.

Q5: Can AI turn my table into a chart directly? A5: Yes, with boundaries. Excel Copilot, WPS AI, and Gemini in Google Sheets can all generate charts or pivot tables from natural language. Note that Gemini's generated charts do not auto-update with the source data; for live linking use Sheets' native chart feature. This article focuses on "generating and processing tables"; chart and visualization techniques are covered further in the site's data analysis and data cleaning topics.

This article is AI-assisted and human-edited. Last updated: 2026-11-01

FAQ

For AI table-making, which tool is best?
There is no absolute best; it depends on the scenario. For tweaking format and formulas inside a workbook in place, Excel native Copilot and WPS AI are smoothest. For uploading files to run Python cleaning, batch processing, and generating downloadable xlsx, ChatGPT Advanced Data Analysis and Claude are stronger. Google Sheets users should use Gemini directly. Decide first whether you want to "edit this table" or "process a batch of files".
The formula the AI gave me is wrong. What do I do?
First test the formula's boundary cases alone: empty cells, zeros, text mixed into number columns, leading/trailing spaces, argument separators (comma or semicolon). Ask the model to write the final formula first, then explain it parameter by parameter, and list the most error-prone boundaries with debugging steps. Diff two or three known-correct results on a small sample, confirm the logic, then run the full set. On older Excel, XLOOKUP raises #NAME?; confirm version support.
Is it safe to paste company data into AI for table-making?
The red line is not feeding company-sensitive data to public models. External files can also be injected with instructions to leak data, so monitor. The safe move is to desensitize first — remove or mask fields like ID cards, bank cards, and client lists; prefer local scripts for sensitive data. When cloud is truly needed, use an enterprise edition, private deployment, or a service under a signed NDA, and monitor inputs and outputs.
The file is too big for AI to handle. What now?
ChatGPT slows and times out above roughly 30 to 50MB, Claude caps a single file at 30MB, and Sheets is unstable above a few hundred rows. For huge files, split, sample, or move to a local Python script; you can also send only the headers and a few sample rows so the AI writes the logic, then run that logic locally on the full set.
Can AI turn my table into a chart directly?
Yes, with boundaries. Excel Copilot, WPS AI, and Gemini in Google Sheets can all generate charts or pivot tables from natural language. Note that Gemini's generated charts do not auto-update with the source data; for live linking use Sheets' native chart feature. This article focuses on "generating and processing tables"; chart and visualization techniques are covered further in the site's data analysis and data cleaning topics.

Related

Field SOP

Invoice OCR to Excel: Batch Recognition Without Manual Entry

A two-route SOP for turning a stack of invoices into one Excel sheet (division of labor with the site's deepseek-ocr local-deploy piece: that one gets the model running, this one gets batches structured and exported). Route A, Baidu AI Cloud's VAT invoice recognition: the vat_invoice endpoint accepts pdf_file directly, with free quotas of 1,000 calls/month for individuals and 2,000 for enterprises issued monthly, failed calls included in the count, and 2 QPS free / 10 QPS paid (official figures; the community-circulated 5/3 QPS is not adopted). Route B, local PaddleOCR (v3.7.0 with PP-OCRv6, 91,929 stars, Apache-2.0, CPU-runnable), with the key caveat in bold: the open-source edition has no invoice-specific model, so field mapping means writing your own regexes — that engineering gap is the core selection argument between the routes. The full pipeline runs as written: pathlib/glob batch collection, PyMuPDF rendering at 300dpi (with an AGPL/commercial dual-license warning and alternatives), per-file recognition into dicts, and styled xlsx export via pandas/openpyxl. Error playbook covers blur, stamp occlusion, skew, wrong ticket types and QPS throttling; authenticity checks go only through the national VAT invoice verification platform (5 checks per invoice per day, invoices from the last 5 years). Tencent/Alibaba comparisons and a large-model route (GLM-OCR) section both carry explicit sourcing limits, with no marketing accuracy numbers.

Oct 30, 202611 min read
Field SOP

ChatGPT Chrome Setup: Six Steps to Minimal Permissions

A hands-on SOP for letting ChatGPT drive your browser, with every step and UI path taken from the official docs at learn.chatgpt.com. Six steps: first, prerequisites (a paid ChatGPT plan, the desktop app, and one of five supported Chromium browsers - Chrome, Edge, Brave, Opera, Vivaldi; Firefox and Safari are not supported); second, installation (desktop app, Settings > Computer Use, pick your browser, Install through the extension store, approve permissions, then confirm the browser shows Manage; on macOS, Computer Use needs Screen Recording and Accessibility permissions); third, invocation (at-mentions like @Chrome, right-click Ask ChatGPT, Cmd+Shift+. on macOS for the side panel, bringing open tabs or selected text into the chat, and the double-Command Appshot); fourth, choosing among three surfaces (tasks needing your existing signed-in profile go to the extension, localhost and preview pages to the built-in @Browser, dedicated integrations to plugins); fifth, permission hygiene with the four-level prompt (Allow once, Allow for this site, Allow for all sites, Decline) plus domain allowlist and blocklist management shared across all five browsers, noting the docs themselves flag Allow for all sites and browser-history access as elevated-risk; sixth, safety habits (treat page content, selected text and video transcripts as untrusted context, review pages before acting, do not leave the agent resident). Known quirks from the official docs: Opera lacks the side chat but supports desktop workflows, only Chromium browsers are supported, and Chrome tasks run grouped in tab groups. Division of labor with the hotspot piece: that one covers OpenAI's product move; this one covers configuring your own machine and keeping permissions minimal.

Oct 18, 202610 min read
Field SOP

Still Writing Weekly Reports at 8 PM Friday?

A five-step workflow that turns weekly fragments into a report worth submitting: ten minutes of Friday triage into three piles (progress, risks, support needed), structured input, generation, manual number-checking, and polish. Two copy-paste prompt templates are the core deliverables: one turns a running log into a draft (role setup, four-part structure, the anti-hallucination line "never write what I did not mention, mark uncertainty as to-be-confirmed," an AI-flavor blacklist, and a hard 500-word cap); the other polishes into executive register (harsh-reviewer self-check, exemplar alignment, and a "do not add or alter any numbers" guard). Anti-hallucination is not paranoia: user reports describe unconstrained models adding growth figures never in the source and computing their own summary values, convincingly enough to fool the author. The data-red-line section is the hardest edge: Nantong police's "three don'ts, three dos," a Chaoyang court ruling (the dismissal was ruled unlawful and the employee won — not a license to upload), and Samsung's 1,024-byte leak precedent, landing on weekly-report specifics: redact client names, amounts, and internal system names before pasting. Methodology: conclusion first, results up front, data speaks; leaders read three things — progress, risks, support needed; surfacing problems earns credit. Tools (a weekly-report generator, Feishu's AI personal weekly report, DingTalk, WPS AI) get one paragraph, not a comparison.

Oct 31, 202611 min read