Recipe 03 · Choose your ingredients
Laravel + PHP + Filament
For structured forms, review queues, and approval workflows.
Learn by building: Open the guided GRC project lesson for this stack.
Each recipe uses the same learning path: understand the ingredients, follow one realistic example, build a small first version, test failure cases, then decide whether to add more. You do not need every ingredient on day one.
All five recipes · Jump to a recipe
When to choose this
What problem does it solve?
An internal process where different people submit, review, approve, and revisit records.
Try the simpler option first: Start with a shared document or static prototype when you are still validating the process.
New to the terminology? Start with What Is a Technology Stack? or follow the browser-to-server diagram.
Under the hood
Meet the ingredients
Laravel views and Filament admin interfaces
PHP and Laravel application logic
PostgreSQL for shared structured records
GitHub
Why it works with AI-assisted coding: Laravel provides established conventions for forms, validation, database migrations, and tests. Filament helps AI coding assistants work within repeatable admin UI patterns.
See the stack in action
One project, from input to result
Goal: Approve a fictional policy request
Policy title, submitter, reviewer, and requested date
Laravel validates and stores requests; Filament displays a review queue; PHP runs permission checks
A queue with Pending, Approved, and Returned statuses
Your first working milestone
One intake form and reviewer list with fictional data and defined roles
An authorized reviewer can approve and the decision is recorded
Unauthorized approval is rejected and incomplete submissions show errors
Only then consider: Add audit history and notifications once role and status tests pass
Three GRC ideas
What could you build?
- Vendor review manager with reviewer assignments
- Policy review and approval workflow
- Audit evidence request tracker
Your first version
Build a little, test a little
- Map who submits, who reviews, and what each role is allowed to change.
- Build a fictional intake form and list view first.
- Add database records, permissions, and status transitions in small increments.
- Test that submitters cannot approve their own requests unless explicitly authorized.
Where it runs: Use a managed Laravel/PHP-capable host or an appropriately configured AWS environment. Plan for a database, secret management, backups, and application updates.
Ask AI, then decide
A prompt worth trying
Design the smallest Laravel workflow for a fictional policy approval. Identify roles, permission checks, status transitions, database tables, and tests before writing code. Explain whether Filament is necessary.
Review the recommendation against your Playbook blueprint. Ask what can be removed, what could go wrong, and how you will test it.