AI Managed Implementation Governance Office - Documentation
We can navigate Action Items from the Road Map. We go into our governance section, and here are our action items. We can click on a brand new one to kind of show you the type of information that will be on an action item. We're going to have our general information, the organization, the portfolio, the program, and the project. You put your action name, the type of action that it is, and the coordinator. If you don't need a coordinator and know who will own it, you can go right through to the action item owner and then the person who's going to sign off. So, if you don't know these two individuals, I would give it to the coordinator and have the coordinator figure it out. You want to put the associated deliverable. If there are any meeting minutes where this action item came from, you can put that in there and then the due date. And then you put a description of what that action item is in a historical comment.

| Object | Usage Notes | Visibility | Filter & Search Criteria |
|---|---|---|---|
| Organization | Any changes in the Organization record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Organization |
| Portfolio | Any changes in the Portfolio record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Portfolio |
| Program | Any changes in the Program record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Program |
| Project | Any changes in the Project record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Projects |
| Deliverable | Any changes in the Deliverable record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Deliverables |
| Work Package | Any changes in the Work Package record will be updated in this Action Item | The users Invited in the Organization record will have access to the particular Portfolio | Work Packages |
In AMIGO, to create an Action Item record, the higher level hierarchy must be created first. That means the user must create Organization, Portfolio, Program, Project, Deliverable, and Work Packages, associating each other like a hierarchy.
The highlights panel is a customizable table of up to four columns at the top of every record page. It helps users see key information at a glance. It can be customized by editing the compact layout in Lightning Experience. Likewise, on the Action Item record page, the highlight panel contains the object's (here it is the Action Item object) name and the particular object's record name on the left column and the action buttons on the right column. Below the compact layout is attached that contains two fields, current status and auto-approval days.

The current status field in the compact layout of the action item record page displays the stage of the record, in which currently it is present. It is a dynamic field, it updates the stage of the record as per it gets changed. The Action Item has different stages of Approval - Initialize, In Coordination, In Resolution, Resolved, and Completed. When the record is created, the current status sets to In Initialize by default, and after the approval actions, the record went through the stages of approval. To know more details about this approval process of action item please refer to the below section - Approvals.
Workflow is slightly different because when an action item is created, we may not know to who to assign that action item. But we should know who our coordinator is. Typically speaking, it's going to be the project manager whenever this action came up from. We can give this if we don't know exactly who is going to be resolving this. We could give it to this coordinator. It gives us some options where we may not know all the RACI Chart or the people who are going to be involved with this at the beginning. We allow this to go from initialized to an in-coordination status. If you know who the person is, you can go right into the result resolution status and assign it directly to the person who will be completing that action. Once they complete that action, it moves to a stage where the person created will review the action item closure and resolve it. If they like it, they close it. If they don't, they reject it. And it goes back to resolution status. So, this is how this approval workflow works. We have our coordinator, our owner, and a "sign-off" person already laid out here. So, when I wanted to go and send us for approval, it's already in coordination, as you can see. Go and take the next action. Put in some historical comments. By clicking on sending resolution, we can see the status is down in resolution. What's happened in the background is that the AI messenger has gone out and started sending these micro messages out to all the different individuals who are going to be impacted by this action item. And that concludes our demonstration of action items. The `Approvals` button is for serving the above purpose in AMIGO Action Item.
Using this Edit button, the record can be edited to do any kind of changes and modifications. After editing and making the required changes, the users must add some meaningful text in the historical comments section before saving the record, so that they can trace their changes later.
If the user wants to delete a record, they can use this delete button.

The Related Tab always contains some information that is related to the object record. This tab of Action Item contains - Notes & Attachments, Approval History, RACI Charts, and Historical Comments. Notes & Attachments contain the files/attachments that are related to the action item record. The files/attachments that are uploaded through the upload button are displayed here. Approval History contains the details of the approval process carried on to the record. It displays the details that when the record was sent for approval, sent by which user, and the status of the approval. The Historical Comments section contains all the historical comments added by the record owner and other users those who edited this record.
The Details Tab contains detailed information about the Action Item record in the form of fields each containing specific values. Refer to the image below.

</br>
The Sections of the Details Tab:</br>
Associated Deliverable - The Associated Deliverable field is a mandatory field in the action item page layout, while creating this record, this field needs to fill. If there is a deliverable associated with the project of this action item record, then only this associated deliverable field populates the value. In the Deliverable record page, there is a quick action present by which an Action Item record can be created. In that case, also the associated deliverable field gets added to the action item record. To learn more about this quick action feature, refer to [here](https://platinum-pmo-llc.github.io/amigo-wiki/Deliverables-(Detail-Page)#add-action).
Created by and Last Modified By - This section consists of two fields, Created by and Last Modified By. Created By displays the name of the Owner or who created the record along with the Creation Date & Time. The Last Modified Date displays the name of the User (can be any other user other than the owner) who did any kind of changes or modification in the record along with the modification Date and Time.
This section contains three columns/fields - Created Date, Created By, and the comment itself. Historical Comment is provided whenever a record is created and at the time of making any modifications by editing it. The best practice that should be followed by the users is to leave an appropriate comment every time they are making any kind of modifications in the record so that in the future the changes could be kept on track.
Action Items in AMIGO support the critical task management activities that fall outside formal project work packages. They provide a governed mechanism for tracking follow-up activities arising from meetings, governance reviews, and ad-hoc requests while maintaining full RACI accountability.
| Benefit | Description |
|---|---|
| Accountability | Clear ownership through coordinator, owner, and sign-off roles |
| Traceability | Link to meeting minutes, deliverables, and work packages |
| Visibility | AI Messenger notifications keep stakeholders informed |
| Governance | Approval workflow ensures proper oversight |