The most useful follow-up question is often discovered while writing. A quotation contains an unclear reference, a date does not fit the chronology or an explanation skips the decision the reader needs to understand. Sending a general request for anything else may produce more material while leaving the original gap untouched. A careful follow-up names the missing information and makes the requested response manageable.

The contributor is not responsible for assembling the writer's argument or locating every fact that reporting should have established elsewhere. Equally, a short factual enquiry should not disguise a substantial second interview. Planning the request means distinguishing what needs confirmation, what needs explanation and what belongs to another source. That distinction saves time and protects the accuracy of the published account.

Audit the draft for missing information, not unfinished prose

Read the transcript and draft with different purposes. The transcript shows what was said; the draft shows what the article now claims. Highlight a sentence whenever its certainty, scope or chronology exceeds the recorded material. A missing date, an unexplained technical term and an unsupported conclusion are different gaps. List them separately rather than sending the contributor the entire unfinished draft and asking whether it looks right.

Check your own records before contacting anyone. The answer may already appear in another section of the recording, an official programme document or a clearly identified source supplied during the interview. Resolve those straightforward gaps through reporting. A contributor should not have to repeat information because the writer did not review the notes.

Create a claim list with the wording you intend to publish, the evidence currently available and the exact point of uncertainty. For example, you may know that an exhibition object was selected after a workshop but not whether the workshop caused the selection. That is a question about the relationship between events, not merely about the date. Naming it accurately prevents a vague answer from being mistaken for confirmation.

Remove questions that concern only your difficulty writing a transition. If two paragraphs do not connect, the problem may be the article's structure rather than missing testimony. Ask for further information when it is needed to understand the subject, not simply to obtain a quotation that will make the current outline easier to finish.

Separate correction, clarification and new reporting

A factual correction asks whether a particular name, date, title or description is accurate. A clarification asks what an existing statement means. A new reporting question introduces a subject not adequately covered in the original conversation. Label these categories in your own preparation so that the contributor understands the scale of the request.

A correction can often be answered briefly. A clarification may require an example or a short call. New reporting deserves enough context and time to produce a thoughtful response. Do not send a dozen complex questions under the description of one quick check. That misstates the work and may encourage hurried answers that are unsuitable for the claim you want to make.

Where a point is independently verifiable, ask the appropriate source. A curator may know the intended role of an object, while a lender's record may be the better basis for an object's loan details. A contributor's recollection does not become documentary confirmation simply because the question is placed in a factual-checking email.

Also distinguish a factual check from an editorial preference. Asking whether a quotation preserves the speaker's meaning is different from asking whether they like the article's conclusion. Both can be discussed, but an editor should know which decision is being made. Otherwise a request intended to prevent error can quietly become an unplanned approval process.

GapUseful enquiryWhat the answer can establish
Uncertain name or dateA precise factual checkThe specified detail, subject to evidence
Ambiguous referenceA question about the original meaningWhat the contributor intended
Missing causal linkA request for explanation and supportThe basis of the claimed relationship
Unreported subjectAn explicit new interview requestAdditional material requiring normal review

Make each question answerable on its own

Give enough context to identify the passage. A timestamp, a short faithful extract or a description of the topic can help. Then state one question. Avoid burying several requests in a long paragraph that also contains the article's developing argument. A contributor replying on a small screen should be able to see which part needs an answer.

Ask neutral questions rather than seeking agreement with your preferred interpretation. Instead of saying that the workshop clearly transformed the exhibition, ask what changed after the workshop and what evidence connects the change to it. The answer may support a narrower claim or reveal that another influence mattered. Either outcome improves the article.

When checking a possible quotation, include the proposed wording accurately and distinguish it from your paraphrase. If an edit combines separate parts of an answer, inspect whether the meaning remains intact before asking the contributor to confirm it. Do not use a rushed approval to legitimise a misleading combination that you could have identified yourself.

Offer a practical response format. A person may be able to confirm a spelling in writing but need a short conversation to explain a technical sequence. Ask what is workable when the distinction matters. You can request brevity without implying that the complexity of the subject must disappear to suit the writer's deadline.

Send a focused request with a realistic deadline

Order questions by consequence. Put the item that could change the article's central claim before minor stylistic preferences. If the contributor can answer only part of the request, the most important information should not be lost among details that could be checked elsewhere. A numbered list can make responses traceable without turning the message into an examination.

Explain the publication deadline honestly and identify when an answer would still be useful. Do not invent urgency to encourage a faster response. If a late answer cannot be considered before publication, say so and describe the available route for later correction. The contributor should understand what the timing means rather than discover it when the article appears.

Keep the request proportionate to the earlier agreement. A person who consented to a short interview may not have time for extensive written research. If the gap is substantial, arrange another reporting session or narrow the article. Sending a longer email is not always a suitable substitute for acknowledging that the story needs more work.

Avoid automatically copying an unnecessary group of recipients. Technical or personal clarifications may be more appropriately discussed directly with the relevant contributor. Share the answer internally with the editors who need it, while respecting any agreed boundaries. A publication's administrative convenience should not expand the audience for sensitive correspondence without a reason.

A compact request outline for a real reporting gap

A practical clarification message can use three short parts. First, identify the article and the passage under discussion. Second, state the exact uncertainty without presenting your preferred answer as established. Third, explain what kind of response would resolve it. For the hypothetical curator interview, the opening might identify the recorded discussion of a workshop, followed by a question about which object grouping changed afterwards. The request should not assert that the workshop transformed the whole exhibition before the contributor has explained the connection.

Place optional background questions after essential checks and label them accordingly. If a spelling is already supported by an official record, tell the contributor that it has been checked rather than asking them to reconfirm every available fact. Conversely, if you need an explanation that could take time, offer a short call instead of implying that one written sentence must settle it. This organisation helps the recipient judge the work involved and lets the editor distinguish a partial answer from a complete response.

Before sending, read the message without the draft beside it. Does each question still make sense? Is any sentence asking the recipient to infer what the writer means by this or that point? Replace those references with a concrete subject. A concise request is not merely a short message; it is a message whose information is sufficient for the recipient to answer the actual reporting question.

Record later answers without rewriting the original interview

Save the follow-up alongside the interview record with its date and context. A written clarification received a week later is part of the reporting, but it was not spoken during the original recording. This distinction matters if a quotation is checked, a contributor disputes the edit or another writer later reuses the material.

Decide how the answer should appear. A factual detail can support ordinary narration once verified. A newly supplied quotation can be attributed appropriately. A correction to the meaning of an earlier statement may require revising the quotation rather than appending a contradictory explanation. Do not blend separate answers into an apparently continuous speech without considering the change in meaning.

If a contributor changes their view, preserve that development where relevant. They may now prefer a different description after further thought. That does not automatically mean the original record was wrong. Ask whether the new answer corrects a factual error, clarifies an ambiguity or represents a later interpretation. The published treatment can then reflect the actual relationship.

Track unresolved items rather than marking the whole request complete after one reply. A response can answer the date while leaving the claimed causal link unsupported. Keep each question connected to the sentence it affects. This makes it easier to remove, qualify or continue reporting the remaining claim instead of assuming that any response supplies blanket confirmation.

A hypothetical curator interview with three different gaps

Imagine a writer preparing an article about a community exhibition. The recording contains a reference to the first workshop, a statement that the selection changed afterwards and a technical term used for a display component. During drafting, the writer realises that these are three distinct gaps: the workshop's date, the nature of the change and the meaning of the term.

The date can be checked against the confirmed programme record. The follow-up to the curator therefore concentrates on the other two points. One question asks which selection changed and what led to the revision. Another quotes the technical expression and asks how the component functioned in this display. The writer does not ask the curator to rewrite the entire section or produce an endorsement of the article.

The answer reveals that the workshop informed one grouping but did not determine the overall exhibition. The draft's broad claim is narrowed. The technical explanation is checked against the installed arrangement before publication. The later email is saved with the source record, and its wording is not inserted into the recording transcript as if it had been spoken at the time.

This hypothetical example shows how a smaller request can produce a better result. The writer first resolves what the existing records can answer, then asks precise questions about the remaining gaps. The final article becomes more accurate because the follow-up tests its claims rather than merely supplies additional colour.

Decide what to publish when an answer does not arrive

No response is not agreement. It does not confirm a proposed quotation, settle an uncertainty or establish that a person has nothing to add. Review the claim using the evidence already available. If the uncertain detail is unnecessary, remove it. If the scope can be narrowed honestly, revise it. If the gap concerns the article's central proposition, publication may need to wait.

Avoid blaming the contributor in the article for a reporting gap that belongs to the publication. A factual statement that a response was sought may be relevant in some reporting contexts, but it should not be used as pressure or as a substitute for evidence. Explain what is known at the level the material supports.

Set a sensible boundary for further contact. Repeated identical reminders can become intrusive without producing better information. One concise reminder may be appropriate within the agreed process; a substantial new request may need a separate conversation. The publication should organise its reporting time rather than make the contributor responsible for rescuing an unrealistic schedule.

After publication, keep a route for meaningful correction. A late answer can reveal an error or provide material for a future article. Assess it normally rather than rejecting it merely because the earlier deadline passed. The aim of the follow-up process is a dependable account, not proof that the first draft was right.

Questions specific to this guide

Should the contributor receive the whole draft?

Only when that fits the agreed review process and serves a clear purpose. A focused factual query is often more useful than an unfinished article. Be explicit about whether you are checking facts, quotation meaning or a broader arrangement.

Can an email answer be used as a quotation?

It may be usable within the understood reporting terms. Preserve the record and do not present it as speech from the original interview. Check any ambiguity about publication before using the wording.

What if the missing answer affects the central claim?

Obtain the necessary evidence, narrow the claim or postpone the piece. A confident sentence and an unanswered request do not supply the information the reporting lacks.

Further reading

Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.