> For the complete documentation index, see [llms.txt](https://doj.secondliferp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doj.secondliferp.com/legislation/doj-legislation/department-of-justice-public-legislation/guidelines-on-subpoena-duces-tecum.md). # Guidelines on Subpoena Duces Tecum Last Updated - 28/09/25 A subpoena duces tecum orders the person subpoenaed to produce Banking Records and Phone Records under their control at a specified time and place. Subpoena must include the following information when submitted. * State the title of the action * State the documentation requested * State the reasoning for the subpoena This will include all information, reports, incidents and further necessary information to invoke the subpoena. Officer’s Signature * Which Officer is seeking for the warrant Supervisor’s Signature * The signature of an officer who is command+ (Sergeant or Higher) or a Federal Agent or a signature of a District Attorney. If the officer who is seeking the warrant is not the rank of Command+, Federal Agent or District Attorney they will require a supervisor’s signature. Judge’s Signature: * the signature of the Judge who has approved the Subpoena with a valid reason why they have approved the Subpoena, if a judge signs the Subpoena "Subpoena approved" and not a reason why they have approved the Subpoena this will not be a valid. * Officer(s) will review and provide evidence that the subpoena has been acted upon * Officer(s) will acknowledge records presented and notified by Judges via appropriate channels. --- # 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://doj.secondliferp.com/legislation/doj-legislation/department-of-justice-public-legislation/guidelines-on-subpoena-duces-tecum.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.