> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opus-world.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare a Planning request

> Turn a schedule file or a short project brief into a reliable selection of activities and milestones.

A good Planning request tells the reader what matters to someone overseeing the project. You can start from an existing schedule, a file listing proposed items, or a description of the work. Identify the project and the date or revision of your source.

## What to supply

For each proposed item, give the work or event a recognizable name. Supply a start and end date for an activity, or one date for a milestone. Explain any dependency that matters to the overview. If a date is provisional or two sources disagree, identify the uncertainty so it can be clarified before the schedule is changed.

For a revision, identify the existing item and specify what changed. Include the reason for a date change when known. A revised end date and confirmation that work has finished are different statements.

## Example request

> Use the October design schedule to prepare the project overview. Show detailed design from 2 to 20 November and the client review on 24 November. Group both under Design. The supplier programme lists each drawing separately. Keep one design activity. The review date is provisional, so check it with me before recording it.

In this example **Detailed design** is an activity and **Client review** is a milestone. The outstanding question concerns the review date. There is enough information to identify the design period without guessing when the review will take place.

See [Planning definitions](https://docs.opus-world.com/definitions.md) and [Planning best practices](https://docs.opus-world.com/planning-best-practices.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.