> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping.md). # What is Pre-Mapping? Pre-Mapping is the first project phase after Project Kick Off in which the integration template is reviewed. {% hint style="info" %} The integration template is a prepopulated set of field mappings from one specific system to another. Likely many will fit your business process, but you will need to adjust others to fit your business process. The purpose of Pre-Mapping is to approve template mappings that fit your business process and flag the others that need to be changed. {% endhint %} Pre-Mapping differs from the Mapping phase in that it's strictly a review of the template at the [Field Mapping](/reference/integration_components/field-mapping.md) level. You will approve Field Mappings that align with your business process. If a Field Mapping does not align with your business process, or you're not sure, you can mark it accordingly and add a comment to be reviewed during Mapping. Changes to mapping logic are not made during Pre-Mapping-- the fields that are not approved during Pre-Mapping are handled during the Mapping Phase. --- # 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://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping.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.