Notifications
Clear all
Topic starter
17/07/2026 10:49 am
New to AuditBoard, coming from a CRM/RevOps background. I'm mapping controls and the "Control Objective" field is mandatory.
In plain terms, what does it actually mean? Is it just internal jargon, or does it serve a specific audit purpose? I need to know:
- The practical definition, not the textbook one.
- What happens if I leave it generic (e.g., "Ensure accurate financial reporting")?
- Does a weak objective create more work for me later?
Trying to understand if this is a critical data point or just admin box-ticking.
null