Project Issue Escalation Questions Checklist

Write down what you actually observed in plain terms, keeping what you saw separate from what you concluded it must mean.

The observation stays valid whatever the explanation turns out to be, while the conclusion may not survive the first answer.

Note when you first noticed it and whether it has changed since, because something that is moving raises different questions from something static.

Change over time is often the most useful single piece of information anyone can be given about a concern.

Record whether the concern is about the work itself, about information you were never given, or about how the project is being run, since these travel different routes.

Sending a coordination complaint down a technical route, or the reverse, usually produces no useful answer at all.

Avoid naming a cause in your first description, because attributing it early tends to close down the explanation you actually need.

Once someone has to defend against your theory, they stop volunteering what they know.

Note who else has seen it and what they said about it, including anyone in your household who noticed it independently.

Independent observation strengthens a record and sometimes reveals that it was noticed earlier than you thought.

Check whether this point was raised before, by you or anyone else, and find the earlier record before writing anything new.

A repeated concern is handled quite differently from a new one, and the earlier record shows what was already promised.

Photograph the concern with enough surrounding context that the location is recognisable, not only a tight close-up that could be anywhere.

Close-ups without context are routinely dismissed because nobody can agree what they show.

Gather the written record of what was agreed for that element, so the conversation starts from a shared reference rather than from two memories.

Most concerns reduce to a difference between what was agreed and what is there, which only the record can settle.

Collect any earlier note where the same point was mentioned in passing, since a concern raised twice carries more weight than a concern raised once.

Passing mentions are easy to forget and are often the first evidence that something was known about.

Note anything you have been told verbally about it, with who said it, even where that account contradicts what you can now see.

Contradictions between accounts are themselves useful information for whoever looks at the matter.

Record the condition of anything adjacent that may be affected, before it is disturbed by work to put the first thing right.

Collateral effects are frequently noticed only after the remedial work has covered the evidence of them.

Do not open up, strip back or test anything yourself to gather evidence; ask a suitably qualified professional what should be examined and by whom.

Keep the evidence unedited and store a separate copy, rather than cropping or annotating the only version you hold.

An edited image invites an argument about the editing instead of about the concern.

Check the route that was agreed for raising a concern and use it, even where somebody else is easier to reach on site that afternoon.

Using the agreed route keeps the record clean and prevents the same point arriving twice from different directions.

Ask who the point should go to when it sits between two parties, rather than telling both and hoping one of them takes it on.

A concern sent to everybody is usually treated as somebody else's responsibility by all of them.

Naming who must answer for a concern can turn on terms you have never seen; ask the appointed professional or a suitably qualified adviser to identify the right recipient.

Note whether the person you are raising it with can actually resolve it or can only pass it on, so your expectations match their role.

Expecting a resolution from someone who can only relay the message produces frustration on both sides.

Avoid raising it directly with a trade where the agreed route runs through an appointed professional, since doing so can confuse who is answering for what.

A trade asked directly may act to please you in a way that cuts across the arrangements in place.

Instructing or negotiating directly with a trade outside the agreed route can affect responsibility for the outcome; keep to the route you agreed.

Write down what you are actually asking for at this stage: an explanation, an answer to a specific question, or a proposal for what happens next.

A message that does not state what it wants tends to receive reassurance rather than a response.

Record when and how you raised it, and keep the message itself rather than a later summary of what you think you sent.

The original wording matters if the matter is looked at by anyone who was not part of the exchange.

Ask what is understood to have caused it, and whether that explanation is settled or still being looked into by someone.

An explanation offered on the spot is often provisional, and recording it as provisional protects everyone.

Ask whether anything else on the project shares the same cause, so a single instance is not treated in isolation when it is part of a pattern.

The same underlying cause frequently appears in several places, only one of which happens to be visible.

Ask who is responsible for resolving it under the arrangements in place, and ask for that in writing rather than as a view offered on site.

Responsibility stated verbally has a habit of shifting once the extent of the work becomes clear.

Responsibility and entitlement under any agreement are legal questions; take them to a suitably qualified adviser rather than settling them on site.

Ask what happens to the surrounding work while the matter is unresolved, and whether continuing affects the ability to put it right afterwards.

Some concerns become far more disruptive to address once the next stage has covered them.

Ask what evidence would settle the question of cause, and who would be gathering that evidence.

Naming the evidence turns a disagreement about opinions into a defined piece of work someone can carry out.

Ask what the options are for resolving it and what each one would mean for the rest of the work, rather than accepting the first proposal offered.

The quickest remedy is not always the one with the fewest consequences elsewhere.

Record the agreed next step with the name of the person doing it and a description of what completion of that step looks like.

A step without a named person and a completion description tends to be neither started nor noticed.

Ask how you will be told when the step has been done, and through which channel, so you are not left checking on your own.

Agreeing the notification removes the need to chase and makes silence meaningful.

Note anything you have to provide before the step can happen, such as a decision, access to a room, or an item that has not arrived.

Owners are often the unstated dependency, and nobody tends to say so directly.

Ask whether the resolution changes anything already agreed, and make sure the change is recorded where the original decision lives.

Resolutions that quietly alter an earlier decision cause a second problem later on.

Write down what you agreed not to do in the meantime, such as touching, cleaning or using the affected area, and why.

Innocent cleaning or use can remove evidence or make a remedy harder, and the reason is worth recording.

Keep the matter on your open list until you have written confirmation that it is done, rather than closing it on a verbal assurance.

Verbal closure leaves nothing to point at if the same issue reappears.

Consider asking a suitably qualified independent professional to look at the matter where the explanations you receive conflict with each other.

Conflicting accounts rarely resolve themselves, and each further conversation makes the record harder to read.

Only a suitably qualified professional can assess cause or adequacy; nothing you or the other parties conclude informally substitutes for that.

Ask what an independent opinion would need in order to be useful, and gather that before anything is altered or made good.

An independent view formed after the evidence has gone is far weaker and sometimes impossible.

Note that once an area is put right, the evidence of what was there is usually gone, so record it fully before agreeing to remedial work.

Owners routinely agree to a quick fix and later find they cannot show what the original condition was.

Recognise that questions of contract, insurance and liability are legal matters and belong with a suitably qualified adviser rather than with the parties on site.

Positions taken informally on these questions can be difficult to withdraw from later.

Nothing on this page is legal, contractual or insurance advice; take those questions to a suitably qualified adviser before committing to a position.

Ask whether any authority or the relevant local requirements bear on the matter, and confirm that directly with the responsible body rather than through site conversation.

Second-hand accounts of what an authority requires are frequently incomplete or out of date.

Only the responsible authority can state what applies to your project; do not rely on an informal summary given by anyone else.

Write down what outcome you would consider resolved, so an independent conversation has a clear question to answer rather than a general grievance.

An independent professional can only address a defined question, and defining it is your part of the work.

Keep one continuous file for this matter, with entries added in order, rather than scattering it across separate message threads.

A single chronological file is readable by someone who was not there, which a set of threads is not.

Record every conversation about it, including the ones where nothing was decided, since the absence of progress is itself part of the picture.

Gaps in a record are often read as the matter having gone quiet by agreement.

Note when a promised response does not arrive, and follow up in writing rather than only mentioning it the next time you are on site.

A written follow-up establishes the pattern; a verbal reminder leaves no trace at all.

Keep the tone of the written record factual and unemotional, because it may later be read by people who were never part of the exchange.

An angry record undermines a good point and shifts attention onto how it was raised.

Note the point at which the matter is considered closed, by whom, and on what basis, rather than simply letting the file stop.

A closing entry prevents the same concern being reopened from scratch if something similar appears later.