Contrast that survives paper and projectors
Contrast is the difference between the ink and the surface behind it. On your laptop, in a dim room, a medium gray can look elegant. On a photocopy, in a hallway, it becomes a smudge. The low-contrast warning exists for this gap. When it appears, change the pair before you debate taste. Dark text on a light body is the combination that fails the least often. Light text on a dark header is the combination that makes the header findable. Those two can coexist because header fill and header text color are separate from body fill and body text.
Build a personal palette of three roles and stop. Role one is header surface and header letters. Role two is body surface and body letters. Role three is a single exception, used on few cells, still dark-on-light or light-on-dark. A stripe is not a fourth idea. It is a slight variant of the body surface so rows stay trackable. If your stripe could be mistaken for the exception color, the code is broken. A reader should describe the exception in words ("the blue row is the field trip") without also describing every other band as meaningful.
Test the way the object will be seen. If it will be projected, step back from the monitor or zoom out until the type is as small as it will be in the room. If it will be printed in black and white, export a PDF and print one draft copy, because a blue header and a navy stripe can collapse into one gray bar. If it will be a JPEG in a chat, send it to yourself and open it on a phone in daylight. Daylight is where thin yellow type goes to disappear. The warning on the editing screen is necessary and not sufficient. Your second look is part of the tip.
Never encode a status only as color. Write Present, Late, or Missing. Then, if you want, tint the row. A color-blind colleague, a grayscale print, and a hurried reader all get the word. The tint is a courtesy after that, not the carrier of the fact. This is the contrast tip that has nothing to do with the warning light and everything to do with whether the table still works when the color is gone.
Alignment and the edge the eye uses
Readers return to an edge. For words, that edge is the left side of the column. For numbers, it is the right side, where ones, tens, and hundreds line up. Pick the edge that matches the content and use it for every cell in the column, including the header if you can. A centered header over right-aligned prices is a small vanity that makes the column harder to associate. Center is justified for a column of single marks and almost nowhere else.
Names with uneven length will look ragged on the right. That is correct. Do not center them to "balance" the rag. The rag is information: it tells you the names are names. A centered name column produces two rags and no reliable return edge. The eye bounces. In a gradebook, bounce is how a score gets attached to the wrong student even when the digits themselves are aligned.
Numeric alignment still wants consistent precision. If you paste 4.5, 4.50, and 4.500 in one column, right alignment cannot save the meaning. Decide on the precision in the source, or retype the column so every price has the same number of decimal places. Tabley will not round for you. Mono font plus right alignment is the combination for codes and for figures that must be compared character by character. Sans plus right alignment is enough for ordinary money. Serif plus right alignment can work on a formal sheet, but check that the digits do not look like they are dancing. If they dance, switch the table to sans or mono for the sake of the column that matters most.
Text that is a sentence does not belong in a narrow centered cell. If a note is a sentence, give it a wide notes column aligned left, or put one sentence in the caption if it applies to the whole table. Shift+Enter can break a sentence across lines inside the cell. That is better than squeezing, and worse than a cleaner column structure. Prefer the cleaner structure when you still have columns to spare.
Headers, scanning, and the one-question test
Before you decorate, finish this sentence: "Each row is one ____, and the columns tell me ____." If you cannot, the table is two tables sharing a border. Split them. A research log that mixes equipment checkout with experimental means will confuse both the lab manager and the reader of the paper. Two short tables, each with a title, scan faster than one wide compromise.
Headers should be short enough to read without wrapping onto three lines, and specific enough that two columns could not swap names unnoticed. "Info" and "Details" are failures. "Room" and "Form still needed" are successes. If a header wraps, try a smaller phrase before you shrink the whole table's type. Wrapping headers are sometimes unavoidable in a gradebook with long assignment titles. In that case, keep body type comfortable and let the header wrap, rather than abbreviating the assignment into a code only you remember. A caption can expand a single unavoidable abbreviation. It should not be a glossary for every column. A glossary means the headers are not doing their job.
Scanning is vertical for comparison and horizontal for one record. Stripes help vertical scanning. Generous padding helps horizontal scanning, because the eye must travel across the row without slipping to the next. If the table is a roster you read one person at a time, roomy or normal padding beats a dense stripe. If the table is a price list you compare down a column, a stripe and compact padding may be better. Choose for the motion the reader actually makes. When both motions matter, as in a gradebook, use both a header on each axis and a restrained stripe, and keep padding at normal unless the printout is crowded.
Blank cells need a policy, stated once. A blank in a habit tracker can mean "not yet." A blank in a contact list can mean "we do not have a phone number," which is different from "this person must not be called." If the difference matters, write a mark such as n/a or unknown, and mention it in the caption. Do not leave readers to treat empty as zero. In a budget, empty and zero are different stories. Type the zero.
Mobile editing without losing a column
A phone can run the same maker as a desk. The grid limits do not shrink. Your precision does. Edit on a phone in passes. First pass: open a template or set the size, and fix headers. Second pass: type or paste values. Third pass: alignment, stripe, and header colors. Fourth pass: export the picture or PDF you need to send. Mixing passes is how a thumb deletes the wrong column while you meant to change a fill.
Zoom with the browser if a cell is hard to place, then zoom back out before you judge the whole table. Selection is everything. Before remove-row or remove-column, read the selected cell's contents aloud in your head. If it is not the row you mean, move the selection. Undo exists for the moment after a mistake. It is a poor plan for the moment after you have also made five more edits.
Wide tables scroll sideways. A reader on a phone may never see column twelve. Put the identifying field first: name, item, time, or task. Put the decision field next: status, price, room, or score. Put notes last. If a middle column is the one that matters, you have designed for a desktop. Either accept that and say so when you send the file, or reorder while you still can by rebuilding the columns. The editor adds columns beside the selection. It does not drag a whole column to a new index in one gesture. When order is wrong, it is often faster to paste the block into a spreadsheet, reorder there, and paste back into the top-left cell, than to rebuild by retyping. That round trip is a mobile tip as much as a desktop tip, because a phone is a bad place to retype twenty names.
Full width on a small screen does not remove the need for fewer columns. Stretching a six-column schedule can be right. Stretching twelve sparse columns makes each word a fragment. Drop stretch if the phone preview looks like a fence of borders with one letter in each gap. Compact padding helps a phone more than it helps a printed poster. If the same file must serve both, prefer the print, and send the phone a simpler table or a JPEG of the printed layout rather than the editable wide grid.
Shared phones have the same privacy shape as shared laptops. The draft sits in that browser. Export and clear site data if the next person should not see the cells. There is no account to log out of. The privacy page is the longer version. The short version, while you are standing in a hallway, is: send the file, then do not leave the roster on the screen.
Printing and the proof copy
Print with an opinion about paper. A weekly schedule on a door wants large type, solid borders, a dark header, and margins the printer will not eat. A meeting agenda in a packet can be smaller and still be kind. Use the print control when you want the browser's print dialog, and use PDF when you want a file that looks composed before it reaches a printer. Either way, print one proof if more than one person will rely on the page.
Look for clipped text. A cell that looked fine while you scrolled may wrap differently on paper, or a caption may sit too close to the edge. Look for color that became gray. Look for a stripe so light it vanished, or so dark it printed as a second header. Look for a title that says the week and a grid that still says the previous week because you edited one and not the other. The proof is where those twins are caught.
If the printer is black and white, choose contrast as if color did not exist, because it does not exist on that device. A dashed border may print more faintly than a solid one. Prefer solid for anything read at a distance. Border weight that looked delicate on a retina display can disappear on a school copier. Slightly heavier is safer than hairline.
Page breaks are the printer's business as much as the editor's. A very tall 40-row table may split across pages. Repeat the understanding in the caption if a second page could be found alone ("page continues, names are in the first column"). You cannot freeze a header on every printed page the way a spreadsheet can. If a split would confuse people, make two shorter tables with the same headers and two titles, such as "Roster A–M" and "Roster N–Z," and print both. That is a better use of the row limit than one fragile scroll.
JPEG and PNG are not prints, but they are often what gets printed later by someone else. Assume a screenshot-like life. Large type, solid borders, and a caption that includes the date will still make sense when the image is dropped into a slide and then printed from the slide. A delicate dotted grid will not.
Pasting from Excel or Google Sheets
Paste into the selected cell, with that cell as the top-left of the landing zone. In the spreadsheet, copy only the rectangle you mean, not an entire worksheet with years of empty formatted columns. Empty copied columns still occupy Tabley's twelve-column budget and push real fields off the edge. If the paste surprises you, undo, clear the destination area if you need a clean pad, select the corner cell, and paste again.
The landing is text. Formulas stay behind as their displayed values if the spreadsheet copied values, or as text of what was on the clipboard. Colors, data bars, and comments do not become Tabley fills. Bold in the source does not become bold here. Plan a few minutes of restyling instead of feeling cheated. The point of the paste is to avoid retyping names, not to move a workbook's theme.
Watch commas, quotes, and line breaks. A CSV import and a clipboard paste are different doors. If a file mis-splits, the usual cause is a comma inside a name or a quote that was not doubled the way CSV expects. The practical fix is often to paste from the spreadsheet's own copy, which is tab-separated, rather than to wrestle a fragile CSV. When you must use a file, open it once in the spreadsheet, confirm the columns, and copy from there. Inventing a cleaner export from the source system is better than repairing thirty shifted rows by hand.
After the paste, set header mode deliberately. If the first pasted row is the field names, top-row header is appropriate. If you pasted only body rows under headers you had already typed, do not include a second header from the sheet. Duplicated headers are a scanning failure that looks like data. Delete the extra row.
Then align numeric columns right and word columns left. Then run a case change only if the source was uniformly wrong, not as a reflex. Then spot-check row count against the source. If the source had 45 data rows, Tabley kept at most 40, and you need a policy for the missing five: a second table, a tighter filter in the spreadsheet, or a decision that the printed list was always going to be the first 40. Do not discover the missing five after the list is on the door.
Copy as tab-separated text to go back. Paste that into the sheet. Confirm you did not overwrite a formula column you meant to keep. The safest round trip uses a blank area of the sheet as the landing zone, then you move values with the spreadsheet's own tools. Tabley will not protect the workbook. It only gives you the text.
Research tables
A research table is a claim with its evidence arranged so a reader can check the claim. The row is usually a condition, a source, a specimen, or a participant group. Columns that earn their place include an identifier, the condition or source, the count, the result, and a note for caveats. Columns that usually do not earn a place in the printed table include the researcher's mood, the file path on a laptop, and a full abstract. Those belong in a notebook. The table belongs on the page where someone decides whether the result is believable.
Use the research template as a skeleton, then rename the columns to the words your field actually uses. Right-align counts and means. Use mono if identifiers are easy to transpose, such as sample codes that differ by one digit. Put units in the header or the caption, not in every cell ("Mean (cm)" once, rather than "14.2 cm" twenty times), unless a column mixes units, in which case you should split the column until it does not mix them. Mixed units are how tables lie by accident.
Notes are for exceptions: a dropped trial, a broken sensor, a source that uses a different definition. They are not for the entire interpretation. If the note cell becomes a paragraph, the paragraph wants to live in the paper, and the cell should keep a short pointer such as "sensor replaced, see methods." Shift+Enter can hold two short lines. It should not hold a literature review.
Stripes help when many conditions look alike. A strong fill on a single row is appropriate for the result you want a discussant to see first, and inappropriate for every row that you personally find interesting. One highlighted finding plus a caption that states the comparison ("Treatment A minus control") is more honest than a heatmap you built by hand without a scale. Tabley will not compute a heatmap. Do not fake one with six unrelated greens.
Export PDF for the appendix the reader sees. Export CSV for yourself if you will rebuild the table next week after new data. Keep the calculation workbook as the source of the means. When a figure changes, paste values again rather than editing digits in two places and hoping they match. The table is a view. The view can be beautiful and still be a copy. Treat it as a copy.
For a class assignment, include the minimum context a marker needs without opening your files: course or experiment name in the title, date or trial id in the caption, and column names that match the words you used in the prose. A table that says "C1, C2, C3" while the essay says "control, warmed, cooled" forces the marker to translate. Translation is where grades and understanding both leak. Spell the conditions.
Schedules people can follow on a Tuesday morning
A schedule answers when, where, and who, in that order of visual priority. Hours or blocks down the first column and days across the top is the weekly pattern, with both headers on. The corner cell should say Time or Block, not the name of the school in eighteen-point pride. The school can live in the title. The cell should orient the grid.
Write events in the language a substitute uses. "Reading groups" is better than a nickname. If a room changes, put the room in the cell with Shift+Enter only if most cells do not need a room. If every event has a room, add a line in the caption ("all events in Room 12 unless a cell says otherwise") or build the room into the event name. A second table for rooms is better than a twelve-column monster that tries to be a calendar and a facilities database.
Color means conflict or exception, not decoration. One fill for "covered by a substitute" is enough. Do not give each subject a private brand color unless the audience is young children who already learned those colors as a code, and even then write the subject name. The low-contrast warning still applies to a cheerful elementary palette. Yellow blocks with white type are a common failure. Dark type on a light tint keeps the cheer and the letters.
Time labels should be consistent. Do not mix "9:00", "9am", and "nine" in the stub. Pick one form. Align the stub left or right as a column of times, and use mono if you want the colons to line up. Include a break row if the day has a real break, and leave it visually quieter rather than filling it with a joke. The joke will be unfunny by November. The break will still matter.
Update by replacing words, not by stacking corrections in the caption. "Ignore Wednesday, see Friday" means the grid is lying. Change Wednesday. Then export a new PDF and take the old one off the door. Dates in the title are how two printouts can be told apart when both are still in a staff room. A schedule without a date is a rumor.
On a phone, a weekly grid of six columns is usable if the type stays large and the events stay short. A grid that also tries to hold learning objectives in every cell is not a phone schedule. Put objectives in a second table, one row per subject, and let the weekly grid stay scannable. Two tables are not a failure of planning. They are the plan.
When to stop
Stop adding columns when you cannot say which decision the new column changes. Stop adding color when you cannot name the role of the new color in one sentence. Stop shrinking type when you would not read it yourself at the distance the audience uses. Stop polishing the browser draft and export when the proof copy matches the question the table was for. The draft in local storage is scratch paper. The PDF, the print, the HTML, or the spreadsheet file is the thing other people will live with.
If a tip and a real audience disagree, follow the audience. A warehouse label that staff already know as a short code may beat a long plain-language header. A legal clinic may prefer initials to full names on a printed door list. Judgment includes knowing when a general rule is the wrong kindness. It does not include ignoring contrast, because illegible text is not a house style. It is a missing message.