Meetings are an interesting one. I’ve made a note on the whiteboard to specifically review the ‘small business’ system with this in mind.
I think there are a couple of ways you could look at ‘meetings’ as a thing. Which you prefer is situational and maybe just a matter of taste.
They are subordinate to some other item
In this situation the meeting isn’t the thing you’d track. The thing it’s about is the item in your system – it’s the thing that has an ID.
Then meetings are just one of the things you store in relation to this item. You might like to tag them in your notes so you can bring them all together, but this pattern looks like this.
Area 10-19
├── Category 11
│ ├── ID 11.11
│ │ ├── Artefact A
│ │ ├── Meeting minutes <<<
│ │ └── Artefact Z
│ └── ID 11.12
│ ├── Artefact A
│ ├── Meeting minutes <<<
│ └── Artefact Z
└── Category 12
└── ID 12.11
├── Artefact A
├── Meeting minutes <<<
└── Artefact Z
Area 20-29
└── Category 21
└── ID 21.11
├── Artefact A
├── Meeting minutes <<<
└── Artefact Z
They are their own thing
I’ve done this in the past – I even remember the category, it was:
10-19 Administration
└── 12 Meetings
└── ...
I feel this works better for the sort of high-level review meeting that might not be about one specific thing. The weekly project review, say. In this case, that gets an ID, 12.11 …, and you sort by date within there.
Though, I’d have an ID for that in the PMP system and my feeling sitting here today is that the weekly project review meeting should follow the first pattern and just be a child of an ID in that structure.
Some other pattern?
There’s probably a third way.
I’ve pinged @Alex by text, he might have a view on this.