Skip to main content

Feature Analysis - Brainstorming Session

Date: November 11, 2025 Source: Swedish brainstorming notes (stakeholder meeting) Purpose: Map brainstormed features against MVP specification

📊 Analysis Summary​

Status: ✅ Complete - All Decisions Made

StatusCountDescription
✅ Fully Covered in v4.012Feature already exists in specification
🟢 Approved for v4.1 MVP5New features added to MVP scope
🟡 Partially Covered8Core functionality exists, no changes needed
⏭️ Post-MVP5Deferred to future releases

Total Features Analyzed: 30 v4.1 New Features: 5 (Favorite crew, Admin task tracking, Contract acceptance, Travel copy, Custom data)

✅ Final Decisions (Session 3 - Nov 11, 2025)​

Approved for v4.1 MVP:​

  1. ✅ Favorite/Star Crew - is_favorite field on company_crew
  2. ✅ Administrative Task Tracking - Manual checkboxes for travel/hotel/roadbook/invoice
  3. ✅ Contract Acceptance - Required checkbox for freelancers
  4. ✅ Copy Travel Functionality - Frontend helpers (crew-to-crew copy + reverse trip)
  5. ✅ Custom Data Storage - custom_data json field on projects

Deferred to Post-MVP:​

  1. ⏭️ QR Code for WhatsApp - Not critical for launch
  2. ⏭️ Structured Accreditation - Free text sufficient for MVP
  3. ⏭️ Useful Links UI - Schema support added, UI can wait
  4. ⏭️ Proximity Search - Basic city filter adequate

1. Crewpool Features​

1.1 Star/Favorite Crew (Stjärna)​

Status: ✅ APPROVED FOR v4.1 MVP Decision: Add is_favorite boolean to company_crew table Implementation:

  • Simple toggle on/off
  • Company-specific favorites
  • Filter: "Show Favorites Only"
  • Star icon visible in crew directory and all views Impact: Low - single boolean field Value: Helps quickly filter to preferred crew when staffing

1.2 Accreditation Tracking​

Status: 🟡 Partially Covered Current v4.0:

  • crew_profiles.capabilities field (free text)
  • Can include accreditation info manually

Gap:

  • No structured accreditation system
  • No expiration dates
  • No verification workflow
  • No accreditation checkboxes in forms

Recommendation: 🔄 Needs Discussion

  • MVP: Use capabilities field for text mentions (e.g., "SVT Accredited")
  • Post-MVP: Add structured crew_accreditations table with expiration dates
  • Impact: Medium - structured system would require new tables
  • Priority: Manual text entry sufficient for MVP

1.3 Company-Specific Notes (Anteckningar)​

Status: ✅ Fully Covered Current v4.0:

  • company_crew.private_notes (GDPR-sensitive, company-specific)
  • Not visible to crew or other companies

Reference:

  • Schema: schema.dbml line 175-176
  • Q&A: Session 2, Q3

No Action Needed - Already implemented in v4.0

1.4 Crew Profile Updates (Uppdatera profil)​

Status: ✅ Fully Covered Current v4.0:

  • Crew can update their own profiles
  • crew_profiles table with editable fields
  • Crew portal has profile editing

Reference:

  • Views: "Crew Portal - My Profile" (docs/views.md)
  • User Case: UC-15 (Edit My Profile)

No Action Needed - Already in MVP

1.5 Location-Based Search (Sök på ort)​

Status: 🟡 Partially Covered Current v4.0:

  • crew_profiles.city field exists
  • Can filter crew directory

Gap:

  • No proximity search ("within 50km of Stockholm")
  • No map visualization
  • No geographical filtering UI specified

Recommendation:

  • MVP: Simple text search/filter on city name (already possible)
  • Post-MVP: Geocoding and radius search
  • Impact: Low - current city filter sufficient for MVP
  • Priority: Low - text search is adequate

1.6 Equipment Skills (Utrustning crew kan)​

Status: ✅ Fully Covered Current v4.0:

  • crew_profiles.capabilities field (free text)
  • Can include equipment skills (e.g., "Sony FS7, Canon C300")

Reference:

  • Schema: schema.dbml line 166
  • Q&A: Session 2, Q2

No Action Needed - Use capabilities field

1.7 Booking Conflict Warnings (Varning dubbelbokningar)​

Status: ✅ Fully Covered Current v4.0:

  • crew_availability table for staff (employed crew)
  • Soft warnings for date conflicts
  • Not blocking, just informational

Reference:

  • Schema: schema.dbml lines 196-211
  • Q&A: Session 2, Q10 (availability tracking)

Note: Only for staff (employer_id IS NOT NULL), freelancers manage own conflicts

2. Gearpool (Equipment) Features​

2.1 Book Equipment (Boka buss, Boka kamera)​

Status: ✅ Fully Covered Current v4.0:

  • company_equipment table (inventory)
  • project_equipment table (bookings)
  • Equipment availability checking

Reference:

  • Schema: schema.dbml lines 428-472
  • Views: "Equipment Management" view
  • Q&A: Session 2, Q5

No Action Needed - Fully implemented in v4.0

2.2 Specify Equipment Costs (Ange kostnad)​

Status: ✅ Fully Covered Current v4.0:

  • company_equipment.default_rate_cents (default daily rate)
  • project_equipment.rate_cents (adjustable per booking)
  • Currency support per booking

Reference:

  • Schema: schema.dbml line 437, 460

No Action Needed

2.3 See Equipment Booking Status (Se status på bokning)​

Status: ✅ Fully Covered Current v4.0:

  • project_equipment.start_date / end_date
  • Availability conflict detection
  • Equipment calendar view (specified in views.md)

Reference:

  • Views: "Equipment Management" view

No Action Needed

3. Staffpool Features​

3.1 See Staff Bookings with Equipment​

Status: 🟡 Partially Covered Current v4.0:

  • Can see crew assignments (assignments table)
  • Can see equipment bookings (project_equipment table)
  • Both are per-project

Gap:

  • No explicit link between crew and equipment
  • No "Camera A assigned to Lisa" relationship

Recommendation:

  • MVP: Visual grouping in UI (show equipment under crew in project view)
  • Post-MVP: Add assigned_to_crew_profile_id to project_equipment table
  • Impact: Low - UI grouping sufficient for MVP
  • Priority: Low - not critical for launch

4. Communication Features​

4.1 QR Code for WhatsApp Group​

Status: ⏭️ POST-MVP Decision: Not critical for launch, can add later Rationale:

  • Easy to implement when needed (URL field + client QR generation)
  • Not essential for core workflow
  • Can be added in future release without schema changes

4.2 Send to Group (Skicka till grupp)​

Status: 🟡 Partially Covered Current v4.0:

  • Can send to all assigned crew (bulk messaging concept exists)
  • communication_logs tracks all sent messages

Gap:

  • No explicit "group" concept
  • No WhatsApp/SMS integration
  • Only email workflow documented

Recommendation:

  • MVP: Bulk email to all crew on project (likely already implied)
  • Post-MVP: WhatsApp Business API, SMS gateway
  • Impact: Medium - requires third-party integration
  • Priority: Email sufficient for MVP

4.3 Communication History (Kommunikationshistorik)​

Status: ✅ Fully Covered Current v4.0:

  • communication_logs table
  • Full audit trail of all emails/requests
  • Status tracking (sent, delivered, opened, responded, failed)
  • Timeline view per project and per crew

Reference:

  • Schema: schema.dbml lines 756-786
  • Q&A: Session 2, Q17
  • Views: "Communication History" view

No Action Needed - Fully implemented in v4.0

5. Travel & Resources Features​

5.1 Send Mail (Travel Confirmation)​

Status: 🟡 Partially Covered Current v4.0:

  • Email functionality exists (for offers, confirmations)
  • travel_bookings table exists
  • Can attach travel documents

Gap:

  • No specific "travel confirmation email" template mentioned
  • Workflow not explicitly documented

Recommendation:

  • MVP: Use existing email system with travel booking details
  • Impact: Low - just a template
  • Priority: Low - can use generic confirmation emails

5.2 Copy Travel Days (Kopiera resedagar)​

Status: ✅ APPROVED FOR v4.1 MVP (Frontend Only) Decision: Add frontend helper functions Implementation:

  1. Copy from crew member to crew member (priority: high)
    • Pre-fills form with another crew's travel details
    • For group travel scenarios
  2. Create return trip (priority: medium)
    • Auto-reverses route and dates
  • Pure JavaScript (no schema changes) Impact: Very low - frontend only Value: Saves significant time when booking travel for large crews

5.3 Extra Costs (Extra kostnader)​

Status: ✅ Fully Covered Current v4.0:

  • project_budget_items table for generic costs
  • Can add rentals, venue costs, catering, etc.
  • Currency support

Reference:

  • Schema: schema.dbml lines 636-661
  • Q&A: Session 2, Q6

No Action Needed - Use project_budget_items

6. Crewinfo Features​

6.1 Upload PDF Documents​

Status: ✅ Fully Covered Current v4.0:

  • documents table with polymorphic attachments
  • Support for PDFs, images, etc.
  • Multi-level access control (company/project/crew/project-crew)

Reference:

  • Schema: schema.dbml lines 687-722
  • Q&A: Session 2, Q18

No Action Needed

6.2 Send Document to All Crew​

Status: 🟡 Partially Covered Current v4.0:

  • Documents can be attached at project level
  • All crew on project can access
  • Email notifications can be sent

Gap:

  • "Send to all" action not explicitly documented
  • Implies email with attachment or download link

Recommendation:

  • MVP: Email notification when document is uploaded to project
  • Impact: Low - notification feature
  • Priority: Medium - useful for road books, call sheets

7. Project Planning Features​

7.1 Manual Invoice Checkbox​

Status: ✅ APPROVED FOR v4.1 MVP Decision: Part of administrative task tracking system Implementation:

  • Add invoice_status to assignments table
  • Values: 'not_handled' / 'handled'
  • Only for freelancers (employer_id IS NULL)
  • Manual checkbox (not auto-detected)
  • Part of workflow tracking grid on project overview Clarification: This is for tracking manual invoicing done outside PBS, not automated invoicing Impact: Low - single enum field Value: Essential for tracking completion of all admin tasks

7.2 Send Confirmation to All (Skicka till alla)​

Status: ✅ Fully Covered Current v4.0:

  • Bulk messaging concept exists
  • communication_logs tracks all sent messages
  • Can send to all assigned crew

Reference:

  • Views: Project detail view includes "Send to All Crew" button
  • communication_logs for tracking

No Action Needed - Already possible

8. System Links & Integration​

Status: 🟢 APPROVED FOR v4.1 (Schema Only) Decision: Add custom_data json field to projects table Implementation:

  • Flexible JSON storage for unstructured data
  • Can store useful links, custom fields, integration data
  • UI for managing links is post-MVP Impact: Very low - single JSON column Value: Future-proof schema for extensions without migrations UI: Post-MVP

9. Preproduction Features​

9.1 Add Staff Travel (Lägg till staff resa)​

Status: ✅ Fully Covered Current v4.0:

  • travel_bookings table exists
  • Can add travel for any crew member
  • Supports flights, trains, rentals, etc.

Reference:

  • Schema: schema.dbml lines 548-585
  • User Case: UC-08 (Book Travel)

No Action Needed

9.2 Connect Travel and Costs (Koppla resa och kostnader)​

Status: ✅ Fully Covered Current v4.0:

  • travel_bookings has cost fields (estimated/actual)
  • Linked to specific crew and project
  • Costs roll up into project budget

Reference:

  • Schema: schema.dbml lines 568-576

No Action Needed

10. Additional Features​

10.1 Accreditation Checkbox (in forms)​

Status: 🟡 Partially Covered Current v4.0:

  • Can be mentioned in crew_profiles.capabilities
  • No dedicated field

Gap:

  • No structured accreditation tracking
  • No checkbox UI element specified

Recommendation:

  • MVP: Free-text in capabilities field
  • Post-MVP: Dedicated accreditation system
  • Impact: Low for MVP
  • Priority: Low

📋 Recommendations by Priority​

🔴 High Priority - Discuss for MVP Inclusion​

  1. QR Code for WhatsApp Groups (4.1)

    • Easy to implement (just URL field + client QR generation)
    • High user value for on-site coordination
    • Action: Decide if MVP or post-MVP

  2. Manual Invoice Checkbox (7.1)

    • Conflicts with "no invoicing in MVP" decision
    • Might just be tracking field
    • Action: Clarify if needed for financial finalization workflow

  3. Star/Favorite Crew (1.1)

    • Simple boolean flag on company_crew
    • Enhances crew directory usability
    • Action: Decide if MVP or post-MVP

🟡 Medium Priority - Consider for MVP​

  1. Send Document to All (6.2)

    • Email notification when project docs uploaded
    • Useful for road books, call sheets
    • Action: Add to email workflow if time permits

  2. Crew-Equipment Assignment (3.1)

    • Link equipment to specific crew (e.g., "Camera A → Lisa")
    • Can be UI-only solution (no schema change)
    • Action: Consider visual grouping in UI

🟢 Low Priority - Post-MVP​

  1. Copy Travel Days (5.2) - UI convenience feature
  2. Useful Links (8.1) - Can use settings JSON
  3. Proximity Search (1.5) - City filter sufficient
  4. Structured Accreditation (1.2, 10.1) - Free text adequate

✅ Already Covered in v4.0 (No Action Needed)​

  • ✅ Company-specific notes (1.3)
  • ✅ Crew profile updates (1.4)
  • ✅ Equipment skills tracking (1.6)
  • ✅ Booking conflict warnings (1.7)
  • ✅ Equipment booking system (2.1, 2.2, 2.3)
  • ✅ Communication history (4.3)
  • ✅ Extra costs/budget items (5.3)
  • ✅ Document upload/sharing (6.1)
  • ✅ Bulk messaging (7.2)
  • ✅ Travel booking (9.1, 9.2)

🎯 Next Steps​

Immediate Actions​

  1. Stakeholder Meeting - Discuss 4 features needing decisions:

    • QR code for WhatsApp groups (MVP or post-MVP?)
    • Manual invoice checkbox (needed for tracking?)
    • Star/favorite crew (MVP or post-MVP?)
    • Send document notifications (include in MVP emails?)

  2. Update MVP Spec (if features approved):

    • Add to schema.dbml
    • Update views.md with UI elements
    • Update relevant user cases
    • Document in Q&A session 3

  3. Document Decisions - Add stakeholder responses to:

    • docs/reference/qa-answers.md (Session 3)
    • Update changelog if MVP changes

Validation Questions​

For User/Stakeholder:

  1. QR Codes: Do you need WhatsApp QR codes for MVP, or can this wait?
  2. Invoice Tracking: The "manual invoice checkbox" - is this for tracking invoice creation, or actual invoicing (which we said was post-MVP)?
  3. Favorites: Would starring/favoriting crew significantly improve your workflow, or is search/filter sufficient?
  4. Document Notifications: Should uploading a project document automatically notify all crew via email?

📊 Final Statistics​

Features from Brainstorm: 30 Already in v4.0: 12 (40%) Partially Covered: 8 (27%) Not Covered: 6 (20%) Need Discussion: 4 (13%)

Conclusion: The v4.0 specification already covers 67% of brainstormed features fully or partially. The remaining 33% are mostly nice-to-have enhancements or post-MVP features. Only 4 features require stakeholder decisions for potential MVP inclusion.

Document Status: ✅ Analysis Complete Next Action: Stakeholder meeting to discuss 4 decision-needed features Last Updated: 2025-11-11