> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/projects/use-cases/boards-and-pipelines.md). # Boards and pipelines Kanban boards, dispatch timelines and live walls, where a drag is a real update. Work that moves through stages, shown on one screen. A card is dragged, the record is updated, the totals follow, and a validation rule can still refuse a move that is not ready.
Cover image

Listings board

A real estate office follows every listing from listed to sold, one swimlane per agent, with the asking total of each stage in view. Kanban.Dynamic ComponentsIntermediate, 20 minhttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FRQHNE5GHUUIE8CcpyDxb%2Fuc-01-listings-board.png?alt=mediaListings board

Opportunity Pipeline Board

Move a deal by dragging its card, and let a validation rule refuse the moves that are not ready.Dynamic Components, Flow ComponentsIntermediate, 20 minhttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FUo8dQw7F47yb7sZLG0ai%2Fpipeline-board.png?alt=mediaOpportunity Pipeline Board

Live Call Board

Give Sales teams real-time visibility on Leads with Dynamic components and Flow.Dynamic Components, Flow ComponentsIntermediate, 20 min, Interactive demohttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FAkUmCtTxSqR1F8NVTwZt%2FScreenshot%202026-04-10%20at%202.25.03%E2%80%AFPM.png?alt=media&token=65223f95-a4b2-4b3c-9914-4823da122a01Live Call Board

Field Service Dispatch Board

Put the technician timeline and the map of the day's jobs on one screen, from one query.Dynamic Components, Flow ComponentsIntermediate, 20 minhttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FNOOyPOCSVAJeeaPuV5lD%2Fdispatch-job-sites.png?alt=mediaField Service Dispatch Board

Shipment Tracking Wall

Track every parcel on one board, refreshed by platform events as the carrier reports.Dynamic Components, Flow ComponentsAdvanced, 30 minhttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FnBy4h2rkFz4CE3gErk6K%2Fshipment-wall.png?alt=mediaShipment Tracking Wall

Live crew board

Seven technicians on one day, 7 AM to 6 PM, with reschedule and reassign one click from any job. One tag, no scheduling code. Scheduler.LWC ComponentsAdvanced, 30 minhttps://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FT182mhaEqg7tjysHhdi1%2Fuc-04-live-crew-board.png?alt=mediaLive crew board
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.avonnicomponents.com/projects/use-cases/boards-and-pipelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.