Write a task intake note that survives a shift change

A task intake note begins with the outcome the requester needs, not with the channel the request arrived through. Name the person who asked, the business reason, and the date the work is due. Record the source record the assistant must use. A note without an outcome invites the next assistant to repeat the conversation instead of doing the work.

Keep the intake note short enough to complete during a normal shift. Four fields are usually enough: requester, outcome, source, and deadline. Add a fifth field for the decision owner when the task involves a commitment, a payment, or a customer promise. The note should be usable by someone who was not on the call.

Write the requester's name and role, not just a team name. A team name gives everyone a reason to assume someone else has it. Record the outcome in one sentence that a reviewer can test. If the requester says the report is late, the outcome might be a corrected report delivered by a stated time.

Separate the request from the proposed solution. A requester may ask for a spreadsheet when the real need is a decision. Write the need first, then the proposed format. That distinction helps the assistant avoid building the wrong artifact efficiently.

Record the system of record and the exact report, folder, or record the assistant should use. A note that says use the usual file is not a source. If the source is ambiguous, write the candidates and the question that will resolve them. The next assistant should not have to guess which version is current.

Write the deadline as a date and a local time, with the time zone if the team spans regions. Distinguish the deadline for the first draft from the deadline for the final version. A note that says as soon as possible cannot be scheduled. A dated deadline can be protected in the queue.

State what the assistant may do and what requires approval. A routine update may be within scope, while a customer commitment or a payment change is not. Name the approver and the evidence they will need. A written boundary prevents a capable assistant from being pushed into a decision the role should not own.

Include the escalation path for missing information. If the source is unavailable, the assistant should know who to ask and how quickly. If the requester is unavailable, the note should name the backup. Escalation is a normal step, not a failure of the intake process.

Use a clear label for anything the assistant has not verified. Write what was observed, what was reported, and what was assumed. A later reviewer needs to know which parts are evidence. An assumption that is never labeled becomes a fact in the next handoff.

When the requester changes the request, record the new version and the time. Do not overwrite the original note without a trace. The history shows whether the work changed because of new information or because the scope drifted. Test the rule on one real task before applying it to the queue.

Before the shift ends, read the intake note as if you were the next assistant. Ask whether the outcome, source, deadline, and boundary are clear. If any field requires a conversation, improve the note rather than relying on a verbal handoff. The check should take less than a minute per task.

Review the first few notes with the team and compare interpretations. A note that two assistants read differently is not ready. Update the template after the review and keep the change small. The goal is a note that makes the next action obvious.

For the support model behind this work, review the [services page](/services) and the scope it describes. Use the [contact page](/contact-us) when the decision needs a written boundary or an approval. The [U.S. Small Business Administration](https://www.sba.gov/business-guide/manage-your-business/manage-your-finances) publishes public guidance on documenting recurring finance and operations work. Keep the links in the handover so the next reviewer can find the same reference.