LEARN BUSINESS INTELLIGENCE

Reusing Reporting Designs Across Customers and Departments

Carry over the parts of the report that still answer the same question. Then check how the new customer records the work, which dates their rules use and what a reader should see.

  
KEEP THE USEFUL PARTS

Decide What to Carry Over

North Quay has a weekly report that shows which orders shipped late and where. Marshfield asks for the same report. You can keep the weekly count, branch comparison and list of orders, but first check how Marshfield records a shipment.

  • Keep the reader’s question, useful layout and agreed rule.
  • Adapt the source fields, branch names, branding and reader access.
  • Test against the new customer’s own orders.

Start from a clean copy

Check captions, filters and saved file paths for the previous customer’s information.

  
MATCH THE RECORDS

When is a Marshfield order actually shipped?

Before reusing a customer reporting setup, check what each source counts. The North Quay data shows one row per order. Marshfield records each parcel separately. For a Marshfield order split across two parcels, use the date the final parcel went out, once dispatch is complete. That order contributes once to the weekly count.

Use the date promised to the customer. Marshfield’s planned ship date serves internal planning. If the promised date changed, agree which date to use before you count late orders. Keep branch codes tied to the customer, since code 01 can mean different places.

Save a worked mapping

Keep one split shipment and its field names. Show which date set the promise and which parcel set the dispatch date.

  
PROVE THE RESULT

Check the Result Against Known Orders

Check known Marshfield orders for the week of 2–8 November in the warehouse’s local time. Use the date the final parcel shipped. Track unfinished orders separately.

Four Marshfield orders and the result the manager expects
Order What the records show Expected result
M-104 Agreed 3 November. Final parcel shipped 3 November. On time
M-105 Agreed 3 November. Parcels shipped 3 and 4 November. Late, counted once
M-106 Agreed 4 November. Final parcel shipped 5 November. Late
M-107 Final parcel shipped 5 November. No agreed date recorded. Date missing

Expect two late orders, M-105 and M-106. M-107 needs a date check. Sign in as the intended reader and confirm the results and supporting rows belong to Marshfield.

Test the week boundary

If the final parcel ships just after midnight on Monday, the order belongs to the new week.

  
CHOOSE A REUSE APPROACH

Choose How to Reuse the Design

A clean reference copy and a field mapping may be enough if the current tool works well.

If Marshfield’s managers need to open the dashboard and look up individual orders themselves, IntelliFront BI is ChristianSteven Software’s reporting platform, hosted on infrastructure you manage. Reuse the dashboard definition, which describes how the view is built. A PDF or spreadsheet gives you the output to compare against. Before moving a definition, check what travels with it, what you need to reconnect and who will have access.

Keep a short handover note

Record the source, field mapping, branch mapping, access owner and any software versions used in the move.

  
HAND OVER THE DESIGN

Leave a Design the Next Person Can Update

Keep a checked split shipment with the design. You can reuse a clearer label for both customers. If you change what counts as late, agree on the rule and check it against familiar orders. If each customer needs its own view of the report and its details, see how to offer reporting views to your software customers.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software