Report a problem

Use Report a problem to create a clear, actionable report. The form collects three pieces of information: what happened, any supporting evidence, and where it happened. The problem description and location are required; attachments are optional.

Quick steps

• 1. Describe the problem in one or two sentences. Be specific (e.g. "broken street light, pole A12 near 123 High St").
• 2. Add supporting files if available (photos are most helpful). You can upload up to four files (15MB each).
• 3. Set the location using search, your current device location, or by dropping the pin on the map. Adjust the pin if needed for accuracy.
• 4. Review the details and press Submit report.

Writing a good report

• Keep the description concise and factual. Avoid long narratives — include the essential details needed to identify and correct the issue.
• Choose the suggested category that best matches the problem; categories help route the report to the right team.

Evidence and attachments

• Supported file types are listed below. Photos are the most useful: provide at least one close-up of the problem and one wider context shot.
• Images may contain embedded GPS (EXIF) — if present, Seiso will use that as the initial map location but you can move the pin.
• Limit: up to four files, 15MB each. Attachments are uploaded with the report and processed for thumbnails where applicable.

Location

• Use the map to precisely position the report. You can search for addresses or places, use the device's current location, or drop the pin manually.
• If the map marker is slightly off (e.g. on the wrong side of the road), move it to the correct position before submitting.

After submission

• You'll see a confirmation and the report's public ID. This ID can be used to view the report and share it with others.
• The report is added to the organisation's reports list and activity timeline. Depending on the organisation, it may be triaged, assigned, or updated with progress messages.

Supported files

• Images: .jpg, .jpeg, .png, .webp, .heic, .heif
• Videos: .mp4, .mov, .webm
• Audio: .mp3, .m4a, .wav
• Documents: .pdf, .doc, .docx, .txt, .rtf
• Spreadsheets: .xls, .xlsx, .csv

Endpoint

• POST /reports/report — creates a report from a multipart/form-data request. The response includes the generated report public ID and any server-side validation messages.

Form fields (example)

description=Broken street light near 123 High St
category=4
location_final_lat=53.4084
location_final_lng=-2.9916
location_source_final=manual
attachments=<optional files>

Notes for implementers

• Use multipart/form-data for file uploads; the attachments field may contain up to four files, 15MB each.
• Image uploads are scanned for EXIF GPS coordinates and thumbnails are generated. Other media types are stored and linked to the report.
• Validate category values and return clear error messages for invalid inputs. Prefer server-side parsing for address resolution and geocoding, but accept client-provided location_final_lat/location_final_lng when supplied.

Security & privacy

• Treat attachments as user-provided content. Sanitize filenames and store media using a secure object store. Strip or carefully handle sensitive metadata if required by policy.