Google Sheets cell limit: when to move
Practical perspective from an IT leader working across operations, security, automation, and change.
8 minute read with practical, decision-oriented guidance.
Leaders and operators looking for concise, actionable takeaways.
Topics covered
The Google Sheets cell limit sets how much a spreadsheet can hold. Google Sheets is Google's spreadsheet tool, often used to track orders, prepare reports and organise shared business information. If your staff depend on a sheet to decide what happens next, extra cells are only one part of the decision about whether it still fits the job.
A tracker with spare capacity can still send the same order to dispatch twice. A larger workbook can remain useful if its users understand the process and can check their work. Establish the operational problem before paying to replace the tool.
What Google announced
On 10 September 2026, Google announced an increase from 10 million to 20 million cells per spreadsheet, covering new, existing and imported files. Google said there was no administrator or user toggle. The announced Rapid Release rollout started on 10 September, with Scheduled Release due to start on 28 September. Each gradual rollout could take up to 15 days. Google's Sheets cell-limit announcement.
Google listed Workspace customers, Individual subscribers and personal accounts. Increased imported-file byte limits were planned separately. The cell increase therefore does not establish that every import constraint changed. It is also not a performance benchmark for your workbook. Check the relevant import requirements and test your own workload before relying on a larger file.
For a business tracker, the useful question is whether people can enter, find and act on the right records within the required time. Capacity, response time, consistent data and access are separate checks.
A fictional order tracker that still has room
Consider a fictional small parts supplier. Four office staff use a spreadsheet to record accepted orders. A dispatch supervisor checks it before preparing the day's work. Customer contact details remain in a separate existing system; the tracker contains an order reference, item reference, quantity, required dispatch date and status. It does not need to become a second customer database.
The team is not approaching its cell limit. Its problem is that a repeated request can become another row, and staff use both "ready" and "confirmed" to mean that an order may be dispatched. A missing dispatch date is sometimes treated as today's date. More cells would preserve those ambiguities.
The operations manager defines the requirement before considering a new tool. Each accepted order must have one authoritative dispatch record. A repeated request must be checked against that record. An incomplete order must remain on hold. The dispatch supervisor and a named deputy must be able to explain which orders they have approved without relying on the person who entered them.
The manager also agrees a boundary: everyone authorised to use this tracker needs to see its full contents. If future work requires different teams to see different customer information, access design must be reassessed. Hiding information in a worksheet or protecting cells must not be treated as proof that it is confidential. Google explains the limits of hiding and protecting sheets.
The failed check changes the decision
The team rehearses the proposed process with invented orders, away from live dispatch work. These results belong to the fictional example, not a test of your workbook or a claim about a client.
| Test case | Expected result | First result | Consequence |
|---|---|---|---|
| Order EX-104 appears again in a repeated request | Staff find the existing order and hold the repeat for a decision | A second row receives "ready" status | The supervisor could dispatch the same order twice |
| Order EX-105 has no required dispatch date | The record stays on hold until its owner confirms the date | Staff assume it means today | An incomplete instruction enters the dispatch list |
| The usual supervisor is absent | The deputy follows the same approval process | The deputy cannot explain whether "confirmed" authorises dispatch | Approval depends on one person's unwritten knowledge |
The operations manager rejects the process as tested. A successful summary formula or a fast-loading sheet would not change that decision. The failure concerns what staff believe the records authorise.
The manager owns the correction. The dispatch supervisor defines two explicit states for this workflow: held for clarification and approved for dispatch. The office team records the existing order reference before adding or changing an order. A repeated request goes to the supervisor, who decides whether it changes the existing order or requires no further action. Staff do not create a second dispatch instruction while that decision is unresolved.
Approval also requires a confirmed dispatch date and quantity. The supervisor records the approval decision against the order, and the deputy rehearses the same steps. These are agreed working procedures. The example does not assume a spreadsheet feature automatically prevents duplicates or enforces the procedure.
The corrected result supports a bounded choice
In the fictional retest, the repeated EX-104 request is matched to its existing record. The supervisor confirms that it adds no new instruction, so the team keeps one dispatch record and records why the repeat needs no action. EX-105 remains held until its owner supplies the missing date. The deputy can then identify the approved work and explain why EX-105 is excluded.
The operations manager accepts this corrected process for the limited tracker. The decision is to retain Sheets and introduce the agreed checks, with the supervisor responsible for the dispatch review and the deputy responsible during absence. The first review of ordinary working records is scheduled after two weeks. Staff will record duplicate requests, unresolved orders and any occasion when the manual check delays dispatch.
That acceptance has limits. The rehearsal establishes that the participants can follow the revised process with those examples. It does not establish production performance, continuous compliance with the procedure or reliable recovery from every error. Before using the revised process for live work, the supervisor must also rehearse how to resolve an accidental change against the original order instruction. If the team cannot establish the correct quantity or dispatch status, the affected order stays on hold for its owner to reconcile. No guessed correction should trigger dispatch.
A short written operating note names the tracker as the dispatch record, identifies the underlying accepted order as the source for investigating a disputed entry, and explains who approves a correction. This avoids treating an unexplained spreadsheet edit as a new customer instruction.
When a database or application would justify the work
The manager considers alternatives against the same order requirements. A database stores structured records and their relationships. Staff still need a way to use it, and someone must design the rules, access and support arrangements. A dedicated application adds an interface for the particular workflow, potentially using a database underneath. Neither choice defines the approval process on the business's behalf.
| Option | Reason to choose it for this tracker | Costs and responsibilities to include |
|---|---|---|
| Retain Sheets with the agreed process | The limited workflow is understood, everyone needs the same information, and the named team can perform the checks | Time for review, training the deputy, maintaining the record structure and investigating mistakes |
| Use a database with a suitable interface | Related records or manual consistency checks become difficult to manage within the agreed process | Data design, interface setup, migration checks, access administration, support and recovery arrangements |
| Commission a dedicated application | The business needs a defined sequence of actions or connections that the current process cannot support acceptably | Requirements, build, testing, integration dependencies, hosting, maintenance and a documented handover |
For this fictional supplier, a replacement is not yet justified. The failed checks exposed missing decisions and ownership, and the corrected rehearsal addressed them without moving records. Building an application before defining those rules would leave the builder to guess what "ready" means.
The manager will reopen the tool decision if staff cannot keep up with the agreed review, disputed records remain unresolved, different visibility is required, or new integrations change how orders enter the process. That review should compare the ongoing staff effort with the full proposed replacement cost. A build quote alone omits migration, support, training and the responsibility for keeping the system usable.
If a replacement is chosen later, identify which system is authoritative during the change. Assign someone to match transferred records against accepted orders and reconcile changes made during the transition. Agree what happens to orders entered in the new system if the team returns to the old process. Copying an older file back would not account for those later decisions by itself.
Review your own tracker before choosing a build
Bring one real workflow to the discussion, with sensitive details removed where possible. Show how a record arrives, what makes it ready for action, who can correct it and what staff do when it appears twice. Include an example that failed and the decision you could not make from the available information.
If the tracker starts with a website request, the website enquiry workflow guide explains how to establish ownership and handle incomplete or repeated submissions before they become internal work.
My web development service covers bespoke websites and business systems shaped around the work your team needs to complete. Discuss your business system with your current tools and the problem you need to resolve. We can assess the workflow, available integrations and required data before agreeing a build, its launch checks and handover. Hosting, maintenance and ongoing support need an explicit scope.
Share this post
About the author
Daniel J Glover
IT Leader with experience spanning IT management, compliance, development, automation, AI, and project management. I write about technology, leadership, and building better systems.
Continue exploring
Keep building context around this topic
Jump to closely related posts and topic hubs to deepen understanding and discover connected ideas faster.
Explore topic hubs
Related article
Google Workspace automation: controls
Google Workspace automation is gaining integration options. Decide permissions, approval boundaries and failure handling before enabling Workspace Studio tools.
Related article
SQL linked queries: test beyond restart
SQL linked queries can work after a restart and still slow down over repeated runs. Agree what evidence your business needs before accepting normal operation.
Related article
Order reconciliation after a shop fix
Order reconciliation after a shop security fix means checking payments, order changes and dispatch evidence before deciding what staff may fulfil or correct.
Related article
Remote Desktop: restore staff access
A Remote Desktop connection that works for an administrator may still fail your staff. Check the business task before accepting a security workaround.
Ready to improve your IT operations?
Request a free 30-minute consultation to discuss your IT challenges. Send a short outline and I will reply to arrange a suitable time. No obligation.
Request a free 30-minute consultationGet Occasional IT Leadership Insights
IT leadership insights, occasionally. No fluff. Unsubscribe any time.
No spam. Unsubscribe any time.