Domain I · Area I-CA1 · Reporting technology, automation and structured data

I.1Select, implement and govern reporting technologies

Working Draft version 1.1

Purpose and scope

This unit covers the capability to define requirements, evaluate, select, implement and govern digital tools used for sustainability reporting, including data, workflow, collaboration, evidence, disclosure, filing and monitoring technologies. It includes fit for purpose, interoperability, ownership, configuration, access, data portability, vendor dependence, controls, testing, support, change, continuity and exit arrangements.

Applied competency statement

Can define reporting-technology requirements, evaluate and select suitable tools, support controlled implementation and maintain ownership, configuration, access, change, continuity and exit governance.

Boundary and escalation

This unit owns reporting-technology requirements, selection, implementation and lifecycle governance. E.10 owns application and data-quality controls, I.2 owns automation design and I.9 owns enterprise digital and AI governance. It does not provide cyber-security, software assurance, procurement legal opinion or enterprise-architecture approval.

Key quality risks

Selecting a tool because of marketing claims or feature volume rather than reporting needs; tool ownership and decision rights undefined; technology dictating reporting methodology; missing source, evidence or audit-trail capability; weak interoperability or export; configuration not tested; excessive administrator access; vendor lock-in; unclear data location or subcontractors; critical workflows dependent on one person or unsupported product; and no continuity, migration or exit plan.

Required knowledge · 6

I.1-K01

Understands common data, workflow, evidence, collaboration, disclosure, taxonomy, filing, analytics and AI tool categories and their role in the reporting process.

Knowledge Type: Reporting technology landscape · Normative Weight: Core

I.1-K02

Understands functional and non-functional requirements, users, volumes, integrations, availability, accessibility, auditability, configurability, portability and support.

Knowledge Type: Requirements and fit · Normative Weight: Core

I.1-K03

Understands interfaces, APIs, import and export, identifiers, master data, versioning, source systems, lineage and the risks of duplicate or disconnected platforms.

Knowledge Type: Architecture and interoperability · Normative Weight: Core

I.1-K04

Understands vendor competence, service model, subcontractors, data location, licensing, intellectual property, support, roadmap, resilience, lock-in, exit and replacement considerations.

Knowledge Type: Vendor and lifecycle risk · Normative Weight: Core

I.1-K05

Understands configuration, testing, migration, acceptance criteria, role design, access, evidence, incident, backup, continuity, change and release controls.

Knowledge Type: Implementation and controls · Normative Weight: Core

I.1-K06

Understands accountable ownership, approval, risk acceptance, user responsibilities and the distinction between reporting-tool assessment and IT, legal, security or assurance conclusions.

Knowledge Type: Governance and professional boundary · Normative Weight: Core

Applied skills · 5

I.1-S01

Translate reporting processes, users, data, controls, evidence and publication needs into prioritised technology requirements and use cases.

Skill Type: Core applied capability · Observable Output or Result: Reporting-technology requirements and use-case specification

I.1-S02

Assess candidate tools against requirements, interoperability, control, accessibility, vendor, data, security and exit criteria and document trade-offs.

Skill Type: Evaluation and selection · Observable Output or Result: Tool selection, due-diligence and implementation assessment

I.1-S03

Define configuration, migration, integration, testing, acceptance, training, ownership and operating requirements and identify unresolved dependencies.

Skill Type: Implementation support · Observable Output or Result: Controlled implementation and acceptance plan

I.1-S04

Maintain a controlled tool inventory, roles, access, configuration, support, change, incident, continuity and evidence procedures.

Skill Type: Operating governance · Observable Output or Result: Tool inventory, operating procedure and lifecycle record

I.1-S05

Review performance, user and control issues, vendor and version changes, continued fit and migration, retirement or exit needs.

Skill Type: Monitoring and lifecycle control · Observable Output or Result: Tool performance, change and exit review

Professional behaviours · 3

I.1-B01

Does not select or retain technology because it appears innovative, popular or comprehensive where it does not meet defined reporting and control needs.

Behaviour Type: Fit-for-purpose discipline · Non-compensable Requirement: No

I.1-B02

Does not allow a tool's default workflow, taxonomy or calculation to replace approved reporting requirements and professional judgement.

Behaviour Type: Technology neutrality · Non-compensable Requirement: No

I.1-B03

Makes vendor, integration, data, access, control and exit limitations visible and does not conceal dependence or implementation gaps.

Behaviour Type: Lifecycle transparency · Non-compensable Requirement: No

Typical tasks · 4

I.1-T01

Map reporting users, use cases, data, workflows, controls, evidence, interfaces, outputs and operational constraints.

Primary Output Link: I.1-O01

I.1-T02

Evaluate candidate tools and vendors, perform demonstrations and controlled tests and document fit, risks, trade-offs and recommendation.

Primary Output Link: I.1-O02

I.1-T03

Define implementation, migration, configuration, access, integration, testing, acceptance, training and continuity requirements.

Primary Output Link: I.1-O02

I.1-T04

Operate the inventory and procedures, monitor incidents and changes and reassess continued use, remediation or exit.

Primary Output Link: I.1-O03

Expected outputs · 3

I.1-O01

Reporting-technology requirements and use-case specification

Output Type: Professional work product

I.1-O02

Tool selection, due-diligence and implementation assessment

Output Type: Professional work product

I.1-O03

Tool inventory, operating procedure and lifecycle record

Output Type: Professional work product

Proficiency indicators

Level 1 · Foundation

I.1-L1-01

Can use an approved reporting tool, maintain assigned inventory and operating records and identify obvious access, workflow, export or support issues.

Indicator Dimension: Task execution

I.1-L1-02

Can recognise when the tool does not match the approved process or when a configuration, vendor or security question requires specialist escalation.

Indicator Dimension: Quality, judgement and accountability

Level 2 · Practitioner

I.1-L2-01

Can independently define requirements and evaluate, implement and govern a moderately complex reporting tool or platform use case.

Indicator Dimension: Task execution

I.1-L2-02

Can assess trade-offs, resolve routine configuration and workflow issues and explain residual vendor, integration and lifecycle risks to management.

Indicator Dimension: Quality, judgement and accountability

Level 3 · Advanced Practitioner

I.1-L3-01

Can design or critically review enterprise reporting-technology selection, architecture and lifecycle governance across complex groups and tool portfolios.

Indicator Dimension: Method design and review

I.1-L3-02

Can challenge technology-led methodology, resolve significant vendor, integration and lock-in risks and advise governance bodies on investment, control, continuity and exit decisions.

Indicator Dimension: Leadership and governance

Illustrative evidence · 6

I.1-E01

Reporting-technology requirements and use-case specification.

Evidence Type: Work product

I.1-E02

Tool selection, due-diligence and implementation assessment.

Evidence Type: Work product

I.1-E03

Tool inventory, operating procedure and lifecycle record.

Evidence Type: Work product

I.1-E04

Demonstration, test, configuration, migration, acceptance, access, incident, change and exit trail.

Evidence Type: Process evidence

I.1-E05

Documented IT, security, privacy, legal, procurement, records, quality or management review and the practitioner's response.

Evidence Type: Review evidence

I.1-E06

Observed evaluation or defence of a reporting-tool selection or lifecycle decision.

Evidence Type: Observed performance

Assessment · 3

I.1-A-L1

Tool-requirements exercise, operating scenario and situational judgement

Use-case understanding; fit and control recognition; lifecycle and specialist-boundary awareness.

I.1-A-L2

Integrated technology-selection case and professional memorandum

Requirements and selection quality; interoperability and control; vendor and exit risk; implementation and communication.

I.1-A-L3

Complex technology-governance case, portfolio and oral defence

Method design; technology neutrality; portfolio and lifecycle risk; governance advice and oral defence.

Relationships · 10

From	To	Type	Rationale
D.4	I.1	Digital and technology linkage	Reporting platforms and workflow tools may automate the request process subject to controlled requirements.
E.4	I.1	Digital and technology linkage	Reporting platforms and system architecture may support source collection and ownership workflows.
E.10	I.1	Digital and technology linkage	Reporting tool selection and implementation should incorporate defined control requirements.
I.1	D.1	Operational and workflow linkage	Reporting-technology requirements should support the approved reporting strategy, outputs and delivery model.
I.1	E.10	Risk and control linkage	Tool selection and operation should incorporate spreadsheet, system, interface and data-quality control requirements.
I.1	D.7	Digital and technology linkage	Technology providers should be scoped, assessed and monitored through controlled third-party governance.
I.1	I.2	Digital and technology linkage	Selected reporting tools may implement automated workflows requiring separate design, testing and exception control.
I.1	I.9	Governance and role linkage	Tool ownership, approval, inventory, monitoring and lifecycle status are maintained through digital and AI governance.
I.3	I.1	Digital and technology linkage	Tagging tools and filing platforms should be selected and controlled against digital-reporting requirements.
I.8	I.1	Digital and technology linkage	Tool selection should consider data flow, provider retention, access, rights and security conditions.

Role profiles for this unit

Role	Target level	Relevance	Evidence expectation
Corporate Sustainability Reporting Practitioner	Practitioner	Required?	A case or work sample demonstrating independent performance, documented judgement and a reviewable professional output.
Sustainability Reporting Manager or Lead	Advanced Practitioner	Role-defining?	A complex case or verified portfolio, supplemented by oral or observed defence, demonstrating method design, challenge and governance capability.
Sustainability Reporting Adviser or Consultant	Advanced Practitioner	Role-defining?	A complex case or verified portfolio, supplemented by oral or observed defence, demonstrating method design, challenge and governance capability.
Sustainability Data, Systems and Controls Specialist	Advanced Practitioner	Role-defining?	A complex case or verified portfolio, supplemented by oral or observed defence, demonstrating method design, challenge and governance capability.
Assurance Readiness and Reporting Quality Specialist	Advanced Practitioner	Role-defining?	A complex case or verified portfolio, supplemented by oral or observed defence, demonstrating method design, challenge and governance capability.
Investor, Capital Markets and Ratings Disclosure Specialist	Practitioner	Required?	A case or work sample demonstrating independent performance, documented judgement and a reviewable professional output.