Template
Internal IT request board template
An internal IT request board template: an employee-only Looph board for hardware, access and tooling requests, with tags and owners.
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet.
- Statuses
- 5
- Tags
- 4
- Things to ask for
- 4
- Setup steps
- 6
Use this template
Copy the setup, import the starter posts
Two ways to start from this template today: copy the checklist below into your setup notes, and import the starter CSV into a new board from the Posts page of your team area. The file holds this page's example posts, with each status mapped to Looph's built-in name so the importer accepts it; delete them before you share the board.
Columns: title, details, status. 3 example posts.
Setup checklist
Internal IT request board template (looph.ing/templates/internal-it-requests) Statuses (the Statuses page in the team area): - Rename "Open" to "Submitted" - Rename "Planned" to "Approved" - Keep "In progress" - Keep "Complete" - Rename "Rejected" to "Denied" Hide Under review and Closed if you do not use them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them. Tags: - Hardware - Software access - Account/Permissions - Internal tools Board description: What do you need, which team are you on, how soon do you need it, and what are you trying to do? Ask for in the details: - What is needed, as a title - Team - How urgent - What they are trying to do Setup steps: 1. Create the board, set it to Private and add your company's @domain to its access list, so every employee with a company email can sign in and see it. 2. Paste the prompt above into the board description, rename the statuses as listed, and create the four tags. 3. Connect Slack so requests can start there: /looph submit, or the Capture as Looph feedback shortcut on any message. Subscribe the IT channel to new posts on this board. 4. Invite the people who handle each tag as workspace members, and assign them posts from the inbox. 5. Approved and In progress requests appear in the roadmap's columns, so "did anyone see my request?" has a self-serve answer. 6. Announce completed changes that affect many people in the changelog.
Templates aren't applied automatically yet: you set the board up yourself by following the steps on this page. One-click templates are coming soon.
Fit
When to use this template
A good fit when
Employees ask IT and internal tools teams for the same things in Slack, by email and in the corridor, and nobody can see what has already been asked. An internal board lets them search first, vote on an existing request and follow it, while IT gets a ranked view of demand.
It fits requests where visible demand helps the decision: a new tool, an access policy, a change to an internal app, the standard hardware kit.
Pick something else when
It is not an incident or ticketing system. Outages, lost laptops and account lockouts need a response time, which is a service desk's job. Use the board for requests that benefit from votes and prioritisation.
Anything involving personal data, such as HR-related access or one named employee's device, should not go on a board the whole company can read.
What's inside
Statuses, tags and what to ask for, and why each one is there
Looph has a fixed set of statuses that you can rename, recolour, reorder and hide, but not add to; each status below says which built-in one to use. Posts are a title plus details, so the last list is what to ask for in the details.
Statuses
- SubmittedRename Open
- Where new requests start. Employees can search here before filing, which is where most duplicates stop.
- ApprovedRename Planned
- Signed off by whoever owns the budget or policy. Separating approval from work tells the requester the decision is made even if nobody has started yet.
- In progressBuilt-in status
- Being set up, ordered or built. Anyone who voted can see it moving without asking in Slack.
- CompleteBuilt-in status
- Done. Anything that affects more than one team is worth a changelog entry, so people learn the new tool or policy exists.
- DeniedRename Rejected
- Not happening, with the reason in a public comment, for example a security policy or an existing tool that already covers it. A written reason saves the same request from being filed again next quarter.
Hide Under review and Closed if you do not use them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them.
What to ask for in the details
- What is needed, as a title
- In plain terms, such as "Design tool licence for the marketing team", so the next person searching finds it.
- Team
- The post already shows who asked. Their team shows at a glance whether a request is one team's need or a company-wide one, which usually decides who approves it.
- How urgent
- The requester's view of how soon. IT still decides the order, but it flags anything blocking someone's work.
- What they are trying to do
- The right answer is often a tool the company already pays for.
Custom fields and file attachments are coming soon. Until then, a post is a title plus up to 5,000 characters of details.
Suggested board description
Put a line like this in the board description, so people know what to include: “What do you need, which team are you on, how soon do you need it, and what are you trying to do?”
Tags
- Hardware
- Software access
- Account/Permissions
- Internal tools
The four tags follow who usually handles each kind of request. Tags are workspace-wide; filter the inbox by one and assign those posts to its owner, who is notified.
Setup
Set it up in Looph
Each step in order, with the guide that covers it.
- 01
Create the board, set it to Private and add your company's @domain to its access list, so every employee with a company email can sign in and see it.
- 02
Paste the prompt above into the board description, rename the statuses as listed, and create the four tags.
- 03
Connect Slack so requests can start there: /looph submit, or the Capture as Looph feedback shortcut on any message. Subscribe the IT channel to new posts on this board.
Setup: Slack integration
- 04
Invite the people who handle each tag as workspace members, and assign them posts from the inbox.
- 05
Approved and In progress requests appear in the roadmap's columns, so "did anyone see my request?" has a self-serve answer.
- 06
Announce completed changes that affect many people in the changelog.
Illustrative examples
Example posts
Made-up posts that show what a useful entry on this board looks like. They are not from real customers.
Example · Hardware
USB-C dock in the standard laptop kit
Most desks have a single monitor cable that no longer fits the current laptops. Voted on by people in four departments.
Approved
Example · Software access
Read-only access to the analytics dashboard for support
Support agents want to check a customer's usage before replying. Read-only is enough; nobody on the team needs to edit reports.
Submitted
Example · Internal tools
Staff directory search ignores nicknames
Searching for a colleague by the name everyone uses returned nothing. Fixed and announced in the internal changelog.
Complete
Plan
Which plan it needs
Needs Starter. An employee-only board is a private board, and private boards start on Starter. Employees who vote count as tracked voters, 1,000 on Starter and 10,000 on Growth, so a larger company needs a higher plan. Employees sign in with email or Google; single sign-on is not on any plan yet. Compare plans.
How the pieces work: Feedback boards. Teams running this workflow: Internal IT and tooling request boards for employees.
More templates
Other starting points
Beta feedback board template
Teams running a private or invite-only beta that need structured, votable feedback before a general release.Design feedback board template
Design and product teams collecting structured critique on in-progress work from stakeholders or users.Feature request board template
Product teams that need a single public place to collect and prioritize customer-driven feature ideas.Public bug tracker board template
Teams that want bug reports separated from feature requests, with triage by impact that reporters can follow.
Related
The features and reading behind this template
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime