> For the complete documentation index, see [llms.txt](https://gitbook.bergelsonlab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.bergelsonlab.com/archive/duke-archive/how-to-start-a-new-protocol/how-to-close-a-protocol-page-under-construction.md).

# How to: Close a Protocol at Duke

When you receive a notice that your protocol is expiring, take stock of whether research activities are continuing.

If you are **collecting new data**, or working on **analyzing identifiable data**, you must **renew your protocol**. However, if the only activities are the analysis of de-identified/unidentifiable data and publication, you may allow the protocol to close.

You CAN do this by just doing nothing and allowing the protocol to expire on its own, but it's nicer to ourselves and to the IRB if you send a quick email saying that your research has concluded and you would like to close the protocol.

Update the `psych/BergelsonLab/Lab_Documentation/Protocols/IRB_protocols_current.xlsx` spreadsheet to say that the protocol is expired and list the closure date. Turn all lines associated with that protocol gray.


---

# 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:

```
GET https://gitbook.bergelsonlab.com/archive/duke-archive/how-to-start-a-new-protocol/how-to-close-a-protocol-page-under-construction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
