# Action item tracker

**Project:** ______________________  
**Owner of this list:** ______________________  
**Reviewed at:** ______________________  
**Last updated:** ______________________  

## Action items

| # | Action | Source | Owner | Due | What done looks like | Status | Latest update |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 14 | Confirm delivery window for AHU-2 (SAMPLE · delete this row) | OAC 12.5 | Mechanical PM |   | Agreed date, time and access instructions sent to super | In progress | Supplier proposing two dates |
| 15 | Send revised door hardware schedule to architect | Submittal 08 71 00-2 | Doors & hardware |   | Resubmittal logged and routed | Initiated |   |
| 16 | Walk L3 ceiling with fire protection before close-in | Coordination meeting | GC super |   | Walk done; issues logged as observations | Closed | Two items logged |
|   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |

## How to use it

1. Write each action as a verb and an object: “Confirm delivery window for AHU-2”, not “AHU-2”.
2. One owner per action. If two people have a part, split it.
3. Say what done looks like, so whoever reviews it knows what to check.
4. Note where it came from (meeting item, RFI, coordination issue) so the context is one lookup away.
5. Review the open list at the same meeting every week, and have owners update their latest-update column before it.

Template by os.construction: https://os.construction/resources/templates/action-item-tracker. Sample rows are illustrative; your contract and specifications govern.