💾 Export Backups
Committee members should save backup files regularly so their work is not lost.
Dashboard purpose: This page explains how TrekHQ backup files should be saved, shared, uploaded, merged, reviewed, and archived so the Trek Director can maintain one accurate master plan.
Important: Do not assume every imported file should automatically overwrite the master plan. Committee uploads should fill missing fields, avoid duplicate records, and flag conflicts for director review before becoming part of the final trek record.
📤 Committee Sharing
Committee chairs may send updated backup files to the Director for review and merging.
🔀 Smart Merge
The goal is one complete master plan, not multiple competing versions.
⚠️ Conflict Review
Conflicts should be reviewed by the Trek Director or assigned committee owner.
🗂 Master Plan
The Director maintains the official current version of the trek plan.
📚 Post-Trek Archive
After trek, preserve the final plan and lessons learned for future committees.
Recommended Merge Workflow
Director Merge Process
This is the simple workflow TrekHQ should follow when committee members send updated backup files.
1. Receive
Committee sends backup file to Director.
2. Preserve
Save original uploaded file before making changes.
3. Compare
TrekHQ compares incoming file with master plan.
4. Review
Fill blanks, avoid duplicates, flag conflicts.
5. Save
Director approves and saves new master version.
Merge Rules
How TrekHQ Should Handle Incoming Data
Use these rules to explain the merge behavior to directors and committee members.
Blank Fields
If the master plan field is blank and the incoming file has data, TrekHQ may fill the blank field.
Exact Duplicates
If the incoming item is an exact duplicate, TrekHQ should avoid adding it twice.
Likely Duplicates
If names or records are similar, TrekHQ should mark them as possible duplicates for review.
Conflicts
If both files have different information in the same field, TrekHQ should flag the conflict.
Fuller Records
If one version clearly contains more complete information, TrekHQ may recommend keeping the fuller version.
Director Approval
Final merge decisions should be approved by the Trek Director before replacing the master plan.
Backup & Merge Workspace
Committee Backup Upload
This placeholder upload area can later connect to TrekHQ import/merge functionality. For now, it provides a clear workflow and visual home for the feature.
Committee Area
Backup File
Merge Status
Import Review Log
Track who submitted an update, what committee it affected, and whether the file was merged.
| Date Received | Committee | Submitted By | File Name | Duplicates Found? | Conflicts Found? | Director Decision |
|---|---|---|---|---|---|---|
Conflict Review Table
Use this table to document merge conflicts and final decisions.
| Record / Field | Master Plan Value | Incoming Value | Recommended Action | Final Decision | Approved By |
|---|---|---|---|---|---|
Post-Trek Archive
Final Archive Checklist
Use this section after trek to decide what should be preserved for future leaders.
Final Master Plan
Route / Map Packet
Permit Materials
After-Action Review
Photo / Media Archive
Sensitive Records Secured
Training & Resources
Backup, Merge & Archive Training
Add short videos here once the platform training is recorded.