Every department must complete annual acknowledgment of key policies. What organization-wide supporting process should compliance run?
Select an answer to reveal the explanation.
Short Explanation
Annual policy sign-off is a company-wide roll call, not a rumor that people clicked something once. Run a compliance campaign that covers every department. Intranet hope, binder archaeology, and new-hire-only skips leave gaps in acknowledgment evidence.
Full Explanation
Organization-wide acknowledgment campaigns assign and track policy acknowledgment tasks across departments for a defined period such as the annual cycle. Running that campaign creates measurable completion status for civic enterprise policy acknowledgment reporting to leadership and examiners. Posting policies on the intranet once and assuming acknowledgment without tracking fails by concept because passive posting proves publication, not individual acknowledgment by staff. Asking managers to collect wet-ink signatures in binders with no IRM campaign record fails by concept because offline binders are hard to reconcile, incomplete, and invisible to compliance dashboards. Acknowledging policies only for new hires and skipping the annual cycle for existing staff fails by concept because returning employees must reaffirm when policies renew or change. Exam caveat: CIS-RC uses compliance campaigns to demonstrate enterprise annual acknowledgment, not intranet hope or new-hire-only shortcuts. Operational check: launch an annual policy acknowledgment campaign across all departments, monitor completion by department, and confirm outstanding tasks remain visible until employees acknowledge.