> ## Documentation Index
> Fetch the complete documentation index at: https://helloluciallc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Logging and Tracking Issues

> The field guide: how to log a maintenance problem with photos and follow it through to verified-fixed.

This is the guide for the person **on the property** — the one who finds the leak, hears the
grinding noise, and needs it handled. No jargon, no ceremony: log it, add photos, keep the
status honest, done.

<Info>
  Fieldwork is invitation-only during the pilot. You sign in with your email address and a
  **one-time code** — no password to remember. Only invited people can see anything.
</Info>

## Logging a new problem

Log it the moment you find it — even before you know how bad it is. A thin record now beats a
perfect record never.

<Steps>
  <Step title="Tap “New issue”">
    One button. That's the whole entrance.
  </Step>

  <Step title="Give it a title and a place">
    One short line — *"Pool pump making grinding noise"* — and the area: pool, kitchen,
    master bedroom, garden…
  </Step>

  <Step title="Say what's going on">
    A few sentences. When it started, what you saw or heard. Rough is fine.
  </Step>

  <Step title="Rate it">
    How serious is it (low → urgent)? Does it affect guests (none → high)? A wobbly shelf in
    storage: none. No hot water: high.
  </Step>

  <Step title="Add photos">
    A couple of pictures are worth everything — the pump, the leak, the stain, the model
    sticker. You can always add more later.
  </Step>

  <Step title="Save">
    Done. It's logged, timestamped, and on the board.
  </Step>
</Steps>

<Tip>
  Don't polish. You can add photos, notes, and details any time — the point of logging early is
  that nothing gets lost.
</Tip>

## Following it through

Every issue has a **status** — where it is in its life:

| Status                   | In plain words                                                  |
| ------------------------ | --------------------------------------------------------------- |
| **Logged**               | Written down. Nothing decided yet.                              |
| **Needs review**         | Waiting to be looked at and decided on.                         |
| **Permission requested** | The owner has actually been asked for a go-ahead.               |
| **Approved**             | The owner actually said yes.                                    |
| **Scheduled**            | There's a real date or vendor slot for the work.                |
| **In progress**          | Someone has actually started working on it.                     |
| **Completed**            | Reported done — but not yet checked.                            |
| **Verified**             | A person looked at it and confirmed it's really fixed. The end. |
| **Blocked**              | Stuck — waiting on something. Always say what, in a note.       |
| **Cancelled**            | Deliberately dropped.                                           |

<Warning>
  **The one golden rule: only record what actually happened.** Don't mark *Scheduled* until
  there's a real date. Don't mark *Verified* until someone looked at the fix. A vendor's name
  means "who we have in mind" — if you actually called them, say so in a note. This rule is what
  makes the record trustworthy — and the app enforces it.
</Warning>

## As things move along

* **Permission** — if the fix costs money or is a big job, mark permission as *requested*.
  That puts it on the owner's list. When they answer, it becomes *approved* (or not).
* **Cost** — add an **estimated cost** when you have a quote or a good guess; add the
  **actual cost** once money is really spent.
* **Owner input** — flip on "owner input needed" when you want an opinion, not just a budget:
  *which tile color? repair or replace?*
* **Notes** — anything worth remembering: "left the pump off overnight," "plumber says
  Thursday." Notes can't be edited or deleted, so they're a reliable diary.
* **More photos** — before, during, after. An "after" photo is the best proof of a fix.

## Finishing

<Steps>
  <Step title="Work done? Mark it Completed">
    That means *reported* done — the record stays open for one last check.
  </Step>

  <Step title="Look at it, then mark it Verified">
    Really fixed? Verify it — the app records who confirmed. Not actually fixed? Send it back
    to *In progress* with a note. Reopening is a feature, not a failure.
  </Step>
</Steps>

## If you're stuck

Mark the issue **Blocked** and write a note saying what you're waiting for. That's not an
admission of defeat — it points the owner's attention exactly where it's needed.