Output and template engineering

Specify a finished artifact so an assistant creates usable work, not just an unstructured answer.

Describe the artifact, not just the topic

“Write about the quarterly results” leaves many choices open. A usable request specifies the intended audience, structure, length, format, evidence, and quality checks. The video calls this template engineering: show the assistant what a finished result should look like and what makes it acceptable.

For a report, provide a reviewed example or blank template and specify:

  • required sections and their order;
  • acceptable sources and how claims should be supported;
  • units, date ranges, and naming conventions;
  • what to do when inputs are missing or conflict;
  • what format to return and what should not be changed.

You can ask for a file in a specific format, but verify that the assistant can produce it correctly. Sometimes the safest handoff is structured text or a draft file that a person imports into the final application. Do not treat visual polish as proof that the figures or claims are correct.

Define acceptance criteria

Use a short checklist alongside the example: “all totals reconcile to the source; every recommendation names its evidence; no customer identifiers appear; headings match the template.” A sample helps communicate style, while criteria help catch errors that a sample alone cannot prevent.

Exercise: Pick a deliverable you create regularly. Add a one-page template and three objective acceptance checks to its task brief. Include what the assistant should do if a required field is missing.

Sources: Supplied video transcript