> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/real-estate/real-estate.md).

# Real Estate Overview

The real-estate vertical organizes work around a property record. The property is the source of truth that connects verified facts, media rights, marketing, deal documents, relationships, transactions, rentals and post-close care.

## Recommended workflow

1. Finish the real-estate setup wizard.
2. Add or import a property from **Properties**.
3. Confirm the property identity, purpose and lifecycle stage.
4. Review imported facts and record a source and confidence for important facts.
5. Add or import media, then confirm location, rights and license.
6. Configure **Voice & Brand** and **Brokerage & Team** as needed.
7. Create property-grounded content, visuals, campaigns, video or reports.
8. Review facts, disclosures and the Compliance result before distribution.

The Dashboard remains the real-estate home and includes the calendar, setup state, recent work, priorities and shortcuts. The full Calendar screen remains available for scheduling and review.

## What Ask can do

The in-product Ask assistant can explain every real-estate hub, property-workspace view, Content Forge real-estate mode and Visual Tool. It can open a safe top-level screen. It does not create, edit, accept, send, schedule, publish, delete, close, sign, approve or run a generation for you.

Ask uses the active property `view` when you choose **Explain this screen**, so it can distinguish Facts, Visual Tools, Transaction, Compliance and the other property views.

## Safety model

* Missing property facts are never invented.
* Sourced facts, public-record matches, estimates and user-entered scenarios remain visibly different.
* Media must be matched to the property and have usable rights before public use.
* Property-line overlays are illustrative and do not replace a survey, title record or local authority.
* Photo edits preserve architecture and permanent features and carry the required disclosure.
* Fair-housing and anti-steering controls apply to content, matching and outreach.
* Financial estimates and scenarios are not appraisals or guaranteed returns.
* A compliance check assists human review; it does not replace broker, legal, MLS or local-policy review.

## Main navigation

* **Dashboard** - calendar, status, priorities and shortcuts.
* **Properties** - all properties and portfolios.
* **People** - contacts, leads, past clients, reviews/referrals and needs/matches.
* **Market** - signals, intelligence and explainable opportunities.
* **Create** - content, video, images, optimization, assets and knowledge.
* **Work** - team operations and automations.
* **Calendar** - scheduled and queued content.
* **Settings** - workspace, team, social, voice, brokerage and import configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/real-estate/real-estate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.