There are two main structures the plan can be viewed by; Packages and WBS. The WBS assigned to a Task has no relation to the Package it may also be grouped in.


All users can create Packages to group their own tasks into.

Package Properties




Descriptive name given to the Package


Start date of the first Task within the Package


End date of the last Task within the Package


User that is accountable for the Package


Only the Owner can use the Package


All users can use the Package

Assigned to

User(s) that have been assigned to all Tasks inside the Package


Additional text notes that can be attached the Package


Thread of communications on the Package


Documents that have been uploaded and attached to the Package

Package Tag Colour

Package Tag colours are generated randomly

Locked and Public Packages

By default, any new Package will be created Locked to the Owner. Only the Owner of a Locked Package can add tasks into it. Packages can be switched to Public, allowing other users to collaborate and add their own tasks into another user’s Package.

Package Codes

Each Package is automatically assigned a unique code that follows this logic:

X-00N (X = First letter of Project name) (N = Number of Packages created)

Default Packages

When a brand new Project is created, three default public Packages will be generated:

Level 1 Structure - X-001

Level 2 Structure - X-002

Level 2 Electrical - X-003

Deactivated and Deleted Packages

Deactivated Packages will no longer be available to add tasks into. However, deactivated Packages will still group all tasks assigned to it before it was deactivated.

If a deactivated Package is permanently deleted, any remaining tasks will be automatically ejected from the Package and placed into the ‘Without Package’ group.


The WBS can be used to group all tasks under a single, controlled structure. Only an Admin can create or edit the WBS.

The WBS can be created manually inside Aphex, imported from CSV, or from connecting to the Master Schedule.

WBS Codes

Each WBS much have a unique code. Changes cannot be saved if a duplicate code is detected.

When indenting / outdenting the exisiting WBS, the newly updated code(s) will be created in the next available position in the branch.

The colours for each WBS are randomly generated.

Default WBS

When a brand new Project is created, three default WBS will be generated:

1 - Construction

1.1 - Level 1

1.2 - Level 2

Deleted WBS

Deleted WBS are automatically removed from the WBS structure and the Gantt. Any tasks that were grouped in a deleted WBS will be ejected from the WBS and placed into the 'No WBS Assigned' group.

Opting to delete the entire WBS branch will delete the selected code, and all WBS nested underneath.

Did this answer your question?