# Templates for run names, daily titles, and proposal notes

Written by Geeta Thakker
Updated 2026-10-04

Name the run for its cohort, name each day for its practical task, and use proposal notes to explain decisions the reviewer cannot infer from the fields. These templates belong in **Propose a run**, not on a new workshop page.

## Make a cohort name recognizable in the dashboard

**Before:** “Ultimate AI Mastery Experience.”

**After:** “November 2026 Evening Run.”

The workshop is selected separately. A cohort label helps the team distinguish deliveries of the same workshop without adding an unsupported learning promise.

```text
[Month Year] [schedule or audience label] Run
```

1. Choose the published workshop first.
2. Fill **Run name** with the month and a useful distinguishing label.
3. Check that the label agrees with the proposed schedule and audience. Do not call it an evening run if you have proposed morning sessions.

## Turn daily titles into visible practice tasks

**Before:** “Introduction” and “Advanced concepts.”

**After:** “Draft a source-grounded project brief” and “Check and revise the brief against its sources.”

```text
Day 1: [Action verb] [a concrete output]
Day 2: [Test or improve] [that output] using [a clear check]
Day 3: [Apply the method] to [a new example]
```

Use only as many lines as the run has days; the form already labels the day number. Enter the task text into each **Session titles** field. Daily titles are limited to 160 characters, so put preparation details in the notes rather than squeezing them into the title.

## Give the proposal reviewer a compact teaching brief

**Before:** “Great topic, lots of demand. Please approve quickly.”

**After:** “For project leads who write weekly updates. Learners will draft a brief from a sample document and check its claims. I propose two two-hour sessions with time for practice and questions. Please confirm whether the required tool access is included or must be arranged by learners.”

```text
Audience: [role and starting knowledge].
Practice output: [what learners will make or test].
Preparation: [accounts, tool access, sample materials].
Schedule: [dates], [start time] IST; [days] days, [hours] hours per day.
Seats: [number], supported by [how you will handle practice and questions].
Daily plan: [short sequence matching the session titles].
Exceptions or decisions needed: [irregular dates, tool access, staffing, or other question].
```

1. Put this in **Notes for the team**, keeping within 4,000 characters.
2. Replace assumptions with explicit questions. If the days are not consecutive, list every intended date.
3. Compare the notes with the date, hours, seats, and title fields before submitting.

Specific notes help the team assess the proposal. They do not guarantee faster review, a particular price, or approval. Follow [Create your first run](/help/articles/plan-and-submit-first-run) for the workflow.

## Explain a resubmission without hiding the decision needed

**Before:** “Updated as requested.”

**After:** “Reduced seats from 50 to 25 and added practice time to day 2. The first session remains [date] at [time] IST. Please confirm the proposed tool setup.”

```text
Changed: [field and old value] to [new value], because [reason].
Still to confirm: [one unresolved decision, or none].
```

Update the actual form fields, then use **What changed?** for this thread message and select **Resubmit for review**. See [Review and resubmit a run proposal](/help/articles/review-run-proposal).