There is a decent workaround for that already. You may setup several Action Buttons to fill many fields with a single click. For example, for Sprint Review you can add this button:
And when you click it it will fill two fields
You may ask your teammembers to add a meeting and then invoke relevant action to prefill it.
My vote is also for the Templates feature. People on my team are used to creating various templates for themselves in Notion.
We have this in plans for Q2
I came across the original use case for entity templates today, applying templates to meeting records, and wanted to share some observations and workarounds from my workspace.
The meeting use case is a great example of the need for dedicated templates because we typically want all meetings, regardless of type, stored in a single database. However, the meeting note template should vary based on the meeting type. To handle that, I’m experimenting with a workaround: creating a rich text field in a multi-select option that holds the appropriate template for each meeting type. I then use an automation or button to insert that template into the meeting notes. (This is similar to the reporting space solution where report types and prompts live in another database, I just prefer fewer databases)
This is a bit of a shift for me, as I’ve generally avoided using a “Meeting Type” select field. The Google Calendar integration doesn’t populate that field automatically, and I prefer to minimize manual input. I may explore using AI to help estimate and fill that field going forward.
The most common workaround is one I use where all entities in a database share the same structure — I use automations that apply a default template when an entity is created. I also include a backup button to reset and reapply the template. I’ve implemented this in my standups, wiki docs, and tasks databases.
