Figpark
← All articles

Parking-host incident reports: record facts without escalating

July 11, 2026 · Guides for hosts

An incident report is a record, not an argument. Whether the issue is a damaged gate, a blocked space, an access failure, or a disagreement about the vehicle's condition, the host's first job is to preserve facts and keep people safe. Do not try to settle a serious dispute at the gate.

Record the minimum useful facts

Note the booking or listing, date and time, exact location, people present, visible condition before and after if known, access events, and the messages exchanged. Take wide and close photographs without publishing private data. Keep the original files and note when they were taken. If a witness or building manager is involved, record their role rather than guessing what they saw.

Separate what you observed from what you infer. “The gate did not open at 18:10” is a record; “the driver broke the gate” is a conclusion that may not be established. Do not enter a vehicle, touch personal property, or ask for unnecessary identity documents. If there is immediate danger, injury, fire, or a serious security issue, use emergency or building procedures first.

Use the right channel

For booking, payment, access, or cancellation questions, use platform support and attach the relevant evidence. Keep messages short, neutral, and limited to the people who need them. Do not threaten a review, demand cash at the roadside, or promise compensation before the applicable terms and insurance position are clear.

The insurance and damage checklist helps before an incident, and the privacy guide covers information handling. Afterward, update the listing or access instructions if the incident revealed a repeatable weakness, then reopen availability only when the space is safe.

Your empty spot is money

List a driveway, garage, or reserved spot on Figpark and earn from the hours it sits empty. Drivers book and pay online — the app keeps the reservation details together.

List your spot Find parking