> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/collections/end-user/marketing.md). # Marketing ### 1. Operational Efficiency Angle Collections brings clarity and simplicity to even the most complex Didge environments. As your organisation grows, so does the volume of forms, procedures, and checkpoints spread across multiple kitchens, zones, and departments. Collections gives you the power to instantly group everything related to a process or control—regardless of where it lives operationally. The result is a cleaner, more intuitive system that helps teams work faster, navigate smarter, and keep daily operations running with confidence. *** ### 2. Compliance & Audit Readiness Angle Collections transforms compliance management by making evidence effortless to access. Whether aligning to HACCP, ISO 22000, BRC, or internal corporate standards, Collections consolidates forms, policies, procedures, and records into a single, audit-ready view. No more jumping between Work Areas or hunting for documents—auditors and QA teams get a complete, structured picture of any topic in seconds. It’s the simplest way to demonstrate control, traceability, and program integrity across your entire operation. *** ### 3. Enterprise Scalability & Strategic Value Angle As your organisation expands and digital systems evolve, Collections becomes the connective tissue that keeps everything coherent. Large enterprises often build multi-year, multi-department workflows on Didge, spanning food safety, quality, operations, training, and beyond. Collections ties these elements together, creating a flexible, future-proof framework that scales with your business. It’s more than organisation—it’s a strategic tool that transforms Didge into a fully contextualised platform tailored to how your enterprise thinks, operates, and grows. --- # 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.didge.io/home/collections/end-user/marketing.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.