1
00:00:00,080 --> 00:00:04,077
The Item, Owner, and Status columns in the workshop checklist have

2
00:00:04,077 --> 00:00:06,985
uneven widths, making the table hard to scan.

3
00:00:06,985 --> 00:00:10,619
Google Docs can distribute the columns with one table action.

4
00:00:10,619 --> 00:00:14,616
First note the Badge and Printed map row values, then equalize

5
00:00:14,616 --> 00:00:18,614
the layout and check that every value stayed in its original

6
00:00:18,614 --> 00:00:21,157
cell, even if the longer label wraps.

7
00:00:21,757 --> 00:00:25,806
Start with a three-column fictional checklist: Item, Owner, and Status.

8
00:00:25,806 --> 00:00:29,855
Record the two rows before changing layout so a visual fix

9
00:00:29,855 --> 00:00:32,432
cannot hide a moved or deleted value.

10
00:00:32,432 --> 00:00:36,481
In the sample, Badge belongs to Ari and is Ready, while

11
00:00:36,481 --> 00:00:39,426
Printed map belongs to Blair and is Pending.

12
00:00:40,026 --> 00:00:44,093
Place the pointer inside the intended Google Docs table, not a

13
00:00:44,093 --> 00:00:48,160
paragraph beside it or a different table farther down the page.

14
00:00:48,160 --> 00:00:51,488
Right-click within a cell to open table actions.

15
00:00:51,488 --> 00:00:55,555
The official Docs help identifies Distribute columns in this menu for

16
00:00:55,555 --> 00:00:57,774
making all columns the same size.

17
00:00:58,374 --> 00:01:01,801
Choose Distribute columns and observe the three vertical boundaries.

18
00:01:01,801 --> 00:01:06,371
This is a layout operation rather than a data sort or merge.

19
00:01:06,371 --> 00:01:10,560
Do not use Distribute rows when the problem is horizontal widths,

20
00:01:10,560 --> 00:01:14,749
and do not drag each boundary by hand unless a specific

21
00:01:14,749 --> 00:01:16,273
custom width is required.

22
00:01:16,873 --> 00:01:20,991
After equalizing widths, a longer phrase such as Printed map may

23
00:01:20,991 --> 00:01:22,863
wrap to a second line.

24
00:01:22,863 --> 00:01:25,858
That is expected when the cell becomes narrower.

25
00:01:25,858 --> 00:01:29,976
Read the entire text in each cell and adjust the table

26
00:01:29,976 --> 00:01:34,094
or page only if the final layout becomes unusable; do not

27
00:01:34,094 --> 00:01:35,966
interpret wrapping as missing content.

28
00:01:36,566 --> 00:01:41,697
Compare the left, middle, and right columns and then re-read both fictional rows.

29
00:01:41,697 --> 00:01:45,728
Item must still pair Badge with Ari and Ready, and Printed

30
00:01:45,728 --> 00:01:47,561
map with Blair and Pending.

31
00:01:47,561 --> 00:01:51,592
If a value moved, undo and inspect the selected table before

32
00:01:51,592 --> 00:01:53,058
repeating the layout command.

33
00:01:53,658 --> 00:01:57,905
The Item, Owner, and Status columns now have equal visual width.

34
00:01:57,905 --> 00:02:02,153
Badge still belongs to Ari with status Ready, and Printed map

35
00:02:02,153 --> 00:02:04,856
still belongs to Blair with status Pending.

36
00:02:04,856 --> 00:02:08,717
A wrapped cell is acceptable when all text remains visible.

37
00:02:08,717 --> 00:02:12,965
Compare both rows against the original values before calling the layout

38
00:02:12,965 --> 00:02:16,826
fixed; column width alone does not prove the contents survived.