Form Mapping Policies

Overview

This document outlines the policies and decision-making framework for managing field mappings across private and public form libraries. These guidelines are intended to ensure consistency, minimize disruption, and maintain data integrity across all supported forms.

Private Libraries

• For private libraries, Quik does not modify any fields unless explicitly directed by the library owner.

• All changes must be requested, reviewed, and approved by the owner before implementation.

Public Libraries

Field changes in public libraries are handled with careful consideration and only when necessary.

When We Change Field Names

We will update a field name in a public library under the following conditions:

1. Incorrect Field Naming

   • The current field name has been identified as incorrect or misleading.

2. Field Name Collisions

   • The field name is broadly correct but causes collisions with other forms, leading to ambiguity or mapping conflicts.

3. Form Usage Considerations

   • When resolving collisions between forms, we evaluate usage:

     • The less frequently used form is typically the one modified.

4. Accuracy Requirement

   • Field names are only changed if the resulting name is accurate and appropriate.

   • Some fields may accept multiple types of data, making naming decisions subjective; in these cases, changes are made conservatively.

5. Adding New Fields

   • If no suitable resolution exists, we may introduce a new field into the form definition.

High-Impact Changes

Top Library Considerations

For high-usage forms within the following libraries:

• Fidelity

• Schwab

• Pershing

We implement additional safeguards:

• A customer notification email will be sent 1–3 months prior to the change.

• This advance notice allows customers to:

  • Update validations

  • Adjust integrations

  • Prevent workflow disruptions

Guiding Principles

• Minimize disruption to users and systems

• Prioritize accuracy and clarity in field naming

• Respect ownership boundaries for private libraries

• Use data-driven decisions when resolving conflicts

• Communicate proactively for high-impact changes

Summary

Field mapping changes are made deliberately and only when they improve clarity, reduce conflicts, or correct inaccuracies. Private libraries remain fully controlled by their owners, while public libraries follow a structured evaluation process to ensure consistency and reliability across the platform.