# Handle the paperwork after the work is done

Build an automation that performs the recurring administration following a meaningful event in the person's work. Build it extremely well around a routine they already understand. Follow the [shared launch](../shared/launch.md).

Choose one complete follow-up with the person: prepare records after a club session, assemble the supplier order after a [group order](../shared-web/group-order.md) closes, or prepare the delivery material for a completed [report](../desktop/ai-photo-report-desk.md). Use the existing application and its actual records.

## Learn what starts the follow-up

Ask the person to show what they do when this part of the job finishes. Learn what information is ready, what still needs judgment, and what the follow-up produces.

Give the trigger a clear meaning in that workflow. A session's scheduled end, confirmed attendance, and completion of its administration are different events. Start the routine from the state that actually supplies the information it needs.

Use the source application's own record of that event. Keep the follow-up associated with the session, order, or job it belongs to, so the person can see why it ran and find its result from the work itself.

## Complete the usual administration

Prepare the records, lists, or delivery material the person normally creates. Use actual recorded information and preserve the distinctions needed for the next activity. A supplier needs item quantities; the organizer may also need each person's collection details.

Keep reusable instructions or layouts separate from the current event's information. Apply the existing formatting and preparation rules where the person already has a working routine.

Agree which actions run automatically and which prepare material for the person to inspect or send. For an authorized automatic delivery, use the agreed recipients and communication method and show its outcome. For preparation-only work, leave the result clearly ready for the person's next action.

## Let the person understand what happened

Show the originating event, the follow-up's current state, and its completed result. Make a missing input or failed action visible with enough context to resolve it. Let the person retry or invoke the routine manually when useful.

Recognize an event that has already been handled so a repeated signal or retry preserves the completed work and any delivery already made. If the underlying event is corrected afterward, make the revised follow-up an explicit update with the earlier result still understandable.

Keep the person's direct edits to prepared material intact according to the workflow you establish together. Give them a clear choice when refreshing a result would affect those edits.

## Run it from the real application

Install the automation where the work actually runs and explain its availability, startup, and external service requirements. Give the person a way to inspect, pause, or stop the routine. Keep its setup and useful history under the shared launch's ownership and recovery guidance.

Deliver the complete follow-up and exercise it from a representative event in the source application. Inspect the generated result, handle a correction, and confirm that repeating the event does the right thing with existing output. Where delivery is authorized, verify the chosen delivery result.

Judge whether the person can finish the original job and find the administration ready in the form they need. Explain how a recorded change in work can start another useful action.

Later, add another follow-up routine with its own trigger and authority. Preserve the existing routine as new actions are added.