Your project budget is only useful if the right person can open it on their device and know which numbers are the latest. Today you'll learn the three spreadsheet formats people actually send each other, and how the cloud quietly saves every version of your work so a mistake is never permanent. These are small habits that save you real time when someone says the numbers don't match, or when you hit delete on the wrong row.
Imagine you email your project budget to someone at a work placement. They open it on their phone and the columns run off the screen, numbers are unreadable. Which format would have shown them a clean, printable copy? Why didn't the .xlsx behave the same way?
Four ideas sit behind every save, export, and rollback you'll do in this lesson. Read through the table and notice the third column, which shows where each one lands in your own project.
| Concept | Why it matters | Example |
|---|---|---|
| .xlsx — the native spreadsheet format. Keeps formulas, multiple sheets, formatting, and column widths. | If the reader might want to change a number and see totals update, they need the live formulas. | You send {{code:05_project_budget.xlsx}} to your placement supervisor so they can try a different price and see the total change. |
| .csv — a plain-text file: one row per line, values separated by commas. No formulas, no formatting, no multiple sheets. | Most databases, accounting tools, and import screens only accept CSV, because it's the simplest possible data format. | A local charity's donation tracker only accepts CSV uploads, so you export your contact list as .csv before uploading. |
| .pdf — a fixed-layout file that looks identical on every device and isn't easily edited. | Useful when you want someone to read your work without changing it, like a finished proposal or a report. | — |
| Version history — a running log the cloud keeps of every significant save, with timestamps. | Lets you recover from a mistake without a separate backup file and without saving v1, v2, v3 copies everywhere. | — |
A change log is one or two visible lines at the top of your sheet saying what changed and when, so whoever opens it can tell instantly whether they're looking at the latest numbers. You'll add one to your own budget later in this lesson. A usable entry looks like: 2025-02-14 — added transport cost (€45), updated total. Keep it one line. Keep it at the top of Sheet1 so nobody has to hunt for it.
You'll build a small sample spreadsheet, delete something important on purpose, and use version history to bring it back. Then you'll export the fixed sheet in all three formats. Practising on a sample sheet first means you're not risking your real project budget.
| Issue | Solution |
|---|---|
| I can't find Version History | Excel Online: {{menu:File -> Info -> Version History}}, or click the filename at the top of the window. Google Sheets: {{menu:File -> Version history -> See version history}}. A pane must open on the right. If nothing happens, check you're signed in and the file is saved to the cloud, not on your computer. |
| I restored the wrong version and now the SUM is missing again | Open version history again. Your "wrong restore" is now itself a version in the list, so you can jump back past it to a version from before the deletion. You cannot permanently lose a good version by restoring. |
| The .csv looks wrong, numbers are in odd places or formulas have vanished | This is expected. CSV is plain text with no formulas and no multiple sheets. Only the currently active sheet is exported, and every formula is replaced by its computed value. |
| The .pdf cuts off the right-hand columns | Before exporting, change the page to landscape or "Fit to width". Excel Online: {{menu:File -> Print -> Page setup}}. Google Sheets: the export dialog has a Landscape option and a "Fit to width" toggle. |