This page defines how the Unicis Handbook is kept accurate, current, and useful. A handbook that is not maintained is a liability — it creates confusion and erodes trust both internally and externally.
Each section of the handbook has a designated owner responsible for keeping it current.
| Section | Owner | Review Cadence |
|---|---|---|
| Leadership, V/TO, Scorecard | CEO (Predrag) | Quarterly |
| Trust Center (all sub-pages incl. TPSRM, Policies, Controls) | CEO (Predrag) | Quarterly + after any security incident |
| Development, SDLC, Testing | CEO (Predrag) | Per release cycle |
| Core Processes | CEO (Predrag) + relevant process owner | Quarterly |
| Communications, Tech Stack | CEO (Predrag) | When tools change |
| Recruitment, open positions | CEO (Predrag) | Monthly |
| EOS pages | CEO (Predrag) | After each quarterly planning session |
| Vendor/Service Providers, Subprocessors | CEO (Predrag) | When vendors change |
Certain events must trigger an immediate handbook update, regardless of the review schedule:
#town-square on MatrixEvery substantive page should include a “Last reviewed” note at the bottom:
//Last reviewed: [Month Year] — [Owner]//
If a page has not been reviewed in more than 6 months, flag it with:
<wrap warning>This page may be outdated. Last reviewed: [date]. Please contact the CEO to request a review.</wrap>
Each year in Q1, the CEO conducts a full handbook review aligned with the ISO 27001 internal audit cycle:
Last annual audit: — (due Q1 2027)
Anyone — team members, contractors, and community members — can suggest edits:
For structural changes (new sections, new pages, navigation), open a discussion in the #handbook Matrix channel first.
Last reviewed: June 2026 — Predrag