Skip to main content
A reliable OPUS planning makes the project’s most important timing easy to understand. Its quality comes from selecting meaningful items, using dates you can explain, and updating the overview as project information changes. The practices below are recommendations for maintaining that overview, not additional required fields or automatic features.

Select items that matter to project oversight

Before adding an item, ask:
  • Would its timing change how someone understands or oversees the project?
  • Does it describe a meaningful period of work or an important event?
  • Would omitting it hide a significant transition, overlap, decision, or delivery?
  • Can it be maintained reliably at the chosen level of detail?
Use those answers to decide whether the item belongs in OPUS, should be combined with a broader activity, or should remain in the detailed operational schedule. There is no recommended universal item count. The aim is a selective overview, not thousands of execution tasks.

Use a consistent level of detail

An overview becomes hard to read when major project periods sit beside minor daily tasks without a clear reason. For example: These are examples of selection, not rules that every project must follow. Keep separate items when combining them would hide a significant timing difference.

Name activities and milestones clearly

Use an activity name that describes a period of work, such as Develop the detailed design. Use a milestone name that describes an event, such as Detailed design approved. Include enough scope to distinguish similar items: Install windows, east wing is more useful than Windows. Avoid duplicate names when the items represent different work. Keep the item’s identity when its dates change. Renaming or rescheduling the existing item retains its continuity; deleting and recreating it does not.

Prepare information from an existing schedule or file

Treat a source schedule as evidence to interpret before entering it. Copying every row usually defeats the purpose of the OPUS overview. Use this sequence:
  1. Identify the source. Establish which project, schedule version, and date the file represents.
  2. Select the scope. Decide which important periods and events belong in the overview.
  3. Distinguish item kinds. Separate activities, milestones, group headings, and explanatory notes.
  4. Clarify dates. Resolve missing years, ambiguous day/month formats, and differences between planned and actual dates.
  5. Review relationships. Identify meaningful predecessors without inferring a dependency from row order alone.
  6. Resolve duplicates. Compare proposed items with existing items before adding them.
  7. Check the resulting overview. Confirm that the selected information tells a coherent project story.
A useful preparation list includes each item’s name, kind, group, start and end or milestone date, predecessor, and unresolved questions. It is a preparation aid, not a prescribed OPUS import format. These steps do not imply automatic file import or support for a particular file format.

Ask for the missing information

When an item is unclear, resolve the ambiguity before treating its dates as reliable. Do not silently turn uncertainty into a precise commitment. OPUS does not have a dedicated confidence field in this Planning workflow; keep assumptions and their evidence available in the project’s supporting information.

Use groups to aid reading

Choose a grouping principle that helps people navigate the overview, such as major stages or project areas. Keep it consistent. Groups should make items easier to find, not imply ownership, contractual scope, or dependency that has not been established. Small plannings may not need groups at all.

Use dependencies deliberately

Link items when their relationship matters to understanding or changing the schedule. Confirm the direction: the successor refers to its predecessor. Avoid circular chains. Remember that an item stores one predecessor, so a link is a simplified relationship rather than a complete representation of every prerequisite. After adding or changing a dependency, check the dates. The link itself does not reschedule either item. Before cascading a move, consider whether every affected successor should shift by the same amount. A downstream event may have a fixed commitment that still needs separate consideration.

Replace defaults and review dates

Creation dates are convenience defaults. Replace them before considering the overview reliable. Check that each activity has a sensible starting and delivery date, each milestone has the intended event date, and overlaps or gaps are intentional. A Gantt helps reveal those relationships. It does not prove that the work is feasible, resources are available, or a contractual date can be met.

Keep changes understandable

Review the planning when important project information changes and as part of the team’s regular project review. For significant revisions:
  • Update the existing item’s current dates.
  • Explain the reason when the form offers a description.
  • Check affected predecessors and successors.
  • Review the whole timeline after a cascade.
  • Preserve history through a new change when recording a new decision.
Use restoration only when you intend to discard later history. See Date history.

Verify completion separately

Review items whose scheduled end has passed. Confirm completion when the item is finished. If the schedule no longer reflects the remaining work, correct its dates. Do not confirm an item simply to clear a prompt. Do not infer actual completion from a calendar label, and do not infer a percentage complete from elapsed time.

Keep the overview useful over time

Retain meaningful finished activities and milestones so the overview continues to explain the project’s sequence. Remove accidental or duplicate entries deliberately, checking their dependencies first. Before sharing an interpretation of the planning, check that:
  • The selected items still represent what matters to the project.
  • Names and groups are understandable.
  • Dates reflect current information rather than creation defaults.
  • Important uncertainties have been clarified or remain explicit in supporting information.
  • Calendar-past items have been checked for completion.
  • Dependencies and the results of recent moves still make sense.
A concise, maintained planning gives people a common temporal reference. That is the foundation for understanding what is happening now, what is coming next, and, as further OPUS features develop, how other project information relates to those periods.