# From a site visit to a finished report

Connect the [photo-report phone companion](../native-phone/photo-report-companion.md), [desktop report desk and AI colleague](../desktop/ai-photo-report-desk.md), and a suitable delivery-preparation routine into one working system. Build it extremely well. The person should finish a visit with material already organized for the report they owe. Follow the [shared launch](../shared/launch.md).

Start from the applications and records they have. Establish any missing foundation needed for this workflow, retaining the native Tauri desk and the phone's useful capture experience. Use a fictional job when demonstrating work that would otherwise expose private customer information.

## Follow one job through the whole process

Learn what the recipient needs, what the person must observe on site, and how a report becomes ready to deliver. Carry the same job identity and purpose through preparation, capture, editing, and delivery.

Before the visit, let the phone receive the useful job details and subjects to cover. During the visit, photographs and observations belong to those subjects, with room for something unexpected. Let the person see enough of what they have collected to notice a missing view while another photograph is still possible.

Use Tailscale as the starting choice for connecting their private devices, adapting to a suitable existing connection. Make connectivity and receipt understandable: material can be saved on the phone while the computer is unavailable, then reach the desk with its context intact.

## Let report preparation begin from collected work

As material arrives, make it available in the desktop's ordinary job records and to the existing coding agent through the report desk's tools. The agent can compare images, group observations, and prepare a useful draft according to the person's direction.

Keep the collected evidence, the person's explanation, and the report's wording distinguishable. Let the person correct a subject or add a late observation without losing edits already made to the report. Make clear which changes have reached the other device and which still await connection.

Give the person a convenient way to indicate that collection is complete enough for the next stage. Several received photographs alone may be only part of the visit. Let them deliberately start preparation early when that helps, with the remaining material still visible as expected work.

## Finish and prepare delivery

Keep the report editable in its established workspace. The person can discuss it with the agent, adjust image choices and wording, and inspect the actual exported document.

Connect a background preparation step when a report is ready: assemble the requested document and supporting files, name the files as the recipient expects, and save the package where the person can find it. The [event-follow-up brief](../background-services/event-follow-up.md) supplies the related automation pattern.

Give each delivered version a recoverable relationship to the report it came from. A later correction should produce an understandable revision while preserving what was previously sent. Let the person choose whether the system prepares delivery or also performs an authorized sending action.

## Deliver the complete workflow

Set up the private connection, receiving operations, agent access, and background preparation as parts of the existing applications. Explain which computer or service must be available for each stage and provide ordinary controls for resuming or retrying unfinished work.

Take a sample job through preparation, several on-site subjects, a connection interruption, report editing, and a usable delivery package. Judge whether the person still has to reconstruct information they already recorded.

Teach how connected software preserves the meaning of work across devices. The phone serves the visit, the desktop serves close inspection and editing, and the agent helps with the same job throughout.