How to Scope a Filament Admin Panel

Filament makes admin panels fast to build, which makes them easy to over-scope. A practical method for defining resources, roles and reports before a line of code is written.

Filament is the reason a serious Laravel admin panel can now be a two-to-three week project instead of a two-month one. The risk is the opposite of the old one: because each resource is cheap, teams add thirty of them and end up with a panel nobody can navigate and nobody wants to maintain.

Scoping is the whole game. Here is how we do it.

Start from jobs, not tables

The wrong first question is "which models need CRUD?" The right one is "what does someone sitting at this screen need to get done today?" Typical jobs:

  • Onboard a new customer and set their plan
  • Investigate why a user cannot log in
  • Refund an order and note the reason
  • Approve content before it goes live
  • Export this month's numbers for the accountant

Each job becomes a page, a table view with the right filters, or an action — not necessarily a full resource. Five jobs done well beats thirty half-built resources.

Define the resource list explicitly

For every model you intend to expose, write down:

Field — Decision

Operations — List / view / create / edit / delete — pick, do not default to all

Key columns — The three or four columns someone scans

Filters — The questions people actually ask of this table

Search — Which columns, and whether it needs to be fast

Relations — Which relation managers are worth the screen space

Bulk actions — Which ones are safe, and which need confirmation

Anything not on this list is out of scope. That is not bureaucracy — it is what makes a two-to-three week estimate hold.

Decide roles before widgets

Authorisation is where admin panels get expensive after launch. Settle these first:

  • What roles exist, and what can each one see and do?
  • Which fields are visible but not editable, per role?
  • Which actions require a second confirmation or a reason?
  • Is an audit trail required — who changed what, when?

Filament respects Laravel policies, so the clean answer is roles in a user_roles table, permissions in policies, and the panel simply reflecting them. Retrofitting this after fifteen resources exist is a rewrite of every one of them.

Budget the non-CRUD work

The parts that consume time and never appear in a resource count:

  • Dashboard widgets. Each meaningful metric is a query that must stay fast as data grows.
  • Exports. CSV or Excel with correct escaping, queued for large datasets.
  • Imports. Validation, partial failure handling, and a preview step.
  • File handling. Uploads, private disks, signed URLs, image variants.
  • Notifications. In-panel and email, with a sensible read/unread model.
  • Multi-tenancy. Filament supports it well, but it changes every query, policy and test in the panel.

The scoping document

A Filament sprint should start with a one-page document containing: the jobs list, the resource table above, the role matrix, the widget list, and an explicit exclusions section. The exclusions section is the most valuable part — it is what prevents the quiet scope creep that turns a three-week build into a three-month one.

What we deliver

Our Filament and Livewire feature build starts at $2,500 and runs two to three weeks against exactly that document: scoped resources, role-based authorisation via policies, the agreed widgets and exports, tests on the destructive actions, and a short written handover. Anything discovered mid-sprint gets quoted separately rather than absorbed and delivered late.

If you are earlier than that — the app exists but nobody is sure what state it is in — start with the $299 Laravel Triage Audit.