Docs / Company research
Capabilities
Company research
The company behind an LLC, its parent, and the people on the project, on planned projects and building permits.
Boardwalk researches the outside parties on planned projects and building permits: the company behind an LLC or a printed name, its parent company, its local office, and the people who work on the project. It is the same research the Boardwalk app shows on a project page, a permit, and a company page. It rides on standard and full records of both datasets, not on compact.
| Field | What it holds |
|---|---|
companyResearch | Whether the research has run on this record, as status: researched (Researched), nothing_found (Researched, nothing found), not_researched (Not researched yet). researchedOn is the day it last ran. Not researched yet means the research has not reached the record, not that nothing exists. |
researchedParties | Each company or person the research tied to the record: name, entityType (company or person), role and roleLabel, trade, foundVia (our_filing (Named on the filing), our_data (From Boardwalk records), web (Found on the web)), namesOnFilings, sourceSite, whyItFits, and companyId. A person also carries title, linkedinUrl, email, and personalEmail. |
researchedCompanies | Each checked company once, including the company a researched person works for: officialName, description, localOfficeName, website, linkedinUrl, phone and phoneScope, legalNames, namesOnRecord, howWeKnow with howWeKnowDocumentId and howWeKnowPage, and parentCompanyName and parentCompanyWebsite. |
Join a party to its company on companyId. For a company it is the company itself; for a person it is the company they work for. phoneScope is market for the local office line and company for the main line. legalNames are the LLCs the company files under, and howWeKnow is the proof that ties them, with the filing and page when it came from one.
{
"companyResearch": {
"status": "researched",
"statusLabel": "Researched",
"researchedOn": "2026-10-30"
},
"researchedParties": [
{
"name": "Alta Ridge Homes",
"entityType": "company",
"role": "developer",
"roleLabel": "Developer",
"trade": null,
"foundVia": "our_filing",
"foundViaLabel": "Named on the filing",
"namesOnFilings": [
"Alta Ridge Development LLC"
],
"sourceSite": "altaridgehomes.example.com",
"whyItFits": "The company lists Alta Ridge Phase II among its current communities.",
"companyId": 5501,
"title": null,
"linkedinUrl": null,
"email": null,
"personalEmail": null,
"contactsWithheldReason": null,
"publicBody": false,
"privateIndividual": false
},
{
"name": "Jordan Pike",
"entityType": "person",
"role": "owner_representative",
"roleLabel": "Owner's representative",
"trade": null,
"foundVia": "web",
"foundViaLabel": "Found on the web",
"namesOnFilings": [],
"sourceSite": "altaridgehomes.example.com",
"whyItFits": "Named as the project lead on the company site.",
"companyId": 5501,
"title": "Director of Land Acquisition",
"linkedinUrl": "https://www.linkedin.com/in/jordan-pike-example",
"email": "j.pike@example.com",
"personalEmail": null,
"contactsWithheldReason": null,
"publicBody": false,
"privateIndividual": false
}
],
"researchedCompanies": [
{
"companyId": 5501,
"officialName": "Alta Ridge Homes",
"description": "Homebuilder in northern Utah",
"localOfficeName": null,
"website": "https://altaridgehomes.example.com",
"linkedinUrl": "https://www.linkedin.com/company/alta-ridge-homes-example",
"phone": "+1-555-0150",
"phoneScope": "company",
"legalNames": [
"Alta Ridge Development LLC"
],
"namesOnRecord": [
"Alta Ridge Development LLC"
],
"howWeKnow": "The LLC's registered office is the company's own office, down to the suite.",
"howWeKnowDocumentId": null,
"howWeKnowPage": null,
"parentCompanyName": null,
"parentCompanyWebsite": null,
"contactsWithheldReason": null
}
]
}Who sees which values
| Value | Who receives it |
|---|---|
| Names, roles, titles, descriptions, legal names, proof, parent company, and websites | Every caller. |
| A company's LinkedIn page and phone; a person's LinkedIn and emails | A paid plan, a live trial, or a project the user unlocked. Otherwise they are empty and contactsWithheldReason is free_tier. |
| Any contact value for a person who asked us to remove it | Nobody. contactsWithheldReason is suppressed; the name and role still ship. |
When a checked company exists, companyEnrichment on planned projects and the CSV company columns use it, so every surface names the same company.
In MCP
List tools (get_projects, search_permits, and the alert and list pulls) carry companyResearch and a short researchedLite list on each card: name, role, company, and website, never an email or a phone. get_project and get_permit carry the full research.
In CSV exports
Planned project exports add these columns to the contacts column group. Up to 3 companies and 3 people fit per row, and lists inside a cell are separated by | .
| Columns | What they hold |
|---|---|
Company Research, Company Research Date | The research status and the day it last ran. |
Researched Company 1, Researched Company 1 Role, Researched Company 1 Website, Researched Company 1 LinkedIn, Researched Company 1 Phone, Researched Company 1 Legal Names, Researched Company 1 Parent Company | The first researched company. Each later company repeats these columns with its own number. |
Researched Person 1, Researched Person 1 Title, Researched Person 1 Role, Researched Person 1 Company, Researched Person 1 Email, Researched Person 1 Personal Email, Researched Person 1 LinkedIn | The first researched person and the company they work for. Each later person repeats these columns with their own number. |
Building permit exports add one column each, with every company or person in the cell: Company Research, Company Research Date, Researched Companies, Researched Company Websites, Researched Company Phones, Researched Company LinkedIn, Researched Company Legal Names, Researched Company Parents, Researched People, Researched People Emails, Researched People LinkedIn, Company Research (JSON).
Ready to make a call?
A free Boardwalk trial includes API access, 50 record-export credits (search, CSV, MCP), and 5 Find Contact Info lookups. Counting, taxonomy, location lookups, and the analytics plane cost nothing, so you can evaluate the data before you spend a credit.