1
Agree on what each stage means
Review the existing status attribute before creating another one. Use your
team’s labels and define a clear reason to enter each stage.
These are example values. If you need to change the schema, use
Design useful attributes first.
2
Check the source records
Open a broad Projects view and review several records. Set each status to
the actual stage and add known target dates. Keep dates empty when no
commitment exists.Decide how your team represents paused projects. For example, Relio’s
supplied record is On Hold; creating a board should not change that
project to In progress.
3
Create the delivery board
Open the view selector and choose Create new view. Select Kanban,
name it Delivery board, and choose the project status attribute for
grouping. A grouping attribute is required before you can confirm the view.Select Confirm and check that known projects appear in the expected
columns. Inspect records with no status instead of assuming they are complete.
4
Create an active-project table
Create another view, choose Table, name it Active projects, and
select Confirm. Show the name, status, date, and client fields your
team needs for review.Add a filter for the statuses that mean active work in your process.
Sort by the relevant date. If you use several filter conditions, check
whether they require all or any conditions to match.
5
Test both perspectives
Choose one known active project and one known completed project. Confirm
that the active table includes the first and excludes the second.
Open the broader board to find both.During a real stage change, update the project’s status and confirm the
change appears in both views. Views do not create independent copies of records.