> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/onboarding/nummernsysteme/projektnummern.md). # Job numbers ### **Best practice for job numbers** #### Why have job numbers at all? * Job numbers can be useful reference numbers in estimates, invoices and correspondence with the customer. * They can be passed on to suppliers when commissioning, who then include the job number on their invoices. This greatly simplifies the allocation of external services to jobs. Contact us if you have further questions on this topic. #### **We recommend**this job number pattern The numbers consist of ‌\ \-\ > TUI-0029‌\ > ‌BAB-0002 The four-digit sequential number therefore counts all jobs within a customer. {% hint style="info" %} There is deliberately no year included in the number, as projects often continue across calendar years.\ \ A year would then only be an indicator of the year the job was created; this information is accessible anyway via agency software. {% endhint %} #### **Further advantages of this pattern** * The number is suitable as a filename - even on a web server * In a file system, job numbers automatically sort by customer and sequential number * The customer abbreviation defines a separate number range for the customer
 * The customer cannot deduce other agency jobs * If customer abbreviations are established in the agency, it is easy to search by them ### --- # 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/onboarding/nummernsysteme/projektnummern.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.