Content management: responsibilities and practical exercise
Content management organises who writes, translates, approves, publishes and retires information. It maintains relationships between a source, its versions and pages reusing it. The aim is to make changes traceable and manageable, including when a regular team member is absent.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
Organise publication and maintenance in a CMS or site files, with clear owners, sources, versions and approval states.
Typical activities
Structure fields, categories, media and publishing rules.
Plan review, validity dates and retirement of outdated content.
Coordinate language versions and check links after changes.
Responsibilities to agree with the team
CMS access does not authorise inventing missing data or changing facts without approval. Coordinate contributors, editorial owners and technical teams.
A first piece of work to demonstrate
Update an entry with its source, authorised media and decision history, then check its cards and links.
This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.
Prepare a program publication in ten languages with identified managers.
Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.
Set ID, Source, Owner and Status for each content.
Distinguish writing, translation, validation and publication.
Identify documents or versions that have become inconsistent.
Organize removal, archiving and revision after a change.
Deliverable and checks
For the multilingual programme, provide an inventory with identifier, source version, owner and status by language. Identify dependent pages and messages and distinguish ready, pending and outdated items. Explain who may publish and how to find the released version.
Change a demonstration date in the source and locate every affected language and channel. Distinguish reviewed translations from those needing revision. Check that a replacement team member can follow the process without using a colleague’s personal account.
Publishing in multiple languages also creates update obligations. An approved translation may become obsolete when its source changes.
Collaboration to explore: Web writing.
Fictional deliverable excerpt : A schedule links each item to its owner, version, review status and next review date. An unapproved translation is not marked ready merely because the source text is ready.
What passes between the roles : The text, sources and open questions enter the approval process together. Follow-up also retains related pages, languages and the person who will review the content when circumstances change.
Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.
Sample excerpt
Reference information: revised reception hours.
Approved source: reception manager.
Copies to review: contact page, footer and language versions.
Deadline: effective date confirmed by the organisation.
Check: old hours absent from pages still active.
Boundary case: revised hours are approved but take effect on Monday.
Check: the prepared version does not prematurely replace information still in force.
What the author should be able to explain
The record identifies a reference and someone who can validate it.
Updating includes repeated copies, not just the first page found.
The effective date differs from the day the change is prepared.
Does fixing one page complete the update?
Only if no other active page repeats the old information. Also inspect navigation, translations, structured data and organisation-controlled material wherever it contains the same fact. Record the effective date and time zone if the changeover time matters. After publication, check a previously visited page and a fresh visit, plus the planned language versions. A cached copy can explain a discrepancy without calling for a second contradictory edit.
Assess the quality of the work
The exercise follows one date reused in a record, listing and several languages. Content management should identify the reference value, correct it and locate reuse. Model quality emerges when a value is missing or changes, not only when every field is completed at initial publication.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
Assess the quality of the work
Skill
Evidence to examine
Failure to spot
Field and provenance
Define each field’s meaning, unit or format, source and treatment of unknown values. Identify who can confirm information before publication.
Absent data is replaced with a plausible value, or one field alternates between a time and an instruction unsuitable for reuse.
Triggered review
Assign an owner and review trigger such as an offer change, expired date or received correction. Distinguish actual review from automatic metadata changes.
The displayed date appears recent although information was not reviewed, or correction stalls because nobody owns approval.
Reuse
Related translations, lists and downloads are identifiable.
Editing a record leaves an old version in categories.
Propagating corrections
Identify pages, translations, listings and structured data repeating the same information.
A changed date reaches related destinations; an older announcement does not contradict the current entry.
A focused next step
On a working copy, correct the reference date and locate listings, translations and structured data reusing it. Also test the previous address if content is removed. The intended result is consistent information and an understandable journey; changing only the main record does not complete the correction.
A WordPress content export can include posts, pages, post types, comments, custom fields and taxonomies. Its scope depends on selected filters. Check media files, theme, plugins and configuration separately before treating it as a complete migration.
If-Match compares a strong validator before a write. Under the illustrated contract, a stale version receives 412; keep the draft to compare changes.
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
A review case to reproduce
A correction updates one occurrence
Situation to examine
A price changes in the page body while the old value remains in a FAQ, document or another language.
Proposed check
Identify reference data and derived supports. Review visible occurrences, metadata and structured data. Assign corrections and inspect downloads before closing the update.
Evidence to retain
An occurrence log records source, owner and correction status. The data is consistent in supports actually presented to visitors.
Fictional finding example
A fictional price changes from €120 to €140. The page shows €140, but its FAQ and English version still show €120.
Interpret this outcome
Start from the approved value and correct every occurrence. A page modification date does not prove that all reused values were updated.
Three complementary checks
Fictional cases: adapt these expectations to your test contract and retain the limits of the check.
1Approved reference
2Located copies
3Checked effective date
Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.
Scenario variations and expected evidence
Variation to test
Expected result in this case
Evidence to hand over
A change is prepared for Monday
Keep current information until the effective date
Prepared version, date and owner
A copy still shows the old value
Find the occurrence and how it is served
Page, language and cache state examined
The decision changes before publication
Withdraw or correct the pending version
Revised decision and affected copies
Decision to hand over : Close the update after checking reused information and the schedule actually applied.
In-depth exercise: Prepare a multilingual publication consisting of a page, a document and a photo. Define the owner of each information and its validation status. Simulate a date change in the source version, then identify all the items to resume. Test also the removal of the old document. The publication must retain its identifiers and useful links. A translated version should not remain presented as up-to-date if an important condition has changed in the source text.
What to deliver with your work
Inventory of content and related documents
Owner, status and validation date of each item
List of translations and dependencies to resume
Procedure for publishing, replacing and archiving
Acceptance criteria
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
A source change is related to the languages concerned.
A replaced part does not remain offered as a current version.
The published contents have an identifiable validation manager.
Transmit inventory, validation process and archiving rules. Keep a distinction between technical change date and editorial verification date. The person picking up the content must know why a document is linked and in which languages it exists. When information is pending, make this status visible in the tracking instead of arbitrarily completing the form.
Compare inventory, responsibilities and publishing rules. Adding pages differs from recovering a catalogue with versions, sources and translations.
Recurring operation
Specify review rhythm, outdated-information handling and media replacement. Separate editorial activity from technical upkeep and assign necessary approvals.
Exit and handover
Request structured data, sources and status history. Check that another team can publish, correct and retire content while preserving useful URLs and relationships.
How should a correction across several languages be prepared?
Identify the reference value, its occurrences and approvers for each language. State what changes, why and from when. Then check pages, confirmations and components reusing the data, rather than the main text alone.
How should outdated information be handled?
Decide first whether it should be corrected, archived or retired and whether a replacement exists. Assign the decision to the content owner. Update navigation, search and relevant links; a dated archive should not keep offering a closed registration or offer.
How should a missing field in a collection of entries be handled?
Define whether it is required, optional or unconfirmed. Avoid filler values that resemble facts. An explicit state and correction owner allow completion without inventing information to standardise entries.