Findings Workflow
This guide covers the complete findings lifecycle, project management patterns, location hierarchy best practices, and the support system. It documents workflows that power users rely on for day-to-day inspection management.
Finding Status Lifecycle
Findings move through 6 statuses that track their full lifecycle from identification to resolution. Status transitions trigger comment entries so the history is always clear.
| Status | Meaning |
|---|---|
| Open | Newly created finding, not yet assigned or actioned |
| In Progress | Assigned and actively being worked on |
| To Be Reviewed | Work completed, awaiting verification by another user |
| Closed | Fully resolved and confirmed |
| Accepted As Is | Acknowledged but accepted without rectification (documented decision) |
| Cancelled | No longer relevant; finding is withdrawn |
| Shipyard Confirmed Rectification | (YachtInspect) Shipyard has formally confirmed that rectification is complete |
Tip
Use Accepted As Is when a finding is a known, deliberate condition rather than marking it Closed. This keeps the record honest and auditable.
Recommended Lifecycle Flow
Open β In Progress β To Be Reviewed β Closed
β Accepted As Is
In Progress β Cancelled
Each status change can include a comment explaining the reason for the transition. These comments appear in the finding's comment thread.
Finding Tabs
The Findings view has multiple tabs for different workflows:
| Tab | Purpose |
|---|---|
| All Findings | Full list of project findings with search and filters |
| My Findings | Filtered to findings assigned to you |
| Deck Plans | Location markers on uploaded drawings (see Deck Plans) |
| Timeline | Gantt chart view with bars spanning Start Date to Due Date (see Findings Timeline) |
| Risk Assessment | Activity-based risk evaluations (see Risk Assessment) |
Project Management
Switching Projects
- Tap the Profile tab.
- Tap Change Project.
- Select a project from the list, or tap Create New Project to set up a new one.
All findings, reports, and inspections are scoped to the selected project.
Creating a New Project
When creating a project you need:
- Project name (required)
- Client / vessel name (required for YachtInspect)
- Location (optional but recommended)
- Start date (optional)
- Project type / category (optional)
Project Status Options
| Status | Meaning |
|---|---|
| Active | Currently being worked on (default for new projects) |
| Completed | Work finished, project closed out |
| On Hold | Temporarily paused |
| Archived | Retained for records but no longer active |
Use Archived rather than deleting completed projects so that historical reports and findings remain accessible.
Location Hierarchy Best Practices
The location system uses a 5-level hierarchy. Planning your location structure before starting a project pays dividends as findings accumulate.
General Principles
- Plan the structure first -- sketch your location levels on paper before creating findings. Changing level names mid-project creates inconsistency in filters and reports.
- Use consistent terminology -- agree on abbreviations and naming conventions with your team. For example: always "Port" not "PS" / "Port Side" interchangeably.
- Start broad, end specific -- Level 1 should be the broadest area; Level 5 should be the most precise position or component.
- Mirror the inspection workflow -- arrange locations in the order you physically move through the site or vessel. This makes data entry faster during an on-site inspection.
Example Structure (Vessel)
| Level | Example Values |
|---|---|
| Level 1 | Main Deck, Engine Room, Accommodation |
| Level 2 | Forward, Midship, Aft |
| Level 3 | Starboard, Port |
| Level 4 | Upper, Lower |
| Level 5 | Component (e.g., "Sea Cock", "Bilge Pump") |
Example Structure (Building)
| Level | Example Values |
|---|---|
| Level 1 | Building A, Building B |
| Level 2 | Floor 1, Floor 2, Basement |
| Level 3 | North Wing, South Wing |
| Level 4 | Room 101, Room 102 |
| Level 5 | Equipment (e.g., "HVAC Unit", "Fire Panel") |
Support and Issue Reporting
If you encounter a problem with the app or need assistance, you can create a support issue directly within the app:
- Navigate to the Profile tab.
- Scroll to Support or Report Issue.
- Describe the issue, attach screenshots if applicable, and submit.
Support issues are tracked in the backend and visible to the app team. You can check the status of submitted issues from the same menu.
For urgent matters, contact: support@quickinspect.me
Role Permissions Summary
| Action | Free | Standard | Key User | Admin |
|---|---|---|---|---|
| View findings | Yes | Yes | Yes | Yes |
| Create findings | No | Yes | Yes | Yes |
| Close / change status | No | Yes | Yes | Yes |
| Delete findings | No | No | Yes | Yes |
| Manage projects | No | No | Yes | Yes |
| Risk Assessment | Read-only | Yes | Yes | Yes |
| User management | No | No | Yes | Yes |
For the full role permissions matrix, see the Team Collaboration Guide and the Settings & Company tutorial.
What's Next?
- Findings Timeline: Visualize findings on a Gantt chart
- Deck Plans: Place markers on vessel drawings
- Risk Assessment: Activity-based risk evaluation
- Team Collaboration: Managing user roles and invitations