MS Planner

Use case

• Plan an event.
• Project planning.
• Track issues.
• Create and follow a process, from scheduling to follow-up.

Not recommended for

• Writing personal identifiable information in specific tasks - keep it general.
• Use as a filing system and for document storage.

Naming conventions

Follow the University of Ottawa Naming Convention (see Best Practices tab).

Limitations

Plans per group: 1

FIPPA

The Freedom of Information and Protection of Privacy Act (FIPPA) applies to Planner and employees must search all information under their control, including all information created or stored in Planner. Contact [email protected] if you have any questions.

Retention period

Project management retention protocol currently under development.

WARNING: if you delete a plan in Planner, it will permanently delete the group. Deletion removes all group conversations, email messages, files calendars and any other related information.

Planner best practices

Tips

When creating a plan, be mindful of private vs public: public plans are visible by everyone in your organization. Private plans are only visible by people you've added to the plan. When people in your organization search for plans, only public plans come up in search results.

Information management best practices

• What to keep (PDF, 216 KB)
• Information disposal (PDF, 232 KB)
• Naming convention for documents (PDF, 150 KB)
• Personal information (PDF, 227 KB)
• Information Management Handbook (PDF, 370 KB)