THE FUTURE MARKETACADEMY
Your classroomRoom 07 · Tech Lab
School of Data & Tech

Sheets Systems: connected tools and dashboards

What you'll be able to do
  • Design a Google Sheets system with clear layers: input, data table, lists, dashboard, read me and log.
  • Turn data into Sheets tables with column types and table references.
  • Build a tracker many people can use at once, with drop-downs, checkboxes, filter views and notifications.
  • Protect sheets and ranges so the right people edit the right cells, and know what protection cannot do.
  • Build an interactive dashboard in Sheets with pivot tables, charts and slicers.
  • Connect a sheet to Data Studio (formerly Looker Studio), set data freshness and choose data credentials.
  • Keep large sheets fast, and know when to move data to a bigger tool.
  • Map, document and check a connected system so it keeps working when people change.

Before this course: Sheets Automation: array formulas, forms and Apps Script basics (course 7.2.2). You should already know ARRAYFORMULA, QUERY, a Form to Raw, Clean and Summary pipeline, simple Apps Script functions and triggers. In 7.2.2 you made one person's sheet do chores. In this course you build a system that a whole team shares, and connect it to other tools.

A note on names: Google renamed Looker Studio back to Data Studio on 10 April 2026. Existing reports and data sources moved over with no action needed. Older videos and guides still say Looker Studio. Menu names in Sheets can also change over time.

Words in this course 46Open the Vocabulary Hall
01

Design a Sheets system

In simple words

A restaurant kitchen has stations: one person takes orders, one cooks, one plates, and the manager watches the screen. Nobody cooks at the order desk. A good Sheets system also has stations, called tabs, and each tab has one job.

Key facts
  • Plan your system in layers. Each tab has one job:
TabJobWho edits it
Input (a Google Form or an entry tab)New records come inTeam members
Orders (a table)The single source of truth: one row per recordTeam, only the input columns
ListsAllowed values for drop-downs (items, staff, statuses)Owner
DashboardPivot tables, charts, slicers, key numbersNobody (formulas only)
Read me and LogHow the system works, what changedOwner
  • One row per record, one fact per column, one unique ID per row (for example ORD-001). IDs let you find, link and fix records without confusion.
  • One data type per column (all dates, or all numbers, or all text) and one header row. Other tools, such as Data Studio in Lesson 5, need this too.
  • Tables in Sheets: select a range, then Format > Convert to table. Tables apply formatting and structure for you.
  • Each table column can have a column type: Number, Text, Date, Dropdown, Checkbox or Smart chips. Column types help stop wrong data, because they report incorrect data types.
  • Table references use the table name and a column name in brackets: =SUM(Orders[Amount]). Table references update when you add or remove data in the table.
  • Table names cannot start with a number, cannot be TRUE or FALSE, cannot look like a cell address (such as A1), can be up to 255 characters, and the only special character allowed is the underscore. Spaces become underscores in formulas.
  • Rename a table from the table menu (the arrow next to the table name), Rename table.
Example (the Orders table used in this course)

A small catering business tracks orders. Prices are in your currency.

OrderIDDateCustomerItemQtyPriceAmountStatusPaidOwner
ORD-0012026-11-02CruzPancit tray24590DoneYesAna
ORD-0022026-11-03LeeLumpia box32060DoneNoBen
ORD-0032026-11-05PatelAdobo tray15555In progressNoAna
ORD-0042026-11-06KimLumpia box520100NewNoCy
ORD-0052026-11-09CruzAdobo tray255110DoneYesBen
ORD-0062026-11-10ItoPancit tray14545NewNoCy

Amount is Qty x Price. =SUM(Orders[Amount]) gives 460.

Step by step
  1. Make a new spreadsheet called Catering System and add tabs named Orders, Lists, Dashboard and Read me.
  2. On Orders, type the headers and the six rows above.
  3. Select the data and choose Format, then Convert to table.
  4. Open the table menu, choose Rename table and call it Orders.
  5. Set column types: Date for Date, Number for Qty, Price and Amount.
  6. In the Amount column, write a formula that multiplies Qty by Price for each row.
  7. On Dashboard, type =SUM(Orders[Amount]) in a cell.
  8. Check: the total is 460, and if you type text into the Qty column the table warns you.
Watch on YouTube
Structured tables for Google SheetsDavid Benaim · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01Design a Sheets system
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
Read the video script
[Host] "A system is not one big messy tab. It is stations, each with one job."
[Text on screen: Input. Orders. Lists. Dashboard. Read me.] "Input brings data in. Orders holds the truth. Lists hold the choices. Dashboard shows results. Read me explains it all."
[Screen: Format > Convert to table, column types set] "Turn your data into a table and give each column a type. Wrong data gets flagged."
[Screen: =SUM(Orders[Amount]) shows 460] "Table references read like English: the sum of Orders, Amount."
Try it now

Draw the tab plan for a system you need (a team task list, a club membership list or a shop's orders). For each tab write its job and who edits it. Then build the main data tab as a table with column types and a unique ID column.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Sheets Systems: connected tools and dashboards" on The Future Market. Lesson 1: "Design a Sheets system".

What the lesson teaches:
- Plan your system in layers. Each tab has one job:
- Tab - Job - Who edits it
- Input (a Google Form or an entry tab) - New records come in - Team members
- Orders (a table) - The single source of truth: one row per record - Team, only the input columns
- Lists - Allowed values for drop-downs (items, staff, statuses) - Owner
- Dashboard - Pivot tables, charts, slicers, key numbers - Nobody (formulas only)
- Read me and Log - How the system works, what changed - Owner

The exercise I'm working on:
Draw the tab plan for a system you need (a team task list, a club membership list or a shop's orders). For each tab write its job and who edits it. Then build the main data tab as a table with column types and a unique ID column.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "Design a Sheets system" from the course "Sheets Systems: connected tools and dashboards".

Here's what the lesson says:
A restaurant kitchen has stations: one person takes orders, one cooks, one plates, and the manager watches the screen. Nobody cooks at the order desk. A good Sheets system also has stations, called tabs, and each tab has one job.

The activity:
Draw the tab plan for a system you need (a team task list, a club membership list or a shop's orders). For each tab write its job and who edits it. Then build the main data tab as a table with column types and a unique ID column.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Open Claude
Sources
My notes
02

A tracker many people can use at once

This lesson is part of full access: every course and every level for one payment.

03

Protect sheets and ranges

This lesson is part of full access: every course and every level for one payment.

04

Dashboards in Sheets with slicers

This lesson is part of full access: every course and every level for one payment.

05

Connect Sheets to Data Studio

This lesson is part of full access: every course and every level for one payment.

06

Larger datasets and speed

This lesson is part of full access: every course and every level for one payment.

07

Map, document and check the connected system

This lesson is part of full access: every course and every level for one payment.

++

Final project

This lesson is part of full access: every course and every level for one payment.

??

Quiz

  1. What should every row in a data table have so records can be found and fixed?

  2. How do you turn a range into a table in Google Sheets?

  3. What happens by default when someone types a value that is not on a drop-down list?

  4. What is the difference between a filter and a filter view?

  5. What are the two protection options for a range?

  6. Is protecting a range a security measure?

  7. Which items does a slicer filter?

  8. What is Looker Studio called now?

  9. How often does Data Studio check a Google Sheets data source by default?

  10. What is the difference between owner's and viewer's credentials?

  11. What is the size limit for a Google Sheets spreadsheet?

  12. Why put TODAY() in one cell instead of every row?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.