Your scope of work doesn’t only live inside Eano. Sometimes you need it on paper, tacked up in the trailer. Sometimes you need it in a spreadsheet so you can sort it, total it, or line it up next to numbers from somewhere else.

The Export button on the Scope tab does both. Click the button itself and you get the polished PDF. Click the small arrow beside it and you can choose Export PDF or Export CSV — CSV being the plain spreadsheet format that Excel, Numbers, and Google Sheets all open natively.

The PDF is the presentation copy: clean, formatted, and ready to hand to a client or a crew lead. It’s the right choice when the scope needs to look finished.

The CSV is the working copy. It’s just rows and columns, which means you can do whatever you want with it — sort it by cost type, drop it into a bid comparison, filter out one trade, add your own columns, or print a bare-bones checklist for the job site. Nothing fancy, and that’s the point.

1. Open the project or opportunity and go to the Scope tab.

2. Find the Export button in the row of controls just above the scope table. It sits between Project Template and, on signed jobs, Add Change Order.

3. To get the PDF, just click Export. The PDF opens in a new tab and you can save or print it from there — no menu needed.

4. To choose a format, click the small arrow on the right edge of the button. A short menu opens with two options: Export PDF and Export CSV. Pick one and your file downloads.

That’s the whole flow. There’s nothing to configure and nothing to wait on.

The spreadsheet mirrors the scope table on your screen, top to bottom, with eight columns:

Everything comes out as a flat list of rows in the same order you see them. Your subproject names, your group names, and your line items each get their own row, with the name in the first column. The very last row is Project Total.

A few things you’ll notice when you open it:

Headers and groups are just rows. A group like “Kitchen” comes out as a row with only a name on it, then its line items follow underneath. There’s no indenting or bolding — CSV files can’t carry formatting. If you want the hierarchy to look like a hierarchy, add it yourself in the spreadsheet once it’s open.

Collapsed groups export the way they display. If you’ve set a group to show one total instead of itemized prices, the group row carries the total and each item beneath it reads Included in the Amount column — exactly what your client would see. Bundled standard services work the same way, under a Standard Services row.

Subproject headers don’t carry a total. On screen a subproject like “Kitchen” shows its rolled-up amount on the header row. In the CSV that name comes across but the Amount cell is left empty, because the numbers underneath it already add up to the same thing — totalling a column in your spreadsheet would count that money twice. The only total in the file is the Project Total row at the bottom.

Amounts are plain numbers. No dollar signs and no thousands separators, so 2000.00 rather than $2,000.00. That’s on purpose: your spreadsheet reads them as numbers you can sum, sort, and chart straight away instead of as text you’d have to clean up first. Format them as currency in the spreadsheet if you want the symbols back.

Client-selectable work is flagged. Anything inside a subproject you’ve marked Optional gets a yes in the Optional column. Everything else gets no, and header and total rows leave it blank.

Selections get a label of their own. Where you’ve grouped line items into a pick-one selection, the group comes out as a row named Selection: [your group name] with the options listed under it.

Markup comes out the way you entered it. A percentage reads like 15%, a per-unit dollar markup reads like $25/ea, and a flat dollar markup reads like $300. Zero markup leaves the cell empty.

Lump-sum lines stay lump sums. If you priced a line as a single total rather than quantity times unit cost, only the name, cost type, and amount come across. The quantity and unit-cost cells stay empty rather than showing made-up numbers.

The file saves as Scope_[project address]_[date].csv, so exports from different jobs and different days don’t overwrite each other in your downloads folder.

You can export at any stage. Estimating, quote sent, contract signed, project started — the Export button is there the whole way through. Once you start a project the scope locks for editing, but pulling a copy of it out still works.

You need at least one scope item. The controls row that holds the Export button only appears once there’s something in the scope. On a brand-new opportunity with an empty scope, build a line or two first.

Treat the CSV as internal. Unit costs and markup come out in the file even when you’ve hidden those columns from your client on screen. The PDF respects your client display settings; the CSV is your own full view of the job. Give it a look before you forward it to anyone outside your team.

If your role can’t see project finances, the money columns come out blank. Names, cost types, quantities, and units still export — unit cost, markup, and amount don’t. That’s the same rule that governs what you see on screen.

The CSV won’t be pretty, and that’s deliberate. No colors, no bold headers, no merged cells. A CSV is plain text by definition. If you want a formatted spreadsheet, open the CSV and save it as an Excel file, then style it however you like.

It opens cleanly in any spreadsheet app. The file is written so accented characters and non-English text come through correctly rather than turning into gibberish — a common annoyance with CSVs from other tools.

Photos and product details aren’t in the CSV yet. Extra fields on a line item like seller, brand, or photos — the ones that make finishes show up as cards for your client — aren’t part of the export. If you need those, use the PDF.

CSV export is on web and desktop. The Eano Pro mobile app can export the scope as a PDF, but the CSV option lives on the web and desktop app.

How do I export my scope of work to Excel? Go to the project’s Scope tab, click the small arrow next to the Export button, and choose Export CSV. Double-click the downloaded file and Excel opens it. From there you can save it as a proper .xlsx workbook if you want to format it.

Can I export the scope after the contract is signed? Yes. The Export button works at every project stage, including after signing and after you’ve started the project. The scope itself is locked for editing at that point, but exporting it isn’t affected.

Where is the Export button? On the Scope tab of any project or opportunity, in the row of controls directly above the scope table, next to Project Template. If you don’t see that row at all, your scope is still empty — add a line item and it appears.

Can I get a spreadsheet of my estimate instead of a PDF? That’s exactly what Export CSV is for. Same scope, same numbers, just rows and columns you can work with instead of a finished document.

Does the CSV include my markup and costs? Yes, as long as your role can see project finances. Both the unit cost and the markup come out in their own columns, even if you’ve hidden them from the client on the quote. Keep that in mind before sharing the file.

Why is the amount blank on my group and subproject rows?

Those are header rows, and they’re deliberately left empty so a column total in your spreadsheet doesn’t double-count. The line items below them carry the money, and the last row of the file gives you the Project Total. The one exception is a group you’ve collapsed to a single price — that row does carry its total, and its items read Included instead.

Can I choose which columns to export? Not right now — the CSV always contains the same eight columns. Deleting the ones you don’t want takes a second once the file is open, and we’d rather give you everything than make you re-export because something was missing.

Why does my group name have a row with nothing else on it? That’s the group header. CSV files can’t show indenting or nesting, so a group comes out as its own row with just the name, and the items inside it follow on the rows below.

Can I export the whole company’s scopes at once? No — the export is per project. If a bulk export of scopes across jobs would help you, let us know what you’d do with it; that kind of request is how features like this one get built.