Information Request Log

Number Urgency Category Topic Description Comment Submission Return by Note the level of urgency that the information is required to be returned. Organization Structure <Enter response and/or attach <dd.mm.yy> <Select Urgency> Category> <Select <dd.mm.yy> 1 (reporting lines and spans of file> control) About the company Business units / functions Key stakeholders Facilities/Locations Business model of the Understanding on 2 company - Services / Revenue streams (Validate and build up on the - Customers preliminary understanding) - Partners - Vendors - Channel Financials (Current and P&L (Revenue streams, cost 3 Historical) streams) Cash flow Financial ratios On going and planned Not applicable 4 business initiatives Management reviews KRAs 5 (monthly, quarterly, annually) Operational and financial KPIs (Overall, LoB wise, Location wise) Other monitored parameters Existing Contracts SLAs and penalty clauses, 6 Commercial models

Name <Name>

Requestor/EY contacts Email <Email>

Telephone

Name <Name>

Client contacts Email <Email>

Telephone <Phone>

Follow-up Date <Date>

Status <Select RAG>

<Phone>

7 8 9 10 11 12

Contractual terms with top vendors Process and procedures

SLAs and penalty clauses, Commercial models Existing process documentation(operating model etc) High level only

Skill profiles and training and development programs Technology architecture

On going and planned technology initiatives Knowledge management

Applications, tools etc (User manuals) History of changes New Platform development

Data Tracking and measurement process

13

DTAC

Business model and other relevant details

<Enter response and/or attach <dd.mm.yy> file>

<dd.mm.yy>

<Name>

<Email>

<Phone>

<Name>

<Email>

<Phone>

<Date>

<Select RAG>

[insert member firm's legal name] 200[9]. All rights reserved. Confidential and proprietary. Field descriptions Urgency - Note the level of urgency that the information is required to be returned (e.g., Low - one week; Med - three days; High - one day) Category - Note the type of information being requested - data, meetings, system access Description - Provide a brief description of information being requested (e.g., approval authority listing for accounts payable) Purpose - Provide a brief purpose for the request (e.g., to understand level of approval authority) Comments - Any additional comments e.g., how the request was made - e-mail, phone, etc Submission - Date the request was submitted to the client Return by - Date the data is requested to be sent to EY

EY contacts - The name, email and telephone number of the EY contact requesting the information Client contacts - The client name, email and telephone number of the client contact who the request was sent to Follow-up Date - Use this field to record follow-up request dates, if required Status - Status of the request - Outstanding (information not received); Incomplete (partial or incorrect information received); Confirmed (information received and is what was requested)