Every container BESS job runs the same official set of sales milestones. You do not retype them â you start the job from the company standard, then work each milestone on its own page.
Start the job from the standard
- Go to Projects and choose New from copy.
- Pick the company standard â it is offered first in the list.
- Give the job its real title and set the target completion date.
- Open the new project. The official milestones are already there, fresh: renumbered, Pending, with no dates and no links.
- Set each milestone's target date from the contracted programme.
Do the dates before work starts. They drive whether the project reads On track, At risk or Overdue, and they are what triggers the overdue nudge.
The standard itself is maintained by an administrator. If it looks wrong, say so â do not compensate by editing the milestones on a live job.
Work a milestone on its own page
Click a milestone's number on the project to open it. The project page is the overview; everything that changes a milestone happens on the milestone's page.
| To do this | Use |
|---|---|
| Mark work as begun | Start |
| Break the work down | Tasks â New task |
| Attach an existing task | Tasks â Link existing task |
| Keep client requirements and evidence | Documents â Create documents folder |
| Add or read files | Open in EDMS |
| Capture the client's signature on a deliverable | Sign-off |
| Record the acceptance test | Record FAT |
| Close it | Complete |
| Drop it from the project | Cancel milestone |
A linked task does not close the milestone
This is the one thing people get wrong. A task records the work. Closing a milestone is always deliberate: press Complete and give a reason, which is recorded on the timeline.
A failed acceptance test sends it back
Recording a FAT as FAIL moves the milestone to Blocked for re-work. It never closes the project. Raise the re-work as tasks on that milestone.
Finished milestones are closed to changes
Once a milestone is Complete or Cancelled you cannot edit it, add tasks to it, or give it a documents folder. If something has to change afterwards, that is a new milestone â not a rewrite of a closed one.
Documents and client requirements
The project gets one documents workspace in the EDMS, created the first time you ask for it, with a standard folder set: Client requirements, Sales, Design, Production, Acceptance.
- The project summary — what this job is, in plain words — is written on the project's own Overview tab, in the same editor tasks and documents use. It is deliberately NOT a controlled document: no type to pick, no doc code, no review, no approval and nothing to acknowledge.
- Anything that has to be controlled — a signed brief, client requirements, drawings, the acceptance record — is a real EDMS document in this workspace, with revisions, comments, review and sharing.
- Each milestone can have its own folder for the evidence that milestone is judged on.
- Files themselves are added in the EDMS, via Open in EDMS â that is where document control, permissions and retention live.
If you see a message saying you are not authorised to create a document type, you need the QMS_CREATE permission. Ask an administrator; it is a normal part of setting up a project manager.
Who can see the job
A project is not visible to the whole company. Four things put somebody on it: they run it, their department runs it, they were given access on the project's Access tab, or their role lets them see every project — and each of those carries a level, view or contribute. Only the PM grants access. The detail is in "Who can see a project, and who can change it".
Who hears about what
Each milestone has its own chat channel, and its updates post there. The project's own channel carries project-level events plus one line per milestone pointing at its channel, so the project thread stays a table of contents rather than a firehose.
Follow a milestone by clicking the star on its page. There is no separate Subscribe button â the star is the control, and it cycles through All, System-only, Muted and off.
The short version
- Start from the standard. Never retype the milestones.
- Set the target dates before work starts.
- Work each milestone on its own page.
- A task records work; Complete closes the milestone.
- Client requirements belong in the milestone's documents folder, not an inbox.
Process, roles and escalation: see the Container BESS Project SOP. This article covers how to use the screens.