These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Meeting Management
- Features
- Decisions and evidence
Decisions and evidence
Recorded review for project meetings and delivery work.
OverviewRecorded Decisions×
Meeting Management · Decisions and evidence
New
Recorded Decisions
Decisions
| Decision number | Subject type | Subject reference | Reviewer | Decided at | Decision | |
|---|---|---|---|---|---|---|
| DCS-62528 | Project | Project dcs-299 | 19 Oct | Approved | ||
| DCS-52516 | Work Package | Work Package dcs-722 | 04 Oct | Approved | ||
| DCS-58524 | Task | Task dcs-638 | 16 Oct | Approved | ||
| DCS-94032 | Milestone | Milestone dcs-793 | 06 Oct | Approved | ||
| DCS-93116 | Deliverable | Deliverable dcs-250 | 24 Oct | Approved |
6 of 6 records
Project dcs-299Decisions · DCS-62528
ProjectDecided at19 Oct
DecisionApproved
What you can do
Recorded review
Decisions keeps reviewed outcomes with a subject type, subject reference, reviewer, date and Approved, Rejected or Returned decision. Operation receipts records that an operation was attempted, when it occurred and whether it Succeeded, Failed or remains Pending. Attendance approval writes both a review decision and an operation receipt; follow-up triage writes a receipt. These records help a delivery lead reconstruct an action taken during project work.
How the work is organized
- 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.
What to agree during setup
Agree how subject references match the source records and which person reviews each kind of decision. Keep the reviewer and the operation actor accurate. Decide when attachments belong on a supported parent record and retain the source file URL when using record attachments. A receipt indicates the result of an operation; it should not be used as a substitute for the underlying attendance or follow-up state.
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.
Check the handoff on an actual case
Approve a positive submitted attendance entry and inspect the corresponding decision and receipt. Check the decision subject reference and reviewer against the source entry; confirm that the receipt reports Succeeded. Then try the same approval after the entry has moved out of Submitted. The guard rejects it, and the failed receipt should remain visible without another approved attendance result. For a raised follow-up, inspect the triage receipt and compare it with the issue’s current status before reporting progress.
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.
What your team sees
- Recorded Decisions — Approved outcomes with subject, reviewer and decision date.
- Attendance Awaiting Approval — Submitted entries whose review will create a decision and receipt.
Follow the work through
What it keeps track of
Data model- Decisions
- Decisions recorded against a meeting or project subject, with the reviewer, the outcome and the date.
- Operation receipts
- Evidence that a delivery operation was executed.
- Record attachments
- Files attached to delivery records.
- Projects
- Engagements delivered for an organization, with budget and schedule.
- Team members
- Delivery staff with role, practice and weekly capacity.
Who uses it
Permissions- Project Manager
- Owns the project handoff; Meeting Organizer prepares the discussion; Team Member updates assigned work; Attendance Approver reviews approval outcomes; Delivery Lead reviews exceptions.
Set up Meeting Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.