When to use a table
Tables are useful when you need to compare options, track a set of values, or keep a small working dataset beside the explanation around it. Because the table lives in the note, the numbers stay close to the decision they support.
| Option | Owner | Status |
|---|---|---|
| Existing flow | Product | Review |
| New flow | Design | Draft |
| Hybrid flow | Team | Open |
Use functions where they help
Core advanced tables add spreadsheet-like functions such as sums, averages, and counts. Use them for the small calculations that belong with a project note or decision, without sending the context to a separate spreadsheet.
Budget items
Design 1200
Development 2400
Testing 600
Total 4200
The exact calculation belongs to the table you are building; the useful part is that the result can stay beside the assumptions and source material.
Keep the explanation nearby
- Introduce what the rows and columns represent.
- Use a table for values that benefit from comparison.
- Record the conclusion underneath, in plain language.
- Link the note to the project or decision that uses it.
Core is additive. The everyday note and table workflow remains useful without advanced calculations; use Core when richer data earns its place.