Syntha Lab RU

Data readiness for standard reports

From a list of data fields with your weights and availability shows how much of the data exists for four reports (brand history, the SKU report, carryover, season results) and which field to close first.

Data model of standard reports For whom: Heads of analytics, commerce and data when preparing standard reports.

Calculate on your data →

At a glance

What question does it answer?
How much of the data for four reports already exists and what to close first.
What data is needed?
A list of data fields with a weight from 1 to 5.
How to read the result?
On the default data (12 fields) the readiness of the brand history is 84.6%, the SKU report 79.5%, carryover 78.2%, season results 76.2%. Season results are the least ready; close “Price and discount separately” first: priority 480. Example on the default values: Readiness: Brand history: 84.6% · fields 7; Readiness: SKU report: 79.5% · fields 9; Readiness: Carryover: 78.2% · fields 7; Readiness: Season results: 76.2% · fields 9. The figures are illustrative: enter your own to see your result.

Why and how to reason

Reports on the brand, SKUs, carry-over goods and season results are built from the same data fields, but each report needs its own set. If a field is missing or half filled, the report either cannot be built or misleads. So the calculation gives each field a weight (how important it is), a share of availability and marks of which reports need it. Report readiness equals the sum of (weight × availability × flag) ÷ the sum of (weight × flag). So “Brand history” is 84.6% ready and “Season results” 76.2%. To see what to close first, weight × (100 − availability) × number of reports is computed: for the field “Price and discount separately” it is 4 × 40 × 3 = 480, more than for the others.

When to use it

It fits when preparing a season analysis, introducing reporting or starting analytics on data collected without a plan. Do not use it as an assessment of the analytics itself: the calculation shows only the completeness of the input. Assumptions: weights and flags are set by you, availability is the share of data present for the period, the readiness threshold is yours. It works well as a checklist before an audit or the start of external analytics: it shows at once what will be missing before work begins.

How to read the result

Find the report with the lowest readiness (here “Season results”, 76%) and the field with the highest “close first” (price and discount separately). If few reports are above the threshold, start with a field that several reports need at once: one step then lifts the readiness of several. Do not try to close every field in sequence: weight sets the order. Compare readiness with the real deadline of the report: whether to wait or to build with the available data and a caveat. Agree who closes each field and by when, and repeat the calculation: rising readiness after every step motivates and makes progress visible.

Common mistakes

Overstating availability by eye, giving all fields the same weight, marking a field as needed by a report that does not need it, mixing the presence of a field with its quality. Check availability with a spot check on 20 rows, otherwise readiness is illusory. Remember that a field may be “present” but wrongly linked to the parent model or season: formally available, but useless to the report.

What data is needed?

  • A list of data fields with a weight from 1 to 5.
  • The availability share of each field.
  • Which report needs the field.

Inputs

FieldUnitValue in the exampleMeaning
Your readiness threshold for a report%—The readiness share from which a report can be built; empty: treated as not set. There is no single standard in Russia: enter your own figure.

How it is calculated

StepFormula
Report readinesssum (weight × availability × flag) ÷ sum (weight × flag)
What to close firstweight × (100 − availability) × the number of reports with the field

Worked numbers

Default values from the app; in the interactive version you enter your own.

Readiness: Brand history
84.6 % · fields 7
Readiness: SKU report
79.5 % · fields 9
Readiness: Carryover
78.2 % · fields 7
Readiness: Season results
76.2 % · fields 9
Least ready
76.2 % · Season results
Close first
480 · Price and discount separatelyWeight × (100 − availability) × the number of reports that need the field.
Reports above the threshold
no threshold set

Readiness of reports

ReportReadinessFields needed
Brand history84.6 %7
SKU report79.5 %9
Carryover78.2 %7
Season results76.2 %9

Close the field “Price and discount separately” first: several reports need it and it is the weakest relative to its weight. The fields and the row format: the data templates in the “Processes and data” section.

The SKU report and the season results usually need sales, stock and receipts by day or week at SKU level; a starting guide is two years of history by day, store and SKU (use your own data). There is no single Russian readiness standard.

Nuances and limits

  • Change the weights for your reports.
  • Availability is the share filled and reliable, not just “the column exists”.
  • There is no single Russian readiness standard.
  • Check the quality of values with the “Completeness and quality of master data” calculation.

Terms used

Calculate on your data →