If you've already read the A1 notation reference covering B2:2, this article goes deeper on the open-ended row pattern specifically: when it's the right call, when it isn't, and what it costs you.
What "Open-Ended Row Range" Actually Means
Standard A1 ranges have a fixed start and end: B4:F47. Open-ended ranges drop one boundary:
A:A- entire column A, all rows2:2- entire row 2, all columnsA2:A- column A from row 2 downward (no bottom boundary)A2:2- row 2 from column A rightward (no right boundary)
The last one is what this article is about. A2:2 tells Sheets: "give me everything in row 2, from column A to wherever the sheet ends." As of June 2026, Google Sheets extends to column ZZZ (18,278 columns), so A2:2 technically covers 18,278 cells even if 18,260 of them are blank.
That span matters for performance, covered below.
When Horizontal Open-Ended Ranges Actually Earn Their Keep
Most FP&A models are laid out vertically - line items in rows, time periods in columns. If you're building a board pack with Q1-Q4 columns and those columns might grow (adding actuals, adding a new fiscal year), the open-ended row range is the natural anchor.
A typical scenario: your Revenue row sits in row 7 of the P&L tab. You're building a summary on a separate sheet that needs to sum all revenue periods, regardless of how far right the model grows.
=SUM('P&L'!B7:7)
This picks up B7 through whatever is in row 7, permanently. When someone adds FY2027 in column K next year, the sum updates without anyone touching this formula.
Compare that to:
=SUM('P&L'!B7:J7)
Which breaks the moment the model grows past column J - and no one remembers to fix it until the board numbers don't tie.
Another real use case: SUMPRODUCT across a full row of assumptions.
=SUMPRODUCT(
('P&L'!B3:3="Actual") *
('P&L'!B7:7)
)
This sums revenue only for columns where row 3 says "Actual". When you flip a column from "Forecast" to "Actual" at quarter close, the formula self-updates. No manual range adjustment.
A2:2 vs. The Alternatives
| Notation | Direction | Covers | Best for |
|---|---|---|---|
A2:A | Vertical | Col A, row 2 to bottom | Line items that grow downward |
2:2 | Horizontal | All of row 2 | Entire period row (including headers) |
A2:2 | Horizontal | Row 2, col A rightward | Period row starting at a specific column |
A2:Z2 | Fixed | Row 2, cols A-Z | Bounded ranges when you control the model |
The difference between 2:2 and A2:2 is the left boundary. 2:2 starts at column A anyway, so in practice they're equivalent unless you're explicitly starting later (like C2:2 to skip a label column and start from the first data column).
For most P&L models where column A holds labels and column B starts data, B7:7 is the pattern you'll use most often. A2:2 comes up when you want to start the open-ended range from the absolute first column - common in helper tabs or when you're referencing assumption rows that begin in column A.
The Performance Tradeoff You Need to Know
The 18,278-column reach of A2:2 is mostly irrelevant when the formula engine sees empty cells. SUMIFS and SUMPRODUCT skip empty cells efficiently. But there are cases where it bites you.
ARRAYFORMULA behaves differently. Wrapping A2:2 inside an ARRAYFORMULA that touches the entire range can force evaluation across thousands of empty cells. In a model with multiple ARRAYFORMULA references to open-ended row ranges, you'll notice recalculation lag.
The practical rule: use A2:2 in SUMIFS, SUMPRODUCT, and SUM. Avoid it inside ARRAYFORMULA when a bounded range will do. If you know your model caps at column Z (26 columns) or ZZ (702 columns), write A2:Z2 or A2:ZZ2 explicitly. You get the same dynamic behavior for any realistic model size, with a fraction of the evaluation cost.
According to Google's Sheets documentation (as of 2026), the cell limit per spreadsheet is 10 million cells. A single A2:2 reference touches roughly 1.8% of that cap per row referenced. Put 20 of them in a model and you're consuming 36% of your cell budget on references alone - before any data.
Practical Pattern: Multi-Tab Revenue Bridge
Here's how A2:2 earns its keep in a real quarterly board pack. Three tabs: Assumptions, P&L, Summary.
The Assumptions tab holds period labels in row 2 (Q1 2025, Q2 2025, etc.) and revenue growth rates in row 8.
The P&L tab references those assumptions:
='Assumptions'!B8:8 * 'P&L'!B7:7
Wrapped in SUMPRODUCT for safety:
=SUMPRODUCT(
('Assumptions'!B2:2=Summary!$B$1) *
('P&L'!B7:7)
)
This pulls revenue for whatever period is in Summary!B1. When Q3 closes and gets added as a new column in both tabs, every formula on the Summary sheet already covers it.
The open-ended row range makes the model forward-compatible by default, not by accident.
A Gotcha With HLOOKUP and MATCH
When using A2:2 as the lookup array in HLOOKUP or as the search range in MATCH, the function scans until it finds a match or hits an empty cell - depending on whether you're doing approximate or exact match.
=MATCH(Assumptions!$B$1, 'P&L'!B2:2, 0)
Exact match (0) will scan the full range until found or returns #N/A. Approximate match (1 or -1) requires the range to be sorted and will stop at empty cells, which can return wrong results if there are gaps in your period headers. For period-column lookups, always use exact match with open-ended row ranges.
For cross-tab SUMIFS using open-ended row ranges as the sum range, the matching criteria range needs to cover the same dimensions. Keep them in sync:
=SUMIFS(
'P&L'!B7:7, -- sum range: open-ended row
'P&L'!B3:3, "Actual" -- criteria range: same row structure
)
Both ranges need to be the same shape. Mixing B7:J7 (fixed) with B3:3 (open-ended) won't error, but if the model grows past J, the SUMIFS silently drops the new columns. Either make both open-ended or both bounded.