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

# Owner Review

> The owner's guide: clear four queues — approvals, costs, feedback, verification — in a ten-minute pass.

The property manager logs and works the issues; the owner reviews **structured state** instead
of scrolling chat history. Your attention is only needed in four places — and each one is a
queue you can actually finish.

<CardGroup cols={2}>
  <Card title="Permission — “may I?”" icon="hand">
    Requests waiting on your yes/no for spend or significant work. These **hard-block** the
    manager — clear them first.
  </Card>

  <Card title="Cost — “what will/did this cost?”" icon="coins">
    Estimates waiting for your approval, and actuals worth an eyeball against the estimate.
  </Card>

  <Card title="Feedback — “what do you think?”" icon="message-circle">
    The manager wants your judgment, not your wallet: repair vs. replace, which material,
    what's the priority.
  </Card>

  <Card title="Verification — “is it really fixed?”" icon="badge-check">
    Work reported done, waiting for a human to confirm it with eyes or evidence.
  </Card>
</CardGroup>

## Permission requests

Check severity, guest impact, photos, and the estimated cost — then answer.

* **Yes** → permission becomes *approved*; the work can be scheduled and started.
* **No** → permission becomes *denied* and the issue moves to *Blocked*, with a note saying
  why (or what cheaper path to take instead).

<Note>
  Said yes in person or in a chat? **Record it here too.** The record is only useful if it
  matches reality — nothing counts as approved until it's in the system.
</Note>

## Cost review

Cost has its own life, separate from status:

| Cost state    | Meaning                 | Your move                                             |
| ------------- | ----------------------- | ----------------------------------------------------- |
| **Unknown**   | No number yet.          | Fine early; chase a number before approving work.     |
| **Estimated** | A figure is attached.   | This is your approval moment.                         |
| **Approved**  | You approved the spend. | Only ever set by your actual approval.                |
| **Incurred**  | Money actually spent.   | Compare actual vs. estimate; big gaps deserve a note. |

The system won't let an issue claim *estimated* without an estimate or *incurred* without an
actual figure — any number you see is backed by a recorded value.

## Feedback requests

Issues flagged **owner input needed** are soft-blocking the manager. Answer in the issue —
your reply is recorded with your identity and timestamp — and the flag clears. A stale
feedback flag holds work up just as surely as an unanswered approval.

## Verification

**Completed** means *reported* done — nothing more. **Verified** is the real end, and it means
a person confirmed the fix, on-site or from evidence (an "after" photo).

* The app stamps *who* verified from the login — it can't be faked or back-filled.
* Not actually fixed? Send it back to *In progress* with a note. The reopen loop is a feature.

<Warning>
  Never verify from memory or from "they said so." Verified issues drop off the active board —
  verifying falsely buries a live problem.
</Warning>

## Reading an issue honestly

* A **vendor name** means "vendor in mind" — not contacted. Contact is real only if a note says so.
* **Scheduled** always carries a real date — the system refuses it otherwise.
* **Severity** and **guest impact** live outside the status. An urgent, high-guest-impact issue
  sitting in *Needs review* for two days is your real to-do list, whatever its status says.
* The **event trail** is ground truth: every change, who, when — append-only. When something
  looks off, read the trail before asking.

## A rhythm that works

A ten-minute pass, a few times a week:

<Steps>
  <Step title="Unblock the urgent">
    Anything urgent or high-guest-impact not moving? Deal with that first.
  </Step>

  <Step title="Clear permissions, then feedback">
    Permissions hard-block the manager; feedback soft-blocks. Both are quick to answer.
  </Step>

  <Step title="Skim costs">
    Approve reasonable estimates; eyeball actuals against estimates.
  </Step>

  <Step title="Verify what you can, skim what's Blocked">
    Confirm finished work — and remember some blocked items are waiting on *you*.
  </Step>
</Steps>