Appearance
Tips, Best Practices, and Troubleshooting
This guide compiles expert tips, proven best practices, and solutions to common problems you might encounter while using Territory Wallet.
Table of Contents
- General Best Practices
- Power User Tips
- Performance Optimization
- Data Management
- Common Problems and Solutions
- Browser Issues
- Mobile Access
- Getting Support
General Best Practices
For New Administrators
Start Small:
- Create 5-10 territories first to learn the workflow
- Test the full lifecycle (create → draft → publish → assign)
- Import a small batch of addresses to test CSV process
- Experiment with filters, visual layers, and reports
Plan Your System:
- Define reference ID conventions before creating territories
- Set up localities early (neighborhoods/zones)
- Establish territory types your congregation uses
- Document your system for future administrators
Build Incrementally:
- Don't try to create all territories in one session
- Work in batches (10-20 territories at a time)
- Save drafts frequently
- Publish in batches after verification
Get Feedback:
- Share with other administrators for review
- Show publishers sample territory cards
- Test assignment workflow
- Iterate based on feedback
Ongoing Management
Daily/Weekly:
- Update for new construction or changes
Quarterly:
- Comprehensive territory review
- Verify all addresses are accurate
- Clean up unused localities/types
- Export backup of all data
Annually:
- Full system audit
- Retrain administrators
- Major updates and improvements
Advanced Map Techniques
Precision Drawing:
- Zoom to max level
- Draw boundaries following visible property lines
- Use street centerlines as logical boundaries
Multi Feature Territory:
- Create one territory completely
- Assign an existing reference ID
- Properties will auto complete
- Adjust boundaries as needed
- Toggle between linked features with the stack dropdown
Filter Stacking:
- Combine type + locality filters for precision
- Example: "Apartment" + "Downtown" shows only downtown apartments
- Use to focus on specific subsets
- Clear filters when done to avoid confusion
Visual Layer Workflow:
- Use "Last Worked" layer to find gaps
- Switch to "Assignment Status" for assignment planning
- Use "Activity Heat" for coverage analysis
- Return to "Default" for general editing
Bulk Operations Efficiency
CSV Import Mastery:
- Prepare data in an online spreadsheet (collaborative editing)
- Use data validation to ensure format consistency
- Test geocoding on small sample first
- Review geocoded locations immediately
Performance Optimization
For Large Congregations (600+ Territories)
Managing Performance:
Load Times:
- Initial load may take 1-5 seconds for large datasets
- Use filters to reduce visible territories
- Work on one locality at a time
- Close other browser tabs to free memory
Map Rendering:
- Zoom in before editing (renders fewer features)
- Hide non-relevant territories with filters
Data Operations:
- Publish in groups (10-20 territories) vs. all at once
- Delete old/inactive territories to reduce dataset
Connection and Bandwidth
Data Management
Backup Strategy
Data Quality Maintenance
Address Quality:
Regular Checks:
Cleaning Process:
- Export address list to CSV
- Review in spreadsheet software
- Identify issues (sort, filter, search)
- Fix in spreadsheet or in app
- Re-import or bulk edit
Standardization:
- Consistent abbreviations (Street vs St)
- Consistent capitalization (Title Case)
- Standardized city names
- Proper postal code formatting
- Remove extra spaces
Territory Boundary Maintenance
When to Update Boundaries:
- New construction in area
- Buildings demolished
- Street changes (closures, new roads)
- Territory too large/small for publishers
- Overlapping boundaries discovered
- Logical improvements to organization
Update Process:
- Edit territory boundary in Map Builder
- Adjust addresses if needed
- Save draft
- Verify coverage is correct
- Publish update
Handling Overlaps:
- Intentional overlaps: Document reason (e.g., shared buildings)
- Unintentional overlaps: Adjust boundaries to eliminate
- Use visual layers to identify overlaps
- Check border territories regularly
Common Problems and Solutions
Map and Display Issues
Problem: Map won't load or shows blank screen
Solutions:
- Refresh the page (F5 or Ctrl+R)
- Check internet connection
- Clear browser cache
- Disable browser extensions
- Try different browser
- Check if firewall/network blocking map tiles
Problem: Territories not showing on map
Solutions:
- Check if filters are hiding them
- Clear all filters
- Check type and locality filters
- Verify territories are published (not just drafts)
- Zoom out - may be off-screen
- Use search to find specific territory
- Check if visual layer is set correctly
Problem: Map is slow or laggy
Solutions:
- Close other browser tabs
- Apply filters to reduce visible territories
- Zoom in (renders fewer features)
- Refresh the page
- Use simpler visual layer (Default vs. Heat Map)
- Clear browser cache
- Restart browser
Drawing and Editing Issues
Problem: Can't enter drawing mode (draw tool doesn't work)
Solutions:
- Deselect any selected features first (click empty space or press Esc)
- This is the most common cause
- Click the draw tool again
- Ensure map is fully loaded
- Refresh page if persistent
- Try different browser
Problem: Drew wrong shape / made mistake
Solutions:
- Immediately click the Undo button in the toolbar
- Or delete the feature and start over (select it, use Delete button)
- Or edit vertices to reshape (select, drag vertices)
- Don't panic - undo history preserves recent changes
Problem: Can't select territory
Solutions:
- Click directly on the boundary or point
- Zoom in closer
- Check if another territory is on top (overlapping)
- Use search bar to find and select
- Check if filters are hiding it
Problem: Changes disappeared
Solutions:
- Check if you saved draft or published
- Use Undo if just made change
- Refresh page if browser crashed
- Check last saved timestamp
- If data loss occurred, restore from backup
Save and Publish Issues
Problem: Save draft fails
Solutions:
- Check internet connection
- Verify required fields are complete (reference ID, title, type)
- Try again (may be temporary network issue)
- Check browser console for error messages
- Copy territory data to clipboard as backup
- Contact support with error details
Problem: Publish fails or gets stuck
Solutions:
- Wait 2-3 minutes (processing can take time)
- Check error message for specific issue
- Verify all required fields complete
- Check address geocoding succeeded
- Try publishing smaller batch
- Refresh page and try again
- Contact support if persistent
Problem: Published but changes not visible
Solutions:
- Verify publish status shows "Published" (not "Publishing...")
- Refresh the publisher view
- Check permissions (publishers may not have access yet)
- Verify correct territory was published
- Check if changes were in draft before publishing
- Wait a few minutes for cache to clear
Address and Geocoding Issues
Problem: Geocoding fails for addresses
Solutions:
- Verify address spelling (street, city correct)
- Check postal code is valid
- Try adding more detail (unit, building name)
- Manually place address on map instead
- Check if address is too new (not in database yet)
Problem: Geocoded location is wrong
Solutions:
- Select the point on map
- Drag to correct location
- Or delete and manually place
- Verify address data is correct
Problem: Duplicate addresses after import
Solutions:
- Export address list to CSV
- Identify duplicates (sort by house + street)
- Delete duplicates manually or in spreadsheet
- Re-import cleaned data
- Use duplicate detection in import settings
Problem: Address ranges not working
Solutions:
- Verify Range High > Range Low
- Ensure both are numeric values
- Check address has building name
- Review how ranges display in publisher view
- May need to enter ranges differently based on configuration
Browser Issues
Cookies and Local Storage
Problem: Keep getting logged out
Solutions:
- Check browser isn't clearing cookies on close
- Disable private/incognito mode
- Allow cookies for Territory Wallet domain
- Check browser privacy settings
- Update browser to latest version
Browser Extensions Conflicts
Problem: Features not working correctly
Solutions:
- Disable ad blockers temporarily
- Disable privacy extensions (Privacy Badger, etc.)
- Disable VPN if using
- Test in private/incognito mode (extensions disabled)
- Enable extensions one-by-one to identify culprit
Cache and Storage Issues
Problem: Old data showing, changes not appearing
Solutions:
- Hard refresh: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
- Clear browser cache:
- Chrome: Settings → Privacy → Clear browsing data
- Firefox: Settings → Privacy → Clear Data
- Safari: Develop → Empty Caches
- Clear local storage
- Restart browser
- Try different browser to verify
Mobile Access
Mobile Browser Limitations
What Works:
- Viewing territories and maps
- Searching territories
- Basic navigation
- Publisher territory cards
- Viewing assignments
What's Limited:
- Drawing new territories (touch precision)
- Complex editing (small screen)
- Bulk operations
- CSV import
Recommendations:
- Use mobile for viewing
- Use desktop/laptop for creation and editing
- Mobile works for field reference
- Tablet better than phone for light editing
Mobile Optimization Tips
For Best Mobile Experience:
- Use latest iOS/Android version
- Use Chrome or Safari browser
- Enable location access for map centering
- Use portrait mode for lists, landscape for maps
- Pinch to zoom, two-finger pan
- Use simplified visual layers
- Filter to reduce visible territories
Getting Support
Before Contacting Support
Gather Information:
- What were you trying to do?
- What happened instead?
- Error messages (screenshot if possible)
- Browser and version
- Operating system
- Steps to reproduce the issue
Try Basic Troubleshooting:
- Refresh the page
- Clear browser cache
- Try different browser
- Check internet connection
- Review relevant documentation
How to Contact Support
Support Channels:
- Email support team
- Contact congregation IT administrator
- Check online help documentation
Include in Support Request:
- Congregation ID / account info
- Detailed description of issue
- Screenshots or screen recording
- Browser console errors (F12 → Console tab)
- Steps to reproduce
- What you've tried already
Feature Requests and Feedback
Suggesting Improvements:
- Email suggestions to development team
- Be specific about use case
- Explain problem being solved
- Suggest priority level
Reporting Bugs:
- Describe unexpected behavior
- Include steps to reproduce
- Note when it started happening
- Mention if it works for others
- Provide browser and system info
Next: Return to the Documentation Index for quick navigation to specific topics.
