> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/diary/web/diary-entries/creating-a-diary-entry.md). # Creating a Diary Entry {% hint style="info" %} **Who can use this feature?** Contributors on the diary template and project admins can create Diary Entries. {% endhint %} A Diary Entry is where you log your day's work. Once created, contributors can add content to the Diary Entry. The Diary Entry workflow is the same whether you're using the mobile or web app, though the interface differs slightly. If you are using a mobile, see our Mobile Diary Guide. Before you can create Diary Entries, you will need to Create a Diary.

**To create a new Diary Entry:** * Navigate to the Diary Entries section and click

* Select which Diary you want to create an entry for, or create a new diary * Select the diary entry date * Select the Shift Start and End time from the dropdown * Click

Diary Entry Creation Rules

* When you create an entry, these details are locked and cannot be changed: * **Template**: Which Diary Template this entry belongs to * **Date**: The calendar date this entry covers * **Shift**: The working period (Day, Afternoon, Night, All) * Diary Entry names follow a standard format: \[Diary Name]-\[Shift]-\[Date]. You cannot change this format.

## Editing Diary Entry Shift Times *** Once you open a diary entry, you can edit the shift start and end times at any point before submitting it for review.

**To edit the Diary Entry Shift Time:** * Open a Diary Entry * Click

on the left hand panel and select Edit Details * Select a new Start and End shift time * Click

## Next Steps *** Once your entry is created and open, you and other contributors can start adding content. See Contributing to a Diary Entry --- # 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://help.aphex.co/docs/diary/web/diary-entries/creating-a-diary-entry.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.