Project Question Tracking Checklist

Keep one place, reachable from wherever you happen to be, where a half-formed question can be dropped without being tidied up first.

If capturing a question requires effort, the questions that arrive while you are busy are the ones that never get captured.

Write the question down as it occurs, including where you were standing and what prompted it, not just the question itself.

The prompt is usually what makes a question intelligible once you come back to it, and it is the part memory drops first.

Encourage other household members to add their questions to the same list rather than raising them separately with whoever they meet.

Questions asked in parallel by different people produce inconsistent answers that then have to be reconciled.

Note questions that come up while looking at a drawing, and mark which drawing version and which part of it they refer to.

A drawing question without its reference is almost impossible to answer, because nobody can tell what you were looking at.

Capture questions that arise on site before you leave the property, since these are the ones most reliably forgotten on the way home.

Site questions are triggered by something physically in front of you and stop making sense once you can no longer see it.

Accept vague entries at the point of capture and sharpen them later, rather than losing a question while hunting for the right words.

A rough note about an uneasy feeling is often the seed of the most valuable question on the list.

Group questions by the party who can answer them, rather than by the room or the subject they happen to concern.

You raise questions in conversations with people, so a list grouped by person is the one that matches how it will be used.

Mark the questions you should put to a supplier rather than to anyone working at the property, such as what a delivery includes.

Supply questions answered on site tend to be answered from memory, and the memory is frequently of a different range.

Mark the entries that need somebody with formal expertise, and put those to a suitably qualified professional instead of letting them sit among everyday queries.

These subjects need a considered answer from someone with the relevant competence, not a quick reply between other tasks.

These questions cannot be settled by an informal conversation on site; ask a suitably qualified professional and confirm locally what applies.

Note where a question falls between two parties, and ask who should take it rather than putting it to both of them at once.

Questions in the gap between trades are the ones that sit unanswered longest, because each party assumes the other holds them.

Where nobody claims a question, ask the appointed professional to say who should hold it rather than putting it to each party in turn.

Identify the questions only you can answer, and move those off the list and onto your own decisions to make.

Owner decisions parked among questions for others are the most common hidden cause of a stalled project.

Flag the questions where you are not sure who to ask, and take that short list into your next conversation as a question in itself.

Asking who owns a question is a legitimate question, and it is usually answered in a sentence.

Mark the questions that would stop something being ordered or started if they remain unanswered, and keep those visible at the top.

Separating these from the rest is what turns a long list into something a busy professional will actually work through.

Ask which of your open questions are holding up the people working, since their view of what is blocking may not match yours.

The question you consider trivial is sometimes the one preventing an order being placed.

Keep the blocking list short so it retains its meaning, and resist the temptation to mark everything as needing an answer at once.

A list where everything is marked pressing is treated exactly as a list where nothing is.

Note the questions that will become blocking later, and record the event that will make them so.

Knowing what turns a quiet question into an urgent one lets you answer it while there is still room to think.

Where a question is blocking something, ask what is happening in the meantime and whether anything is proceeding on an assumption.

Work sometimes continues around an open question on a working assumption, and it is worth knowing what that assumption is.

Ask the appointed professional what continues while a question stays open, since work does not necessarily pause because you are waiting.

Distinguish a question that genuinely blocks work from one that is simply troubling you, and be honest in how you mark each.

Credibility in this list is a resource; spending it on anxiety leaves nothing for the moment something really does need attention.

State what you already understand before asking, so that the answer corrects your understanding rather than repeating it back to you.

It also exposes the misunderstanding directly, which is often the real thing that needed fixing.

Ask one thing per entry, and split a compound question into separate entries even when they concern the same element.

Compound questions come back partly answered, and the unanswered half is rarely noticed by either side.

Say what you intend to do with the answer, because knowing the purpose often changes the answer that is given.

An answer good enough to choose a finish is different from one good enough to place an order.

Reference the drawing, room or record entry the question relates to, rather than describing the situation afresh each time.

Referencing keeps the question short and lets the person answering look at exactly what you were looking at.

Avoid phrasing that invites a yes or no where you actually want an explanation, and ask what or how instead.

A yes answered quickly can conceal a set of conditions that nobody thought to mention.

Say when a rough answer would be enough for now, so that a question is not held while a precise answer is being prepared.

Many questions sit unanswered because the recipient is waiting to be able to answer fully.

Batch outstanding questions into one message rather than sending a separate reminder for each of them.

A single consolidated list is easier to work through and reads as organisation rather than as pressure.

Repeat the question in the chase rather than referring back to an earlier message the other person now has to go and find.

Every step you remove between the reminder and the answer makes the answer more likely to arrive.

Say which of the outstanding questions matter most to you, so that even a partial reply is useful when it comes.

People answer what they can when they can, and a priority order lets them start with the ones that help you.

Note where you have already had a partial answer, and ask only for the part that is still missing.

Asking again for something already provided is the fastest way to make a reply feel unrewarding.

Check the list for questions already answered before you chase, since chasing an item that was closed weakens the next reminder you send.

Answers arrive verbally, in passing and by other household members, so the list is not always as open as it looks.

If a question has gone unanswered through several attempts, ask who else could answer it rather than simply asking again.

Persistent silence usually means the question is with the wrong person or is harder than it appeared.

Ask the appointed professional how an unanswered question should be escalated on their side before approaching anyone else about it.

Write the answer into the list in the words you were given, rather than in your own interpretation of what they meant.

Technical answers usually carry qualifying conditions, and paraphrasing is how those conditions get lost.

Note who gave the answer and in what setting, since an answer given in passing on site carries different weight from one in writing.

When two answers conflict, knowing the setting of each is often the only way to work out which to rely on.

Close a question only when the answer actually covers what you asked, and reopen it plainly if it turns out that it did not.

Questions closed on a nearly relevant answer are the ones that reappear as a problem at the end of the works.

Where an answer on a consequential subject arrived verbally, ask for it in writing before you treat the question as closed.

A verbal answer about something that will later be concealed leaves you with nothing to point at afterwards.

Ask for written confirmation of any answer concerning services, structure, consents or anything that will be built over.

Keep closed questions in the list rather than deleting them, so that the same question is not asked again by someone at home.

The closed section becomes the fastest reference you have for what you were told during the project.

Note where an answer contradicts something recorded earlier, and raise the conflict rather than quietly choosing between them.

An owner choosing between two professional answers is making a decision they are not placed to make.

Watch for entries that are really you deciding something, and move them onto your decision record instead of leaving them as questions.

A decision disguised as a question waits for an answer that will never come, because nobody else can give it.

Notice when an answer, once received, means something already agreed has to change, and prepare that conversation separately.

Treating a change as a continuation of the question thread is how changes end up agreed without ever being recorded.

Where an answer reveals an assumption you did not know you had made, write the assumption down alongside the answer.

The assumption is usually shared by other parts of your thinking, and finding it once saves several later surprises.

Reread the closed questions before a significant stage begins, since some answers assumed conditions that have since moved on.

Answers have a shelf life on a live project, particularly those given before anything was opened up.

Ask whether an answer given earlier still holds once conditions on site have changed, rather than relying on the original reply.

Feed answers that affect a selection back into the relevant selection or drawing record, rather than leaving them only in the question list.

An answer that never reaches the record it affects tends to be contradicted by that record at the moment somebody uses it.

As the works come to an end, read the list for anything still open and ask for a final position on each remaining item.

Open questions left at handover become your questions permanently, once the parties have moved on to other work.

Ask the appointed professional to confirm the final position on any question still open as the works come to an end.