3.1 Multi-Source & Composite Data Synthesis

3.1 Multi-Source & Composite Data Synthesis

In the UK Civil Service Numerical Test (CSNT), the highest-difficulty questions rarely present data in a single, isolated table. Senior operational delivery roles (Executive Officer, Higher Executive Officer, and Senior Executive Officer/Fast Stream) require officials to synthesize disparate data streams to make evidence-based policy and resource allocation decisions.

Composite test items mirror this operational reality by requiring you to draw inputs from two or three distinct exhibits—such as an intake ledger, a task-handling benchmark chart, and a set of operational footnotes—to solve a single chained problem.

---

The Anatomy of a Multi-Source Question

A typical composite item in the CSNT contains three interconnected layers of information:

1. The Primary Volume Asset (Table 1): Captures high-level operational counts (e.g., incoming claim applications, citizen queries, regional staffing allocations).
2. The Operational Benchmark Asset (Table 2 or Chart 1): Provides rate-based parameters (e.g., average handling time in minutes per case type, triage complexity distributions, or unit processing costs).
3. The Qualifying Footnotes: Contain critical policy constraints, working hour definitions, overhead allowances, or regional anomalies (e.g., staff absence rates, contracted hours per Full-Time Equivalent, IT maintenance downtime).

If you attempt to perform calculations using only the primary table, you will almost certainly select an attractive distractor—an answer choice deliberately engineered by the test writers to match the result of omitting the footnote adjustments.

---

The 4-Stage Synthesis Methodology

To navigate composite scenarios without losing your place, adopt a structured four-stage execution pipeline:

Stage 1: Target Definition  -->  What exact unit and metric does the prompt ask for?
Stage 2: Variable Mapping   -->  Which table or footnote provides each required parameter?
Stage 3: Noise Filtering    -->  Which columns and figures are irrelevant distractors?
Stage 4: Chained Execution  -->  Execute intermediate equations in dimensional sequence.

Stage 1: Target Definition

Always read the question stem before examining the exhibits. Identify the target unit. Are you solving for net hours of capacity deficit, additional FTE caseworkers required, total expenditure variance, or average cost per completed case? Knowing your destination prevents you from calculating interesting but irrelevant intermediate figures.

Stage 2: Variable Mapping

Deconstruct the target metric into its algebraic components. For example: $\text{FTE Shortfall} = \frac{\text{Total Casework Hours Demanded} - \text{Total Productive Hours Available}}{\text{Net Productive Hours per FTE}}$ Map each variable in this formula to its corresponding exhibit. For instance, Casework Demanded comes from Table 1 and Table 2; Productive Hours Available comes from Table 1 combined with the policy footnotes.

Stage 3: Noise Filtering (Distractor Rejection)

Civil Service test exhibits are deliberately cluttered with extraneous data: customer satisfaction scores, appeal rates, prior-year historical benchmarks, or data for unaffected regions. Practice aggressive selective attention: glance at headers, confirm they do not match your mapped variables, and visually disregard them.

Stage 4: Dimensional Chaining & Execution

Execute calculations step-by-step. At each stage, verify your units using dimensional analysis. If you divide total hours demanded by hours per caseworker-month, the unit 'hours' cancels out, leaving you with 'caseworkers (FTE)', which aligns with your target requirement.

---

Comprehensive Worked Scenario: Operational Casework & Staffing Shortfall

Let us examine a full-scale operational delivery scenario modeled directly on operational tests used by the Department for Work and Pensions (DWP) and HM Revenue & Customs (HMRC).

Exhibit 1: Regional Casework Intake & Staffing (October)

Exhibit 2: Claim Handling Benchmarks & Regional Complexity Mix

Exhibit 3: Operational Policy Footnotes

• Note 1 (Working Hours): Full-Time Equivalent (FTE) staff are contracted for 37.0 gross hours per week over a standard 4-week reporting month (148.0 gross hours per FTE).
• Note 2 (Overhead Allowance): A mandatory operational allowance of 15% of contracted gross hours is dedicated to case conferences, supervision, and digital system latency across all regions.
• Note 3 (Regional Sickness Absence): In Yorkshire & Humber, an unplanned viral outbreak resulted in an aggregate sickness absence rate of 8.0% of available working time during October.
• Note 4 (Backlog Policy): Each region is required to clear exactly 20% of its opening legacy backlog during October. All legacy backlog cases require Tier 1 Standard Claim handling time (1.25 hours each).

---

The Operational Prompt

Question: In the Yorkshire & Humber region, what was the net operational capacity position (in productive casework hours) for October, and how many additional full-time equivalent (FTE) staff would have been required to prevent any operational shortfall? (Round required FTE to one decimal place).

Step-by-Step Solution Breakdown

Step 1: Calculate Net Productive Hours Available per FTE (Footnotes 1, 2, and 3)

First, calculate the standard contracted hours per caseworker for the 4-week month: $\text{Gross Contracted Hours} = 37.0 \text{ hours/week} \times 4 \text{ weeks} = 148.0 \text{ hours/FTE}$

Next, deduct the mandatory 15% overhead allowance for non-casework duties: $\text{Standard Overhead} = 148.0 \times 0.15 = 22.2 \text{ hours}$ $\text{Base Productive Hours} = 148.0 - 22.2 = 125.8 \text{ hours/FTE}$

Now incorporate Note 3: Yorkshire & Humber experienced an 8.0% sickness absence rate, reducing available productive hours by a further 8%: $\text{Effective Hours per FTE} = 125.8 \times (1 - 0.08) = 125.8 \times 0.92 = 115.736 \text{ hours/FTE}$

Step 2: Calculate Total Productive Hours Supplied in Yorkshire & Humber (Exhibit 1)

From Exhibit 1, Yorkshire & Humber has 35 FTE assigned: $\text{Total Productive Hours Supplied} = 35 \times 115.736 = 4,050.76 \text{ hours}$

Step 3: Calculate Casework Demand for New Claims (Exhibit 1 & Exhibit 2)

From Exhibit 1, Yorkshire & Humber received 2,700 new claims. We determine the total hours needed by applying the regional complexity proportions from Exhibit 2:

• Tier 1 (Standard): $2,700 \times 0.60 = 1,620 \text{ claims} \times 1.25 \text{ hours} = 2,025.0 \text{ hours}$
• Tier 2 (Complex Disability): $2,700 \times 0.25 = 675 \text{ claims} \times 3.20 \text{ hours} = 2,160.0 \text{ hours}$
• Tier 3 (Rapid Renewal): $2,700 \times 0.15 = 405 \text{ claims} \times 0.50 \text{ hours} = 202.5 \text{ hours}$ $\text{Subtotal (New Claims Demand)} = 2,025.0 + 2,160.0 + 202.5 = 4,387.5 \text{ hours}$

(Shortcut verification: Weighted Average Handling Time per claim = $(0.60 \times 1.25) + (0.25 \times 3.20) + (0.15 \times 0.50) = 0.75 + 0.80 + 0.075 = 1.625 \text{ hours/claim}$. Total hours = $2,700 \times 1.625 = 4,387.5 \text{ hours}$.)

Step 4: Calculate Demand for Legacy Backlog Cases (Exhibit 1 & Footnote 4)

From Exhibit 1, the opening backlog is 600 cases. Note 4 dictates that 20% must be cleared, each requiring 1.25 hours: $\text{Backlog Cases to Process} = 600 \times 0.20 = 120 \text{ cases}$ $\text{Backlog Hours Demanded} = 120 \times 1.25 = 150.0 \text{ hours}$

$\text{Total Operational Demand} = 4,387.5 + 150.0 = 4,537.5 \text{ hours}$

Step 5: Determine Net Capacity Shortfall and Required Additional FTE

Compare total operational demand against total productive hours supplied: $\text{Capacity Variance} = \text{Hours Supplied} - \text{Hours Demanded}$ $\text{Capacity Variance} = 4,050.76 - 4,537.50 = -486.74 \text{ hours (Shortfall of 486.74 hours)}$

To find how many additional FTE are needed to cover this deficit, divide the shortfall hours by the effective productive hours delivered by one FTE in that region ($115.736$ hours): $\text{Additional FTE Required} = \frac{486.74}{115.736} \approx 4.2056 \text{ FTE}$

Rounding to one decimal place yields 4.2 FTE.

(Notice the distractor traps! If a candidate ignored the 8% sickness rate, effective hours would be 125.8, producing an erroneous shortfall of 134.5 hours and an incorrect answer of 1.1 FTE. If a candidate ignored both the overhead allowance and sickness absence, using 148 hours, they would compute an entirely erroneous answer. Psychometric exams build these exact omissions into the multiple-choice options.)

Managing Complex Distractors in the Civil Service Test

Psychometric test designers rely on specific cognitive traps to slow candidates down. Recognizing these patterns allows you to bypass them instantaneously:

1. Percentage Footnotes for Unrelated Units: In the example above, Exhibit 1 contained a 'Customer Satisfaction Index' column (82%). Candidates frequently attempt to apply this percentage as an operational factor (e.g., assuming only 82% of cases are accepted). Never apply a percentage unless the text explicitly states it modifies the target workload or capacity.
2. Aggregated Totals vs. Specific Subsets: Prompts frequently ask about a single region, division, or grade. Do not spend time calculating national totals or summing across rows if the question only concerns 'Yorkshire & Humber'.
3. Unit Mismatches (Hours vs. Minutes): Handling benchmarks are often quoted in minutes (e.g., 75 minutes) while contracted staffing is quoted in hours (e.g., 37 hours/week). Standardize all time components into decimals of hours ($75 / 60 = 1.25$ hours) before performing chained multiplications.
4. Calendar Ambiguities: Always confirm the reporting period specified in the prompt or footnotes. A civil service month in numerical testing is defined either as exactly 4 weeks (20 working days) or as specified in the exhibit footnotes. Never use a generic 30-day or 31-day assumption unless directed.

---

Summary of Chained Execution Rules