--- title: "Chicago inspection and violation IDs: reconcile job records" description: "Group Chicago violation records by inspection and property without merging findings. Prepare a trade job handoff with evidence gaps and named reviewers." canonical: "https://scalewithsearch.com/articles/chicago-inspection-violation-ids-trade-job-reconciliation" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Chicago inspection and violation IDs: reconcile several findings on one trade job Keep one row for each violation when reviewing a Chicago inspection against a trade job. Group related rows for reading, then preserve each finding's identity, description, and status. One favorable status cannot describe findings you have not checked. Chicago's publisher states that violations belong to inspections and that one inspection can have several violation records. That relationship appears in the [Building Violations publisher description](https://data.cityofchicago.org/Buildings/Building-Violations/22u3-xenr/about_data), verified through the [official metadata on 2026.10.28](https://data.cityofchicago.org/api/views/22u3-xenr.json). For an authorized job, prepare a finding-by-finding comparison with the office records. Ask which finding each work note supports. Preserve anything unmatched. The goal is a supervisor handoff that explains the relationships before anyone summarizes the inspection. This guide recommends a reading method. It does not supply a city closure procedure or decide technical compliance. The [plumbing and electrical office overview](/for/plumbing-and-electrical-contractors) describes the surrounding staff responsibilities. ## Separate the references before comparing the wording Use different columns for the public violation reference, inspection number, inspection category, property group, and internal job reference. Avoid a generic ID column that changes meaning between rows. Chicago's metadata lists `id`, `inspection_number`, `inspection_category`, and `property_group` as separate fields. It supplies category and property-group definitions, but no explanatory description for the ID or inspection-number fields in the checked version. [Chicago field metadata, accessed 2026.10.28](https://data.cityofchicago.org/api/views/22u3-xenr.json). Use the published ID to refer back to the source row. Keep the inspection number exactly as displayed. Do not infer an encoded year, trade, or location from either value without documentation. | Reference in the comparison | Purpose in your review | What to keep separate | | --- | --- | --- | | Violation ID | Point to the individual source finding | Other findings under the inspection | | Inspection number | Group rows with the same published inspection reference | The status of each violation | | Inspection category | Preserve the publisher's inspection context | Trade scope and office priority | | Property group | Review the publisher's address grouping | Unit, room, equipment, and job scope | | Internal job reference | Locate your company's authorized work records | Public inspection and violation identifiers | The internal job reference is your office's addition. Do not present it as a Chicago field or assume the public source contains it. Record why your supervisor accepted the link between a public finding and the job. ## Read inspection category as context Chicago defines COMPLAINT as resulting from a 311 complaint and PERIODIC as a recurring inspection, typically annual. PERMIT results from a permit. REGISTRATION results from a registration, typically vacant-building registration. [Chicago inspection-category definitions, checked 2026.10.28](https://data.cityofchicago.org/api/views/22u3-xenr.json). Preserve that category beside the inspection number. Do not convert it into a determination of technical severity or your company's responsibility. The category definition does not answer who performed work or which contract includes a correction. For a PERMIT row, ask which supporting permit record belongs in the authorized review. Do not substitute the inspection number for a permit identifier. For a COMPLAINT row, retain the category without guessing who complained or why. A category can help frame the next document question. It should not decide whether an estimator creates a quote, dispatch sends a technician, or an office marks a job complete. Those decisions require their own source records and owners. ## Worked example: three findings under one inspection Every identifier, address label, description, date, and job document in this example is fictional. The labels are training references, not real Chicago addresses. The supervisor has authorized review of internal job `TRAINING-J42`. Three source rows share inspection `TRAINING-I90` and property group `TRAINING-P07`. Two address labels appear in the saved records. | Violation reference | Inspection | Property group | Address label | Historical finding | Saved status | | --- | --- | --- | --- | --- | --- | | TRAINING-V31 | TRAINING-I90 | TRAINING-P07 | Training corner entrance | Component finding A | Complied | | TRAINING-V32 | TRAINING-I90 | TRAINING-P07 | Training side entrance | Component finding B | Open | | TRAINING-V33 | TRAINING-I90 | TRAINING-P07 | Training side entrance | Access-related finding C | No Entry | The office has a signed work note describing component A. A separate scheduling note mentions a proposed visit concerning component B. Nothing in the supplied job file explains a later authority disposition for finding C. Keep three comparison rows. Attach the signed work note to the first row as candidate supporting evidence. Attach the proposed visit note to the second row as a plan. Leave the third row's authority-evidence slot unresolved. Do not mark the inspection closed because the first row says Complied. Do not count the proposed visit as completed work. Do not treat the shared inspection number as evidence that one document resolves every finding. A useful inspection summary reads: “Three findings appear in the saved set. Their statuses differ. The office supplied one work note and one planned-visit note. Supervisor review remains finding-specific.” This summary describes the material examined without claiming the set is complete. For the meanings and limits of the labels, use the [Chicago violation status guide](/articles/chicago-violation-status-trade-job-review). Keep that interpretation beside each finding rather than applying one status to the inspection heading. ## Reconcile address labels with the property group Chicago explains that a property can have multiple point addresses, address ranges, or buildings. Related records may therefore carry different addresses. Its property-group key connects the point and range addresses assigned to one property. [Chicago `property_group` definition, accessed 2026.10.28](https://data.cityofchicago.org/api/views/22u3-xenr.json). In the fictional example, the common property group gives the supervisor a reason to examine both address labels together. It does not identify the room, equipment, or exact work location. Preserve the two labels in the comparison until the job evidence resolves their relevance. Ask the trade lead which location appears on the signed work note. Ask the supervisor which approved job document connects that location to the public finding. Record both answers with their document references. If one finding refers to a rear building and the job record names only a street address, leave the match incomplete. A property-level relationship does not fill an equipment-level gap. Likewise, an office nickname should not overwrite the published address. Keep rejected matches as short notes within the authorized job review. Explain the mismatch that caused rejection. This lets a later reviewer understand why a similar address or repeated phrase was excluded. ## Preserve individual findings when descriptions repeat Two rows can look alike to a reader because their descriptions use similar wording. Do not merge them solely on that basis. Start with the published references, inspection numbers, locations, and dates. If two saved versions show the same ID with different fields, preserve the versions while investigating. Record when your office retrieved each version. A changed status is useful comparison evidence, but it does not explain every administrative event behind the change. If different IDs carry similar descriptions, keep them separate pending review. Ask whether the records concern different locations, separate findings, or another documented distinction. Do not invent that distinction when the source leaves it unclear. Write unresolved identity explicitly. “Same description, different violation references; relationship unconfirmed” gives the supervisor a concrete question. A single merged paragraph would hide the very difference that needs attention. The same discipline applies to internal records. One technician note may mention several work items. Map each relevant passage to the finding it supports, with the supervisor checking the connection. Avoid attaching the whole note as universal evidence without explaining its coverage. ## State exactly which records you examined A grouped table needs a boundary statement. Record the source, retrieval date, inspection number used for the review, and the saved rows examined. Note any filters that limited what you saw. For example, reviewing only Open rows would exclude the Complied and No Entry rows in the fictional set. Describe such a view as a filtered selection. Do not label it all findings for the inspection. If the interface limits the displayed records, preserve that limit in the review note. Ask the supervisor whether another source view or authority record is needed. A short result list is not evidence that no other records exist. Avoid a completeness claim unless your review process establishes it. “These three saved rows were compared” is precise. “The inspection contains exactly three findings” requires further support beyond the fictional table or a partial view. This boundary matters when another supervisor returns to the job. They should be able to distinguish a changed public record from a change in the office's selection. Preserve the selection description beside the saved evidence. ## Prepare a finding-by-finding handoff Give every finding its own identity question, supporting office document, missing authority evidence, and responsible reviewer. Keep task ownership separate from technical conclusions. A named supervisor can own an unanswered question without claiming the underlying work is accepted. | Fictional finding | Office evidence supplied | Unresolved question | Proposed owner | | --- | --- | --- | --- | | TRAINING-V31 | Signed component A work note | Which authority record supports the displayed disposition? | Supervisor | | TRAINING-V32 | Proposed visit note | What work, if any, was performed for this finding? | Trade lead | | TRAINING-V33 | No matching authority follow-up supplied | Is there a later access or inspection record? | Supervisor | Use this as an example format, not a required city form. Replace the roles with the people responsible for your authorized job. Give each question an internal follow-up date chosen by its owner. Keep authority responses attached to the finding they address. If a response covers several findings, record that coverage explicitly. If its reference is unclear, ask for clarification before copying its conclusion across the group. The [business memory guide](/articles/business-memory-for-ai-agents-guide) explains how to retain source references and accepted corrections. Use those practices to preserve why a relationship was accepted, rejected, or left unresolved. A future reviewer should not need to reconstruct that decision from scattered messages. ## Keep the group summary narrower than the evidence Write the group summary after reviewing the individual rows. Name the findings examined and the questions still open. Do not let a short heading such as resolved property replace the mixed statuses beneath it. Chicago warns that these historical records may not describe current property conditions. Its dataset also includes cases with differing liability outcomes. A group summary therefore cannot decide present condition or liability from the presence of rows. [Publisher limits, accessed 2026.10.28](https://data.cityofchicago.org/api/views/22u3-xenr.json). Keep professional judgments with the responsible authority and trade lead. The supervisor's comparison should identify the next document or clarification needed. It should not instruct technical repairs or determine whether a property is safe. The [contractor intelligence overview](/intelligence/plumbing-and-electrical-contractors) describes how external information can support internal review. For this task, limit the record comparison to the authorized job and its documented relationships. Before handing over the table, ask a colleague to trace one row from public reference to office evidence. If the connection cannot be explained, keep the relationship unresolved. Repair the explanation before shortening the summary. Scale With Search can scope a record-review function using approved examples, defined source boundaries, and named supervisors. [Request a written scope](/work) Continue the website review: [AI-native plumbing and electrical: first functions to build](/articles/ai-native-plumbing-electrical-first-functions); [Chicago violation statuses: read Open, Complied, and No Entry before job review](/articles/chicago-violation-status-trade-job-review); [Contractor license details: make your website verifiable](/articles/contractor-license-verification-website); [Contractor online booking: request or confirmed visit](/articles/contractor-online-booking-request-confirmation); [Digital marketing for electricians: a website plan](/articles/digital-marketing-electricians-website-plan); [SEO for electrical contractors: an owner checklist](/articles/electrical-contractor-seo-owner-checklist); [Plumber and electrician Google categories: choose a fit](/articles/plumber-electrician-google-profile-categories); [Plumber website prices: explain the fee and estimate](/articles/plumber-electrician-website-pricing-estimate); [Marketing for plumbers: fix the website inquiry path](/articles/plumber-marketing-website-local-search); [Plumbing and electrical AI rules: data, approvals, and spend](/articles/plumbing-electrical-ai-rules-data-approvals-spend); [Emergency plumber website: make after-hours claims clear](/articles/plumbing-electrical-emergency-website-hours); [Plumbing and electrical services: one site, clear pages](/articles/plumbing-electrical-separate-service-pages); [Plumbing city pages: decide which places need a page](/articles/plumbing-electrical-service-area-city-pages). [plumbing and electrical contractors](/for/plumbing-and-electrical-contractors): website and search resources. ## Related: plumbing and electrical contractors - [Chicago violation statuses: read Open, Complied, and No Entry before job review](/articles/chicago-violation-status-trade-job-review) - [Contractor license details: make your website verifiable](/articles/contractor-license-verification-website) - [Contractor online booking: request or confirmed visit](/articles/contractor-online-booking-request-confirmation) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```