A spoken method for describing sheets, conditions, and formula checks.

Dictating Prompts for Spreadsheet formulas works best when you describe the sheet before you describe the calculation. Name the tab, the header row, the first and last column, and the row where the values begin. Say what one row represents, such as one order, one shift, or one customer. This context tells the assistant which columns are inputs and which are outputs. Without it, a request for a total can land on the wrong column or include the header row. Two sentences of framing save several rounds of correction later. Keep the file open beside the prompt while you speak, so you can read the header text instead of recalling it, and correct the note when a label changes.
Write the columns you will use on a note, in order, with their exact header text. Header text is a fixed string, and a misheard label becomes a formula that points at nothing. Read each header slowly and repeat any that contain a number or an abbreviation. If a sheet has merged cells or blank columns, mention them now. The assistant needs to know where the real table starts, and a person reading the rendered prompt should be able to confirm the layout without opening the file. If a header contains a date or a version number, say it twice and check it in the rendered prompt, because a small change breaks every reference below it.
State the output you expect before the method. Say whether you want one value, a column of values, a count, or a flag. Name the cell or column where the result should sit. If the formula will be copied down a column, say so, because a relative reference and a fixed reference produce different results when copied. A clear output statement lets you check the answer on one row before trusting it across a thousand rows. If the result feeds a chart, say so, because a chart may need one clean column rather than a formula copied across many cells. Keep the output rule in the note.
Decide how to handle blank or malformed rows before you speak. Say whether a blank should count as zero, be skipped, or produce a warning. Say what should happen when a value is text where a number is expected. These rules are the difference between a formula that works on clean sample rows and one that breaks on the first unusual row. Write the rules in plain words and speak them as a short list, so the assistant applies them deliberately. Write each rule as a short numbered line, so you can read it back and so a colleague can apply the same rule to a copy of the sheet.
Describe ranges by their boundaries rather than by a rough size. Say the range starts at the first value row and ends at the last filled row, or name the exact cells. If the table grows each week, say that the range should follow the filled rows rather than a fixed block. A formula tied to a fixed range quietly drops new rows, and the total looks correct while it is incomplete. Naming the boundary rule is more useful than naming a number that will soon be wrong. If the last row contains a total, exclude it from the range and say so, because a total inside the range doubles the figure you are calculating.
Speak conditions as complete sentences. Instead of saying filter the big ones, say include rows where the amount is greater than one hundred and the status is not cancelled. Each condition should name a column, a comparison, and a value. When two conditions combine, say whether both must hold or either may hold. A spoken and can blur into or if you rush, so pause between conditions and repeat the connector once. When a condition uses a date, say whether it is before, after, or between, and give the format, because a text date and a real date compare differently.
Use the column names you wrote on your note, not pronouns. Saying the date column and the amount column is clearer than saying that one and this one. If two columns have similar names, add a distinguishing word such as the ship date column or the order date column. The assistant cannot see your screen, so every reference has to stand on its own. Clear references also make the rendered prompt readable when a colleague reviews it. If a column name contains a space or a symbol, say it exactly as it appears, because a shortened name may match nothing in the header row.
Read the spoken conditions back before you ask for the formula. Check that every column name matches the header text, every comparison is the one you meant, and every value is in the right units. If the sheet stores dates as text, say so. If amounts are in cents, say so. A single unit mismatch turns a sensible condition into a wrong answer that looks plausible. The read-back is quick, and it is the cheapest place to catch this kind of error. If a value could be negative, say whether it should be included, because a total that silently excludes refunds can look correct and still mislead.
Ask for the formula in pieces when the calculation is not simple. First ask for the inner expression that produces one intermediate value, check it, then ask for the outer step that uses it. A nested formula dictated in one breath is hard to verify and harder to repair. Building it in layers means each layer can be tested on a sample row. If a layer fails, you replace only that layer instead of reworking the whole formula. Name each intermediate value in plain words, so you can describe it in the next request instead of repeating the whole formula from the start.
Say the function names exactly and spell unusual ones. Ask for the formula in the syntax the sheet expects, and say whether you want a separated list or a modern array form. If you are unsure of a function name, describe the job instead, such as count the rows that meet a condition, and let the assistant choose. Describing the job is safer than guessing a name and building a formula around a wrong one. If the sheet has an older version of a function, say which version you use, because a modern function may not open in a shared file.
Ask for one worked example with the formula. Request the formula, the row it was tested on, the inputs from that row, and the result. A worked example lets you confirm the logic before you copy the formula anywhere. If the example result is wrong, the explanation usually shows which reference slipped. This step turns a formula request into a small test, and a test is what makes a dictated prompt trustworthy. If the worked example uses a row you can also see, compare the two results line by line, rather than only the final number at the end of the formula.
Ask for the formula and its plain-language reading. A short sentence that says what the formula does in ordinary terms is easier to check than a string of functions. If the reading and the formula disagree, stop and resolve the difference before using either. When the formula is long, ask for the reading line by line. This habit catches a misplaced parenthesis or an off-by-one row reference that a quick glance would miss. If the reading uses a term you do not recognize, ask for the plain meaning, because an unexplained term hides the exact place where the formula can fail.
Test the formula on a row you can calculate by hand. Pick a row with ordinary values and a row with an edge case, such as a blank cell or a zero. Compute the expected result yourself, then compare it with the formula output. If both rows match, the formula is a reasonable candidate. If one row fails, read the intermediate values before changing anything. A test on two rows takes a minute and prevents a wrong column from spreading down the sheet. If the two test rows agree, copy the formula to one extra row and check again, because a boundary row often behaves differently from an ordinary one.
Use Voiskey to describe the test results in plain language when you ask for a fix. Put the insertion point in the message window, press the shortcut, and say the row, the expected value, the actual value, and the likely cause. The app removes filler and false starts, so the report reads like a short bug note. Clear reports get clear fixes, and the same habit works when you hand the problem to a colleague. Say the sheet name and the cell as well as the row, so the fix targets the right copy when you keep more than one version of the file.
Copy the formula down one column at a time and spot-check three rows. Check the first row, a middle row, and the last filled row. A relative reference that works at the top can drift at the bottom if the range was anchored incorrectly. If a row fails, note whether the failure comes from the reference or from the value. Then fix the formula at the top and copy it down again, rather than patching individual cells. If the last row is a summary, skip it in the spot check and test the row above it, because a summary row rarely follows the column pattern.
When the sheet is shared, download Voiskey on the second machine and keep the same test rows available. The same prompt and the same two sample rows make the check repeatable wherever you work. Write the expected values next to the test rows in a note, so a colleague can repeat the comparison without recalculating by hand. A formula is only verified when someone else can reproduce the check with the same evidence. If the second machine opens the sheet with a different locale, recheck any formula that uses a comma or a decimal separator before you trust it. Keep that check in the saved note.
Save the prompt that produced a working formula. Keep the sheet description, the column names, the condition rules, and the output shape together, with blanks for the changing parts. The next similar task starts from a tested brief instead of a blank line. Name the saved prompt by the job it does, such as monthly totals by region or overdue order count. A clear name makes the saved prompt easy to find when a deadline is close. If the prompt uses a condition that changes each month, put the condition on its own line so it is easy to replace without touching the rest.
Keep a short note on each saved prompt about the sheet it was built for. Record the layout, the unit conventions, and any quirk such as a header in row three. A prompt that assumes the wrong layout produces a formula that looks right and points at the wrong cells. When the layout changes, update the note first, then test the prompt on the new sheet before using it for real work. If the layout has moved a column, fix the note and the prompt before you rerun, because the formula will otherwise point at the old position. Test the updated prompt before relying on it.
Use Voiskey to fill a saved prompt by voice. Open the prompt, place the insertion point where the new details belong, press the shortcut, and speak the sheet name and the changed columns. The text lands in the saved prompt, so the tested structure stays intact. Read the filled version once before sending. This is faster than retyping the brief and safer than editing many small parts from memory. If the sheet uses a different name on the second machine, say the new name rather than the old one, and keep every other part of the prompt exactly unchanged, so the test stays comparable.
Share the saved prompts with anyone who builds similar sheets. Give them the prompt, the test rows, and the note about the layout. Show one formula that worked and one that failed, with the reason. When you set up another computer, download Voiskey there and copy the prompt folder in the same structure, then test one entry on a sample sheet. A shared, tested prompt set makes formula work consistent across a team. If a teammate reports a wrong total, ask them for the row and the expected value before changing the shared prompt, so the change addresses the real case.
Voiskey turns spoken requests into AI-ready prompts, so you can say the tab, the header text, and the row range in one pass. It removes filler and false starts and keeps names as spoken. Read the rendered prompt before sending, because header text and cell references must match the sheet exactly.
Yes. Speak each condition as a full sentence that names the column, the comparison, and the value. Voiskey adapts punctuation and formatting to the request, which keeps a short list of conditions readable. Pause between conditions so that a spoken and does not blur into or before the prompt is sent.
State the output cell and whether the formula will be copied down, because relative and fixed references behave differently. Ask for one worked example with inputs and result. Voiskey renders the request as a prompt you can check, and it learns names, jargon, and acronyms, which keeps header text stable across repeats.
Put the insertion point in the message window and say the test row, the expected value, the actual value, and the likely cause. Voiskey removes filler and grammar slips, so the report reads like a short bug note. Include the formula version and the sheet name so the fix addresses the right copy.

Download Voiskey for Mac and Windows and speak your next prompt in seconds.
Use it across macOS, Windows, iOS, and Android