Tab prefixes
DB_Sales, DB_Products, RPT_Dashboard, REF_Countries keep the tab bar scannable after months of growth.
Naming conventions are agreed rules for files, tabs, columns, and named ranges so anyone can guess where data lives. Good names reduce VLOOKUP errors, make IMPORTRANGE links obvious, and stop duplicate Dashboard (2) tabs from spreading across your Drive.
Adopt naming rules before three people touch the same template: client workbooks, company ops files, course templates, or any sheet that will be duplicated monthly.
Skip heavy rules for a personal scratch pad you delete in a week. The cost of documentation should match how long the file will live and how many hands touch it.
{:"Prefix tabs by role"=>"DB_, REF_, RPT_, or INPUT_ so sort order groups related sheets."}
Use snake_case or Title Case consistently for column headers; never change spelling mid-year.
{:"Include ISO dates in file names for snapshots"=>"ClientAcme_2026-07-21_export."}
Name ranges after headers (tblOrders, cfgTaxRate) for formulas readable in audits.
Document the convention on a README tab with one example row and forbidden patterns.
When renaming, search formulas for old tab names with Ctrl+F before you announce the change.
DB_Sales, DB_Products, RPT_Dashboard, REF_Countries keep the tab bar scannable after months of growth.
order_id, customer_email, created_at instead of ID, Email2, Date fixed, so QUERY and SQL exports align.
Tracker template v3 in Drive with changelog note; copies rename to ClientName_Tracker_v3_2026Q3.
Build this without starting from a blank cell
Use a Better Sheets tool for naming conventions, then watch a walkthrough when you want the full pattern.
Watch how naming conventions works
Guides that explain naming conventions in more depth.
Users can also customize the appearance of their spreadsheets with different fonts, colors, and themes.
Read post →I’ve been using 1-cell sheets for a while now. And I use 1 column sheets too. Or 2 column sheets. So here are the reasons I use it and can imagine you can use little, tiny, small sheets too.
Read post →Introduction to Tiny Sheets a free google sheet add-on to make tiny spreadsheets. Delete unnecessary rows and columns easily.
Read post →A tracker is a living list you update over time: tasks, leads, inventory, habits, or bugs. Good trackers use one row per item, clear statuses, and columns that sort and filter without cleanup scripts. They often feed a dashboard tab when the team outgrows scanning raw rows.
Read guide →A workflow is the path work takes through your sheet: intake, review, approval, done. Good workflows use consistent columns, statuses everyone understands, and just enough automation to move tasks forward without hiding steps from the team.
Read guide →KPI tracking means choosing a small set of numbers that show whether you are winning, then updating them on a rhythm everyone trusts. In Sheets, each KPI usually has a definition, data source, target, and actual cell on a dashboard fed by formulas, not hand-typed guesses.
Read guide →Protection limits who can edit specific cells, ranges, or entire tabs while others keep view or comment access. It is how you let teammates update input columns without touching formula blocks, summary rows, or archived data. Protection is not encryption; owners and editors with rights can still adjust protections.
Read guide →Done reading about naming conventions?
Membership unlocks 636+ tutorials, unlimited generators, and every template. Practical lessons. Zero fluff.
Need this once
Jump to a free tool or a single tutorial for this topic.
Learning Sheets for real
Unlock the full library, generators, and templates with membership.