Internal team tools: when spreadsheets and email are no longer enough

Internal tools support concrete work such as request approvals, asset tracking or combining system data. Build one around a defined process problem and outcome owner. Moving a chaotic spreadsheet into an attractive portal does not automatically remove the chaos.

Understand current work before designing screens

Consider purchases approved by email. Identify request creators, required data, decision makers and where results appear. Include exceptions: clarification, reassignment and absent staff.

Observe actual work and speak with participants as well as the automation sponsor. Check whether existing systems and configuration can solve the need. Custom development carries maintenance obligations and needs a justified benefit.

Agree states, roles and data ownership

Requests need meaningful states and permitted transitions. Servers enforce approval, amount-editing and attachment-viewing rights. An interface job title should not automatically grant access across departments.

For imported staff directories or inventory, define ownership and update frequency. Manual corrections need rules or subsequent imports may overwrite them. Users should understand data freshness.

Make exceptions visible

Change history records who performed important actions and when, with appropriate detail and retention. Agree notifications, overdue-task discovery and correction of mistaken steps. Every change need not notify the entire team.

Forms need clear labels and errors near relevant fields. The ALL IT Agency site uses shared forms and buttons to avoid duplicated behaviour. The same principle supports consistency and maintenance in internal tools.

Introduce it with a controlled handover

The first version should complete the agreed process, including rejection and correction. Test roles, required-record migration and rollback with test data. Tell the team when the system becomes authoritative to avoid conflicting copies.

Hand over concise instructions, access ownership and issue-reporting procedures. Assess agreed process outcomes such as visible status and manual transfers. Measure actual savings after introduction rather than promise them in a presentation.

Sources and further reading

• GOV.UK: process participants’ needs
• OWASP: server-side authorisation

• Related subservice: Internal tools
• Explore this service area