Terra Vita · Restricted routeFieldTrace Operator Console
Operator intake · protected test surface

Evidence intake, routed to Hub review.

This restricted console exercises the same backend route used by the direct field evidence app: operator authentication, task context, visit creation, protected evidence upload, submission and reviewer queue creation.

Jazira Phase 0 · FieldTrace intake confirmation

This operator console is prepared for the Jazira Phase 0 July implementation evidence cycle. Use these presets before 18–28 July capture begins so evidence is not submitted as loose, unbound material.

Current programme status: Accepted for Phase 0 pre-mobilisation reviewer record. Not funding-ready / not funding-cleared. FieldTrace captures and binds evidence only; funding-readiness remains a separate Terra Vita reviewer decision.

Programme binding

ProgrammeJAZIRA-SOM-2026
PhasePhase 0 — Capacity Building for Environmental Conservation
Window18–28 July 2026
Data ownerSabir Ibrahim · backup Abdinasir Sheikh Mohamed Hassan
Hub statusPre-mobilisation accepted · funding-readiness open

Quick presets

Use a preset to populate the operator note and coordinates before starting a visit. Site and assigned task still come from the authenticated FieldTrace/Supabase context.

Minimum July evidence categories

FT-01 Participant register FT-02 Daily attendance FT-03 Training sessions FT-04 Pre-training baseline FT-05 Post-training survey FT-06 ToT scorecards FT-07 Field practicum FT-08 Action plans FT-09 Endorsements FT-10 Daily notes FT-11 Final summary FT-12 Follow-up

Training pack and evidence templates

Use the issued training pack and XLSX templates during the 18–28 July implementation cycle. Evidence generated outside this structure may be received but must be corrected before it can be treated as fully programme-bound.

Open training pack route Open XLSX templates Open DOCX guide
Step 01
Start visitCreate an attributable field visit record.
Step 02
Upload evidenceWrite file and metadata to protected storage.
Step 03
SubmitRoute the visit into reviewer intake.

02 · Start visit

03 · Upload evidence

Console upload limit: use a small test file. Larger production files should use the signed-upload app route.

04 · Submit to reviewer queue

Reviewer queue

Admins, managers and reviewers can load pending queue items after submission.

No queue loaded.