Keep the task, progress, and deliverable together in Planner.

Write the definition of done before assigning work

Use a title that names a result, such as “Prepare the October supplier review.” Include the source packet, reporting period, expected file, unresolved questions, and reviewer. Assign the exact Project so the task points to the right context.

An Agent assignment is a durable task field. It does not start a Session, connect an account, or configure a schedule. Tell the authorized assistant to begin the work, or start the Session yourself, when you want execution.

Record progress where the next person will find it

Add a note when you find a missing source, make a consequential correction, or hand the task to someone else. Keep earlier notes rather than replacing their history. Read the current task before changing it, especially when more than one person or assistant is involved.

A useful note says what was checked, which file was saved, what remains unknown, and the next action. “Nearly done” tells the next operator much less than “Workbook totals checked; approved launch date still missing.”

Attach the saved result and keep its version

Planner supports deliverables as text, a web URL, or an exact saved file and file revision. Use the file reference returned by the file operation. Earlier deliverable versions remain visible, so a correction can be attached without erasing the previous handoff.

Open the attached file and compare it with the task’s definition of done. A URL is a reference, not proof the reviewer has permission to open it. A saved file revision identifies the version under review; an ambiguous filename is a weaker handoff.

Complete the task after reviewing its output

Check the sources, calculations, missing facts, and reader requirements. Attach the reviewed version and record any remaining limitations. Then mark the task complete. Task status is a workflow record, not independent proof of factual accuracy.

If work changes later, update the task and attach the new deliverable version. Archiving removes a task from the normal active view; restoration is separate. Avoid deleting a Project or source packet simply because its task is complete.

Separate planning from recurring execution

Use a Loop or Schedule when you have tested a repeatable job and want it to run again. Define the fresh-input source, permitted actions, failure handling, review process, and usage limit. Keep a manual Planner handoff when a person needs to decide the next step.

For a custom Agent, reuse the method across Projects while each task identifies its own facts and deliverable. For an external assistant, verify the connection’s supported tools and permissions before expecting it to manage Planner or produce files.

Try it with a small example.

Before you use the result.

• The task points to the intended Project and a clear definition of done.
• Assignment has not been confused with starting execution.
• The attached deliverable opens and is the version the reviewer checked.
• The handoff states unresolved questions and the next action.