IT templates

Capture every field session with a GPS unit, noting the setup used, the weather and any obstructions that interfere with the signal. Technicians can add written observations and a photo of the measurement point. Built for surveyors, field technicians and engineering crews validating device accuracy.

A sign-up form for developers, designers and students who want a place at a hackathon. It collects contact details, the school or company someone belongs to, their technical strengths, team information and whether they have competed before. Organisers use the answers to balance teams, plan mentoring and size the venue.

Score a product against recognised usability principles in a single pass. Reviewers work through the analysis steps, rate learnability, effectiveness, efficiency, error tolerance and engagement, then leave written notes under each score. Handy for design teams running structured expert reviews.

Log each reported issue with a reference number, a priority and the systems it affects, then follow the actions taken until it is resolved. Support desks and operations leads gain a running register instead of scattered emails. Ideal for teams that must show how quickly problems were handled.

Ten questions that measure whether a team really understands the basics of cybersecurity: encryption, phishing, firewalls, multi-factor authentication, strong passwords, malware, network segmentation, VPNs, social engineering and backups. It mixes multiple choice with open answers so genuine knowledge gaps show up. Ideal for awareness programmes, technical onboarding and internal training audits.

Takes a few minutes to gauge how staff see the organisation's technology: overall satisfaction, the operating system they use, the services they requested in the last month and the quality of helpdesk support. It closes with an open field for improvement ideas. Useful for IT leads who want concrete data before planning investment.

Explores how people live with connected devices and how ready they are to adopt more of them. It mixes habit questions, knowledge scales and perceived privacy risk. Serves manufacturers, market researchers and product teams designing connected hardware.

Takes the details of anyone wanting a connection installed at home or at a business. It covers contact data, the installation address, the chosen plan and upload of whatever paperwork the provider requires. Built for local operators and installers handling sign-ups every day.

Logs real speed measurements alongside the provider, the connection type and the equipment in use. With enough responses you can compare performance by area and spot weak points in the network. Useful for user groups, IT offices and coverage studies.

Finds out how often people go online, from which devices and in which places. It cross-references that with age, gender and education level so results can be segmented. Practical for teachers, digital analysts and teams preparing an audience report.

Log each issue with a title, description, related files and links, category, priority and the person assigned to it. Built for support, development and project teams that need an organized record of problems and their follow-up.

Log each internal problem along with its description, priority, assignee and date. Built for IT teams that need to organize and resolve the problems staff report.

Gathers the new hire's details, role and location together with the hardware, access levels, phone service and building entry they will need. Made for supervisors and IT teams getting ready for someone's first day.

Lets businesses ask for a technology consultation by describing their needs, preferred format and a convenient date and time. Useful for consultants and IT providers booking meetings with prospects.

Managers list everything IT has to prepare for a new hire here: shared folders, ERP role, mailbox, distribution lists, VPN and equipment. That way the newcomer starts with accounts and tools ready from day one.

Funnel device breakdowns, access requests and technology purchase needs through a single intake. Every report arrives with location, urgency, attached evidence and the email of the manager who must approve it. Your service desk can prioritise without chasing details over chat.

Document a technology incident with its timing, severity, location, impact, witnesses and supporting files. Suited to companies and support teams that must investigate and fix outages or security breaches.

Department leads use it to ask IT for the computer, software, peripherals, mapped drives and printers a new colleague will need. It also records the start date and the deadline for having everything ready.

Support staff confirm on each round that servers, networks and systems are running as expected. The sheet records the date, time, room temperature and the officer's signature.

Technicians record every scheduled check on a device: tasks done, parts swapped, problems found and corrective steps. It keeps an asset history and helps spot failures before they happen.

Ask users what they think of the help desk and its staff, which technical problems they run into and how often. The answers show IT teams where their service needs work.

Records a laptop or desktop being handed in at the IT support counter. It captures the owner's details, device identifiers, accessories left with the machine, its physical condition, the reported fault and the collection appointment. Aimed at service desks and internal support teams.

Employees ask for technical help by giving their department, building and the category of the problem. The support team gets a clear description so it can prioritize and handle each case.

Covers a server request from end to end: who is asking, the environment and machine type, public exposure, SSL certificate, disaster recovery, handling of personal data, remote access, CPU, memory and storage sizing, business justification, budget and the date it is needed. It then routes through department and IT leadership signatures and leaves room for the administrator to record the final build. Built for IT departments with a formal provisioning process.

Open a ticket with the date, time, affected computer and a description of the fault. Technicians can log every request and follow it until it is solved.

A help-desk ticket with category, urgency, and a screenshot upload.

Users report a technical problem and include their computer ID plus a screenshot of the error. The help desk grasps the case faster and fixes it with less back-and-forth.

Gather personal details, education, skills and certifications from people applying for a Java development role. Candidates can attach a resume and tell you how they heard about the opening.

Let researchers and technical teams request materials datasets by entering keywords and the material family they need. A simple way to narrow down what information each user downloads.

Helps consultants and technology partners understand how a customer uses or is evaluating Office 365, OneDrive and SharePoint. It captures use cases, challenges, rollout timelines and how the tools are perceived today.

Collect an app's name, icon, splash screen and store descriptions before sending it for review on the App Store or Google Play. Handy for agencies and development teams.

Keeps ideas, enhancements and defects that nobody owns yet in one shared place. Every entry records the goal behind it, the stage it has reached, the expected impact on conversion and how urgent it is. Made for product squads that groom their backlog on a regular cadence.

A simple form for creating a user account with basic personal details, a national ID number and a signature. Useful for internal systems or portals that register new members before granting access.

Gather goals, scope, references, and budget before quoting a website.

Take a census of your technology estate by asking each user which device they were assigned, which operating system it runs and which peripherals they use. Answers grouped by branch reveal where machines or browsers need refreshing. It is the starting point for any upgrade plan.