Decline, reopen and add notes
- Owner
- Organization admin
- Concierge
- Estate admin
Not every request gets done, and not every finished job is right first time. Declining closes a request with a reason on record, reconsidering brings it back, and sending work back reopens a completed task. Every one of these moves carries a note that lands in the card’s history.
Decline a request
Section titled “Decline a request”-
Open the card’s ⋯ menu and choose Decline, or drag the card onto the Declined column.
-
Give a Reason. It is required; submitting without one shows “Say why this is being declined”.
-
Select Decline.
What happens to the work depends on where the card was:
| Declined from | What happens to the task |
|---|---|
| Proposed, Quoted or Ready to Begin | There is no task yet. Any quote is kept for history. |
| In the Queue or In Progress, work not started | The task created at approval is deleted. |
| In the Queue or In Progress, work started | The task stays in the visit’s history. |
| Complete | The completed work stays in the visit’s history. |
The estate’s owners are emailed, and the reason is shown on the card under Declined.
Who can decline changes at approval. Before it, the estate’s servicing staff or the Estate admin who owns the estate may drop a proposal. After it, declining undoes an approval, so only whoever could approve the spend - the Estate admin who owns the estate, an Owner or an Organization admin - may do it.
Reconsider a declined request
Section titled “Reconsider a declined request”Declined is history, not a dead end. The Declined column is collapsed to a rail by default; select Expand Declined to see what is in it.
The only move offered on a declined card is Reconsider, which returns it to Quoted if it carries a quote and to Proposed if it does not.
Send completed work back
Section titled “Send completed work back”When a job is not right, reopen it rather than raising a second request.
-
Open the Complete card and choose Send back. Homeowners on the simplified view see this as Reopen.
-
Under What needs another look, say what is wrong or missing. This note is required.
-
Select Send back.
The task is reopened. If its visit is still open the work goes back onto that visit; if the visit has already been closed out, it is re-raised on the next one. Either way the card leaves Complete and the board works out where it lands again. The assignees and the estate’s Concierge are emailed.
Notes and history
Section titled “Notes and history”Requests have no separate comment thread. Instead, every move carries a note, and those notes are the record:
| Move | Note field | Required |
|---|---|---|
| Quote, Revise quote | Note - what the price covers | No |
| Mark ready to begin | Note | No |
| Add to the queue | Note - anything the crew should know | No |
| Mark complete | Completion notes | No |
| Decline | Reason | Yes |
| Send back | What needs another look | Yes |
| Move back, Withdraw quote, Reconsider | Note | No |
Open any card and scroll to History to read the whole timeline: who raised it, every move since, the note that rode along with each, and the time it happened. The same lines, across all the requests you can see, appear under Recent updates on your notifications page.
What happens next
Section titled “What happens next”Nothing in a request’s history is ever edited or removed. A withdrawn quote keeps its figure in the timeline, a declined request keeps its reason, and a reconsidered one carries the whole story forward.

