# data[].attributes.body
Cybersecurity - cybersafety

# data[].attributes.body
Accessing CNA project funding

# data[].attributes.body
Tracking who is using the apps

# data[].attributes.body
Regular CNA-level communication of new approvals. Let people know there is ongoing work happening.

Potentially showcase examples where existing approved applications were used as opposed in place of a new application.

# data[].attributes.body
Sell the WHY - marry it with data retention & security

# data[].attributes.body
Tech assessment framework = OBJECTIVE; Subjective assessment takes place at diocesan level

# data[].attributes.body
Focus on 80/20 - what’s similar across CNA versus what can be manga Ger or tailored at local level?

Criteria against which assessment is done - marking rubric

# data[].attributes.body
System wide data - when is this needed and appropriate?

# data[].attributes.body
Technical

Pedagogical

Governance

Impacts and need

# data[].attributes.body
Understand ongoing maintenance of assessment - not a once off.

Need to be efficient rather than duplicating effort across all dioceses

# data[].attributes.body
Start at the top. System leadership influence

# data[].attributes.body
Involve users in approval process (eg. threshold assessments)

# data[].attributes.body
Clarity around what the local versus CNA component is. What is the responsibility and what is being delegated to CNA collective

Sharing existing assessments

Proactive approach to what is coming next

# data[].attributes.body
Communication core - winning hearts and minds

Case study approach - how it has worked

Start at the top - System Leadership influence

# data[].attributes.body
Sharing learning journeys across dioceses

# data[].attributes.body
Providing easily accessible resources and information to raise awareness & inform users

# data[].attributes.body
Know what will be achieved through CNA collaboration, and what is required at a diocesan level

# data[].attributes.body
Empowering teachers to understand risks and process, protection of PII and student data.

# data[].attributes.body
Ensure leadership are on board/informed & set expectations across the system

# data[].attributes.body
Clearly define what the process will do and won't do, e.g. will do tech review, won't do pedagogical review