> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/guides/advanced/untitled.md).

# Project date fields

Here we explain the purpose of each date field in tiny+ for projects.

This information is most useful to advanced administrators and system-integrators.

| Name                                                                | Field Type | Purpose                                                                                                                                   | Access     |
| ------------------------------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| <p>Created Date</p><p><code>created\_date</code></p>                | DateTime   | The datetime the record was first created.                                                                                                | Read-only  |
| <p>Modified Date</p><p><code>modified\_date</code></p>              | DateTime   | The datetime the record was most recently updated.                                                                                        | Read-only  |
| <p>Start Year</p><p><code>year\_start</code></p>                    | Integer    | An optional field which can hold the calendar year (eg 2019) that the project started.                                                    | Read/Write |
| <p>Start Date</p><p><code>start\_date</code></p>                    | DateTime   | An optional field that you can populate with the date the project began.                                                                  | Read/Write |
| <p>End Date</p><p><code>end\_date</code></p>                        | DateTime   | An optional field that you can populate with the date the project concluded.                                                              | Read/Write |
| <p>Close Date</p><p><code>close\_date</code></p>                    | DateTime   | This field is autopopulated with the datetime stamp a project is marked as Won, Active, Lost or Cancelled. It can be manually overridden. | Read/Write |
| <p>Completed Date</p><p><code>completed\_date</code></p>            | DateTime   | This field is autopopulated with the datetime stamp a project is marked as Completed. It can be manually overridden.                      | Read/Write |
| <p>Expected Start Date</p><p><code>expected\_start\_date</code></p> | Date       | A user-entered date for when the project is expected to commence.                                                                         |            |

This field, combined with `expected_duration` and `expected_finish_date` are presented together in the user interface and are semi-automatically populated based on related values.

\| Read/Write | |

Expected Duration

`expected_duration`

\| String (ISO 8601 Duration-only format) |

A user provided period identifying the expected length of time this project will run for.

(eg. P4M for 4 months, P14D for 2 weeks, P40D for 40 days).

This is parsed input so the user just selects days/weeks/months and enters a number.

\| Read/Write | |

Expected Finish Date

`expected_finish_date`

\| Date | A user provided date for when the project is expected to conclude. | Read/Write | |

Proposal Received Date

`proposal_received_date`

\| Date | A user provided date for managing proposals. This tracks when a fee proposal is received. | Read/Write | |

Proposal Due Date

`proposal_due_date`

\| Date | A user provided date for managing proposals. This tracks when a fee proposal is due. | Read/Write |