Moukangwe & Co., home

Approval should identify the decision

A publishing approval should identify the claim examined, the evidence considered and the version authorised for release. We examine how professional firms can allocate review responsibilities, delegate routine decisions and manage exceptions without losing a usable record of accountability.

Moukangwe & Co. · Published Nov 16, 2026

An approval is a decision to let the firm stand behind a particular piece of professional material. Its value depends on whether the firm can establish what the reviewer examined, the evidence available at the time and the version authorised for release. A message saying “approved” leaves those questions open when the decision and the published item have become separated.

Moukangwe & Co.’s position is that material professional claims should carry a retrievable decision record. The depth of review should reflect the consequences of the claim. Responsibility must remain clear as the material moves between subject specialists, communications teams and external suppliers.

Decide what the approval covers

Technical accuracy, attribution and permission to publish are distinct judgements. A specialist may confirm that an account of a project is accurate while remaining unaware that a client has restricted its public use. A communications reviewer may approve the wording without being qualified to verify a credential. An effective approval process identifies which judgement belongs to each role and where final release authority sits.

This distinction matters because an approval can otherwise acquire more meaning than its author intended. If an expertise statement later becomes disputed, the firm needs to know whether the reviewer verified the underlying experience or merely accepted an edit. Recording the scope of the decision protects the reviewer’s accountability and gives the firm a usable basis for investigation.

Connect the decision to the released version

W3C’s PROV overview describes provenance through the entities produced, the activities involved and the people or organisations responsible (W3C, 2013). Applied to professional publishing, this directs attention to the relationship between a claim, its production history and the people accountable for it.

Consider a hypothetical engineering practice preparing a project account. A project lead checks the technical description, an authorised person confirms the terms of public disclosure, and the communications team prepares the page. The final wording should be identifiable in the approval record. If a later edit broadens the practice’s role from participation to overall responsibility, the earlier approval no longer answers the relevant question. The claim has changed, even if the page looks almost identical.

A practical record therefore connects the supporting source, the reviewed version, the reviewer’s responsibility and the release decision. It also identifies the person who owns subsequent changes. The firm can then trace a disputed assertion without depending on the availability or memory of the original participants.

Apply judgement to the cost of control

Requiring the same review for every amendment creates its own weakness. Senior reviewers become a bottleneck, routine changes accumulate and teams develop informal ways around the process. The firm should distinguish changes that affect meaning from changes that preserve an approved meaning.

A correction to punctuation can follow a delegated editorial route. A change to a professional qualification, the scope of a service or the firm’s role in a project warrants a different decision. Delegation works when the permitted changes are defined, the people applying the distinction understand it and uncertain cases have an escalation route. A short record can be sufficient for a modest claim; a consequential claim requires a stronger evidential basis.

Give exceptions an owner and an end point

Urgency sometimes means that the normal sequence cannot be completed. The firm still needs an authorised decision about what may proceed. That decision should identify the outstanding check, the reason for proceeding and the person responsible for resolving the exception by a stated date.

An exception that remains open indefinitely becomes an alternative process. Oversight should therefore examine recurring exceptions alongside individual incidents. Repeated delays at the same approval point may indicate an impractical control, unclear delegation or insufficient reviewer capacity. The appropriate response follows the cause. Adding another signature can make the original problem worse.

Test whether the record supports a decision

Review a sample of consequential published items and work backwards from the live version. Can the firm retrieve the supporting source, identify the reviewer’s judgement and establish who authorised release? Then examine a material amendment to one of those items. The original control is useful only if the amendment is governed as well.

The resulting measure is the firm’s ability to reconstruct and defend a publishing decision within a reasonable time. Counting approval messages gives a weaker account of control. A sound process leaves enough evidence for another authorised person to understand why the firm stood behind the claim and what should trigger its next review.

W3C (2013). An Overview of the PROV Family of Documents. Edited by P. Groth and L. Moreau. Working Group Note, 30 April.

Discuss this position

If this position bears on a decision your firm is facing, screening is the place to start.