> ## Documentation Index > Fetch the complete documentation index at: https://www.composer.id/llms.txt > Use this file to discover all available pages before exploring further. # Question types > The 32 question and data types Triage can ask, and the 20 whose answers composerID carries into a destination field. Every answer Triage captures arrives with a declared data type: an enum, a boolean, a float, an ISO date, a money amount, a file reference. That is what lets composerID map an answer onto a destination field without a separate transform for every intake surface. Of the 32 types Triage can present, 20 capture an answer that composerID carries; the other 12 are screens or experimental data questions that stay inside Triage. ## Carried into destinations ### Choices | Type | Data type | Carried as | | --------------- | ----------------- | -------------------------------------------------------------------------------------------- | | Multiple choice | Enum | An enum value mapped to a destination picklist. | | Multi-select | Enum array | An array of enum values, mapped where the destination field accepts several. | | Dropdown | List | An enum value mapped to a destination picklist. | | Yes / No | Boolean | A boolean mapped to a destination flag or gate. | | Ranking | Ordered array | An ordered list carried with the decision reference; mapped where a destination supports it. | | Drill down | Hierarchical enum | A selection that filters the next level (vendor, category, role), mapped level by level. | ### Text | Type | Data type | Carried as | | --------------- | ------------------------- | -------------------------------------------------------------------------------- | | Short text | String | A string mapped to a destination text field. | | Long text | Long string | A text value mapped to a destination long-text field. | | AI-prompted box | String, assistant-drafted | Text carried with a model-drafted provenance flag; not mapped to a strict field. | ### Contact | Type | Data type | Carried as | | ------------ | ------------------ | ------------------------------------------------------------------ | | Email | Email | A validated string mapped to a destination contact field. | | Phone number | Tel | A validated string mapped to a destination contact field. | | Website | URL | A validated URL mapped to a destination field. | | Address | Structured address | A structured address mapped onto the destination's address fields. | ### Dates and numbers | Type | Data type | Carried as | | ---------- | ------------- | ------------------------------------------------------------------- | | Date | ISO date | An ISO date written into the destination's date field. | | Date range | ISO date pair | A start and end date mapped to the destination's period fields. | | Number | Float | A number mapped to a destination numeric field. | | Currency | Money | An amount and its currency mapped to the destination's money field. | ### Evidence | Type | Data type | Carried as | | ----------- | -------------- | -------------------------------------------------------------------------- | | File upload | File reference | A reference written onto the destination record. The binary is never sent. | | Legal | Acceptance | An acceptance stored with the version of the terms that was shown. | | Attestation | Acceptance | A declaration stored with the actor and the time it was given. | ## Kept inside Triage These present information or model a scenario. Nothing is captured to map, so nothing is published. | Type | Kind | Why nothing is carried | | --------------------------------------------------- | -------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Launch screen, Risk launch screen, Super user intro | Screen | Context and instructions before the questions begin. | | Statement, Statement (image) | Screen | A bridging statement between sections. | | Outcome screen, End screen | Screen | The decision shown back to the requester. The decision itself is what gets the reference; the screen is presentation. | | Scenario planner | Experimental data question | Pre-flow what-if modelling. Educational, not transactional: no request is created. | | Context setting, Informational card | Experimental data question | Live data shown to the requester. Presentation only. | | Interactive compare, Outcome recommendation | Experimental data question | Reads data to display; the decision, not the card, is published. | Which fields are sent to a destination, which are read back, and which never leave. The Intent Record and Compliance File schemas the answers land in.