A system migration is planned quickly to meet operational deadlines. Records governance is seen as a blocker rather than a requirement. What’s your role? - Insist on full controls? - Negotiate minimum safeguards? - Document risks and proceed? Explain your approach.

A new system automatically captures large volumes of content as “records”. Storage grows rapidly, search becomes harder, and disposal is unclear. What do you do next? - Turn automation off? - Refine capture rules? - Accept the trade-off and document the risk? Explain your reasoning.

Automation can significantly improve records capture and classification when it is well designed and governed. Without clear rules, automation can replicate mistakes at scale. Governance must guide automation decisions from the outset, not be added later. Reflection questions: - Are records automatically captured where it makes sense today? - Are the rules behind that automation clearly defined? Action: Identify one business process that could benefit from automated records capture.

Cloud platforms introduce new governance challenges, including data residency, access control, and retention enforcement. Governance must extend beyond on-premise systems. Clear responsibilities are critical. 1. Do you know where your records are stored in the cloud? 2. Who controls retention settings? Action: Review retention capabilities in one cloud platform you use.

Email remains one of the most common and unmanaged record types. Without clear rules, important decisions are lost or retained indefinitely. Clear guidance reduces risk and improves efficiency. 1. Do your employees know which emails are records? 2. Is there guidance on email retention? Action: Draft a short guideline defining when an email becomes a record.