# Organizational content system: implementation and maintenance checklist

Companion article: How to keep business content consistent and up to date

Version V1.0 | Internal working and limited implementation reference | Andrew David W.Y.

Start with one actual business activity. This general reference must be adapted to the organization's authority, resources and work. Example IDs do not establish that a real company has implemented the system.

## 1. Define the initial scope

| Item | Entry |
| --- | --- |
| Problem to solve |  |
| Business and content scope |  |
| Main users and audiences |  |
| Initial channels, materials and languages |  |
| Exclusions and reasons |  |
| Existing sources and main discrepancies |  |
| Authorized scope/resource confirmer |  |
| Owner, backup and handover method |  |
| Staffing, production, translation and maintenance resources |  |
| Criteria for expanding the limited scope |  |

## 2. Inventory existing materials

One material per row. Keep originals under access control; this table may contain authorized references only.

| Material ID/name | Purpose, audience, channel and language | Current version and actual location | Current users | Content owner | Check result and next action |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

Conclusions may be: continue using, evidence needed, revision needed, expired, internal only or discontinue. “File received” is not “content verified”.

## 3. Record shared content and evidence

An entry may define service scope, standard wording or indicators. Keep IDs stable and manage versions for actual changes.

| Field | Entry |
| --- | --- |
| Content ID/name | Example ID C-014; assign actual-use IDs separately |
| Content type | Business fact / Positioning claim / Target or plan / Illustration |
| Confirmed content and necessary conditions |  |
| Original evidence, index and check date |  |
| Period, units, entity and business scope |  |
| Fact-checking owner and conclusion |  |
| Authorized confirmer, date and approval record |  |
| Permitted audiences, channels and languages |  |
| Current usable version and effectiveness conditions |  |
| Next review date or trigger |  |
| Invalidation conditions and handling |  |
| Related material IDs/links |  |
| Maintenance owner and backup |  |

Record factual status, publication status and actual channel updates separately. Agree meanings of draft, verification pending, confirmed, review pending and discontinued. A newer version does not automatically mean facts remain valid or publication is authorized.

## 4. Connect organization, business and scenario levels

| Level | Question to answer | Referenced content IDs | Output materials | Conditions that must remain |
| --- | --- | --- | --- | --- |
| Organization | Who the company is, whom it serves and what it does |  |  |  |
| Business | Specific problem, method, capability and limits |  |  |  |
| Scenario | The audience's current decision and next need |  |  |  |

Adjust detail as needed, but retain meaning-critical conditions in this content, not hidden solely in other files.

## 5. Assign responsibilities and confirmation authority

| Role | Main responsibility | Assigned person | Confirmation authority / Escalation beyond scope |
| --- | --- | --- | --- |
| Business owner | Check facts, scope, dates, figures and conditions |  |  |
| Content owner | Organize levels, audience-specific content and references |  |  |
| Visual/production owner | Text/graphics, templates, clarity and actual presentation |  |  |
| Authorized confirmer | Approve audience, channel and scope within authority |  |  |
| Specialist reviewer, where applicable | Handle matters needing professional confirmation |  |  |
| Channel owner | Publish, replace, discontinue and verify actual results |  |  |
| Ongoing maintenance owner | Receive changes, trace impacts, review and archive |  |  |

One person may combine suitable roles, with clear authority. Business checks, brand wording, publication approval and actual channel updates do not replace each other.

## 6. Checks before and after publication

| Check item | Evidence of passing / Issue and owner |
| --- | --- |
| Facts have sources; figures have units, periods and scope |  |
| Targets, plans and examples are not presented as actual results |  |
| Audience, channel and assets match publication permission |  |
| Necessary conditions are visible in this content |  |
| Confirmed template used; proposals not presented as adopted standards |  |
| Languages align in meaning, names, statuses, graphic text and downloads |  |
| Readable on phones; graphics and links actually usable |  |
| Approval records complete; required post-edit rechecks performed |  |
| Actual pages, images, subtitles and downloads opened and checked after publication |  |
| Current access points, owners and review triggers registered |  |

Check layout-only changes within their scope. If meaning, conditions or figures change, reopen the related content review.

## 7. Complete one change cycle

Register the change, then handle each affected item.

| Change record field | Entry |
| --- | --- |
| Change ID / Proposer / Date | Example ID U-006; assign actual-use IDs separately |
| Related content ID and previous version |  |
| Change type and reason | Fact change / Correction / Authority change / Wording / Layout |
| Scope affected in accuracy or use permission |  |
| Whether to suspend use first, and who handles it |  |
| New evidence and checking conclusion |  |
| New version, approval and effectiveness conditions |  |
| Affected materials, channels and languages |  |
| Internal archive location and old/new relationships |  |
| Open matters, owner and review arrangements |  |

**Impact list: one entry per material and actual publication location.**

| Content ID / Change ID | Material ID, location and language | Action | Owner | Action status | Actual check evidence and date | Outstanding items / Next action |
| --- | --- | --- | --- | --- | --- | --- |
|  |  | Update / Replace / Discontinue / Notify |  |  |  |  |

Separate pending, edited/not published, published/not checked, checked, and unreplaceable/follow-up pending. If retaining use, record reviewer and reason; do not classify this as an unchecked omission.

Check webpage text, SVG text, video subtitles, translations, downloads and distributed materials separately. Confirming a new version does not synchronize every channel.

Open and verify replaceable materials. For irretrievable distributed files, record known destinations/risks and notify reachable users. A notice is not evidence of retrieval or replacement.

Close only after the entire current scope is handled and checked. Keep uneditable/unreachable items pending with owners; report completed parts without claiming all channels complete. Public access points offer current versions by language and authority. Keep discontinued working versions/history internally; genuinely required public historical reports retain their original content with clear date, status and scope.

## 8. Rehearse before expanding

| Stage | Work to complete | Basis for advancing |
| --- | --- | --- |
| Define limited scope | Choose business, audience, channels, roles and resources | Document issues and current boundaries confirmed |
| Build shared content assets | Content entries, evidence, references and templates | Facts and publication scope confirmed; sample legible/usable |
| Controlled use and change exercise | Publish a sample, then complete a real or clearly labelled simulated change | Impacts traceable; review, update and actual checks completed |
| Handover maintenance; review expansion | Arrange recurring review, backups, budget and new scope | Ongoing owner, open-issue ownership and reviewed maintenance capacity for expansion |

Use fictional/de-identified exercise content; do not publish false test commitments to real audiences. Test records are not actual operating results.

Combine routine and event-triggered checks. Record each review interval and who initiates updates after factual, authority or scope changes. Set intervals by change rate and use, not a universal day count.

Assess accuracy/usability, update completeness, user understanding and communication effects separately. Track time to find current versions, obsolete remnants, repeated questions, rework and maintenance effort with defined scope and measures. Publication/view counts alone prove neither trust, sales nor operating improvement.