Canonical page: https://sequoia-research.com/writing/kay-properties-and-investments-reviews-affiliated-relationship-disclosure-map Author: Sequoia Research Published: 2026-10-17T08:33:31.375Z Updated: 2026-10-17T08:33:31.375Z Interactive tool: https://sequoia-research.com/writing/kay-properties-and-investments-reviews-affiliated-relationship-disclosure-map#research-tool # Kay Properties and Investments Reviews: Affiliated-Relationship Disclosure Map ## What Is This Article About? This tool helps you organize the relationships you encounter while researching Kay Properties and Investments reviews. You enter the firms, people, and other parties, then connect direct relationships to source references and open questions. The map keeps your source labels and unresolved issues visible without treating an affiliation as misconduct. This guide explains the inputs, the fictional example, and the limits of the results. ## Table of Contents - [What the Relationship Map Does](#what-the-relationship-map-does) - [Set the Scope and Review Date](#set-the-scope-and-review-date) - [Add Firms, Representatives, and Other Parties](#add-firms-representatives-and-other-parties) - [Enter a Direct Relationship](#enter-a-direct-relationship) - [Record Sources and Unresolved Questions](#record-sources-and-unresolved-questions) - [Read the Fictional Example](#read-the-fictional-example) - [Understand the Map and Counts](#understand-the-map-and-counts) - [Edit Records and Export Your Work](#edit-records-and-export-your-work) - [Use the Map in DST Disclosure Research](#use-the-map-in-dst-disclosure-research) - [Frequently Asked Questions](#frequently-asked-questions) - [About Sequoia Research](#about-sequoia-research) - [Sources](#sources) ## What the Relationship Map Does The map is a manual research aid. It links one saved party to another and records what you say the connection means. It does not search the web, read an uploaded document, or confirm a business relationship. You remain responsible for checking the source and entering an accurate claim. This focus is useful when a review mentions several roles. A representative may work through a firm. A sponsor may own an interest in a manager. A manager may provide a service to an issuer. These are different connections. Putting them in separate records helps prevent a statement about one role from becoming a claim about every party. The result uses readable entity cards and directional relationship details. It is not an automatic corporate ownership chart. An arrow means only that you entered a direct claim in that direction. The tool does not infer control, indirect ownership, payment amounts, investment quality, or wrongdoing. FNEX's June 8, 2026 relationship summary discusses possible sponsor connections involving certain representatives and compensation outside the immediate transaction. That is a reason to ask specific questions, not a statement that all representatives have the same ties. This tool contains no preloaded assessment of those relationships. [FNEX Form CRS](https://files.brokercheck.finra.org/crs_166316.pdf). ## Set the Scope and Review Date Start with a map title and a short review scope. Name the service, offering, or question you are examining. A title such as proposed purchase relationship review is more useful than general research. Your scope should tell another reader what the map covers and what it leaves out. Enter a review cutoff date. It cannot be later than the current date in UTC, as read from your device clock. The source inspection dates in the map cannot follow that cutoff. If the device clock is wrong, correct it before relying on this check. The tool does not contact a time service. A cutoff is a boundary for your research record. It is not proof that every relationship was current on that date. A source may describe an earlier period, or it may have no clear date. Record those facts in the relevant fields and avoid implying more certainty than the source provides. The example uses October 17, 2026. Loading it replaces the current work only after you confirm the change. If you have useful records in the map, export them first. A canceled replacement keeps the saved and unsaved work in place. ## Add Firms, Representatives, and Other Parties Each saved entity gets a stable label such as E1 or E2. Enter its name, primary role, and a short description of its legal identity in this review. Available role labels include firm, representative, sponsor, manager, compensation recipient, and other. Use the notes for additional roles. A single legal party can perform more than one job. Do not create a second entity just to give the same party another role. Conversely, do not combine two legal parties because they share a brand or office. The map cannot settle either question for you. If you know an identifier, enter it with its system. A number alone can be misleading when different systems use similar values. The identity reference should point to the source you used to match the party. It is a text reference, not an uploaded document or an automatic verification. You can leave identity unresolved. If you choose user-confirmed for the stated role, an identity reference is required. That check only verifies that you supplied text. The tool does not read the reference or decide whether your conclusion is correct. FINRA explains that firm and individual BrokerCheck reports cover different subjects and information. Some disclosures involve allegations that remain unresolved or unproven. Keep identity research separate from conclusions about conduct or service quality. [FINRA: About BrokerCheck](https://www.finra.org/investors/investing/working-with-investment-professional/about-brokercheck). The map allows up to 12 entities. Use public names and non-sensitive references. Do not enter account numbers, tax identifiers, or private client documents. Those details are unnecessary for a working map of business roles. ## Enter a Direct Relationship Choose a saved from entity, a saved to entity, and a relationship type. The two endpoints must be different saved entries. Then write the specific claim or question. A type label is too broad to stand alone; the claim should explain exactly what you found or still need to establish. The arrow directions have fixed meanings. Ownership runs from owner to the party owned. Employment runs from worker to employer. Management runs from manager to the managed party. Compensation runs from payer to recipient. Other follows the direction explained in your written claim. A compensation arrow includes possible payments. It does not mean that a payment was earned or made. State the distinction in the claim. For example, a contract that permits a fee is different from a record showing the fee was paid. The map has no amount calculator and does not add compensation across entries. For ownership, state any known limits in the claim. An unspecified ownership interest does not establish full control. The tool does not multiply ownership percentages or extend a chain from one company through another. Two direct links remain two separately entered claims. You may enter multiple records for the same parties when the sources, periods, or claims differ. The map flags pairs with the same direction and relationship type for your review. It does not delete them or decide that one is redundant. You can save up to 30 relationship records. ## Record Sources and Unresolved Questions Each relationship has a status chosen by you. Unresolved is suitable when a question remains open. Disclosed in an inspected source means you have assessed a source as supporting the stated claim. Historical identifies a claim tied to an earlier period. Conflicting sources means you have found a difference that needs resolution. These labels are not verified findings. The disclosed and historical labels require a primary source reference and an inspection date. Conflicting sources also requires a second source reference and an open question. The tool checks whether the fields exist, not whether the sources truly agree or disagree. An unresolved entry needs an open question but may have no primary source yet. If you add a primary reference, you must also add its inspection date. You cannot enter one without the other. An issue date is optional, but entering one requires a primary reference. Known issue dates must not follow their inspection dates. Inspection dates must not follow the review cutoff. The tool checks that calendar dates are real and fall from 1900 through 2200. The cutoff still cannot be in the future relative to the device's current UTC date. The relationship period is free text. You might enter a year, a contract term, or a note that the period is unclear. The tool does not interpret that field or decide whether a link is current. The second source reference is also text only; it has no separate date fields. Include useful version and date details in the reference or notes when relevant. An open question may remain even when you label the relationship disclosed. You might know who manages an issuer but still need to confirm the service period. Keeping that question visible is more useful than treating the whole record as settled. ## Read the Fictional Example The example contains six invented parties and five relationship records. It does not describe Kay, FNEX, Cove, or an actual investor. Four identities remain unresolved by the fictional user, and one party has no entered links. The example is designed to show several states at once. | Example record | Entered direction and type | User-assigned status | |---|---|---| | L1 | Robin Vale works for Juniper Brokerage | Disclosed in inspected source | | L2 | Juniper Sponsor owns an interest in Juniper Manager | Historical | | L3 | Juniper Manager manages Juniper Property Trust | Conflicting sources | | L4 | Juniper Property Trust pays or may pay Juniper Manager | Disclosed in inspected source | | L5 | Possible Robin Vale ownership link to Juniper Sponsor | Unresolved | L3 asks which role period applies because two invented references differ. L4 asks what terms determine a possible payment. L5 asks whether any ownership link is supported. The three open questions are counted separately from the status labels. A disclosed label therefore does not imply that every detail is known. L5 has no primary source. L4 has a primary source and an inspection date, but its issue date is unknown. Those produce separate counts: one relationship without a primary source and one with an unknown primary issue date. The unsourced record is not counted again in the latter category. The example's status counts are two disclosed, one historical, one conflicting, and one unresolved. They add to five relationship records. These counts do not describe five proven connections. They describe five entries with user-selected labels. Notice that the manager-to-trust management link and trust-to-manager compensation link run in opposite directions. That is intentional. One describes a service role; the other describes a possible payment path. The tool does not combine them into a claim that the service was performed or the payment occurred. ## Understand the Map and Counts The entity cards show incoming and outgoing relationship IDs. They help you locate the records connected to each party. A party with no incoming or outgoing record is labeled by the isolated-entity count. That means no link was entered in this map, not that the party has no business relationships. The detail section shows each arrow, claim, status, source information, period, question, and limits. It also lists selected field gaps. A gap may concern a missing source, an unknown issue date, an unresolved endpoint identity, or a parallel record. An empty gap list does not certify the entry as true or complete. The map checks exact text overlaps in entity names and full identifier strings after trimming spaces, collapsing repeated spaces, and ignoring letter case. It does not use fuzzy matching. Punctuation and spelling differences remain. Notes are not searched, and records are never automatically merged. Parallel relationship pairs require the same from entity, to entity, and type. A reversed direction is different. If three records have the same endpoints and type, there are three pairs to inspect, not three extra relationships. The original records remain in the map. Use the status filter to narrow the relationship details. Entity cards and their connection lists continue to show the full saved map. Downloads also retain every record. A filtered view is a reading aid, not a change in the underlying research scope. ## Edit Records and Export Your Work Save or clear an unfinished form before building the map or working on another record. Editing opens the saved record in its form. Saving replaces that record while keeping its ID. Earlier text is not retained as version history. Export a copy before an important change if you need a dated record. You cannot remove an entity while relationships still point to it. Remove those links or reassign their endpoints first. Removal requires an in-page confirmation. A change to a form cancels a pending confirmation so an old removal or reset request does not silently apply after new edits. Invalid saves leave the saved records unchanged. They also clear the old displayed result and disable downloads. Correct the fields, save the form, and build again. Changes to the map title, scope, cutoff, or record forms similarly require a fresh result before export. Download the full map as JSON or plain text. JSON preserves the structured records and results; text gives a readable report. Neither file is an import format for this tool because import is not supported. There is no automatic storage, account sync, or record history. Leaving or reloading the page loses work that has not been downloaded. The normalized saved map is limited to 200,000 UTF-8 bytes. Each formatted export is limited to 1 MiB. Long notes and characters that use several bytes can reach the limit before the record count does. Shorten the notes or divide the research into clearly scoped maps if needed. ## Use the Map in DST Disclosure Research A useful map should lead to better questions. For each important connection, ask what source supports it, what period it covers, and what decision it could affect. Do not treat a dense set of arrows as a risk score. The number of entered links depends partly on the scope and detail of your research. SEC staff guidance explains that conflicts can arise at both firm and professional levels and that disclosure alone does not satisfy the best-interest obligation. The guidance does not mean that every affiliation is improper. This tool helps organize the relevant questions; it does not test compliance or decide whether a recommendation meets a legal standard. [SEC staff bulletin on conflicts of interest](https://www.sec.gov/about/divisions-offices/division-trading-markets/broker-dealers/staff-bulletin-standards-conduct-broker-dealers-investment-advisers-conflicts-interest). Use the [compensation and disclosure guide](/writing/kay-properties-and-investments-reviews-2026-what-to-review-about-compensation-and-disclosures) when you need to trace a payment and avoid counting a share of a fee twice. Use the [source and entity index](/writing/kay-properties-and-investments-reviews-source-and-entity-index) when the main task is organizing documents by subject. These tools have different jobs and do not exchange records automatically. ## Frequently Asked Questions ### Does This Tool Verify Kay Properties Affiliations? No. It organizes claims and sources you enter. The example is entirely fictional. No website, registration record, or private agreement is fetched or checked. A user-confirmed identity or disclosed relationship label remains your assessment, not a finding made by Sequoia Research or the software. ### Can I Enter a Relationship That Is Only a Question? Yes. Use unresolved status and explain the open question. A primary source is optional for that status. The resulting record remains visibly unresolved. Do not word the claim as a proven relationship if the evidence only raises a question. ### Does an Ownership Chain Prove Indirect Control? No. The map records direct links only. It does not calculate indirect ownership, voting power, control, or legal affiliation. Each link needs its own evidence and scope. Two connected arrows do not establish that the first party controls the last. ### Why Can a Disclosed Relationship Have an Open Question? A source may support the basic connection while leaving its period, scope, or payment terms unclear. The tool preserves those questions. The status count and open-question count measure different fields, so they can overlap without being inconsistent. ### Does Filtering Change the Download? No. The filter narrows relationship details on screen. Entity cards, connection lists, and both downloads retain all saved records. Check the scope and totals in the exported report before sharing it with someone who did not see the full map. ### Can I Recover Work After Reloading the Page? The tool has no automatic storage or import. Download the JSON or text report before leaving. Those files preserve the saved information for your records, but you would need to enter it again to continue in a new map. Unsaved form text is not included in a completed export. ## About Sequoia Research Sequoia Research publishes educational articles and tools for DST investment research. Its materials explain source scope, calculations, and limits so readers can examine the basis for a conclusion. This manual disclosure map is not a credit rating, legal opinion, or recommendation of a firm or investment. ## Sources - [FNEX Form CRS](https://files.brokercheck.finra.org/crs_166316.pdf). Displayed June 8, 2026; inspected October 17, 2026. Bounded context for possible professional and sponsor connections. - [FINRA: About BrokerCheck](https://www.finra.org/investors/investing/working-with-investment-professional/about-brokercheck). Undated current page; inspected October 17, 2026. Firm and individual record scope. - [SEC staff bulletin on conflicts of interest](https://www.sec.gov/about/divisions-offices/division-trading-markets/broker-dealers/staff-bulletin-standards-conduct-broker-dealers-investment-advisers-conflicts-interest). August 3, 2022; inspected October 17, 2026. Firm and professional incentives and disclosure limits.