Log and track issues

Use Fieldwork when you are at the property and need to capture a maintenance or housekeeping problem without losing the details. The current experience begins with Lucia, not a blank issue form or a shared status board. The form is still there when you want it: Log Issues Manually is its own page.

​

Capture a problem with Lucia

Fieldwork opens into the tall chat shell. During a cold open, the Lucia Orbit loader spins, kicks, and fades as the empty chat appears. The blank conversation and docked composer are the home surface. The manual form is a real routed page of its own, reached from the drawer’s Log Issues Manually row or from the Rather type it in? Fill in the form link under the composer; it is no longer a modal or a secondary door inside the chat.

​

Leaving the chat: the exit law

If you type into the composer and then leave the chat, by tapping any other control in the app, opening the drawer, or multitasking away from the app, Fieldwork saves what you typed as a titled draft and clears the composer. Nothing is lost and nothing lingers in the input field. The founder’s ruling of 2026-08-29 (Leaving chat saves and clears, FILD-133):

If a user types something into the chat interface with Lucia and then navigates away, either by multitasking out of the app or by clicking any other button in the app, what the user typed is auto-saved as a titled draft.

The header’s New button and the drawer’s New Chat row run that same save path. A structured card Lucia already delivered becomes a titled draft the same way.

​

Editing a draft: the draft routing law

A saved draft never reopens into chat. Tapping the pen on any row in Drafts opens the Log Issues Manually form with the draft’s fields filled in. This is the founder’s standing rule, recorded verbatim on Pen icon never reopens chat (FILD-156) on 2026-08-31:

Drafts list → click to edit → goes to the manually edit form → ALWAYS. … The pen icon should never re-open a chat with Lucia on the same topic/issue. EVER.

The one exception path he ruled in the same law (FILD-133): chatting with Lucia always starts fresh unless a structured draft card was created by Lucia in the chat. The fix shipped on app main at 19676a5 and was verified on his phone on 2026-09-01 (his words on the record: “Ahhh, excellent design choice. I love it.”). Any further exception needs his explicit yes. See Log Issues Manually for the form itself.

​

Drafts and recovery

Fieldwork saves conversations and draft state as you work. Use Drafts to continue an earlier report.

• Drafts do not expire because of age or inactivity.
• New in the header and New Chat in the drawer preserve earlier work and immediately start an empty conversation; there is no reset modal.
• The saved notice links directly to Drafts.
• A Drafts row opens the exact named record on the first tap; the pen opens the manual form.
• Delete is an explicit, confirmed move to Deleted, not a hard purge.
• Deleted work can be restored.
• Submitting an issue does not silently delete its draft or conversation history.

Fieldwork may use device storage for fast recovery, but the authenticated API owns the durable conversation and draft truth. If local recovery and server state disagree, the server-owned record is authoritative.

​

Track what you handed off

Use Submitted for issues that Fieldwork successfully handed to Lucia. A saved draft is not a submitted issue, and an unacknowledged delivery attempt must not be treated as one. Fieldwork separates reporting from downstream decisions:

• An employee-reported assignee remains a suggestion, not a dispatch.
• An estimate remains an estimate, not approved or incurred spend.
• An approval request records employee intent to ask; it is not owner approval.
• A vendor name, possible date, or proposed action is not proof that contact or scheduling occurred.

The successful-submit sheet remains until you choose Log another or Done. A later reopen shows the canonical submitted receipt, never a stale draft-ready card. When an operator needs more information, continue on the submitted item’s thread; see Messages and replies. For the downstream boundary, see Owner review.

​

In-app tips

The first time you reach a moment the app wants to teach, one small tip appears: in the composer, on the drawer’s Drafts and Log Issues Manually rows, on the manual page, on a draft card, and on a submitted item. A tip closes with its ✕, or quietly when you scroll or start using the thing it points at. Replay the guides in the drawer brings them all back. See Tips and guides.

​

Recurring work

If Lucia recognizes recurring intent, she can direct you to the explicit Recurring flow. Use that flow to review and save the schedule. Conversation alone does not create a recurring definition, assign anyone, or claim that an occurrence was submitted. Recurring definitions and their occurrence history are server-owned records. The setup experience is available but still evolving, so rely on the state Fieldwork shows rather than assuming a future occurrence has run.

​

Current language and media boundary

The current V1 conversation is typed English. Spanish, audio, transcription, and photo understanding are future capabilities. Photo upload and attachment are available now.

​

Verification basis