Start with the approved-tools list
Use a listed tool when it fits the work; seek review before buying or installing software that is not listed.
Fictional example: At Northstar Services, an employee checks the approved-tools list before choosing software for a work task. Your organization's current list and request route determine what applies to you.
If a listed tool fits, use it within its stated purpose. If the tool is absent, the intended use differs, or an important need is not met, prepare the details below and use your organization's established IT request route. An absent listing is not approval.
This page helps you prepare for review; it does not submit a request or authorize purchase, installation, or use.
Choose the path that matches the need
Illustrative Northstar scenarios; these examples do not identify approved products.
| Details | Use a listed tool | Prepare a new request |
|---|---|---|
| Work need | Routine team file sharing | A partner workflow needs a capability not covered by the listed tool |
| First check | Confirm the listed tool covers the intended work | Check the list and describe the capability gap |
| Next action | Use it within its stated purpose | Seek review before purchase, installation, or use |
| Decision rationale | The use matches the tool's listed purpose | A new service may raise data, access, integration, or licensing questions |
When to use each path
Judge the intended work, not just the product name.
Use the listed option within its stated purpose and follow its applicable access and sharing conditions.
Describe the work the listed options cannot support and the capability needed.
Prepare details for review before starting a subscription, accepting vendor terms, or installing the software.
Ask for guidance when the new use involves different data, users, integrations, or access than the listed purpose.
Prepare for a useful review
These are preparation steps, not a submission or approval workflow.
Use your organization's established IT route for the handoff. The requester explains the need; IT coordinates the software review, while Security and other relevant specialists assess questions within their responsibilities.
-
1
Describe the work problem
Name the task, who needs to do it, and what outcome current tools cannot support.
-
2
Check listed tools
Note which listed options you checked and the specific gap that remains.
-
3
Identify the product and intended use
Provide the product name, work purpose, expected users, and whether this involves a new purchase, subscription, or installation.
-
4
Consider data, access, and connections
Describe the kinds of work information involved, who would access it, whether external parties are involved, and any connections to other systems or data sharing.
-
5
Follow the established review route
Send the prepared details through your organization's real IT request route and respond to follow-up questions from IT, Security, or other assigned reviewers.
Questions employees ask
If local guidance or the correct route is unclear, ask through your organization's established IT route before proceeding.
What if a listed tool almost meets the need?
Use the listed option for work it supports. Explain the specific unmet need and check with IT before adopting another product or changing the intended use.
What should I include about data and access?
Describe the kinds of work information involved, who needs access, whether external parties are involved, and any connections or transfers to other systems. If you do not know an answer, say so rather than guessing.
Who considers a request?
The requester explains the work need and provides available details. IT coordinates the software review; Security and other relevant specialists assess issues assigned to their roles. Your organization's established route identifies the actual handoff.
Can I purchase or install software while review is pending?
This page does not authorize purchase, installation, or use. Wait for guidance through your organization's established review route before proceeding.