Build an Objective Summary Formula in Excel or Sheets
Summary
An objective summary of a spreadsheet shouldn't need a person to retype it every week. This guide builds a single formula, TEXTJOIN wrapped around SUMIFS, COUNTIFS and MAX, that generates a fact-only recap sentence straight from your data, updating itself whenever a row changes. It covers where Excel and Google Sheets diverge on TEXTJOIN and dynamic arrays, when UNIQUE plus SUMIFS beats one sentence, and why the usual "objective summary" writing advice was never built for numbers that change daily.
An objective summary of a spreadsheet is one line built entirely out of formulas: no adjectives, no judgment calls, just totals, counts and a last-updated date pulled straight from your data. You can build the whole thing with TEXTJOIN wrapped around SUMIFS, COUNTIFS and MAX. Below is the exact formula, why it beats retyping the same recap every Monday morning, and where Excel and Sheets quietly go their separate ways on it.
Biscuit went looking for "objective summary" tutorials before writing this, and almost all of them are about summarizing a meeting or an essay: strip your opinions, keep the facts, three paragraphs max. Good advice for a document. Useless for a spreadsheet, because nobody's paragraph regenerates itself when row 4,102 gets added tomorrow morning. A formula does.
Why Most "Objective Summary" Advice Falls Apart on a Spreadsheet
Search the phrase and you'll find the same seven-step list everywhere: read the whole thing, find the main idea, cut the opinions, rewrite it in your own words, check it's still neutral. Fine advice for turning a report or a call into a paragraph. It assumes a human writes the summary once, from a text that already exists.
A weekly sales recap doesn't work that way. The "text" is a table that changes every day. Somebody has to reread it, requalify it and rewrite the same three sentences on a schedule, forever. Do that for six months and the phrasing starts drifting: this week's summary calls a dip "a slight softening," last month's called the same size dip "a concerning trend." Same data, different adjectives, because a person picked the words both times. That's not objective anymore. That's mood.
A formula can't have a mood. It reads SUM, COUNTIF and MAX off the same cells every single time, so the wording never creeps even when the numbers do. That's the part the generic "how to summarize" guides miss entirely: for recurring data, objectivity is a property of who (or what) regenerates the sentence, not just how carefully the first draft was worded.
The One-Line Test For "Is This Summary Actually Objective?"
If a human has to retype it, it's not objective, it's a guess dressed up as a fact. If a formula pulls it straight from the cells, it's objective by construction: it can only say what the data says.
Build the Formula: SUMIFS, COUNTIFS and TEXTJOIN Doing the Talking
Say you've got a table with columns for Region, Status and Amount, and someone keeps asking "can you just give me the summary" every Friday. Here's the cell that answers before they ask:
=TEXTJOIN(" ", TRUE, "Total:", TEXT(SUM(Amount), "$#,##0"), "| Open:", COUNTIF(Status, "Open"), "| Last entry:", TEXT(MAX(Date), "mmm d"))Argument by argument:
" ": the delimiter between chunks. A space keeps it readable as one sentence.TRUE: ignore empty cells so a half-filled row doesn't leave a stray gap.Everything after that is a pair of a label and a live value:
SUM,COUNTIF,MAXdoing the actual counting.
Paste it into one cell, point it at your ranges, and you get something like: Total: $84,200 | Open: 12 | Last entry: Jul 22. Nobody wrote that sentence. The data did. Change one row and the summary updates itself before you've finished your coffee.
Want it to react to more than one condition, like "West region only"? Swap COUNTIF/SUM for COUNTIFS/SUMIFS and add the extra criteria pair:
=SUMIFS(Amount, Region, "West", Status, "Open")That's the formula that goes inside the TEXTJOIN once you need to slice by more than one column.

If describing the columns in plain English is faster than remembering TEXTJOIN's argument order at 5pm on a Friday, that's exactly the situation Formula.dog exists for. Describe the table, get the formula back, paste it in. We checked and it handles this exact TEXTJOIN-plus-SUMIFS combo without blinking.
One warning worth taking seriously: if any of the ranges inside TEXTJOIN are themselves array results (like a FILTER output) on an older, non-365 Excel, you may need Ctrl+Shift+Enter instead of a normal Enter. Skip that step and the formula returns the first value only, silently, no error message, which is the spreadsheet equivalent of Biscuit coming back with an empty mouth and a low tail.
Excel vs Sheets: Where the Objective Summary Formula Diverges
The TEXTJOIN skeleton above works in both, argument for argument. Where they split is the age of the feature and a few naming quirks.
TEXTJOIN: Excel 2019 and 365 only, not 2016. Available in every current version of Sheets.COUNTIFS/SUMIFS: All modern versions of both.Dynamic array spill (
UNIQUE,FILTER): Excel 2021 / 365 only. Sheets has had it available for longer, no separate license needed.Row ceiling: 1,048,576 rows in Excel. Sheets caps at about 10 million cells total across the sheet, which limits rows far lower on wide tables.
If your team is still on Excel 2016, the TEXTJOIN version of this formula won't work; you'll need the older, clunkier CONCATENATE plus & chain instead, which does the same job with worse readability. Microsoft's own documentation is worth a bookmark for the exact version cutoff before you promise this formula to a coworker on an old license.
What About UNIQUE and GROUPBY? (And Why They Won't Save You on Excel 2016)
UNIQUE paired with SUMIFS builds a full summary table instead of a single sentence: one row per category, auto-updating as new categories show up in the source data. GROUPBY goes further and collapses the whole thing into one formula, but it's Microsoft 365 only, rolled out gradually enough that some business licenses still don't have it in mid-2026. Sheets doesn't have a GROUPBY equivalent; QUERY covers similar ground with SQL-flavored syntax instead.
None of these three replace the TEXTJOIN sentence above. They solve a different problem: a whole table of objective facts instead of one line of them. Use the sentence for a status update in a shared doc. Use UNIQUE + SUMIFS when someone actually needs the breakdown, region by region, without opening a pivot table and remembering which filters were set last time.
A quick real-world case: an ops analyst tracking support tickets across five regions used to keep a separate mini-table updated by hand, one row added per new region, formulas copied down manually every time. Swapping to =UNIQUE(Region) next to =SUMIFS(Tickets, Region, H2#) (spilling down from the unique list) meant a sixth region showing up in the raw data just appeared in the summary table on its own, no copy-down, no forgotten row.

Once the summary cell exists, a lot of teams paste the result into a wiki page every week by hand, which reintroduces the exact copy-paste lag the formula was built to avoid. If your recap already lives in Notion, Notion AI can pull the number in through an embed instead of someone retyping it there too.
If You Actually Meant "Summarize My Meeting," You're in the Wrong Kennel
Most of the "objective summary" articles ranking right now, including one from a meeting-notetaker company, are about turning a conversation into a neutral paragraph: no opinions, no "I think," just what was said. That's a real, different problem, and a spreadsheet formula won't touch it.
If you came here looking for that, a transcription tool built for calls is the right fetch, not a formula generator built for cells. Come back once the meeting produces numbers that need summarizing.
Reporting Weekly? Make the Summary Regenerate Itself So Nobody Rewrites It

Picture an ops team of four, rotating who "does the Friday update" in Slack. Whoever draws the short straw that week scrolls the sheet, eyeballs the totals and types a summary that's roughly right. Three different people, three slightly different summaries, none of them wrong exactly, all of them shaped a little by whoever was typing.
The actual point of building this as a formula instead of a habit: a habit breaks the week someone's on vacation, or rushed, or new to the sheet and unsure which column means what. A cell doesn't take vacation, doesn't rush and doesn't guess at column meanings. Whoever's on Friday-update duty just screenshots the top row.
Three ways to make it stick:
Put the
TEXTJOINcell at the very top of the sheet, above the raw data, so it's the first thing anyone sees when the file opens.Name the cell (
Formulas > Define Name) something likeWeeklyObjectiveSummaryso it survives someone inserting a row above it.If the summary needs to travel outside the sheet (Slack, email, a status doc), link to the cell instead of copying its current text:
='[Report.xlsx]Sheet1'!$B$2pulls the live value, a pasted string doesn't.
For anyone drafting the surrounding report by hand and just wants a faster first pass at the prose around the numbers, general-purpose writing assistants like ChatGPT can turn the raw TEXTJOIN output into a sentence or two of context. Worth being precise about the division of labor though: the formula is the source of truth, the AI is only dressing it up in words afterward.
So, Would We Actually Use This Formula Ourselves?
Yes, for anything that gets asked about weekly: sales totals, open tickets, a headcount that changes every sprint. The setup cost is one formula, once. The payoff is every future Friday where nobody has to write "here's where things stand" from scratch.
Where we'd skip it: a one-off report nobody's going to ask about again. Writing a TEXTJOIN formula for a summary you'll read exactly once is more setup than a plain sentence typed by a person who already knows the numbers. Objective doesn't mean automatic is always better, it means the summary should say only what the data actually supports, whether a formula wrote it or you did.
Five minutes with TEXTJOIN, SUMIFS and a name box beats another Friday spent re-typing the same three sentences with slightly different adjectives. Good boy, formula. Go fetch the numbers.