# T Level Core — Content Weight Reference
**Spec Version:** 1.0 (May 2025)
**Generated from:** CORE_Content_Specification.md

Use this table when deciding how much content each section needs and what structural components are required.

## Tier Guide

| Tier | Score | What it means | Required components |
|------|-------|--------------|---------------------|
| **A** | 20+ | High demand — many spec items, multiple "Be able to" outcomes | 3+ worked examples, full exam practice block (4+ Qs), detailed glossary |
| **B** | 12–19 | Medium demand | 1–2 worked examples, 2–3 exam Qs, glossary |
| **C** | <12 | Lower demand — mostly "Know" and factual recall | Clear factual content, definitions table, 1 short exam Q |

## Command Word Interpretation

| Command Word | In the exam | In the document |
|---|---|---|
| **Know** | State or give | Short factual paragraph or table row |
| **Know & Understand** | State and explain | Paragraph with why/how follow-up |
| **Understand** | Explain, describe, interpret | Full explanation with context |
| **Be able to** | Apply to a scenario | Worked example required |

---

## Content Area 1: Problem Solving

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 1.1 | Computational Thinking | 17 | 35 | **A** | 5 | needs worked examples |
| 1.2 | Algorithmic Design | 10 | 24 | **A** | 5 | needs worked examples |
| 1.3 | Strategies | 9 | 14 | **B** | 0 | explanation depth |

## Content Area 2: Digital Support

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 2.1 | Infrastructure | 6 | 14 | **B** | 2 | needs worked examples |
| 2.2 | Cabling | 5 | 9 | **C** | 0 | recall-focused |
| 2.3 | Unified Communications | 6 | 10 | **C** | 0 | explanation depth |
| 2.4 | Support | 6 | 14 | **B** | 3 | needs worked examples |
| 2.5 | Testing | 8 | 16 | **B** | 2 | needs worked examples |
| 2.6 | Using Data in Digital Support | 5 | 9 | **C** | 1 | needs worked examples |
| 2.7 | Using Diagrams in Digital Support | 8 | 20 | **A** | 4 | needs worked examples |
| 2.8 | Risk and Risk Assessment | 5 | 12 | **B** | 2 | needs worked examples |
| 2.9 | Project Management | 4 | 9 | **C** | 1 | needs worked examples |
| 2.10 | Strategies for Responding to Issues | 5 | 11 | **C** | 1 | needs worked examples |
| 2.11 | Sources of Knowledge | 3 | 4 | **C** | 0 | recall-focused |

## Content Area 3: Data

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 3.1 | Data, Information and Knowledge | 5 | 10 | **C** | 0 | explanation depth |
| 3.2 | Methods of Transforming Data | 1 | 2 | **C** | 0 | recall-focused |
| 3.3 | Data Taxonomy | 6 | 8 | **C** | 0 | explanation depth |
| 3.4 | Data Types | 4 | 8 | **C** | 1 | needs worked examples |
| 3.5 | Data Formats | 2 | 3 | **C** | 0 | explanation depth |
| 3.6 | Structures for Storing Data | 4 | 6 | **C** | 0 | explanation depth |
| 3.7 | Data Dimensions and Maintenance | 6 | 9 | **C** | 0 | explanation depth |
| 3.8 | Data Systems | 8 | 14 | **B** | 0 | explanation depth |
| 3.9 | Data Visualisation | 2 | 4 | **C** | 0 | recall-focused |
| 3.10 | Data Models | 4 | 8 | **C** | 1 | needs worked examples |
| 3.11 | Data Access Across Platforms | 3 | 6 | **C** | 0 | explanation depth |
| 3.12 | Data Analysis Tools | 2 | 3 | **C** | 0 | explanation depth |

## Content Area 4: Legislation & Regulatory Requirements

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 4.1 | Legislation | 9 | 17 | **B** | 0 | explanation depth |
| 4.2 | Guidelines | 6 | 10 | **C** | 0 | explanation depth |

## Content Area 5: Business Context

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 5.1 | Organisational Structures | 3 | 3 | **C** | 0 | recall-focused |
| 5.2 | Digital Value to Organisations | 2 | 4 | **C** | 0 | explanation depth |
| 5.3 | Risk to Organisations | 2 | 4 | **C** | 0 | explanation depth |
| 5.4 | Technical Change Management | 5 | 10 | **C** | 0 | explanation depth |
| 5.5 | Digital Support Roles | 7 | 13 | **B** | 0 | explanation depth |

## Content Area 6: Emerging Issues

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 6.1 | Impact of Digital Technologies | 4 | 8 | **C** | 0 | explanation depth |
| 6.2 | Emerging Technologies | 2 | 4 | **C** | 0 | explanation depth |

## Content Area 7: Digital Environments

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 7.1 | Hardware | 2 | 4 | **C** | 0 | explanation depth |
| 7.2 | Software | 3 | 6 | **C** | 0 | explanation depth |
| 7.3 | Networks | 11 | 21 | **A** | 0 | explanation depth — largest single section |

## Content Area 8: Security

| Ref | Subtopic | Items | Score | Tier | Be able to | Notes |
|-----|---------|-------|-------|------|-----------|-------|
| 8.1 | Security Risks | 3 | 5 | **C** | 0 | explanation depth |
| 8.2 | Threats and Vulnerabilities | 5 | 10 | **C** | 0 | explanation depth |
| 8.3 | Threat Mitigation | 2 | 4 | **C** | 0 | explanation depth |
| 8.4 | Interrelationship of Security Components | 2 | 4 | **C** | 0 | explanation depth |

---

## Tier A Sections (prioritise these first)

| Ref | Subtopic | Why |
|-----|---------|-----|
| 1.1 | Computational Thinking | 17 items, 5 × Be able to — highest demand in entire spec |
| 1.2 | Algorithmic Design | 10 items, 5 × Be able to — needs flowchart walkthroughs |
| 2.7 | Using Diagrams in Digital Support | 8 items, 4 × Be able to — practical diagram tasks |
| 7.3 | Networks | 11 items, most heavily "Understand" weighted in the spec |