How to implement Laravel-Auditing to bulk CRUD operations and multiple model operations

[jericho-yu-llanes]

Hi everyone 👋

I'm currently working on a Laravel project where I use the laravel-auditing package to log changes to models. It's working great for single record operations like create, update, and delete.

However, I’m now facing a challenge on how to best implement auditing when performing:

1. Bulk operations – for example, updating or deleting multiple records at once using Eloquent's update() or destroy() on a query builder.
2. Multiple model operations in a single request – e.g., updating a User, creating related Profile, and deleting some Permissions all within one action.

---

Questions:

• What is the recommended or best practice to log audit data for bulk operations where no individual model events are fired?
• For multi-model operations, how do you track and group them together in a meaningful way?
• Would using a custom Batch ID or Audit Tag be a good approach to logically group audit logs from the same action? If yes, how can this be implemented properly?
• Is there any plan or existing feature in the package to natively support bulk/multi-model auditing scenarios?

---

Context:

• Laravel version: 11.x
• PHP version: 8.2
• Laravel-Auditing version: latest (13.x)
• Use case: Admin dashboard with features like bulk crud and multi-model form submissions.

Any advice, examples, or implementation patterns would be greatly appreciated 🙏

Thanks in advance!

[willpower232]

This package relies on model events, you would have to write something incredibly complicated in order to match it without using the model events so I would say definitely easier to use chunkById to apply your changes directly to the models (and so have the events fired).

I don't think there is a grouping in the package currently but presumably there is nothing stopping you adding a column and perhaps using laravel context or a session value to group changes per request with a small change to the trait.

Mostly I tend to group things by time, url, or user to pin the blame on a certain process.

[jericho-yu-llanes]

Thanks so much for the detailed response!

Yes I tried a several approaches like using services/events to manually grouped the audit log records and it's so complicated but using chunkById() and looping through models to trigger events makes a lot of sense, I’ll definitely try to explore and follow that approach for bulk operations.

As for grouping, I like the idea of tagging by time/user/url, and adding a batch_id column sounds promising too. I’ll explore using Laravel’s Context::add() or session-based tags inside the getAuditTags() method to dynamically attach a shared value per request.

Again, thank you! your insights are a big help! 🙏