First-Week Checklist
A practical rollout checklist for your first week on Holy Resource.
Use this page as a simple first-week rollout plan. The goal is not to master every feature in seven days. The goal is to get your church into a stable, confident working rhythm so real ministry work can begin quickly.
By the end of the first week, your team should be able to sign in, work in the right church workspace, manage core data, send a basic message, and run a simple volunteer scheduling test without confusion.
Day 1: Set Up The Church Workspace
Complete onboarding, sign in as the first admin, create the main working branch, confirm the church profile, and make sure a full backup works.
Day 2: Set Up The Right People
Add the key users who will help run the church, assign the right access, and test at least one non-admin sign-in.
Day 3: Load Core Ministry Data
Bring in members, ministries, and events so the app reflects real church activity.
Day 4: Prepare Volunteer Scheduling
Add initial volunteers, define a few real ministry roles, and run a simple test schedule so your team understands the flow before a live weekend.
Day 5 To Day 7: Test Reliability And Ownership
Check sync, run a recovery drill, confirm who owns backups and admin tasks, and make sure the team knows what to do if something goes wrong.
Day 1: Foundation
Complete onboarding and the first admin sign-in. Create the main working branch your team will use, confirm the church profile details, and verify that at least one full backup or export works before you move on.
Day 2: Access Setup
Add the people who will actually run operations inside the app. Give each user the branch access and level of responsibility they need, then test at least one non-admin sign-in so you know the setup works in real life and not just on paper.
Day 3: Core Data
Import or add the core records your church needs first, especially members, families, ministries, and upcoming events. Then confirm that two different users can see the right information in the right workspace.
Do this before scheduling volunteers
Do not rush into volunteer scheduling before ministries and events are in place. The schedule will make more sense once the church structure is already visible in Holy Resource.
Day 4: Volunteer Setup And Messaging
This is the best day to introduce your team to the volunteer flow. Add a few real volunteers, create the main ministry roles they will serve in, and run one small scheduling test using upcoming events. The purpose is not to perfect the rota. It is to make sure the team understands how volunteers, roles, assignments, reminders, and replacement offers fit together.
Also review your messaging setup during this stage. If your church plans to use reminders or replacement offers, send one real test message to a device or inbox your team controls.
Day 4: Sync & Reliability
Choose the sync approach your church will use and test it in a realistic way. If you use LAN sync, pair trusted devices and confirm data moves cleanly. If you use server sync, connect a second device and verify the connection. Then review sync status so your team knows where to look later.
Day 5: Recovery Drill
Run a fresh backup, open an import preview on that backup, and make sure at least one person besides the main admin knows where recovery steps live. A calm recovery plan is part of a good rollout.
Day 6–7: Governance
Use the final days of the first week to confirm ownership. Review permissions one more time, confirm invite continuity, and write down who owns daily admin work, backups, messaging setup, and incident response.
Success Criteria
By end of week one, you should have:
- at least one active branch with real data
- verified user access boundaries
- a working volunteer setup with real roles and at least one test schedule
- tested backup and recovery readiness
- a chosen sync model that fits your operations
Keep week one simple
Do not try to launch every feature at once. A successful first week is one where your team can complete the basics confidently and repeat them without confusion.
Last updated on