/
/
Check Procore asset naming standards before names collide
For asset and operations teams who want company and project naming standards compared and checked, by asking their AI assistant.
On this page
Connector
Connect Procore, pick your AI tool and paste the prompt.
The problem
Naming rules fail where nobody looks
Company and project naming standards have rules, fields and codes on separate screens. A bad code or a field no rule uses is only noticed when two asset names collide.
Without PopdockAI
- Open the company naming standard and its codes
- Open the project standard and compare rule by rule
- Check each code is still active
- Find the problem when two names collide
With PopdockAI
- Company and project standards are pulled together
- Expressions using missing fields are flagged
- Inactive codes still used by a rule are caught
- Differences are listed, and counters and codes are never changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Audit the company asset naming standard and, if `{project-name}` is given, compare it with that project's standard.
**Step 1: Pull the company standard**
* `procore-get-assets-settings-naming-standard`
* `procore-get-assets-settings-naming-standard-fields`
* `procore-get-assets-settings-naming-standard-codes`
* `procore-get-assets-naming-std-fields-lov`
* `procore-get-assets-naming-std-def-expr-fields`
**Step 2: Pull the project standard**
If `{project-name}` is given, call `procore-get-project-assets-settings-naming-standard`, `procore-get-project-assets-settings-naming-standard-fields`, `procore-get-project-assets-settings-naming-standard-codes` and `procore-get-proj-assets-naming-std-def-expr-fields` with `project-name`.
**Step 3: Check**
* Rules whose expression uses a field that is not in the naming fields.
* Codes in the list of values that are inactive but still used by a rule.
* Fields marked `available-on-all-asset-types` that no rule uses.
* Differences between the company and project rules.
**Step 4: Report**
A short summary of the standard (fields in order, fallbacks), then each problem and each company versus project difference.
**Rules & Guidelines:**
* This prompt is read-only. Do not call any write tool: Every `procore-create-*`, `procore-update-*`, `procore-delete-*`, `procore-sync-*`, `procore-add-*`, `procore-bulk-*` and `procore-send-*` tool, plus `procore-respond-*`, `procore-terminate-*`, `procore-restart-*`, `procore-refresh-*`, `procore-reset-*`, `procore-link-*` and `procore-retrieve-*`, are off limits.
* Report only values the tools returned. Do not estimate or fill gaps.
* If `{company}` is not blank, pass it as `company` on every call.
* Never reset sequences or collision counters, and never upsert codes.
**Validation:**
* If the company has no naming standard, say so and stop.Who it's for
One answer, three teams that use it
Asset managers
Check the standard before rollout
See problems in the company standard first, so every project inherits something sound.
Audit the company asset naming standard and flag any inactive codes that rules still use.
Project controls leads
Compare a project with the company
See where a project's naming rules differ from the company's, rule by rule.
Compare the Riverside Tower asset naming standard with the company standard.
Procore administrators
Find unused naming fields
List fields that are available on all asset types but used by no rule, to tidy the setup.
Which naming fields in our Procore asset naming standard are not used by any rule?
How it works
What PopdockAI does when you ask
You ask for the audit, optionally naming a project. Your AI assistant reads the standards and checks them. It is read-only and keeps reset and code changes off limits.
Ask
You ask for an audit, optionally naming a project to compare against.
Pull
It reads the company standard, then the project standard when one is named.
Check
It tests rule expressions, codes and fields, and compares company and project rules.
Report
It summarises the standard and lists each problem and each difference.
What PopdockAI provides
The tools behind the answer
Ready made tools for Procore and one secure connection to your AI tool. No code, no exports.
procore-get-assets-settings-naming-standard
procore-get-assets-settings-naming-standard-fields
procore-get-assets-settings-naming-standard-codes
procore-get-assets-naming-std-fields-lov
procore-get-assets-naming-std-def-expr-fields
procore-get-project-assets-settings-naming-standard
procore-get-project-assets-settings-naming-standard-fields
procore-get-project-assets-settings-naming-standard-codes
procore-get-proj-assets-naming-std-def-expr-fields
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Naming standards you can trust across projects
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
