First week operating checklist
Review daily Edmissa work during the first week and tune the initial setup.
Use this checklist during the first week after an Edmissa workspace starts live work. The goal is to confirm that Leads, student profiles, applications, documents, tasks, permissions, and reports support the way your team actually works.
Before you start
Complete the First day setup checklist and make sure at least a small group of daily users can work in Edmissa.
During the first week, keep notes on:
- Questions users ask more than once.
- Fields users skip or fill incorrectly.
- Application stages that do not match real work.
- Document types that are missing or unclear.
- Notifications that are too quiet or too noisy.
- Permission problems that stop users from doing assigned work.
First week checklist
- Review new Leads each day and confirm every useful Lead has an owner or next action.
- Check for duplicate student profiles before users convert Leads or create new student profiles.
- Confirm new student profiles have the right owner, location, contact details, and study context.
- Create test and live applications in the correct pipeline and starting stage.
- Watch how applications move through pipeline stages and note any stage names, rules, or forms that confuse users.
- Confirm users can complete stage checklists without skipping important work.
- Upload and review documents using the correct document types.
- Assign and complete tasks and follow-ups so ownership is visible.
- Review notifications with daily users and adjust events that create confusion.
- Check reports and oversight for Lead activity, application progress, task completion, and workload.
- Review permissions and scope after real users try their assigned work.
- Update training notes or team process notes with the decisions made during the first week.
Daily review questions
Use these questions in a short manager or admin review:
| Question | Why it matters |
|---|---|
| Are new Leads reviewed quickly? | Slow review can cause missed student follow-up. |
| Are useful Leads assigned to the right person? | Clear ownership keeps work from sitting unclaimed. |
| Are users creating duplicate student profiles? | Duplicate profiles split documents, applications, and activity history. |
| Do application stages match real progress? | Stages should reflect the actual state of student work. |
| Are required documents easy to classify? | Clear document types make review and reporting easier. |
| Are tasks being completed or overdue? | Tasks show whether follow-up work is happening on time. |
| Do users have the right access? | Permissions should support work without exposing too much. |
What to tune first
Tune the areas that block daily work before adding more complexity.
| If you notice | Start here |
|---|---|
| Leads arrive with missing or confusing data. | Review Lead sources, Integrations, and Lead capture troubleshooting. |
| Users create duplicate student profiles. | Reinforce the Student profiles search habit before creating new student profiles. |
| Applications move to the wrong stage. | Review Applications and Application stages troubleshooting. |
| Forms ask for too much information too early. | Review Form templates, Student fields, and Application fields. |
| Users cannot see or update assigned work. | Review Access and permissions troubleshooting. |
| Files are hard to classify or find. | Review Documents, Document types, and Document issues troubleshooting. |
End of week decisions
At the end of the first week, decide what should change before the next group of users relies on the workspace.
| Decision | Good next action |
|---|---|
| Which Lead sources are ready for wider use? | Keep reliable sources active and fix mapping problems before adding more channels. |
| Which pipeline stages need changes? | Rename unclear stages and adjust stage rules before the team builds habits around them. |
| Which fields are essential? | Keep required fields focused and move optional detail to later forms when possible. |
| Which checklists are trusted? | Shorten or clarify checklist items that users skip or misunderstand. |
| Which reports matter first? | Start with Lead review, application progress, task completion, and workload. |
| Which users need access changes? | Adjust roles, permissions, scope, and locations based on real assignments. |
Related guides
| Guide | Use it for |
|---|---|
| First day setup checklist | Confirm the initial setup was completed before first week review. |
| Daily work | Review the main work areas users touch each day. |
| Configure Edmissa | Tune the workspace settings that shape daily work. |
| Reports and oversight | Review progress, workload, and team activity. |
| Troubleshooting | Investigate issues that appear during the first week. |