Schedule Activity List and Attributes

Maintain one coordinated list of project activities and their planning attributes.

This Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.

Prepare project brief

The form prepares a separate brief; it does not fill the Word or Excel file.

Read product descriptions in your language. The Word and Excel template files are in English.

Schedule Activity List and Attributes · Document preview — Selected page preview · XLSX

Learning

How to use this template

When you need it

Use this register when schedule activities need consistent definition before or alongside programme development, particularly where outputs, logic, calendars, resources, constraints, and ownership must be checked across several work packages.

What it helps you decide

It exposes the planning assumptions behind activity names and dates, helping planners build credible relationships and identify missing outputs or unsupported constraints before an attractive programme graphic conceals weak underlying logic.

How to complete it

Assign Activity ID and WBS / package, then define Activity / output so completion represents an identifiable result rather than an unclear general effort.
Record Predecessor / logic and Successor / logic with Calendar / unit and Resource / quantity using actual sequencing needs and credible production assumptions.
Document Constraint / source, Owner, and Status / revision, challenging unsupported restrictions and reconciling the register with the current controlled programme information used by the team.

Who prepares and reviews it

A planner normally maintains the register with engineering, procurement, construction, and package owners. Delivery leads verify realistic outputs and dependencies, while the project planning authority controls revisions and interfaces with the accepted programme process.

A mistake to avoid

Using fixed dates to compensate for missing predecessor logic can hide true dependencies and prevent the programme from showing the consequences of delayed inputs.

Illustrative example

Illustrative example: a pumping-station planner defines cable termination as an activity. The register identifies cable installation and panel readiness as predecessors, records the working calendar and crew basis, and names the responsible package lead. A missing panel-delivery dependency is corrected before the integrated programme is reviewed.

Explore the wider topic

Document contents

Activity ID
WBS / package
Activity / output
Predecessor / logic
Successor / logic
Calendar / unit
Resource / quantity
Constraint / source
Owner
Status / revision

Required inputs

Project name, location, company, document number and revision
Actual project scope, source records and responsible roles

Practical tools.
Professional judgment.

Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.