Turn a document into a tracked action

Go down the correspondence list, the RFIs or your inbound captures and pick out the item that is not asking for a reply but for something to happen on site. Note the response-required-by date it carries, because that is the date the task will inherit.

Why: Most documents need filing and a handful need doing, and telling those apart is the whole job. It is also the job that gets skipped at four on a Friday, which is how a letter with a fourteen-day deadline gets read properly on day fifteen.

Use Create task on the item itself. It prefills the title from the subject, a description pointing back at the record, the due date from the response-required-by date and an assignee where one can be worked out. Adjust what needs adjusting, submit, and the task lands in the tasks list with its origin recorded.

Why: Retyping a task out of a letter is where the reference number goes missing and the deadline quietly becomes next Friday. Creating it from the source keeps both, and keeps the letter and the task as one piece of work rather than two records nobody ever links back together.

Work the task from the list. It shows a badge naming the kind of document it came from, and the badge links back to the record, so whoever picks it up can read the original before they act. Close it only when the thing the document asked for is genuinely done.

Why: A task with no visible origin gets closed on somebody's guess about what it meant. Months later, when a client asks what was done about a particular letter, the badge is the difference between answering in a click and losing an afternoon in the archive.