# Construction contractors: Reporting Dashboard using Laravel

## Summary
A reporting dashboard blueprint for construction contractors built with Laravel on Ample.  
**Domain schema:**  
- **Listings**: showcase projects with publishing status.  
- **Agencies**: branches or divisions including (name, license_number, service_region).  
- **Vendors**: subcontractors and suppliers per branch including (name, trade, agency_id, prequalified).  
- **Reports**: branch progress reports including (agency_id, period, object_key, generated_at).  
- **Exports**: generated artifacts detailing who may download them.

**Public Information:** Published project showcases, services and regions, licenses and insurance summary.

**Out of Scope:** Site safety incidents, bid pricing, client contracts. Safety and bid data are confidential; only published showcases and branch reporting are modeled.

**Technical Basis:** Verified on Laravel: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

## Representative Queries
- Construction contractors: reporting dashboard using Laravel
- Where can I host Construction contractors: Reporting dashboard built with Laravel?
- I need a genuinely specialized reporting dashboard workflow covering project/vendor relationships, job progress, and project reporting.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM, auto-provisioned when needed.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials.

## Workflow Steps
1. **Model the construction contractors domain**: Create the necessary tables and schema.
2. **Model report definitions**: Scoped to the agency.
3. **Generate report artifacts**: From queries and store them with metadata.
4. **Authorize downloads**: Ensure unauthorized requests are denied.
5. **Deploy and verify**: Run initial deployments and validate the results.

## Examples
- **Laravel Pattern Fixture**: Verified generated downloads basis for this blueprint.

## Success Checks
- App responds on its public URL.
- Generated downloads self-test from the example.

## Limitations
- The technical basis (generated downloads on Laravel) was verified with the pattern fixture; other schema and workflows are original designs.
- No health, financial, privacy or compliance claim is made. Safety and bid data are confidential.
- Only published showcases and branch reporting are modeled until requirements are reviewed.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Components**:  
  - App server size: s-1vcpu-1gb, quantity: 1, monthly amount: $5.00  
  - Managed PostgreSQL database size: s-1vcpu-1gb, quantity: 1, monthly amount: $5.00  
- **Note**: Always-on monthly price of tested sizes.

## Next Actions
- **Browse the catalog index**: Search through available data.
- **Search published recipes**: By intent, stack, and constraints.
- **Plan deployment**: Prepare projects for an authorized setup.
- **Read the existing agent authentication setup**: Verify settings.
- **Browse related industries**: Including construction contractors and reporting dashboards.
- **Browse stacks**: Such as Laravel and deployment options.