Skip to main content

Editable Text Responses

Editable text responses present reviewers with pre-filled draft text that they can revise before submitting. This is ideal for AI-generated content that needs human refinement — product descriptions, email copy, translations, or any text that benefits from a human editing pass.

When to Use Editable Text Responses

Editable text responses are ideal for:

AI Draft Editing

Refine AI-generated content like product descriptions, blog posts, or marketing copy before publishing

Translation Review

Review and correct machine-translated text while preserving the original structure and intent

Copy Editing

Polish drafts for grammar, tone, clarity, and brand voice consistency

Template Customization

Personalize templated messages, notifications, or responses before they reach end users

Configuration Options

Editable text responses require the draft text that reviewers will start with:

Required Parameters

string
required
The initial text presented to the reviewer for editing. This is pre-filled in the text editor when the reviewer opens the request.
integer
required
Maximum number of characters allowed in the revised text (1-5000)

Optional Parameters

string
Placeholder text shown if the reviewer clears the draft entirely
integer
default:"0"
Minimum number of characters required in the revised text
boolean
default:"false"
Whether a response is mandatory for completion

Implementation Examples

AI-Generated Product Description

Refine an AI-generated product listing before publishing:

Translation Review

Review and correct machine-translated content:

Email Draft Refinement

Polish an AI-drafted customer response:

Response Format

When a reviewer submits an editable text response, you receive the revised text and a flag indicating whether changes were made:
When the reviewer submits without making changes:

Use Case Examples

1. Content Publishing Pipeline

2. Automated Email QA

Validation and Error Handling

Automatic Validation

The mobile app and web dashboard automatically validate editable text responses:
  • Type validation: Ensures response is a string
  • Length validation: Enforces min_length and max_length bounds
  • Required validation: Prevents empty submissions when required=true

Server-Side Validation

Best Practices

  • Start with well-structured, nearly-complete drafts
  • Include proper formatting (paragraphs, punctuation) in the draft
  • Make the draft good enough that minor edits are sufficient
  • Avoid placeholder text like “[INSERT NAME HERE]” — use realistic content
  • Set min_length to prevent empty or trivially short responses
  • Set max_length generously — reviewers may expand the draft
  • Consider the output context (email subject vs. blog post)
  • Match limits to the target platform’s constraints
  • Track edit rates to measure AI draft quality over time
  • If was_edited is consistently false, your AI drafts are already strong
  • If was_edited is consistently true, analyze diffs to improve the AI model
  • Use the edit patterns as training data for future AI generations
  • Include the original source material or prompt that generated the draft
  • Specify the target audience and tone (formal, casual, technical)
  • Highlight specific areas to focus on (grammar, factual accuracy, brand voice)
  • Mention any constraints (character limits, required keywords)

Next Steps

Response Types Overview

Compare all seven response types and choose the right one for your use case

Text Responses

For free-form text input without a pre-filled draft, use text responses instead

Boolean Responses

For simple approve/reject decisions on content, use boolean responses

Mobile Experience

See how reviewers interact with editable text on mobile devices