Do's:

• Create and save commonly used search filters to streamline recurring administrative tasks and ensure consistency across your team
• Customize your column display to show only the information relevant to your current task, improving screen readability and efficiency
• Use bulk actions when managing multiple pre-plans with similar attributes to save time and ensure consistent updates
• Leverage the map view feature to visualize geographic distribution of pre-plans and identify coverage gaps or clustering
• Review the pre-plan history (clock icon) before making significant changes to understand previous modifications and reviewer feedback
• Establish naming conventions for saved searches that clearly describe the criteria for easy identification by all team members

Don'ts:

• Don't forget to click "Apply" after selecting filter criteria, as selections won't take effect until applied
• Don't modify parent/child relationships without understanding the impact on primary and secondary address associations
• Don't use the quick approve (check mark) or reject (X) functions without establishing clear departmental policies about when direct approval is appropriate
• Don't delete saved searches created by other team members without coordination, as they may be using them for regular workflows
• Don't overlook the comments/feedback icon when reviewing pre-plans, as it contains valuable information from the approval process
• Don't assume all columns are editable—only Address, Parent/Child, Assigned Member/Team, Cycle, Due Date, Target Hazard, and Address Status can be edited directly in the organizer

Tips & Recommendations:

• Start with basic searches and progressively add criteria to refine results rather than building complex searches immediately
• Use the target hazard filter combined with geographic or assignment filters to prioritize high-risk occupancy reviews
• Review pre-plans that are past due regularly by creating a saved search specifically for overdue items
• Take advantage of the printer icon to generate reports for station tours or training sessions
• When managing review cycles, use bulk actions to update due dates for multiple pre-plans in the same occupancy type or geographic area
• Monitor the alert tiles display toggle to ensure critical information is visible to responders when needed

Troubleshooting & FAQs

Q: Why can't I see the Pre-Plan Organizer option in my Pre-Planning module?
A: You likely don't have the "Pre-Plan Organizer" permission assigned to your user role. Contact your system administrator to request access. This permission is found in Pre-Planning > General.

Q: I created a saved search but other users can't see it—what's wrong?
A: Verify you completed the save process by entering a name and clicking "Save." Once properly saved, searches are automatically available to all users with Pre-Plan Organizer access. If the problem persists, check that other users have the "Pre-Plan Organizer Saved View - Read" permission.

Q: What's the difference between the Address column link and the Parent/Child column link?
A: The Address column link takes you to the occupancy record for that specific address. The Parent/Child column link (when an address is displayed) always takes you to the primary address occupancy record, even if you're viewing a secondary/child address row.

Q: Can I edit pre-plan details directly in the organizer or do I need to open the full pre-plan?
A: Limited editing is available directly in the organizer through editable columns (Assigned Member/Team, Cycle, Due Date, Target Hazard, and Address Status). For comprehensive pre-plan editing including annotations, units, and detailed information, use the pencil icon in the Actions column to open the full pre-plan editor.

Q: Why do some pre-plans show a clock icon while others don't?
A: The clock icon only appears for pre-plans that have history records (previous edits, reviews, or status changes). Pre-plans without modification history won't display this icon.

Q: How many pre-plans can I select for bulk actions at once?
A: While First Due doesn't specify a hard limit, best practice is to work with manageable groups (typically 25-50 pre-plans at a time) to ensure system performance and allow for verification of changes. For very large bulk updates, consider breaking the work into multiple batches.