Task Templates

SurveyJS-based task definitions that structure the questions crowd workers answer during verification.

Task templates define the structured questionnaire presented to crowd workers during a crowd stage. Every crowd stage in a verification pipeline is backed by a task template that determines what workers see, what questions they must answer, and what response formats are accepted. Templates are built on SurveyJS, a JSON-based survey framework that supports conditional logic, multiple question types, required fields, and rich media display. Because SurveyJS is an open standard, templates can be designed and validated in any SurveyJS-compatible editor before being uploaded to Crowdee.

Template Scope

Task templates can be created at two scopes, each suited to different use cases.

Organization-scoped templates are available across all projects within your organisation. They are the right choice for standard review questionnaires you expect to reuse across multiple campaigns or pipeline configurations — for example, a general image authenticity assessment template that applies regardless of which project the content belongs to. Organization-scoped templates are managed centrally and require admin-level access to create or modify.

Project-scoped templates are tied to a specific project and are not visible to or reusable by other projects. They are suited for one-off or highly specialised tasks where the questionnaire is meaningfully different from anything you would use elsewhere — for example, a template written specifically for a single investigative journalism project that references that project's subject matter. Project-scoped templates are managed within the project and require at minimum user-level access.

Versioning

Templates are versioned automatically. Every PUT request to update an existing template creates a new version; the template itself always reflects the latest version. In-flight crowd tasks — those that have already been distributed to workers — always use the version that was active at the time the task was created. This ensures that workers within a single crowd stage all see the same questionnaire even if the template is updated while that stage is running.

Previous template versions are accessible via the versions endpoint:

GET /v2/survey-templates/{templateId}/versions

This returns a list of all historical versions in reverse chronological order, including the surveyJs JSON, the version number, and the creation timestamp.

Modifying a template does not affect crowd tasks already in progress — those use the version that was active when the task was distributed. Only new crowd stages created after the update will use the new version. If you need to revise the questions for an in-flight stage, you must cancel the current run and start a new one.

Creating a Template

Templates are created via the survey templates API. The request body requires three fields: a human-readable name, the scope (either "project" or "organization"), and the surveyJs object containing the SurveyJS page and elements definition.

POST /v2/projects/{projectId}/survey-templates
X-API-Key: crw_YOUR_API_KEY
Content-Type: application/json

The following example creates an organization-scoped template for a basic image authenticity review. It presents workers with a multiple-choice question on manipulation assessment and a free-text reasoning field:

{
  "name": "Image Authenticity Review",
  "scope": "organization",
  "surveyJs": {
    "pages": [{
      "elements": [{
        "type": "radiogroup",
        "name": "assessment",
        "title": "Does this image appear to have been digitally manipulated?",
        "isRequired": true,
        "choices": [
          "Clearly manipulated",
          "Possibly manipulated",
          "No signs of manipulation",
          "Cannot determine"
        ]
      }, {
        "type": "comment",
        "name": "reasoning",
        "title": "Briefly explain your assessment",
        "isRequired": true,
        "rows": 4
      }]
    }]
  }
}

The surveyJs object supports the full SurveyJS schema, including multi-page questionnaires, conditional visibility (visibleIf), rating scales, file upload questions for annotated screenshots, and matrix questions for multi-attribute evaluation. Refer to the SurveyJS documentation for the complete schema reference.

Managing Templates

Once created, templates are managed through the following endpoints.

List all templates accessible to your organisation (both organization-scoped and project-scoped, filtered by your access level):

GET /v2/survey-templates
X-API-Key: crw_YOUR_API_KEY

Update a template (creates a new version):

PUT /v2/survey-templates/{templateId}
X-API-Key: crw_YOUR_API_KEY
Content-Type: application/json

{
  "name": "Updated name",
  "surveyJs": { ... }
}

Delete a template:

DELETE /v2/survey-templates/{templateId}
X-API-Key: crw_YOUR_API_KEY

Deleting a template prevents it from being selected for future crowd stages. It does not affect in-progress crowd tasks that were created while the template existed — those workers will continue to see the questionnaire that was active when their task was distributed. Template deletion is permanent and cannot be undone.

Crowdee ships with a set of built-in task templates that correspond to each of the 14 verification pipelines. These are read-only and cannot be modified. If you want to customise the questionnaire for a crowd stage, you must create your own template and configure the pipeline run to use it. Contact hello@crowdee.ai for guidance on custom crowd stage configuration.

Template Scope

Versioning

Creating a Template

Managing Templates

On this page