Executive Follow-up & Decision System
A structured follow-up system for turning scattered actions, dependencies and decisions into clear ownership, attention and next steps.
- Type
- Independent professional work
- Role
- Follow-up structure · decision control · management information
- Tools
- Excel
- Microsoft 365
Used for action tracking · ownership · due dates · decision logging · structured follow-up
- Evidence
- Synthetic operational model based on independent professional work patterns.
Context
Actions, dependencies and decisions can become difficult to manage when they are tracked across messages, documents and separate lists. The challenge is not only knowing the status, but knowing what requires intervention and what must happen next.
My responsibility
I structured the follow-up model around clear ownership, due dates, dependencies, decision references and next actions so open work could be reviewed consistently.
Control model
- Action
- Owner
- Due date
- Dependency
- Decision
- Next action
The model separates execution state from intervention priority.
Status is not attention
Status shows where the work is.Attention shows what needs intervention.
- Blocked
- may need dependency follow-up
- Waiting Decision
- may need decision escalation
- In Progress
- may still need attention if overdue
Follow-up register
- Case model grain
- One synthetic record per action item.
- Trace key
- Action ID
| Action ID | Action | Owner | Due Date | Status | Dependency | Decision Ref | Next Action | Last Update | Attention |
|---|---|---|---|---|---|---|---|---|---|
| A-001 | Prepare weekly summary | Operations | Done | None | None | None | Closed | ||
| A-002 | Confirm missing input | Operations | Blocked | External input | None | Follow up on dependency | Overdue | ||
| A-003 | Update action register | Coordinator | In Progress | None | None | Complete remaining items | On Track | ||
| A-004 | Approve reporting format | Manager | Waiting Decision | None | D-002 | Confirm decision | Decision Required | ||
| A-005 | Review document index | Coordinator | Not Started | None | None | Start review | Due Soon | ||
| A-006 | Close completed follow-up | Operations | Done | None | D-001 | None | Closed | ||
| A-007 | Confirm handoff owner | Operations | Blocked | Owner confirmation | None | Confirm responsible owner | Needs Attention | ||
| A-008 | Prepare next review list | Coordinator | In Progress | None | None | Update review items | On Track | ||
| A-009 | Resolve incomplete follow-up | Operations | In Progress | None | None | Verify outstanding item | Overdue | ||
| A-010 | Confirm approval route | Manager | Waiting Decision | None | D-004 | Confirm approval route | Decision Required | ||
| A-011 | Archive completed record | Coordinator | Done | None | D-005 | None | Closed | ||
| A-012 | Prepare next action summary | Operations | Not Started | None | None | Prepare summary | Due Soon |
Control rules
- Every open item has an owner.
- Every open item has a due date.
- Every blocked item identifies its dependency.
- Every waiting-decision item references the required decision.
- Every open item has a next action.
- Completed items leave the active view but remain traceable.
Attention logic
| Order | Condition | Attention |
|---|---|---|
| 1 | Status = Done | Closed |
| 2 | Due date passed and item is open | Overdue |
| 3 | Status = Waiting Decision | Decision Required |
| 4 | Status = Blocked | Needs Attention |
| 5 | Not started and due date approaching | Due Soon |
| 6 | Otherwise | On Track |
Attention is a review aid; it does not replace professional judgement.
What needs attention now
| Action ID | Attention | Next Action |
|---|---|---|
| A-002 | Overdue | Follow up on dependency |
| A-009 | Overdue | Verify outstanding item |
| A-004 | Decision Required | Confirm decision |
| A-010 | Decision Required | Confirm approval route |
| A-007 | Needs Attention | Confirm responsible owner |
Decision log
Excerpt: three decision records and the actions that reference them.
| Decision Ref | Decision | Owner | Date | Linked action |
|---|---|---|---|---|
| D-001 | Close completed follow-up item | Manager | A-006 | |
| D-002 | Approve reporting format | Manager | Pending | A-004 |
| D-004 | Confirm approval route | Manager | Pending | A-010 |
Management summary
Synthetic model- Total items
- 12
- Open
- 9
- Closed
- 3
- Blocked
- 2
- Waiting decision
- 2
- Overdue
- 2
Derived from the 12 synthetic records shown in this case model.
Why separate Status from Attention?
Two items can share the same workflow status but require different intervention. Separating the two fields prevents status from carrying more meaning than it should.
| Action ID | Status | Attention |
|---|---|---|
| A-003 | In Progress | On Track |
| A-009 | In Progress | Overdue |
Capabilities demonstrated
- Ownership control
- Dependency tracking
- Decision traceability
- Attention-based follow-up
Analytical boundaries
- Attention logic is a case-model rule, not a production system.
- Due dates and statuses are synthetic and used only to demonstrate control logic.
- A decision flag identifies the need for review; it does not make the decision automatically.
Evidence boundary
This case uses synthetic actions, owners, dates, statuses and decision references to demonstrate an independent professional follow-up model. No employer, client, customer or confidential operational data is shown.