> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/quotes/see-context-while-quoting-or-invoicing.md). # See property, customer, and deficiency context while quoting or invoicing When you build a quote or an invoice, the right side of the editor has two tabs: **Document** and **Context**. Document shows the live preview of what the customer will receive. Context shows everything Essential knows about the property and customer you're billing — so you can price and bill accurately without opening other pages. The tabs appear as soon as the quote or invoice has a property. The Context tab is available on new drafts and on saved documents of any status, for both quotes and invoices. On desktop, the form column and the Document/Context column scroll independently. You can keep the relevant preview or property context in view while moving through a long quote or invoice form, and scroll either side without moving the other. ## What the Context tab shows * **Billing** (always first) — the billing details that apply to the document, with a tag showing whether they come from Property Billing (the property has its own profile) or Customer Billing: payment terms, autopay, tax exemption, the billing address, billing notes, and the saved payment method on file. This replaces the separate billing link the editor used to show next to the property picker; the "Autopay enabled" tag still appears there because autopay changes how you send or charge an invoice. * **Deficiencies** (quotes only) — the findings from the deficiency task the quote was created from, grouped under their inspection report. Each group's "View report" opens a preview of the report right there (or the report's page if no PDF has been generated yet). Every finding shows its status, the report description, the internal description, any photos (click to preview), and a Preview link that opens the asset's details. A finding whose **asset** is covered by a line item shows a "Quoted as" note with that line's name — the note tracks asset coverage, so an asset with several findings shows it on each of them. A quote that wasn't started from a deficiency task (and has no linked job with findings) has no Deficiencies section, and invoices never show one. * **Assets** (invoices only) — a compact summary of the property's asset groups, one line per group with its asset count, like the scheduling form's context panel. Quotes don't list assets — each finding in the Deficiencies section already identifies its asset. * **Property** — the property's address (linked to its page), its contacts with their titles, roles, and contact details, the date of the last visit, access info, and property notes. * **Customer** — the customer (linked to their page) with their status and property count, an alert when they have overdue invoices, and customer notes. When the quote has open deficiencies from its source task, the Deficiencies section opens first and the rest start collapsed; click any section header to expand or collapse it. ## Jump from a line item to its context On an AI-generated quote, line items cite the assets they came from ("From …" tags under the line). Clicking a citation opens the Context tab, where the matching finding shows its "Quoted as" note — so you can verify the work behind the line without leaving the editor. > **Where to find it:** On an open quote or invoice, the Document / Context tabs above the preview (right side of the editor) ## Related guides * [Create a quote](/revenue/quotes/create-a-quote.md) * [Create an invoice](/revenue/invoices/create-an-invoice.md) * [Create a quote from a job task](/revenue/quotes/create-a-quote-from-a-job-task.md) * [Set payment terms and the due date on an invoice](/revenue/invoices/set-payment-terms-and-the-due-date-on-an-invoice.md) * [Deficiencies](/field-operations/deficiencies.md) --- # 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://learn.withessential.com/revenue/quotes/see-context-while-quoting-or-invoicing.md?ask=&goal= ``` `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.