> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a project pipeline

> Create a delivery board and an active-project table from the same records.

Give your team two useful perspectives: a board for seeing project stages and
a table for scanning upcoming commitments. Both views use the same Projects records.

**Before you start:** you need a Projects object, a choice attribute for its
delivery status, a few project records, and access to create views. Add a date
attribute if you want to sort by deadline.

<Steps>
  <Step title="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.

    | Example stage | Meaning                                                 |
    | ------------- | ------------------------------------------------------- |
    | Planned       | Scope is being prepared; delivery has not started.      |
    | In progress   | Someone is actively working on the agreed deliverables. |
    | In review     | Work is ready for a named reviewer.                     |
    | Complete      | The agreed outcome has been accepted.                   |

    These are example values. If you need to change the schema, use
    [Design useful attributes](/documentation/data/attributes) first.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Check the result

The board answers **“Where is each project in delivery?”** and the table answers
**“Which active commitments need attention?”** Keep a broader view available for
finding completed, paused, or undated work excluded by your filters.

If a project seems missing, check its status and the view's filters before
creating another record. See [Create focused views](/documentation/data/views)
for more detail.


## Related topics

- [Build an automation](/documentation/build-an-automation.md)
- [CLI configuration and CI](/documentation/cli-configuration.md)
- [How your data fits together](/documentation/data/how-data-connects.md)
- [Create focused views](/documentation/data/views.md)
- [Prepare for a client meeting](/recipes/prepare-client-meeting.md)