BUSINESS INTELLIGENCE QUESTIONS

What Should a Self-Hosted Reporting Tool Let Your Team Do?

At the morning dispatch review, the team needs to know which orders are late and who can get them moving. The answer should be available even when the person who prepares the spreadsheet is away.

Use one report to test three jobs before you choose a tool: building it, working from it in a browser, and handing it over to a new owner.

  
THE REPORT’S JOB

Define what the report must answer

A self-hosted reporting tool should let authors create and maintain reports, and let authorized readers find, filter and use them in a browser. Start with the decision the report supports. For dispatch, that’s deciding which late orders to chase first and who should follow up.

Use one row per order. Include orders that are still open after their promised dispatch date, and show the order number, promised date, branch and assigned team. Agree which time zone and cutoff apply so two readers can reconcile what they see.

Agree on “late”

Write down the cutoff and what counts as an open order.

  
FOR REPORT AUTHORS

Build and maintain the report

Ask a report author to work from the same prepared data they’d use after rollout. Have them build the overdue rule, group by branch and sort the oldest orders first. If the source contains several lines per order, check that a three-line order counts once.

Then change the rule or add a column and rerun the report. Check what a reader sees on a day with no late orders, and how the report distinguishes that result from a failed refresh.

Check the count

An order with three line items should still count as one order.

  
FOR REPORT READERS

Put the report in a reader’s hands

Sign in as a branch manager and filter the report to North. Starting from the count of two late orders, find the two records and decide which team to call first. In this example, order 1048 is the older exception.

North branch · open orders overdue at 8 a.m. on Nov 18
OrderPromised dispatchAssigned team
1048Nov 15Dispatch
1071Nov 17Inventory

If the team works from an exported file, export the filtered report and make sure the same two orders appear there.

Follow the count

Give readers a way to find the orders behind the number.

  
ACCESS AND OWNERSHIP

Decide who can see and change it

Test access with ordinary reader accounts. If the North manager should see only North orders, check that opening a shared link or changing a filter can’t expose another branch’s data. Include exports in that test if readers can use them.

Assign someone to maintain the report and show readers when its data was last refreshed. Ask the dispatch team how old the data can be before they need to check the order system.

Test a shared link

Check that a link still applies the signed-in reader’s access.

  
THE BUILD OR REUSE DECISION

Choose which reports to build or reuse

Build a native report when you need a new layout or a new view of the data. If an existing Crystal Reports or SQL Server Reporting Services (SSRS) report already answers the question, check whether the tool supports that report. Test its parameters, access and any exports the team uses.

IntelliFront BI is self-hosted and includes browser-based tools for creating reports. See how to create reports and dashboards for your team, then use the evaluation guide to plan a trial with one author and one reader.

Download the IntelliFront BI Internal Evaluation Guide

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software