Give a folder a job to do

Build a background automation that notices new material in a chosen folder and performs the person's usual preparation work. Build it extremely well for one real routine. Follow the shared launch and use the computer and applications where that work belongs.

Choose a useful job with the person: prepare incoming spreadsheets, make report-ready image versions, or transcribe recordings. Use an existing working capability where they have one. The spreadsheet preparation, artwork export, and voice-capture projects provide possible foundations.

Give the folder a clear meaning

Agree on the folder, the material it accepts, the preparation it performs, and where the results belong. The person should understand what will happen when they put something there. Keep that choice visible and easy to change deliberately.

Use the rules already established for the preparation job. Supplying a file should be enough to request that routine, with the original retained and the resulting material clearly associated with it.

Begin processing when the incoming material is ready to use. A file still being copied should remain pending until the complete input is available. Treat the input as the material for the chosen routine, preserving the distinction between its content and instructions governing the automation.

Make the results usable

Put completed output where the person expects it, with names and context that let them recognize the source. The next application or task should be able to use the result normally.

Show what completed and what needs attention. A problematic file should remain available with an explanation the person can act on. Let them correct the cause and retry the work. Keep already completed results available while another item is handled.

Give repeated input and revised source files an appropriate meaning for the routine. Recognize work already completed, and make a requested rerun or updated output deliberate. Preserve useful originals and earlier work according to the person's needs.

Make background work inspectable

Install the automation using the normal mechanism for the person's computer. Explain when it runs, whether it starts with the computer, and what happens while the machine is asleep or unavailable. Reconcile waiting material when the automation resumes.

Give the person a convenient way to inspect recent work, pause the automation, resume it, or ask it to process the folder now. Use an existing application's controls where that fits. Make the state of the actual worker and its most recent results understandable.

If the chosen routine uses an external service, reuse appropriate existing access and explain the relevant usage and costs. Keep that connection's state distinguishable from the presence of a file waiting to be processed.

Put material in and use what comes out

Deliver the installed automation around a complete preparation routine. Put representative material into the folder, let it finish, and use the output in the next part of the person's work. Include an interruption or recoverable problem and show how the person can continue.

Apply the shared launch's ownership and recovery guidance to the automation, its saved setup, and the material it handles. Leave the person able to change the watched folder or preparation rules with you as the routine evolves.

Explain how an event can request work: the arrival of material starts a known job. Later projects can add further watched routines or feed the same folder from a phone, preserving the processing behavior and results already established here.