Reviewed and updated: 21 July 2026.
An issue is a problem that already exists and needs resolution. Meeting transcripts often blur issues with future risks, general complaints and possible improvements. A controlled issue log preserves status, impact and ownership.
Search for issue language
- “This is currently blocking…”
- “The system has failed…”
- “We cannot proceed because…”
- “The deadline has been missed…”
- “The customer has raised…”
Create one issue record per problem
| Field | Required content |
|---|---|
| Issue | Present-tense problem statement |
| Evidence | Source, timestamp or system reference |
| Impact | What is affected now |
| Owner | One accountable person |
| Next action | Immediate resolution step |
| Target | Review or resolution date |
| Status | Open, controlled, resolved or closed |
Do not convert risks into issues
“The supplier may be late” is a risk. “The supplier missed today’s delivery” is an issue. Keep both registers linked where appropriate.
Verify resolution
A meeting statement that an issue is “sorted” is not enough. Record evidence, acceptance criteria and the person authorised to close it.
How NERALVO Halo fits
NERALVO Halo can preserve discussion and timestamps while DOWAY supports extraction. The project or operational issue log remains the authoritative record.
The final issue log should contain active problems that require management—not every negative sentence spoken in the meeting.
Ready to capture meetings properly?
View the NERALVO Halo AI voice recorder with 64GB local storage, meeting capture, compatible phone-call recording workflows and one year of DOWAY Max included.
View NERALVO Halo