Tables

Tables in Docs lay out information in a grid of rows and columns, ideal for comparisons, schedules and structured lists, with control over borders, cell colour, merging and alignment to keep the layout clean.

8 min read · 8 cards · 2 checks

Read in: English · हिन्दी · ગુજરાતી


Theory

Who does what, by when?

Priya's team needs a clear 'responsibilities' section in the report: each member, their task, and the deadline. Written as sentences it is a muddle; the eye cannot line up who-does-what.

This is what a table is for: a grid that aligns related pieces of information into rows and columns, so comparisons read at a glance.

Docs makes tables easy (Insert > Table). This short lesson covers building and tidying them, and, importantly, when a table is the right tool versus when you actually need a spreadsheet. Structure the right things in a grid, and the report reads cleanly.

Theory

A timetable, not a paragraph

Imagine your class timetable written as a paragraph: 'On Monday first period is Maths, then Physics...'. Painful to read. As a grid (days across, periods down) it is instant. Tables do exactly that for any information with a repeating structure, members and tasks, items and prices, options compared on features. When data has natural rows and columns, a grid beats prose every time.

Follow along

Build a responsibilities table

  1. Insert > Table, pick the size (e.g. 3 columns x 5 rows) Columns for Member, Task, Deadline.
  2. Type the header row, then fill each member's row Bold the header row for clarity.
  3. Right-click to add or delete rows/columns as needed The table grows with the team.
  4. Format: shade the header, set borders and alignment A tidy grid reads at a glance.

Quiz

The team's survey has 200 responses they need to total and average. Should this go in a Docs table or a Google Sheet?

  1. A Google Sheet, it is data to CALCULATE on, which tables in Docs cannot do
  2. A Docs table, tables can compute sums
  3. Either, they are identical
  4. A drawing
Show the answer

A Google Sheet, it is data to CALCULATE on, which tables in Docs cannot do

A Docs table is for layout, presenting small, structured content neatly, but it cannot calculate (no SUM, no AVERAGE). 200 responses that need totals and averages belong in a Google Sheet, which is built for computation. Use a Docs table for a tidy responsibilities grid; use Sheets for anything you compute on. Knowing this table-vs-spreadsheet boundary is the key judgement.

Think first

Table or paragraph?

Priya is unsure whether to put the project's 'background and motivation' section in a table or as normal paragraphs. Which fits, and what is the general rule?

Show the answer

Paragraphs. 'Background and motivation' is flowing prose, an argument that reads sentence to sentence, with no repeating row/column structure. A table would fragment it awkwardly. General rule: use a table when the information has a repeating structure to align (members/tasks, items/prices, options/features); use paragraphs for narrative and explanation. Match the layout to the shape of the content.

Watch out

Where marks leak

Expecting a Docs table to calculate, it is for layout, not computation (use Sheets for maths). Forcing prose into a table (paragraphs suit narrative). And not knowing the formatting controls (merge cells, cell colour, borders, add/delete rows via right-click). The exam point: tables organise structured, comparable content; spreadsheets handle data you compute on.

Theory

The document is nearly ready, now share it

With structure (headings), visuals (images, charts) and neat tables, Priya's report looks professional. But a group project's whole point is that the team works on it, so the crucial question arrives: who is allowed to view, comment on, or edit it? That is the next lesson, and the single most important cloud-collaboration skill: sharing modes and permissions.

Summary

Key takeaways

  • Insert > Table creates a grid (rows x columns) for structured information.
  • Format tables with header shading, borders, cell colour, merging and alignment; add/remove rows via right-click.
  • Use a table for repeating, comparable structure (members/tasks, items/prices), not for flowing prose.
  • Docs tables are for LAYOUT, not calculation, use Google Sheets for data you compute on.
  • Match the layout to the content's shape: grid for structure, paragraphs for narrative.
  • Memory hook: a timetable grid, not a paragraph.

Study this properly

This page is the lesson to read. In Gri-Learn the same topic is a graded deck: the self-checks are scored and your weak topics are tracked. Free to start.

Start this topic

Already have an account? Sign in

More from Google Docs

Gri-Learn · syllabus-mapped B.C.A. lessons in English, Hindi and Gujarati

Tables · Fundamentals of Google Cloud Application (SEC-01 option B) · Gri-Learn