13.1 Developing Digital Content & Document Processing (DigComp 3.1)

13.1 Developing Digital Content & Document Processing (DigComp 3.1)

Official Reference: European Commission Joint Research Centre (JRC) DigComp 2.2: The Digital Competence Framework for Citizens. Competence 3.1 establishes that public servants must be capable of creating and editing digital content in different formats, expressing themselves through digital means, and applying advanced formatting and structural standards to administrative assets.

Under Notice EPSO/AD/427/26, the Digital Skills examination constitutes one of three ranked multiple-choice components determining a candidate's placement on the AD5 reserve list. Comprising 40 questions to be answered in 30 minutes (an average of just 45 seconds per question), the test carries a mandatory pass threshold of 20 out of 40 points and counts for 30% of the preliminary ranking and 25% of the final ranking. Administered entirely in Language 2, this module rigorously evaluates whether incoming administrators possess the practical digital competencies needed to draft legislative proposals, analyze complex budgetary tables, and ensure digital assets adhere to Union accessibility standards.

Within the European civil service, document creation is never a purely mechanical exercise. Policy officers in European Commission Directorates-General, Council working parties, and European Parliament committee secretariats author documents that establish statutory rights, impose financial obligations, and circulate among thousands of institutional stakeholders. Applying fragile formatting or incorrect calculation logic compromises institutional credibility and creates severe administrative risks.

---

Structured Document Production & Typography Architecture

Administrative documents within European Union institutions—such as Commission Staff Working Documents, Legislative Financial Statements, and Council Presidency Compromise Proposals—often span hundreds of pages and involve dozens of contributing drafters. To maintain structural consistency and auditability, administrators must employ structured document production techniques.

Semantic Formatting vs. Direct Formatting

The fundamental principle of professional document production is the strict separation of content and structure from visual presentation:

• Direct (Physical) Formatting: Applying visual attributes (such as bold, italic, font size, or custom indents) directly to selected words. This practice is fragile; changing a formatting convention requires manually locating and editing every instance across a multi-chapter dossier.
• Semantic (Style-Based) Formatting: Applying structured Paragraph Styles and Character Styles that define the structural role of the text element (such as Title, Heading 1, Body Text, Legal Citation, or Table Note). Styles establish a centralized hierarchy: updating the style definition instantly propagates formatting modifications across the entire document repository.

Heading Hierarchies & Structural Integrity

Institutional drafting tools (such as the Commission's LegisWrite templates for legal acts) rely on predefined styles for each structural level. A typical four-level semantic hierarchy looks like this:

1. Heading 1 (H1): Major thematic divisions or legislative Titles (e.g., Title I: General Provisions).
2. Heading 2 (H2): Primary substantive sections or Chapters (e.g., Chapter 2: Scope and Definitions).
3. Heading 3 (H3): Subsections or Articles (e.g., Article 4: High-Risk AI Classification).
4. Heading 4 (H4): Operational paragraphs, technical sub-clauses, or institutional procedures.

Skipping heading levels (for instance, jumping from an H1 directly to an H3 merely because the font size appears visually preferable) invalidates the underlying structural tree. Screen readers, search indexers, and automated document compilers rely on continuous hierarchical progression to map the document's logical architecture.

Automated Table of Contents & Cross-Referencing

A manually typed Table of Contents (TOC) is bad practice in long administrative documents, because it goes out of date with every edit. When semantic heading styles are applied consistently, word processors compile the TOC dynamically by parsing outline levels:

• Outline Levels: Headings H1 through H3 are assigned outline levels 1 through 3, allowing the automated TOC field to harvest section numbers, text strings, and corresponding page numbers.
• Field Updating: TOC fields must be updated before final distribution, distinguishing between Update page numbers only (rapid check after minor text revisions) and Update entire table (mandatory whenever headings have been rephrased, added, or deleted).
• Dynamic Cross-References: Internal references to other sections (e.g., 'as established in Article 12 on page 45') must use automated cross-reference fields tied to bookmarks or headings. If Article 12 is subsequently renumbered or shifts to page 48, the cross-reference updates automatically upon document compilation, preventing dead citations.

Master Documents and Subdocuments

When authoring massive inter-institutional dossiers—such as the Multiannual Financial Framework (MFF) or comprehensive Trade Agreements—institutions deploy Master Documents:

• A Master Document acts as an administrative container linking multiple independent files known as Subdocuments.
• Each unit or Directorate drafts its assigned chapter within a dedicated subdocument, ensuring concurrent drafting without file-locking conflicts.
• The Master Document compiles the individual subdocuments into a unified file, applying a single continuous pagination schema, generating a consolidated Table of Contents, and standardizing shared style definitions.

Section Breaks vs. Page Breaks

Controlling pagination and layout across multi-part EU publications requires an understanding of document division boundaries:

• Page Breaks (Ctrl + Enter): Forces the subsequent text to begin at the top of the next page while preserving identical margins, orientation, and header/footer configurations.
• Section Breaks (Next Page, Continuous, Even Page, Odd Page): Creates an independent layout partition. Section breaks are required whenever an administrator needs to:
  • Switch orientation between Portrait (standard narrative text) and Landscape (wide statistical tables or financial annexes).
  • Vary margin dimensions across separate chapters.
  • Unlink headers and footers (Link to Previous toggled off) to display distinct chapter titles or restart page numbering schemas (e.g., lower-case Roman numerals i, ii, iii for executive summaries and Arabic numerals 1, 2, 3 for substantive legislative articles).

---

Advanced Spreadsheet Proficiency for Administrative Policy Modeling

European administrators analyze trade flows, monitor national structural fund allocations, and calculate greenhouse gas emissions baselines. Spreadsheet errors in these domains can trigger audit findings by the European Court of Auditors or distort budgetary allocations across Member States.

Modern Lookup Functions: VLOOKUP vs. XLOOKUP vs. INDEX/MATCH

Retrieving data across relational tables is a daily administrative task. While legacy formulas remain widespread, modern public administration relies on robust, non-fragile lookup methods.

For two-dimensional coordinate lookups (e.g., retrieving a tariff rate based on both Member State row and Product Category column), public administrators use the two-way INDEX/MATCH formula:

=INDEX(Tariff_Matrix, MATCH(Target_Country, Country_List, 0), MATCH(Target_Product, Product_Headers, 0))

Conditional Logic & Multi-Criteria Aggregations

Administrative decision rules frequently require evaluating multiple operational conditions:

• IF & Nested IF: Evaluates a single logical test: =IF(B2>=50, 'Compliant', 'Infringement'). When multiple tiers exist, nesting IF statements becomes unreadable and prone to parenthesis errors.
• IFS Function: Evaluates multiple conditions sequentially without nesting: =IFS(C2>=90, 'Optimal', C2>=75, 'Satisfactory', C2>=50, 'Review Required', TRUE, 'Deficient'). The final TRUE condition serves as the default catch-all.
• SUMIFS and COUNTIFS: Perform multi-criteria aggregations across administrative datasets. Unlike legacy single-condition functions, the multi-criteria syntax handles diverse conditions simultaneously:
  • =SUMIFS(sum_range, criteria_range1, criteria1, criteria_range2, criteria2, ...)
  • =COUNTIFS(criteria_range1, criteria1, criteria_range2, criteria2, ...)
  • Critical Syntax Distinction: In SUMIFS, the sum_range is strictly the first argument, whereas in legacy SUMIF, the sum_range was the final argument.

Cell Referencing Mechanics in Administrative Calculation Models

Formulas copied across administrative worksheets adjust according to referencing markers. Misunderstanding the placement of the dollar sign ($) is a primary source of budget modeling errors:

• Relative Referencing (A1): Both column and row adjust dynamically when the formula is copied or filled across cells. Used when calculations apply across adjacent tabular rows (e.g., multiplying quantity in column A by price in column B row-by-row).
• Absolute Referencing ($A$1): Both column A and row 1 are permanently locked. Copying the formula across rows or columns maintains an exact, unchanging reference to cell A1. Used for universal model parameters, such as a statutory co-financing rate, standard VAT percentage, or common inflation factor.
• Mixed Referencing ($A1): Column A is locked, while the row adjusts dynamically. Essential when creating horizontal summary tables where the input metric always resides in column A regardless of how far right the formula is copied.
• Mixed Referencing (A$1): Row 1 is locked, while the column adjusts dynamically. Essential when applying a common header value across a vertical column of records.

Data Validation Rules & Error Alert Typology

To ensure Member State data submissions conform to institutional reporting standards, administrators apply Data Validation rules to input fields:

• Validation Criteria: Restricts user inputs to whole numbers, decimal ranges, valid date intervals, text length limits, or specific list items (e.g., restricting Member State codes to a static dropdown: BE, BG, CZ, DK, DE...).
• Input Messages: Contextual tooltips displayed when a user selects a cell, providing operational instructions before data entry occurs.
• Error Alert Levels: Dictates system response when an operator enters invalid data:
  • Stop Alert: A hard block. Displays an error dialog with Retry and Cancel. The invalid data cannot be committed to the cell under any circumstances.
  • Warning Alert: A soft warning. Displays 'Continue? Yes / No'. Allows the user to override the validation rule and retain the invalid entry if exceptional justification exists.
  • Information Alert: An informational notification. Displays 'OK'. Notifies the user of the standard range but automatically accepts the entered value without requiring explicit override.

Multidimensional Pivot Tables

Pivot Tables enable rapid data summarization, multi-variable policy analysis, and exploratory analysis without writing complex array formulas:

• Four Core Quadrants: Filters (global slicers), Columns (horizontal dimensions), Rows (vertical categories), and Values (numeric aggregations, such as Sum, Count, Average, or % of Total).
• Calculated Fields: Custom mathematical expressions created within the Pivot Table engine (e.g., calculating the absorption rate as =Allocated_Funds / Programmed_Funds), preserving source data integrity.
• Slicers and Timelines: Visual filtering controls linked across multiple Pivot Tables and charts to construct interactive policy dashboards for executive briefings.

---

Digital Accessibility Standards & Document Remediation

Public sector information must be equally accessible to all European citizens, including persons with visual, auditory, cognitive, or motor impairments. Accessibility is a legal obligation for Member States' public-sector bodies under the Web Accessibility Directive, and the EU institutions apply the same benchmark to their own web content as a matter of policy.

The EU Legal and Standard Framework

• Directive (EU) 2016/2102: The Web Accessibility Directive requires the websites and mobile applications of Member States' public-sector bodies to meet harmonised accessibility requirements. The EU institutions themselves are not addressees.
• European Standard EN 301 549: Defines statutory accessibility requirements for public procurement of ICT products and services within the EU. It incorporates the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for web content, electronic documents and software, and conforming to it gives a presumption of compliance with the Directive.
• PDF/UA Standard (ISO 14289-1): The international standard for Universal Accessibility in PDF documents, defining exact technical requirements for tag hierarchies, content navigation, and semantic reading order.

Technical Remediation for Accessible PDF Documents

Converting a working word processor document into an accessible public PDF requires strict adherence to technical remediation protocols:

1. Tagged PDF Structure: An accessible PDF must contain an underlying Tags Tree that parallels the visual display. Assistive technologies (such as screen readers and refreshable braille displays) parse the tag hierarchy (<Document>, <H1>, <P>, <Table>, <Figure>), completely ignoring visual typography. Documents lacking tags appear as blank pages or unstructured character streams to screen readers.
2. Artifact Marking: Decorative visual elements—such as aesthetic background borders, colored separator rules, or background watermark logos—must be tagged as Artifacts. Marking elements as artifacts instructs assistive software to ignore them, eliminating cognitive clutter.
3. Logical Reading Order: In multi-column publications, visual reading order does not always match programmatic reading order. Administrators must verify the Reading Order Panel to ensure assistive software does not read across columns horizontally (reading line 1 of column A followed by line 1 of column B), but instead traverses column A completely before proceeding to column B.
4. Alternative Text (Alt-Text) for Graphics: Every image, organizational chart, and data visualization conveying substantive information must include concise, descriptive alternative text:
   • Alt-text must describe the meaning and administrative conclusion of the visual rather than its physical appearance. For instance, rather than 'Bar chart with green and blue bars', the alt-text must state: 'Bar chart illustrating EU-27 renewable energy share rising from 18% in 2020 to 24% in 2025'.
   • Never begin alt-text with redundant phrases such as 'Image of' or 'Graphic showing', as screen readers announce the element as an image automatically.
5. Color Contrast Ratios: Under WCAG 2.1 Level AA, the visual presentation of text and images of text must maintain a minimum contrast ratio against the background:
   • Standard Body Text (below 18pt regular or 14pt bold): Minimum contrast ratio of 4.5:1.
   • Large Text (18pt+ regular or 14pt+ bold): Minimum contrast ratio of 3.0:1.
   • User Interface Components & Graphical Objects: Minimum contrast ratio of 3.0:1.
   • Prohibition of Color Alone: Color must never serve as the sole visual means of conveying information, indicating an action, prompting a response, or distinguishing an element (e.g., distinguishing audit failures using both red shading AND a visible text label or distinct icon).
6. Accessible Data Tables: Tables must be used exclusively for structured data presentation, never for visual page layout. Accessible tables require:
   • Designated header rows (<TH>) with explicit scope attributes (Scope='Col' or Scope='Row').
   • Header rows configured to repeat automatically across page splits.
   • Strict avoidance of merged, split, or nested cells, which sever the mathematical coordinate relationship between data cells (<TD>) and their governing headers.