Flood depth, duration, entry route, removed material, equipment exposure, site flow, and repair valuation are different inputs. A contractor scope cannot silently answer the City floodplain decision.
The practical answer is to keep each decision in its own record. Start with the exact address, vehicle, material, or project; identify the authority; then preserve the source-dated result beside the scope it actually covers.
Build this evidence ledger
| Record | What to capture | Why it matters |
|---|---|---|
| Address and authority | Address, parcel if available, municipality/county, office, scope sent, response date | Prevents a neighboring jurisdiction’s process from controlling the project |
| Existing condition | Dated wide and close photos, affected locations, sequence, temporary measures, unknowns | Separates observations from cause and proposed work |
| Component scope | Roof/entry route; HVAC exposure; electrical exposure; aluminum roof edge; drywall removal; primer/paint; grading, vegetation, and drainage | Makes every genuinely affected service visible in the proposal |
| Flood and value inputs | Water observations, event date, floor/equipment elevations, market-value source, repair valuations, and official response | Makes the floodplain screen reproducible without calculating a private result |
| Permit and closeout | Application, plans, contractor/trade records, revisions, inspections, completion photos, receipts | Connects the reviewed scope to the final record without assuming approval |
What the official records establish
The Flood Hazards from City of Vicksburg supports the city flood-hazard and local confirmation route. The guide does not classify a private parcel or calculate substantial damage.
The Building Inspection Permits from City of Vicksburg supports the current city building, trade, and project-permit starting routes. The City must classify the address and complete project scope; the page is not an issued permit.
The Building Inspections from City of Vicksburg supports the city inspection-request and result route. The required sequence and result remain project-specific.
These records should be read together only through their stated roles. A registration does not become a permit; a permit page does not establish physical condition; a rate table does not classify a private event; and a material list does not authorize an unlisted load.
Keep the boundary visible
Observed water does not establish flood-zone status, substantial damage, contamination, dry-out completion, safe re-energization, structural condition, or insurance coverage.
Write “not established” when a field has no reliable answer. If the scope or event changes, preserve the earlier version and record the new decision instead of overwriting the evidence chain.
Practical sequence
- Freeze the pre-work condition and identify the exact jurisdiction.
- Write each affected component as its own scope line and record exclusions.
- Send the unchanged scope to the responsible office and preserve its answer.
- Verify contractor or trade credentials separately from the project permit.
- Match revisions, inspections, and final evidence to the same scope ledger.
Before acting, revisit every live official page. The access date proves what Local Service Ledger reviewed; it does not freeze a form, rate, office route, eligibility rule, or permit interpretation.
Source and method
Local Service Ledger reviewed 3 official records on 2026-08-29. We assigned each source a limited job, compared its fields, and produced the 5-row ledger above. The matrix keeps flood and valuation inputs outside seven physical scopes while connecting each official decision to the same event and address.
This guide does not diagnose damage, determine causation, design work, classify a private permit or program outcome, interpret insurance, establish credential sufficiency, or recommend a contractor or product.