Keep the next publication change manageable

After release, an editor still needs to add an edition, correct an external reference or respond when a provider changes its service. Support should make those tasks easier to handle without leaving the organisation dependent on undocumented knowledge.

Faith Forge Labs can provide defined maintenance and investigation work for websites and connected tools. The arrangement depends on the platform, account access and responsibilities you want covered.

Start with an ownership record

Identify who controls the domain, hosting, content-management system, document store and connected services. Record where renewal notices go and which authorised person can change an account. The organisation should also know who approves publication content and who can request a technical change.

A shared login passed between editors is not a substitute for a maintained access plan. Where the platform supports individual accounts and suitable roles, the handover should explain their use and the procedure when someone leaves or changes responsibilities.

Report the affected task

A useful issue report names the page or record, what the person tried to do and what happened. Include the language edition and relevant role. A public reader opening a file and an editor previewing an unpublished item may use different routes even when the title looks identical.

Send a safe screenshot or fictional reproduction if necessary. Avoid sending credentials or private partner material in an ordinary support message. Access and diagnostic information should be limited to what the investigation requires.

Agree the boundaries of maintenance

Routine platform updates, content changes, connection repairs and recovery work are different activities. The agreement should identify which are included, how requests are prioritised and how additional work is approved. Urgent response, continuous monitoring and round-the-clock coverage should never be inferred from the word “support.”

Provider outages or policy changes may require action by the account owner. We can investigate the website's behaviour and supported options, but cannot promise control over an external institution's page or service.

Preserve the historical reading path

Publication sites need care around old citations. A correction may require a note on the record, a retained edition or a deliberate replacement destination. Deleting an old file because it is no longer featured can disrupt readers who received its URL elsewhere.

Agree who can make those editorial decisions. Technical maintenance can implement the intended result, but the organisation determines which historical material remains useful and what qualifications a reader needs to see.

Practise a successor's task

Instructions are most useful when someone other than their author can follow them. The handover exercise follows a source-reference change through an existing link registry and its public uses. It shows the kind of bounded task that reveals missing access or unclear ownership before the original editor becomes unavailable.

For a new issue, describe the current behaviour. For an ongoing arrangement, review the website-care service and identify the systems and tasks you want it to cover.