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

# Review a page and resume work later

> Use Follow-ups to move attention without changing vault access.

**Outcome:** a focused review request, a private continuation note, and any
durable conclusion filed into Knowledge.

**You need:** a readable page and a teammate who already has access. Promotion
also needs a writable wiki vault with SCHEMA folders.

## 1. Ask for a specific review

Open the saved page and choose **Send to…**. Pick the teammate and write a
request such as: “Check the cancellation steps against our approved policy; flag
anything that is out of date.” Select **Send**.

If the teammate is unavailable in the picker, verify workspace membership and
vault access. Creating a follow-up does not grant permission.

## 2. Complete the review

The recipient opens **Follow-ups → Waiting on me**, reads the request, and opens
the referenced page. If they have Editor access, they can save corrections in
Knowledge. They then select **Mark done**, or **Decline** with a note when they
cannot take it on.

The request is not an email campaign, chat thread, or automatic agent run.
Discuss larger decisions in your usual collaboration tool and file the approved
result into Knowledge.

## 3. Park your own remaining work

On a page, choose **Park** and explain the next step. Later, open **Follow-ups →
Parked** and use **Copy resume prompt** in the tool that should continue the
work.

Include a concrete stopping point: “The procedure is updated; next compare the
example with the new wording.” A resume prompt is more useful when it says what
has already been decided.

## 4. Promote durable conclusions

If the cover sheet contains reusable knowledge, choose **Promote**, select a
writable vault and SCHEMA folder, review the proposed file, and save it. Confirm
the new page exists and the request is closed.

Follow-ups expire and are not synchronized as Markdown. They should carry
unfinished work; approved procedures and reusable conclusions belong in
Knowledge.

## Check your result

The recipient can open the page, the requested review has a clear outcome, and
durable conclusions are saved in Knowledge. Mark the request done after
completing its work.

## If it did not work

If no recipient is available, confirm they already have read access. If
promotion is unavailable, check write access and the destination wiki structure.
Save a normal Knowledge page manually when needed; do not rely on an expiring
Follow-up for durable facts.

**Next:** [Client handoffs](/tutorials/client-handoff).