Guide: Using custom fields for client budget and scope tracking

Hey folks! 👋 I've been seeing a lot of questions pop up about managing client projects in Runway, especially when it comes to keeping budgets and scope changes from spiraling. I wanted to share a workflow I've settled on that's been a lifesaver: leveraging **custom fields** to create a real-time dashboard for each project.

It's surprisingly simple to set up. The trick is to create a few key custom fields on your Project type and then use them in your views. Here's my go-to configuration:

```yaml
# Example custom fields for a 'Client Project'
- Field: Initial Budget
Type: Currency
Scope: Per Project
Required: Yes

- Field: Approved Scope (Document Link)
Type: URL
Scope: Per Project

- Field: Change Request Log (Document Link)
Type: URL
Scope: Per Project

- Field: Current Forecast
Type: Currency
Scope: Per Project
Formula: SUM(Linked Tasks.Cost)
```

You can then create a dedicated "Project Health" table view that surfaces these fields alongside your task list. The real power comes from:
* **Linking tasks with cost estimates** to auto-calculate that `Current Forecast`.
* **Using the document links** to keep your SOW and change requests one click away, reducing "where's that file?" chatter.
* **Creating a "Budget Status" formula field** that compares `Initial Budget` to `Current Forecast` and returns a color-coded status (e.g., "On Track", "At Risk", "Over").

This setup has helped my team catch scope creep early because the numbers are always visible and updated automatically. It turns Runway from a basic task tracker into a lightweight project financial dashboard.

Has anyone else built out similar tracking? I'm curious if you've used different field types or formulas to track time vs. budget.