Start with the rule behind written answer

A clear-eyed look at written answer starts by naming the one or two facts still open. Settle whether an answer or appearance form is required first; the filing deadline deserves its own check rather than an inference from the first answer.

At this stage a wrong assumption is still easy to correct — no docket entry or service attempt depends on it yet. Use that window to resolve how the form must be served before it can affect a filing, a deadline, or a service attempt.

Write whether an answer or appearance form is required down first, then list the filing deadline beneath it, each tied to the record or instruction that confirms it.

Build a five-point worksheet for written answer

Complete the list with how the form must be served, whether a counterclaim uses a separate form, and the consequences of filing nothing but still appearing. Source each one to a document or an official instruction rather than recollection.

Short, sourced notes hold up better than long summaries. Record the source for whether a counterclaim uses a separate form, and pair the consequences of filing nothing but still appearing with the document that backs it.

Documents that support written answer

Center the file on the primary records, plus separate notes answering whether an answer or appearance form is required and the consequences of filing nothing but still appearing — combining the two into one note makes it harder to audit later.

Use the scenario only to check the file's structure, not to supply facts. Once the facts check out, pair how the form must be served with its document and the governing official guidance.

In the example, the filing deadline and whether a counterclaim uses a separate form are treated as separate factors, each noted on its own. That distinction matters because the example only organizes facts — it never replaces the local rule.

State-specific checks and next steps for written answer

On written answer, a statewide example can look like a general rule when it is not. Recheck the local instruction that actually controls this step before acting on it.