> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-3-pre-survey-communication-and-setup/participant-information-file/change-date-of-birth-and-length-of-service-to-ranges.md).
# Change Date of Birth and Length of Service to Ranges
When creating or making changes to your Participant Information File, it is important NOT to upload columns that provide identifiable information as the data will not work for reporting due to TalentMap's confidentiality threshold.
If your file has fields such as **Birth Date (Age)** or **Hire Date** you can adjust the data to a range in Excel by following these steps:
1. Create three extra columns
2. Inset today's date into the second column
Now you will insert the following formula into Column 3 called Actual Age: =YEARFRAC(E2,F2,1) Where E2= Date of Birth F2 = Today’s Date 1 = the fraction argument. Read more about the options [HERE](https://exceljet.net/excel-functions/excel-yearfrac-function)
3. Now you can create the Age Range
Use the formula =LOOKUP(G2,{0,"20 and Under";20,"20 and Under";21,"21-25";26,"26-30";31,"31-35";36,"36-40";41,"41-50";51,"51-55";56,"56 and Over"}) Where G2 is equal to the actual age. Start with zero and move your way up. Make sure that this is the breakdown that you want. Spot check your age ranges to make sure that they make sense.
**Note**: The below formula will work for **Length of Service**:
\=LOOKUP(L2,{0,"Under 1 year";1,"1-3 years";3,"3-5 years";5,"5-10 years";10,"10-20 years";20,"20+"})
{% hint style="info" %}
When you are done. Save your .csv without any of the formulas. You can do this by copying the columns and repasting them as values only.
{% endhint %}
---
# 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://docs.talentmap.com/knowledge-base/step-3-pre-survey-communication-and-setup/participant-information-file/change-date-of-birth-and-length-of-service-to-ranges.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.
.png?alt=media&token=39b99f13-f3e7-4f0a-b545-164628ba557e)
.png?alt=media&token=dd79fc9e-636d-4085-be7c-4325f5747f4e)