Agiled Docs

Reports show the same dataset in multiple formats so you can scan trends and inspect the underlying rows.

Summary Cards

Summary cards appear when a report has high-level totals. Use them for quick answers before reading the chart or table.

Examples include totals such as revenue, expense, profit, count, hours, billable hours, payroll gross, payroll net, overdue amount, or conversion rate depending on the report.

Treat summary cards as a starting point. When the number will drive a decision, open the table and compare at least one source record before sharing the total.

Chart View

Select Chart to see the data visually. Reports use the chart type that fits the dataset:

Area charts for trends over time.
Bar charts for comparing amounts or counts by category.
Pie charts for status or type distribution.

Use chart view to spot spikes, trends, outliers, and mix changes. If a chart looks unusual, switch to table view to inspect the exact rows.

Check the date range before interpreting a chart. A spike can be caused by a real event, a status cleanup, an import, a backfilled payment, or a changed filter.

Table View

Select Table to inspect rows and exact values. Table view is the default working view and is best when you need to validate totals or export the data.

Click a column header to sort the table. Click the same column again to reverse the sort direction. Numeric columns sort by number; text columns sort alphabetically.

Use table view before exports, billing reviews, payroll checks, or leadership updates. It is the easiest place to spot rows with missing owners, wrong status, unexpected currency, or test data.

Breakdown

Some reports include a breakdown table below the main chart/table. Use breakdowns to see secondary detail, such as method mix, category mix, or record-level subtotals.

Breakdowns are helpful when the main report answers "how much" or "how many" but you also need to understand the source mix.

When a number looks wrong, identify one row that contributes to the total and open the matching source record in its module. For example, compare an invoice row against the invoice detail page, a task row against the task, or a timesheet row against the time entry.

This prevents report cleanup from becoming guesswork. Fix the source record, then refresh the report and confirm the chart, summary card, and table changed as expected.

Validate A Report

When numbers matter, validate the report before sharing it:

Confirm the active report name.
Confirm filters and currency.
Check summary cards.
Sort the table by the most important value.
Compare one or two rows against the source module.
Export CSV only after the table looks correct.

Common Reading Mistakes

Avoid these report-reading mistakes:

Comparing different date ranges between two reports.
Reading a chart before checking filters.
Exporting a table that still contains test or duplicate records.
Treating draft, sent, paid, and void records as the same status.
Sharing a summary total without checking the currency or workspace.

Read Charts and Tables