BI Report Narrative Vocabulary
Master BI report narrative vocabulary: KPI declined, root cause analysis, trend reversal, period-over-period comparison, metric within acceptable range — the language of data storytelling in business reports.
0 / 45 completed
1 / 45
The analyst writes in the report: 'The KPI declined by 12% due to reduced conversion rates in the checkout funnel.' What is the purpose of the phrase 'due to' in this context?
'Due to' introduces the causal explanation — the identified reason for the metric movement. In report narratives, pairing a metric change with its cause ('declined by 12% due to...') is standard data storytelling practice. It transforms a raw number into an actionable insight by linking the what to the why.
2 / 45
The data analyst presents: 'The root cause is the drop in email open rates following the subject line change on 15 April.' What does 'root cause' mean?
Root cause refers to the fundamental, underlying reason for a problem — not the immediate symptom. Root cause analysis (RCA) goes beyond surface-level observations to identify what actually caused the issue. In BI reporting, identifying the root cause is essential for recommending actionable fixes rather than just describing the problem.
3 / 45
The report states: 'The trend reversal was triggered by the product price increase in Q3.' What is a 'trend reversal'?
A trend reversal is the point at which a metric changes its direction of movement. For example, a sales metric that was growing month-over-month that suddenly begins declining has undergone a trend reversal. Identifying what triggered the reversal (a price change, a product launch, an external event) is a core task in BI narrative writing.
4 / 45
The analyst says: 'Compared to the same period last year, revenue is up 8%.' Why is 'same period last year' comparison used rather than comparing to last month?
Comparing to the same period last year (year-over-year, or YoY) controls for seasonality. Many businesses have predictable seasonal patterns (e.g., higher sales in December). Comparing December this year to November this year would conflate seasonal effects with underlying business performance. YoY comparison isolates true growth from seasonal fluctuation.
5 / 45
The report concludes: 'The metric is within the acceptable range at 3.2%, against a target of 3.5% ± 0.5%.' What does 'within the acceptable range' communicate?
'Within the acceptable range' (or 'within tolerance') means the metric value falls inside the defined upper and lower bounds around the target. This is a key phrase in automated monitoring and executive reporting — it signals that no action is required. The opposite ('outside the acceptable range' or 'breached the threshold') would trigger an alert or escalation.
6 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
7 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
8 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
9 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
10 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
11 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
12 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
13 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
14 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
15 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
16 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
17 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
18 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
19 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
20 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
21 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
22 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
23 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
24 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
25 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
26 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
27 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
28 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
29 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
30 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
31 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
32 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
33 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
34 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
35 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
36 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
37 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
38 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
39 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
40 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
41 / 45
git checkout main; git add report.md; git commit -m "Update BI Report Narrative Vocabulary"
Sarah's comment highlights the importance of providing context and explanation when describing metrics in a BI report. Simply stating that something 'increased significantly' doesn't convey any information about potential causes or underlying factors driving the change. A good PR description should always explain *why* a metric changed, allowing stakeholders to understand its implications and take appropriate action. The correct option reflects this need for added context.
42 / 45
David is focusing on 'latency,' which specifically refers to the delay experienced during data transfer. While 'volume' and 'error rate' are related concepts, David's statement directly addresses the performance issue indicated by the API response times. 'Throughput,' measuring the *rate* of processing, isn't the core concern here; it's about the *delay* itself.
43 / 45
Liam's initial comment only provides a raw data point. While percentages are important, understanding *what* was being measured and *when* is crucial for technical stakeholders to assess the significance of the change. The phrase 'last week' adds minimal value and could be misleading if the report covers longer periods. Including a comparison timeframe—like 'compared to the previous week'—provides context and allows others to evaluate whether this decrease represents a critical issue or simply a normal fluctuation.
44 / 45
Mark is writing a description for a PR introducing a new BI report showing website traffic. He writes: 'Traffic decreased by 15% last month.' His team lead, Emily, asks him to provide more detail. Which of the following additions would best help Emily understand the significance of this change?
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
'The bounce rate increased significantly' isn't enough – we need to explain why it increased.
The original statement, 'Traffic decreased by 15% last month,' only presents the raw data. Emily needs context – how this decrease *affects* the business. Option B correctly adds the impact on user engagement, which is a crucial metric for website traffic reports. Options A and C offer potential explanations but don't address the overall significance of the change, while option D introduces a target comparison which isn't necessarily relevant at this stage.
45 / 45
Ben is drafting a narrative for a BI report on website conversions. He writes: 'Conversion rates dropped sharply during the promotional period.' His manager, Alex, asks him to refine this statement. Which of the following options best explains what Ben needs to add to provide more actionable insight?
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
Option D: sufficient – 'sharply' indicates a significant change, implying an immediate response is needed.
The original statement, 'Conversion rates dropped sharply during the promotional period,' only describes *what* happened but not *why*. The correct answer highlights that Ben needs to provide context regarding potential causes for the drop – such as external factors or changes in user behavior. This allows stakeholders to investigate and take appropriate action, rather than simply noting a problem.
Frequently Asked Questions
What will I practice in "BI Report Narrative Vocabulary"?
This is a BI Analytics Language exercise set. It walks through 45 scenario-based multiple-choice questions built around real usage of BI Analytics Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 45 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the BI Analytics Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more BI Analytics Language exercises?
See the BI Analytics Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — BI Analytics Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.