> ## Documentation Index
> Fetch the complete documentation index at: https://help.terriqon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects and Forms in Terriqon: A Complete Overview

> Projects in Terriqon organize your data collection work. Each project links a form to Field Officers and tracks submissions, KPIs, and AI reports.

Forms and projects are the two structural building blocks of Terriqon. A form defines what data your team collects — the questions, field types, and sensitivity classifications. A project puts that form to work by assigning it to a group of Field Officers, setting a scope, and housing the resulting submissions, KPI dashboards, and AI reports. Together they give you a clean separation between *what you collect* and *where and by whom you collect it*.

## Forms

Forms are created in the drag-and-drop form builder, accessible from **Forms** in the main navigation. You add fields by dragging them from the component panel onto the canvas and configure each one in the right-hand properties pane.

Terriqon supports the following field types:

* **Text** — short answer and long answer
* **Number** — integer and decimal
* **Date / Time** — date picker, time picker, or combined
* **Single choice** — one answer selected from a list of options
* **Multiple choice** — one or more answers selected from a list of options
* **GPS location** — captures device coordinates at the time of submission
* **Photo** — single or multiple image capture
* **Signature** — finger-draw or stylus signature pad
* **File upload** — document or media upload
* **Audio** — voice memo or audio recording
* **Case ID** — a structured identifier field for linking submissions to case records

### Sensitivity tagging

Every field can be tagged with a sensitivity classification. Two tags are available:

* **Personally Identifiable** — any data that could identify an individual (names, national ID numbers, phone numbers, biometric data)
* **Restricted** — data that is sensitive but not strictly PII (financial figures, organisational codes)

Fields tagged with either classification are automatically excluded by the PII stripping pipeline before any data reaches the AI. GPS location is always stripped by this pipeline regardless of how the field is tagged — device coordinates never reach the AI. The pipeline also pattern-detects untagged personal data such as national IDs, passport numbers, and bank account numbers in free-text fields, and excludes those values as well.

<Tip>
  Tag any field that might contain names, IDs, phone numbers, or sensitive figures with a sensitivity classification. Terriqon will automatically exclude these from AI processing — and GPS coordinates are always excluded even without a tag.
</Tip>

### Deploying and reusing forms

A single form can be deployed to any number of projects. You do not need to duplicate a form to use it in a different region or season. Any updates you publish to a form are pushed to Field Officers the next time their device syncs.

You can also import existing forms from a JSON export or copy a form from another project to use as a starting template.

## Projects

A project is the operational container that links a form to a set of Field Officers and gives managers a live view of activity. Create a project from **Projects → New Project**, then attach a form and assign the Field Officers who will submit data under it.

Each project includes:

* **KPI dashboard** — real-time metrics including submission counts, completion rates, field officer activity, and any calculated indicators you have configured on the form
* **Submission log** — a full, timestamped record of every submission with audit trail entries
* **Reports panel** — where you trigger AI report generation and manage the approval workflow
* **Team panel** — the Field Officers assigned to this project and their submission status

### Report types per project

From a project's Reports panel you can generate any of the four AI report types:

| Report type      | What it covers                                                    |
| ---------------- | ----------------------------------------------------------------- |
| Project Report   | Submission data, KPIs, and field activity for this project        |
| Ops Report       | Team performance, submission rates, and data quality for managers |
| Donor Report     | Funder-ready narrative with outcomes and impact metrics           |
| Portfolio Report | Cross-project summary for programme directors                     |

### Downgrading and plan limits

If you downgrade your plan, all existing projects remain fully readable — your historical data is never removed. Creating new projects above the limit of your new plan is paused until you upgrade or archive projects to make room.

## The Form–Project Relationship

One form, many projects. A standard farmer-survey form, for example, can serve a Northern Region project and a Southern Region project simultaneously without any duplication. Each project maintains its own independent submission log, KPI calculations, and report history, even though they share the same underlying form schema.

When you update a shared form — adding a field, adjusting validation rules, or retagging sensitivity — the change propagates to every project using that form on the next sync cycle. Review the impact on downstream reports before publishing major structural changes.