Most weekly reports are a spreadsheet and a chart pasted into a slide. A dashboard is the same data as cards and charts that respond when you click: choose a region, and every number on the page redraws. Claude can build one from a spreadsheet inside a chat, on the Free plan, from a single prompt.
Claude is not made by webridgeAI. What Free includes was checked on two of Claude's help pages, What are artifacts and how do I use them? and Create and edit files with Claude, on 17 October 2026. Plans and limits change, so check those pages before you rely on them.
Before you start with work data: check your company's rules before you upload anything confidential to any AI tool. Section 9 says what to look for. Use made-up numbers the first time.
1. What Free gets you
| What | What Claude's help pages say |
|---|---|
| Artifacts | "Artifacts are available on Free, Pro, Max, Team, and Enterprise plans." An artifact is the page Claude builds beside the chat, such as a dashboard or a small interactive tool. |
| Code execution | Code execution and file creation is available to all users, on by default on Free. Claude uses it to read your file and do the calculations in code. If no dashboard appears, check that it is switched on under Settings, then Capabilities. |
| Uploads | CSV and TSV files, plus "other files for data analysis and visualization". The maximum is 30MB per file. |
| Excel files | The help page lists CSV. It does not list .xlsx as an upload type, so try your Excel file and use the CSV fallback in section 2 if it is rejected. |
| The Dashboards template | Listed for Pro and above, not Free. You do not need it. It builds from connected data platforms such as Salesforce, which is different from uploading a sheet. |
| Usage | Creating files uses more of your limit than a normal chat. On Free, one strong first prompt beats ten small fixes. |
| Privacy of the result | New artifacts start private to you. |
2. Get your sheet ready
Claude can only be as clear as your data. Five minutes here saves a rebuild later.
- One table, header row first. Column names in row 1, then one row per record (a sale, an order, a ticket). No title rows above the header.
- Remove totals rows. A "Total" line at the bottom gets counted as if it were a sale.
- No merged cells and no blank rows or columns inside the table.
- Real dates and plain numbers. Dates as dates, numbers without text such as "Rs." or "units" in the cell.
- Keep it under 30MB.
- CSV fallback. In Excel, open the sheet you want, choose File, then Save As, and pick CSV UTF-8 (Comma delimited). A CSV holds one sheet only, so save the one you want on the dashboard.
If the data is confidential, replace names and customer details with made-up ones, or use totals by month and region instead of individual rows.
3. The main prompt
Attach your file, then send this. Replace everything in square brackets.
I've attached [a CSV / an Excel file] with [what it is, e.g. monthly sales by region and product].
Build an interactive dashboard from it, as an artifact I can click through in this chat.
Include:
1. Three KPI cards at the top: [e.g. total revenue, number of orders, average order value].
2. A line chart of [revenue] by [month] to show the trend.
3. A bar chart that breaks [revenue] down by [product category].
4. Working filters for [region] and [month] that update every card and chart at once.
Rules: use only the numbers in my file, and do the calculations in code instead of estimating.
Label every card and chart in plain words. One accent colour, light background, no decoration.
If a column is unclear or a value looks wrong, tell me before you build.What each part does:
- "Interactive dashboard, as an artifact I can click through" is the line that matters. Claude can also answer a chart request with a picture: its help page says it can create visualizations "in image files like PNG". Asking for an interactive dashboard, built as an artifact, is how you ask for the clickable version.
- The numbered list gives it a layout. Three cards, one trend and one breakdown is enough for most weekly reports, and it keeps the page readable.
- "Working filters" is what makes it a dashboard instead of a picture of one.
- "Do the calculations in code instead of estimating" and "use only the numbers in my file" keep it from guessing.
- The last line gets questions asked before the build, not after. If Claude comes back with a question, answer it and let it continue.
4. Check what you got
The dashboard should open beside the chat as a page you can click. Before you trust it:
- Click everything. Change each filter and watch the cards and charts change.
- Check three numbers against Excel. Compare a total, an average and one month with your own sum. If one is off, Claude has probably misread a column or counted a totals row.
- Ask how it was calculated. Send this and compare the answer with your sheet:
For each KPI card and chart, tell me which columns you used and exactly how the number is calculated.The dashboard is a snapshot of the one file you uploaded. It does not update when your spreadsheet does; to refresh it, upload the new file in the same chat and ask Claude to update it.
5. Follow-up 1: show it by region
Show it by region. Add a bar chart of [revenue] by region, sorted from highest to lowest,
and make clicking a region filter the whole dashboard.
Keep the cards, the trend chart and the other filters as they are.The last line stops Claude from redesigning what already works. If you do not have a region column, swap "region" for anything you do have: team, product, store, customer type.
6. Follow-up 2: add last month
Add a comparison with last month. On each KPI card, show the change from last month
as a percentage with an up or down arrow. Mark last month on the trend chart.
If last month is not in my file, tell me what to attach instead of guessing.If you need to bring in a second file, attach it to the same chat before you send this.
7. Follow-up 3: make it presentation-ready
Make this ready to show in a meeting on a large screen. Bigger numbers and text that can be read
from the back of a room. A title that states the main finding in one sentence, and a one-line
takeaway under each chart. Consistent number formats, bars sorted, no scrolling on a widescreen display.
Do not change any of the figures.Read the title and the takeaways before you present. They are Claude's reading of the data, and you are the one who has to stand behind them.
8. Show it in a meeting
Claude's help pages do not confirm whether a Free account can share a public link to a dashboard, and a new artifact starts private, so this guide does not rely on sharing. Show it on your own screen instead.
Before the meeting:
- Open the chat and the dashboard on your laptop and click through every filter once.
- Compare your key numbers with Excel one last time.
- Keep the spreadsheet open in another window as a backup.
- The dashboard is a page inside your Claude chat, so plan for a working internet connection in the room. Open it early and keep the tab open.
In the meeting:
- Share your screen, or the browser window only. Close other tabs and silence notifications.
- Enlarge the page with your browser's zoom (Ctrl and plus on Windows, Cmd and plus on a Mac) if the room is large.
- Start with the three cards. Say the one finding you want people to remember.
- When someone asks "what about the north region?", use a filter live. That moment is the point of a dashboard.
Afterwards, take screenshots of the views you want and paste them into an email or a slide.
9. Before you upload work data
Check your company's rules before you upload anything confidential. When you attach a file, you are sending its contents to Claude's service, and many workplaces have a policy on which AI tools may receive which data. If you are not sure, ask whoever looks after IT or data protection.
- Use made-up data to practise. Everything in this guide works on invented numbers.
- Remove what you do not need. Names, emails, phone numbers and account numbers rarely belong on a dashboard.
- Summarise first. Totals by month and region are often enough, and carry less risk than one row per customer.
- Watch what Claude does. The help page for file creation advises monitoring Claude while it uses code execution and stopping it if you see it using or accessing data unexpectedly.
10. When something goes wrong
| What you see | What to try |
|---|---|
| You get a flat picture of a chart | Reply: "Make this an interactive dashboard as an artifact that I can click, not an image." |
| The Excel file is rejected | Save the sheet as a CSV (section 2) and attach that. |
| No dashboard opens | Check Settings, then Capabilities, and switch on code execution and file creation. Then ask again. |
| A number does not match Excel | Run the "how it was calculated" prompt in section 4. Look for a totals row, a merged cell or a column Claude read as text. |
| A filter does nothing | Reply: "The region filter does not change the charts. Fix it so every card and chart responds." |
| You run out of usage | File creation uses more of your limit than a normal chat. Wait for it to reset, or start the next session with one complete prompt rather than many small ones. |
Honest notes
- Check the numbers. Claude can misread a column or build a calculation you did not mean. The dashboard is only as reliable as the check you do against your own sheet.
- It is a snapshot, not a live report. It shows the file you uploaded, as it was.
- Results differ each time. The same prompt can give a different layout on another run. If you like a version, say so and ask Claude to keep it while you change one thing.
- We could not confirm Excel (.xlsx) uploads from the help page. CSV is the listed format, so keep the CSV route in your pocket.
- Free has limits. Claude's usage limits apply, and building a dashboard uses more of them than a normal chat.