Creating Service Logs in Componentry is the foundation of comprehensive bike maintenance tracking. Each Service Log is tied to a specific piece of gear and provides a structured way to plan, track, and document maintenance work. Whether you're planning routine maintenance or responding to specific issues, Service Logs ensure nothing is missed and everything is properly documented.
Accessing Service Log Creation
From the Service Logs Page
The primary way to create new service logs:
- Create New Service Log button - Prominent button on the Service Logs page
- Gear selection required - Must select which bike needs service before proceeding
- Full creation interface - Access to all service log options and settings
From Gear Detail Pages
Context-aware service log creation:
- Gear-specific creation - Create service logs directly from bike detail pages
- Automatic gear linking - Service log automatically associated with the current gear
- Component context - Full visibility of installed components during creation
Quick Creation Options
Streamlined creation for common scenarios:
- Dashboard shortcuts - Quick access from the main dashboard
- Maintenance reminders - Create service logs directly from reminder notifications
- Component alerts - Create service logs when components need attention
[Screenshot placeholder: Different service log creation entry points shown across the interface]
Service Log Creation Process
Step 1: Gear Selection
Every service log must be associated with specific gear:
Gear Selection Requirements
- Single gear focus - Each service log is associated with exactly one piece of gear
- Active gear priority - Active gear is shown first in selection lists
- Retired gear access - Retired gear is available for historical service logs
- Gear cannot be changed - Once created, the gear association is permanent
Gear Selection Interface
- Visual gear picker - See photos and key details of each bike
- Gear filtering - Filter by gear type, status, or other criteria
- Search functionality - Quickly find specific gear by name or model
- Recently serviced - Quick access to recently serviced gear for follow-up work
[Screenshot placeholder: Gear selection interface showing available bikes with photos and details]
Step 2: Basic Service Information
Configure the essential service log details:
Service Log Name
- Automatic naming - System generates names based on gear and date
- Custom naming - Override with custom names for specific services
- Descriptive names - Include service type or specific work being done
- Naming conventions - Follow consistent patterns for easy organization
Service State Selection Choose the appropriate initial state:
- New - For service planning and preparation
- Booked - When service is scheduled with a mechanic
- Completed - When creating logs for already completed work
Service Date Information
- Creation date - Automatically recorded when service log is created
- Planned date - When service is scheduled to be performed (for Booked services)
- Completion date - When service was completed (for Completed services)
- Flexible dating - Dates can be adjusted as service progresses
[Screenshot placeholder: Basic service information form showing name, state, and date fields]
Step 3: Service Details
Add comprehensive information about the service:
Service Notes Document planned or completed work:
- Markdown support - Rich text formatting for detailed notes
- Work description - Detailed description of work to be performed or completed
- Special instructions - Specific requirements, procedures, or considerations
- Reference information - Links to manuals, guides, or previous service notes
Service Provider Information Track who is performing the work:
- Service provider name - Mechanic, shop, or person performing the service
- Optional field - Not required for self-service or planning-stage logs
- Contact information - Store contact details for future reference
- Service history - Track which providers have worked on each bike
Crash-Related Service Indicate if service is related to a crash:
- Crash indicator - Mark services that are result of crashes or accidents
- Insurance documentation - Important for insurance claims and documentation
- Component assessment - Helps identify components that may need extra attention
- Safety prioritization - Crash-related services get priority treatment
[Screenshot placeholder: Service details form showing notes, provider, and crash-related options]
Service States and Their Purposes
New Service Logs
Initial state for service planning:
Purpose and Use Cases
- Service planning - Plan upcoming maintenance before scheduling
- Component assessment - Review component conditions and plan replacements
- Work preparation - Prepare parts lists and service requirements
- Initial documentation - Record initial observations and planned work
Available Actions in New State
- Edit service details - Modify notes, provider, and other service information
- Review components - View all installed components and their conditions
- Plan replacements - Identify components that may need replacement
- Progress to Booked - Move to Booked state when ready to schedule service
Limitations in New State
- No component retirement - Cannot retire components while planning
- No service reports - Cannot generate service reports until Booked
- Limited finality - State indicates work is still in planning phase
[Screenshot placeholder: New service log showing available actions and limitations]
Booked Service Logs
State for scheduled or ready-to-start services:
Purpose and Use Cases
- Scheduled maintenance - Services that are booked with a mechanic or shop
- Ready for execution - Self-service work that's ready to begin
- Professional coordination - Services being coordinated with external providers
- Component freeze - Lock current component state for service documentation
Available Actions in Booked State
- Generate service reports - Create comprehensive reports for mechanics
- Email reports - Send service information via email to service providers
- Edit service details - Continue to modify notes and service information
- Progress to Completed - Mark service as completed when work is finished
Limitations in Booked State
- No component retirement - Components are locked to preserve service snapshot
- No component changes - Cannot add or modify components during booked service
- Service focus - Interface focuses on service execution rather than component management
Service Report Generation Key feature available in Booked state:
- Comprehensive reports - Complete gear and component information
- Professional formatting - Suitable for sharing with mechanics and service providers
- Email integration - Send reports directly via email
- Documentation snapshot - Captures current state for service reference
[Screenshot placeholder: Booked service log showing service report generation and email options]
Completed Service Logs
Final state for finished services:
Purpose and Use Cases
- Service documentation - Record completed work and final results
- Component management - Retire old components and add replacements
- Historical record - Create permanent record of service work performed
- Maintenance history - Build comprehensive maintenance history for gear
Available Actions in Completed State
- Component retirement - Retire worn or replaced components
- Component addition - Add new replacement components
- Service reports - Generate final service documentation
- Historical documentation - Complete service record for future reference
Component Management Features Full component lifecycle management:
- Retirement workflow - Guided process for retiring components
- Replacement linking - Link new components to retired ones
- Installation dating - Proper timestamps for all component changes
- Service attribution - Track which service made each component change
Completion Documentation Record final service details:
- Completion date and time - Precise timing of service completion
- Final service notes - Summary of work completed and findings
- Service provider confirmation - Final confirmation of who completed the work
- Cost tracking - Record service costs for budgeting and history
[Screenshot placeholder: Completed service log showing component management and completion documentation]
Service Log Management Interface
Service Log List View
Organized display of all service logs:
Chronological Organization
- Monthly grouping - Services grouped by month for easy navigation
- Date-based sorting - New services by creation date, others by completion date
- Visual timeline - Clear progression of service history over time
- Quick navigation - Easy jumping between time periods
Service Log Cards Each service displayed as informative cards:
- Service summary - Key information at a glance
- State indicators - Clear visual indication of service state
- Component counts - Number of components retired during service
- Service provider - Who performed the service
- Quick actions - Direct access to common actions from the card
Filtering and Organization
- Gear filtering - View services for specific gear
- State filtering - Filter by New, Booked, or Completed services
- Date range filtering - Focus on specific time periods
- Search functionality - Find specific services quickly
[Screenshot placeholder: Service log list view showing monthly grouping and card layout]
Service Log Detail View
Comprehensive interface for managing individual services:
Service Information Section
- Editable details - Modify service information directly in the detail view
- State management - Progress service through different states
- Service provider tracking - Manage service provider information
- Notes management - Add and edit comprehensive service notes
Component Management Section
- Installed components list - All components currently on the gear
- Component details - Wear information, installation dates, and conditions
- Retirement actions - Retire components as part of the service
- Replacement tracking - Add new components to replace retired ones
Service Actions Section
- State progression - Buttons to move between service states
- Report generation - Create and email service reports
- Delete service - Remove service logs when necessary (with confirmation)
- Historical access - Links to related service logs and component history
[Screenshot placeholder: Service log detail view showing all management sections and actions]
Best Practices for Service Log Creation
Planning Effective Services
Service Timing Plan services for optimal timing:
- Regular intervals - Create service logs on consistent schedules
- Component-driven - Time services based on component wear and replacement needs
- Seasonal considerations - Plan major services during appropriate seasons
- Preventive approach - Create service logs before problems become critical
Comprehensive Planning Use New state effectively for planning:
- Component assessment - Review all components before scheduling service
- Work scope definition - Clearly define what work will be performed
- Parts preparation - Identify and order necessary parts before service
- Service coordination - Plan service timing with provider availability
Documentation Standards Maintain consistent documentation:
- Detailed notes - Record comprehensive information about planned and completed work
- Standard formats - Use consistent formatting for similar types of services
- Reference information - Include links to manuals, guides, and previous services
- Photo documentation - Include photos when helpful (future feature)
State Management Best Practices
Appropriate State Usage Use each state for its intended purpose:
- New for planning - Use New state only during active planning phase
- Booked for execution - Move to Booked when service is ready to begin
- Completed for documentation - Mark Completed only when all work is finished
- Timely progression - Progress through states in reasonable timeframes
Service Coordination Coordinate effectively with service providers:
- Clear communication - Use service reports to communicate requirements clearly
- Professional documentation - Provide comprehensive information to mechanics
- Progress tracking - Keep service state updated as work progresses
- Completion verification - Verify all work is completed before marking Completed
Organization and Management
Service Log Organization Keep service logs organized for easy access:
- Consistent naming - Use clear, consistent naming conventions
- Regular updates - Keep service information current and accurate
- Historical maintenance - Preserve historical service logs for reference
- Cross-referencing - Link related services and component changes
Integration with Other Features Coordinate with other Componentry features:
- Reminder integration - Create service logs from maintenance reminders
- Component tracking - Use component wear information to plan services
- Gear management - Coordinate with overall gear management activities
- Activity integration - Consider activity patterns when planning services (future feature)
Service Log creation is the first step in comprehensive maintenance tracking. Once created, service logs provide structure and documentation for all bike maintenance activities, ensuring nothing is forgotten and everything is properly recorded for future reference.
[Screenshot placeholder: Completed service log creation showing the final result and next steps]