Delegation Framework (Intermediate Level)

← Back to “AI for Good” Nonprofit Workshop Resources

Chiv Heng Consulting — www.chivheng.consulting • LinkedIn

</aside>

Last reviewed: July 2026

The baseline prompt engineering framework described in the Prompt Engineering (Beginner Level) page is a strong starting point for new users of AI platforms:

Prompt then Response. You ask something, the model answers, you refine your question, the model answers again. Quick exchanges, real-time iteration.

This is how most users begin using AI. Delegation asks the tool to produce a defined work product.

Moving from Prompting to Delegation

As your comfort and proficiency with AI increases, you can move toward a delegation framework:

Delegated assignment, intermediate checks, then deliverable. You define a job (audit this spreadsheet, synthesize this user feedback, stress-test this pitch deck) and expect a work product, not just an answer to mull over.
Before assigning work, state what good looks like and what done looks like. This gives the AI a target and gives you a basis for review.
The model can help examine large datasets and surface potential anomalies. You must validate them against the source data.

Intermediate checks mean checking progress against the definition of done. Without that standard, a check only confirms that work happened, not that it meets your needs.

Delegation Brief (copy, paste, fill in)

PURPOSE AND DECISION
- Purpose:
- Decision this supports:

CONTEXT AND APPROVED INPUTS
- Context:
- Approved inputs:

TASK AND BOUNDARIES
- Task:
- Boundaries:

DELIVERABLE AND AUDIENCE
- Deliverable:
- Audience:

DEFINITION OF DONE
- Acceptance criteria the work product must meet:

CHECKPOINTS
- Where I will review before work continues:

Worked example (synthetic only)

Task: A food-security nonprofit needs a one-page memo before its monthly leadership meeting.

PURPOSE AND DECISION
- Purpose: Summarize anonymized parent-survey feedback.
- Decision this supports: Choose two service improvements to explore next month.

CONTEXT AND APPROVED INPUTS
- Context: Feedback came from a synthetic survey export about pantry pickup.
- Approved inputs: The attached anonymized survey responses only.

TASK AND BOUNDARIES
- Task: Group common themes, note recurring concerns, and identify strengths.
- Boundaries: Do not infer demographics, name respondents, or recommend changes beyond the feedback.

DELIVERABLE AND AUDIENCE
- Deliverable: One-page memo with three themes, two strengths, and two questions for discussion.
- Audience: Executive director and program leads.

DEFINITION OF DONE
- Acceptance criteria the work product must meet: Use plain language, cite response counts for each theme, stay under 500 words, and distinguish feedback from interpretation.

CHECKPOINTS
- Where I will review before work continues: Review the theme list before the memo is drafted. Review the final memo against the acceptance criteria before sharing.

Next: Context Documents for Nonprofits (what makes delegation reliable) and Featured Tool: Claude Cowork (delegation in action).