Project Details Guide

The project detail page is the day-to-day control centre for a single project. Everything you need to manage, update, and report on a project lives here, organised into tabs.

Project detail page showing tabs for overview, plan, budget, documents, and settings

This article refers to a live TurfWise screen. Media is omitted here so the written steps stay current across releases.

---

What this page does

When you open a project from the Projects list, you land on the project detail page. At the top, you'll see health cards showing budget status, progress, timeline, and total budget. Below that, five main tabs organise everything:

• Overview -- current status, updates, and issues
• Plan -- timeline, tasks, phases, and milestones
• Budget -- BOQ, costs, resources, and forecast
• Documents -- files, photos, and approvals
• Settings -- project details and archive/restore controls

Each tab has section buttons inside it for more specific work.

---

When would you use this?

• You're checking the current health of a specific project
• You need to log an update or issue
• You're managing tasks and timeline for the current week
• You need to review or update the budget and forecast
• You want to upload evidence or documents
• You need to archive or restore a completed project

---

How to work through a project (first time)

If you're new to a project, follow this sequence:

---

What each tab is for

Overview

This is where you check status and communicate changes.

• Summary -- budget status, progress, and timeline health. If something looks wrong here, drill into the relevant tab to fix the source data.
• Updates -- add short notes about what was completed, what changed, and what's next. Good updates include specifics, not just "progress made".
• Issues -- log blockers as soon as they appear. Keep issue status current. If an issue affects dates or costs, immediately check the Plan and Budget tabs.

Plan

This is where you manage the work sequence.

• Gantt / Timeline -- see delivery dates, dependencies, and knock-on effects. See Project Gantt and Timeline for detailed guidance.
• Tasks -- day-to-day task list and completion tracking. Link tasks to the current plan, not old assumptions.
• Phases -- group work into delivery stages for clearer reporting. Update phase status when moving between stages.
• Milestones -- critical checkpoints like start/finish gates, approvals, or handovers. Mark milestones as soon as they're completed.

Budget

This is where you keep scope, cost, and resources aligned.

• BOQ -- the scope definition. If scope changes, update BOQ first, then check costs and forecast. See Project BOQ Guide.
• Costs -- actual and committed spending. Keep this current so "remaining budget" is meaningful.
• Resources -- labour and machinery utilisation. Adjust allocation early when workload shifts.
• Forecast / Budget Gap -- whether you're trending over or under budget. Add corrective actions when the gap starts to drift.

Documents

This is your project evidence folder.

• Files -- formal documents like method statements, contractor docs, and drawings.
• Photos -- progress and condition photos. Use meaningful file names so you can find them later.
• Approvals -- sign-offs and decision evidence. Missing approvals are a common source of late-stage friction.

Settings

Use carefully -- changes here affect archive/restore behaviour.

• Details -- update project metadata. Use archive when a project is finished. Restore if work reopens.

---

What to do when things change

When dates move in the Plan tab:

1. Check what tasks depend on the moved dates
2. Update affected tasks and phases
3. Add an update note in Overview explaining why
4. Check Budget > Forecast to see if the cost profile changed

When scope changes in Budget > BOQ:

1. Update the BOQ lines first
2. Check Budget > Costs for alignment
3. Check Budget > Forecast for impact
4. Log an issue or update note if the change is significant

---

When should I archive a project?

Archive a project only when:

1. Delivery is fully complete (or officially stopped)
2. All financial and admin closeout is handled
3. Required evidence is already uploaded to Documents

Archiving hides the project from active screens but keeps all the history. You can restore it later if work reopens.

---

Common problems and fixes

• Health cards don't match reality -- health cards pull from the data in Plan and Budget. If the source data is wrong, fix it there and the cards will update.
• Updates are empty -- nobody has been logging updates. Start adding a short note after every significant site activity or decision.
• Budget gap is growing -- check whether BOQ was recently changed, new costs were entered without updating resources, or schedule changes shifted the spend profile.
• Documents tab is empty -- evidence needs to be uploaded proactively. TurfWise doesn't pull documents from external systems.
• Can't find the Archive button -- it's under Settings > Details on the project detail page.

---

Good habits that prevent issues later

• Check the project health cards at the start of every review, not just when you sense a problem
• Log updates weekly. A project with no updates for three weeks looks abandoned.
• Upload evidence in the same week it's produced. Waiting until project end means missing files.
• When you change the plan, always check the budget impact. They're connected.
• Keep all project communication in Overview > Updates, not in emails or external notes.

---

Where to find it

Open a project from Projects > Projects Overview (direct link: /projects), then click on the project you want to manage.

---

Related articles

• Project Gantt and Timeline
• Project BOQ Guide
• Finance and Budgets