You can use Airtable and miniExtensions to collect everyday IT service requests, organize a triage queue, and give each requester a place to check the latest update. Keep the requester-facing explanation separate from internal diagnostics so the IT team can communicate clearly without exposing its working notes.

This example is for a small internal IT team handling matters such as a monitor that will not connect or a shared printer that needs attention. It is not a security-incident intake system, an asset-management platform, or a promise of a particular response time. Use your established urgent support channel for incidents that cannot wait for routine triage.

Define the handoff, not just the intake form

At the fictional Cedar Studio, Morgan reports a display connection problem. The IT coordinator reviews the report, assigns a technician, and asks Morgan which adapter was in use. Morgan returns to the same request to add that detail. Later, the technician writes a short public update and separately records technical findings in Airtable.

The useful outcome is a shared answer to three questions: what was requested, who needs to act next, and what can the requester expect to do? A status of In progress alone is not enough. Pair it with an actionable public update such as “Please bring the adapter to the service desk so we can check it.”

Build a small, explicit record structure

  • People: Name as primary single line text; Email as email; Department as single line text. Use a separate record for each person.
  • Service Requests: Request title as primary single line text; Requester as a linked record to People; Reported problem as long text; Service category as single select; Device reference as single line text; Supporting image as attachment; Requester follow-up as long text.
  • Staff-managed fields on Service Requests: Triage status as single select with New, In progress, Waiting on requester, and Completed; Assigned technician as collaborator; Public update as long text; Internal diagnostics as long text; Next review date as date.

Use a fictional device reference such as DESK-14 rather than passwords, recovery keys, or access codes. Describe the symptoms and relevant context without collecting credentials. For the example, one request says “External display remains blank with adapter attached,” while another says “Printer queue shows a paper warning.” Keep them linked to different test people.

Give each person their own requests

Create a miniExtensions Portal using Service Requests as the Data Table and Requester as its linked User Field. Prepare the People records and links first; the users-table guide explains the required relationship. A text email field on a request is not a substitute for the linked person record.

For each request view, choose Personal records only under Choose Records to Display in Filter and Sort. Follow the personal-record filtering instructions rather than assuming a view named “My requests” provides the restriction. Configure email verification for the People Email login field; use addresses you control for test accounts.

Allow request creation through the portal’s form, and review the resulting Requester link in a test record. Expose the problem, category, device reference, image, and follow-up fields. Make the staff-managed public fields read-only in the requester form, and leave Internal diagnostics out of the requester-facing fields entirely. Also inspect expanded records and any other views, rather than checking only the initial list.

Separate the triage queue from the public status

In Airtable, give the team a New requests view and a Waiting on requester view. An IT coordinator sets the triage status and technician manually in this design. Nothing in the proposed schema automatically assigns urgency, starts an SLA clock, or routes a security incident.

Use Public update to communicate a concise next action. Use Internal diagnostics for working theories or details that do not belong in the employee view. When the requester responds, the coordinator reads the follow-up and returns the item to In progress. If you later automate reminders or routing, design and validate those separately; the baseline workflow does not depend on them.

Check the experience before sharing it

  • Sign in as two fictional requesters. Each should see their own request set, not the other person’s.
  • Create a request, refresh, and verify its saved title, requester relationship, and initial staff handling state in Airtable.
  • Change Public update as staff, then reload the requester view. Check that the message is visible but not editable.
  • Try every requester-facing expansion and view. Confirm that diagnostics, technician assignment, and triage controls are not exposed for editing.
  • Move an item to Waiting on requester, add a reply from its test requester, and verify the coordinator can identify the next action without relying on a new record.

Know when a lightweight request tracker is enough

This works best when the team can review a modest queue and maintain concise updates. It does not replace emergency escalation, device monitoring, incident response, or a purpose-built service desk when those are operational requirements. Agree on where urgent issues go and who reviews ordinary requests before inviting employees.

For purchase or access approval before software is adopted, use the separate internal software request review workflow. This service-request design instead follows an existing problem through triage, clarification, and completion. The distinction keeps an approval queue from becoming a catch-all for every support issue.