Replace Excel for FF&E schedules

If your FF&E schedule lives in a workbook, you may not need a new operating system. You may need a calmer way to collect products, keep room context and hand a schedule to the next person.

This guide is for you if you use Excel or Google Sheets alongside browser tabs, screenshots and Drive folders.

Make your product organisation less fragile.

What the spreadsheet workflow looks like today

You find a pendant on a supplier website. You copy the name into a sheet. You paste a link into another column. You save a screenshot in a project folder. Later, someone adds a price from a quote or product page.

The workbook may have tabs for each room. It may have one master tab with filters. Both can work for a while.

The trouble starts when the project grows. A link is pasted without its product context. A screenshot is saved without a source URL. A product moves rooms but stays on the old tab. A price is overwritten and nobody knows when it was captured.

Excel is not the problem by itself. It becomes difficult when the grid is also a scrapbook, a product library, a review board and a handoff document.

What a good FF&E workflow needs

For each product, capture these basics.

• Project
• Room or area
• Product name
• Supplier or maker
• Price captured at save
• Product specifications available at save
• Source URL
• Selection or review status
• Notes that affect the decision

Price and specs are captured at save. Aalto stores them when you save. You can rescrape prices on demand when you need current ones. Prices do not auto-update in the background.

Where the old workflow breaks

Context gets separated from the product. A row called chair 02 is not enough.

Room decisions become hard to review. A long master list does not show which products belong together.

Handoffs depend on memory. Missing source links create another round of questions.

Prices need a clear capture point. Show what was known at save time. Rescrape on demand when you need a current price. Prices are not continuously live.

A practical migration path

1. Choose one live project. Start with one room that has enough variety.
2. Agree on the minimum fields.
3. Triage keep, revisit and archive.
4. Save new products with price, specs and source URL at that point.
5. Build a room view.
6. Run a short QA pass.
7. Export a schedule when needed.
8. Stop and decide whether to expand beyond the test room.

How Aalto fits

Aalto is a visual workspace. Save products from anywhere. Capture price, specs and source URL at save. Store products across many projects or for future ones. Add a product once. Reuse it easily across jobs. Organise by room and project. Share boards and export schedules. It is lighter than a full practice OS such as Programa. You can rescrape prices on demand when you need current ones.

Try it on one live project

Pick one active room. Save the next five products into Aalto with source and price at save.