> For the complete documentation index, see [llms.txt](https://techresources.gitbook.io/adobe-premiere-basics-windows-edition/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://techresources.gitbook.io/adobe-premiere-basics-windows-edition/importing-and-logging-clips/writing-a-script.md).

# Writing a script

After you’ve carefully logged your video, you’re ready to write the script. You need a script, or road map, for every video story you produce.

## Introduction

On a Word doc, write the anchor introduction first. This is a sentence or two that a news anchor would read to introduce your story on television OR that would appear on a Media Milwaukee web page to set up your story. Example: Hundreds of UW-Milwaukee students filled the Union ballroom for the spring career fair. Eduardo Lopez reports.

## Package script

Next, start creating your package script with the best sound bites and natural sound you have to work with. Place the transcribed sound bites and natural sound pops in a logical order on your Word doc. For TV news stories, sound bites are usually about 8-13 seconds long. For longer stories or documentaries, they can run longer.

After you’ve arranged all your best sound bites and natural sound on the Word doc, you’re ready to write narration – that’s the “voice over” you will record to tie the story together. Use narration 1) to add facts, info and detail about the story and 2) to transition from sound bite to sound bite.

Sometimes you’ll want to introduce an interviewee with a sentence. *Example: Alana Jones has been working retail jobs ever since high school.* Sometimes you can just use a graphic over the video to identify the interviewee. *Example: Alana Jones/Store Manager.* Remember, if you introduce an interviewee with a sentence or two, you need B-roll of that interviewee to “cover” your sentence of narration.

Avoid “echoes” in your narration. That means repeating the same words or phrases in the narration that are already in the sound bite. Read your narration out loud to be sure it sounds clear and conversational.

End your package with a sign-off: *For Media Milwaukee, I’m Eduardo Lopez.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://techresources.gitbook.io/adobe-premiere-basics-windows-edition/importing-and-logging-clips/writing-a-script.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.