BHG Infra
Project tabs

Management tab

Running the project. Derived health and progress, outstanding items, budget and burn, team, RAID, data check, intake usage, history and restore, and the review setting.

The Management tab is for the project lead. It shows how the project is running and holds the controls that change how it runs. Infra is the authority on every permission: you see only the controls you can use.

Health

Health is computed from the plan, hours and dates by the kind's playbook ("computed from the plan, hours and dates, by the Implementation playbook"). It has an overall colour and three parts: Schedule, Budget and Scope. A line under each tile says what it reads. Nobody sets health by hand.

Progress and status are derived too:

  • Progress is the share of milestones complete. Proposed and cancelled milestones do not count.
  • Status follows the milestones: Planning until one is complete, Completed when all are.

The project's start and end dates are shown here. A lead's change to them applies at once, is logged, and can be reverted.

See Project kinds for what each part reads on each kind.

Outstanding items

Outstanding items shows counts only. The list and its actions are on Items.

Budget and burn

Budget and burn charts hours logged over time against planned hours, with one "used" line per person. The note reads, for example, "120h of 195h planned". On a Managed service, hours are read against the purchased hour block.

Team

The Team section is the BHG roster: who is on the project, the project lead, and planned hours. The lead or a manager adds, updates and removes people here.

RAID

RAID tracks risks, issues, assumptions, dependencies and constraints "in one log the client can see". It shows the open count. Click a row to open it in the item pane, where the lead can confirm it. Adding or changing a row goes through Stage a change: a lead's change applies at once.

Data check

Data check finds problems in the project's data and groups them by type: Duplicates, Orphans, Stale, Conflicting values, Evidence contradicted and Links to retired items. It runs weekly on its own, and the lead or an admin can click Run data check.

It only stages. Changes it proposes wait on Events (under Needs a look), and tasks it creates wait on Items. The section shows what the last check found by type, what it staged, and the trend across checks. It stages at most 30 fixes per run; the next check stages the rest.

Intake usage

Intake usage (lead or admin only) shows how Sync's and the agent's suggestions were answered over the last 8 weeks: the approve, edit and dismiss rates for each change type, most dismissed first, and the reads and tokens per week. Use it to see which kinds of suggestion are noisy.

History and restore

History and restore is the audit trail: every applied plan change and every task edit, newest first, with who, when, how (by hand, Sync, the agent or a key), the source and quote, and before and after.

  • Filter by person (Anyone), item type (All items) and source (Any source or No source).
  • Open one item's full history, including suggestions that were rejected or dismissed.
  • The lead can Revert one change, or Restore to here to undo everything after a point. Both show a preview first and stop at a conflict.

Task edits are made directly and logged. They read "edited directly" and cannot be reverted from here.

Review setting

The Review setting decides who applies a team member's own hand edits:

  • Lead reviews: a team member's own edits wait for the lead on Events.
  • Team writes directly: a team member's own edits apply at once and are logged.

"Sync, the project agent and API keys always wait for review." Only the lead or an admin can change this. See Changes and review.

On this page