Reference point

Example

Present reference

The delay is reported to affect four client accounts.

Past reference

The bottleneck is understood to have originated in Week 3.

Future reference

The resolution is expected to be delivered by Friday.

With modal

The shortfall is believed to have been foreseeable.

Modal + have been

Example

should have been

The flag should have been escalated within 48 hours.

could have been

The delay could have been prevented with earlier intervention.

might have been

The risk might have been identified during the planning phase.

would have been

The client would have been notified had the protocol been followed.

must have been

The decision must have been taken without full information.

Impersonal clause

That-clause content

It is understood that

the delivery target was not adjusted when staffing changed.

It is believed that

the resourcing gap emerged in early February.

It has been established that

the project manager raised a flag on 14 January.

It is alleged that

the escalation protocol was not followed.

It is recommended that

all future engagements undergo a mid-point resourcing review.

Subject-shift form

Equivalent it-clause

The cause is believed to stem from a staffing shortfall.

It is believed that the cause stems from a staffing shortfall.

The flag is known to have been raised six weeks prior.

It is known that the flag was raised six weeks prior.

The protocol is said to have been unclear.

It is said that the protocol was unclear.

The decision is alleged to have bypassed standard sign-off.

It is alleged that the decision bypassed standard sign-off.

Register comparison — The same fact, four levels of formality

● Level 1 — Board report (incident section):

   "It has been established that the resourcing shortfall, which is believed to have originated in the week of 3 February, was not escalated in accordance with the project governance framework. This should have been identified and addressed at the mid-point review."

● Level 2 — Executive briefing:

   "We now understand that the resourcing issue started around early February. The flag that was raised should have been escalated — that didn't happen, and we're addressing that process gap."

● Level 3 — Team meeting:

   "So it turns out the staffing problem started in February. Someone flagged it, but it didn't get escalated the way it should have."

● Quick message to a colleague:

   "Basically someone spotted the problem in Feb but it never got escalated. Now we're dealing with it."

Term

Meaning

Example in context

to escalate

to raise an issue to a higher level of authority

"The flag was not escalated within the required timeframe."

to allege

to claim something without full proof

"It is alleged that the protocol was not followed."

to stem from

to originate from, to have as its root cause

"The delay is understood to stem from a staffing shortfall."

foreseeable

able to be predicted or anticipated in advance

"The risk was foreseeable given the timeline."

to mitigate

to reduce the severity of a risk or problem

"Steps have been taken to mitigate the impact."

remediation

the process of correcting or fixing a problem

"A remediation plan has been submitted to the board."

post-mortem

a review conducted after a project failure

"The post-mortem identified three process gaps."

accountability

responsibility for decisions and their outcomes

"The report assigns accountability to the project governance team."

to flag

to draw attention to a concern or risk

"The concern was flagged by the project manager on 14 January."

oversight

supervision, or a failure to notice something

"The gap was an oversight in the resourcing review process."

MERIDIAN TECHNOLOGIES | INTERNAL INCIDENT REPORT

Ref: INC-2026-03 | Client: TechNova Solutions | Date: 25 March 2026

3. Findings

It has been established that the three-week delivery delay affecting the TechNova

implementation is attributable to a resourcing shortfall in the engineering

team. The shortfall is understood to have originated during the week of

3 February 2026, following the departure of a senior contractor whose

replacement had not yet been confirmed.

A risk flag is known to have been raised by the project manager on 14 January

2026 via the standard project governance channel. It is now understood that

this flag was not escalated to the project steering committee as required

under the Meridian Project Governance Framework (v2.3).

It is believed that, had the flag been escalated in a timely manner, the

delay could have been prevented or significantly reduced. The resourcing

decision is alleged to have been taken without full visibility of the

downstream delivery commitments to TechNova.

4. Remediation

A revised delivery schedule has been agreed with TechNova and is expected

to be confirmed by 28 March 2026. A full resourcing review of all active

Q2 engagements has been commissioned. It is recommended that the project

governance escalation protocol be reviewed and re-communicated to all

project managers by end of Q1.