Integrated Circulation Reporting Prototype Demo 30 th May 2013

Background Initiated Digital Circulation Reporting project end of Feb 2013  Consolidate Digital reporting via QlikView and strategic data warehouse  Currently in analysis phase to agree requirements and high level design  Followed by build, test and implementation of the solution  Tentative go-live September 2013 Use an Agile approach to build a QlikView prototype in parallel to the analysis phase 2

Project Goals/Objectives 3 NoGoal/ObjectiveSuccess Measurement Metric 1Time saving and error reduction Processing time reduced to 1 man day from 7-8 (??) man days including error handling 2Timeliness of report deliveryReport available on every Monday 3Integrated Digital Circulation reporting Digital report incorporating:  “Unbundling”, “QSS” and “non-QSS” digital data  Linked volume and revenue  Budget/forecast data using a common template across all regions 4Integrated “Print” and “Digital” reporting with standardisation of the global reporting process Single access point for all reporting via QlikView 5Improved report formatting and visualisation Reporting “Dashboard” with KPI warning indication and drill down capability

Project Update 4 NoGoal/ObjectiveCurrent Status 1Time saving and error reduction  iTunes and Android automated  Zinio, Amazon and MULs automation in progress  WorldPay and Nook remains manual 2Timeliness of report delivery  Automation will result in delivery on Monday 3Integrated Digital Circulation reporting  Digital report will include QSS and non-QSS digital data  Volume and revenue rules agreed (nearly!)  Common template and process for providing budget/forecast data agreed 4Integrated “Print” and “Digital” reporting with standardisation of the global reporting process  Prototyping in progress 5Improved report formatting and visualisation  Prototyping in progress

Integrated Reporting KPIs 5 No.KPIEnables Business ToPriority 1Average active paid subs Volume variance Measure growth/decline and take appropriate action MUST 2Total Earned Revenue varianceMeasure growth/decline and take appropriate action MUST 3Revenue per Copy (RPC) varianceMeasure growth/decline and take appropriate action MUST 4YTD average weekly circulation volume against the budgeted average weekly circulation volume target Monitor how year is progressing versus budget MUST 5YTD cumulative earned revenue against the budgeted FY earned revenue target Monitor how year is progressing versus budget MUST Other KPIs to be added in future phases: Starts Volume variance Sales Revenue variance Revenue Benefit of Premium Bundle Volume Impact of Premium Bundle

Integrated KPI Reporting Dimensions Product Groups - Bundle (aka Premium), Print only, Digital only and Legacy Global Regions - Americas, EMEA, Asia Regions - NAM, LAM, UK, Europe, MEA, India, Rest of Asia Input Route – QSS and non-QSS Time Periods  Week  Month  Last Year  YTD Purchase Type  Subs - Revenue Generating (RG)  Subs - Non-Revenue Generating (NRG)  Single Issues  Bulk 6

Prototype Objectives Confirm that Integrated QlikView reporting fits business needs Demonstrate improved report formatting and visualisation  KPI Dashboard  Trends  Detailed Analytics Gather feedback from stakeholders Not meant to be a tactical or the final solution 7

Prototype Constraints Data has been created and uploaded into QlikView manually  No automation of feeds  No automated transformations applied Data set used is for Americas* and UK Single Issue & NRG break-up for UK is not available Revenue for Third Party Sales is based on fixed RPC Currency conversions have not been applied to data No budget/forecast data = No variance calculation * Americas Bulk and NS data not available 8

Prototype 9

Next Steps Project Team  Consolidate business requirements  Group sessions to review and sign-off requirements  Planning for build, test and implementation phase  Build road map What we need from the stakeholders  Make yourselves available for consultation as you always have!  Provide subject matter expertise  Focus on “what we need in the future” rather than “how we do it now”  Aim for a single global reporting model 10