Capture intake questions without changing source documents

Put questions beside the evidence

Keep the question beside the original document so the next person can resolve it without wondering what was changed.

If supplier invoice PDFs need to become a business-expense workbook, test that step in ParseMill. It extracts invoice fields and line items for your review and Excel export. For tax forms, package completeness and preparer handoffs, bring one recurring bottleneck to a scoped workflow review.

A note written directly over a figure can make later review difficult, especially when the working copy is mistaken for the original. If annotations are useful, create an explicitly labeled working copy under your approved document process and retain a reference back to the supplied artifact. A question register remains useful even when that copy exists.

Define a question that can be answered

Record an observation before the question. For example, the total on page three differs from the attached schedule, followed by please confirm which schedule is current. Avoid embedding a proposed answer that nudges the respondent toward a conclusion. Capture the actual response and let the responsible practitioner decide its effect.

TaxDome: PDF editing notes that saving edits replaces the previous PDF version. TaxDome: Organizer answers describes reviewing organizer answers individually. These are different controls: editing a document changes an artifact, while reviewing an answer records progress on information. Neither removes the need to preserve the relationship between a question and its evidence.

Use an evidence-linked question card

This fictional card shows the minimum useful context. The register keeps the uncertainty visible without altering the source or copying unnecessary sensitive information into a general task list.

Receiving the response does not automatically resolve the professional issue. The card can move from awaiting client to awaiting practitioner, retaining the same question identity. This makes the remaining action visible without sending another request for information already provided.

Preserve a readable history

When an answer changes, append the new statement and identify what it supersedes. Do not erase the original question or silently edit staff notes to look as though the new information was always known. If a question was unnecessary, close it with that reason so another reviewer does not reopen it from the same ambiguous source.

• Verify the source reference still opens the intended page.
• Distinguish client words from staff interpretation.
• Record the person who resolved the uncertainty.
• Keep affected preparation work linked.
• Avoid placing sensitive extracts in broadly shared task titles.

A screenshot alone can lose the surrounding context. If using one as an aid, retain the full source reference and explain which part raised the question. Do not treat an annotation marked resolved as proof that the underlying workpaper was updated.

Check the handoff from question to decision

Ask the preparer to trace one resolved question from source to response to final decision. Then test an unresolved card: it should show who acts next and what is still missing. These two checks reveal whether the register is helping preparation or merely collecting comments.

Use the related workflow guide to place the register inside the intake workflow. the workflow audit checklist can help separate delays caused by missing evidence from delays caused by unanswered interpretation questions, which often require different owners and different follow-up messages.