Follow-ups

Follow ups records issues raised from project and meeting work. Each issue belongs to a project and can identify the person who raised it, an owner, severity and reported date. Its status can progress from Open through Triaged and in progress to Fixed, Verified and Closed. The configured triage workflow acts when an existing issue is raised as Open. It requires severity, moves the issue to Triaged and writes an operation receipt.

• Set the context. Start from the project and use its named team members to make the owner of each record clear.
• Keep the handoff visible. Move the work through the existing status values and record who took the next step.
• Review exceptions. Open the relevant saved list when a date slips, an approval waits or a follow-up needs verification.

Agree who reviews triage results, how severity is chosen and who verifies a fix. A triaged issue still needs an owner and a next action. Use the reporter note to preserve the original observation and keep the project link stable when work passes between team members. Discuss whether a related risk needs its own Risks record; a risk and a follow-up are separate records with different review questions.

Map the project’s real operating language to the record names before importing history. Have the Project Manager and Delivery Lead rehearse the same case with ordinary team accounts. If a role sees too much or cannot complete its assigned step, correct access before the first live cycle. Preserve the project reference and the person responsible when records are moved or corrected.

After a meeting exposes a recurring delivery issue, a team member raises a follow-up on the project, selects High severity and adds a reporter note. The triage workflow changes Open to Triaged and records a succeeded receipt. The Delivery Lead assigns an owner, who works the issue through in progress and Fixed. Follow-ups Awaiting Verification shows it for the lead to inspect before marking Verified and Closed. Rehearse a second issue with no severity: the triage attempt fails and a failed receipt explains the outcome.

Open the source record again after the handoff. Compare its status, owner, project and dates with the list used by the receiving person. The team should be able to explain the next action from the record itself, including a blocked or failed attempt. Rehearse the correction path with the same roles who will use it in ordinary work.

• Open Follow-ups — New project issues with severity and a responsible owner.
• Follow-ups Awaiting Verification — Fixed issues awaiting an explicit verification decision.

See the related process and review the data model.