1. Home
  2. Docs
  3. TALA Flow
  4. Submission table, map and corrections
TALA Flow

Submission table, map and corrections

Review submissions without losing provenance or allowing map/table interfaces to hide correction history.

Supervisor v2026.10 Updated 9 Nov 2026

Review surfaces

Use the table for structured review and filtering, and the map when location is meaningful. A submission detail or edit dialog must remain visually above the map layer so reviewers never lose context behind map controls.

Corrections

A correction should validate the edited record itself rather than re-triggering irrelevant required-field failures from historical submissions. Preserve the original submission and correction history where governance requires it.

Location checks

GPS is evidence, not automatic truth. Investigate repeated coordinates, impossible travel, boundary outliers, and device-sharing patterns with timestamps and operational context before concluding misconduct.

Was this page helpful?

Still stuck?

Open a ticket and reference this page — we will pick it up from there.

Open a ticket