Detailed guide

Reports

Performance reporting across revenue, margin, delivery, and spend.

Reports turns operational data into decisions. It exists to help you answer business questions without exporting everything first.

Quick summary

  • Set filters before interpreting the report because the same layout can answer many different questions.
  • Save commonly reused views instead of rebuilding them each time.

Put it into practice

  1. Start by selecting timeframe and filter context before reading results so the report answers one specific business question.

    InteractionsReports page: set sidebar filters for period, client, and metric focus.
  2. Run or refresh the report after filter changes, then review the main canvas in the context of active filters.

    InteractionsReports builder toolbar: use refresh or run actions after adjusting filters.
  3. Compare revenue, cost, and margin signals together before drawing conclusions from a single metric.

    InteractionsMain report canvas: inspect aggregate and segmented performance values together.
  4. Save useful report configurations when the same operational question will be revisited.

    InteractionsReports toolbar: open Save Report and name the filtered view.
  5. If anomalies appear, pivot into project, time, or expense workflows to validate source records.

    InteractionsFrom report findings, open related operational areas to trace the underlying record-level cause.
    Open workflow: Projects

What to review

Reporting header

Defines the current reporting area and often frames the report you are looking at.

Sidebar filters

This is where you shape the report by period, client, metric, or saved configuration.

Main report canvas

Shows the actual results after filters are applied. Always read it in the context of the current sidebar selections.

Builder toolbar

Contains actions for refreshing, adjusting, or saving the current report view.

Save Report modal

Stores a useful configuration so the same business question can be answered faster next time.

Guardrails

  • Report accuracy depends on the underlying project, time, expense, and billing data being current.
  • Some report dimensions may be limited for users without commercial or admin visibility.

If it starts drifting

  • If a report looks empty, confirm the filter set first before assuming the reporting logic failed.