You can use a QR code on equipment to identify the asset in an Airtable fault report, then collect symptoms and photos through a miniExtensions Form. Keep each report as a separate record linked to the asset. Scanning helps select the equipment; staff still assesses the fault, decides the next action and manages equipment availability.

Imagine fictional Cedar Workshop with three portable projectors. A staff member notices that Projector PJ-014 shuts down after several minutes. Selecting “projector” from a generic list would leave the repair coordinator guessing which unit is affected. A stable asset label and a linked report connect the observation to the particular device without overwriting earlier service history.

Keep assets and reported faults in separate tables

Prepare a connected Airtable base with this proposed schema:

  • Assets: Asset code as primary single-line text, Asset name as text, Code value as text, Location note as long text and Operational state as a single select.
  • Fault reports: Report reference as text, Asset as a linked record to Assets, Reported on as a date, Reporter name as text, Contact email as email, Observed symptoms as long text, Circumstances as long text and Photos as an attachment.
  • Fault reports, staff fields: Review state as a single select, Assigned owner as text, Staff assessment as long text, Next action as long text, Next review date as a date, Related report as a linked record to Fault reports and Closed on as a date.
  • Work records: Work reference as text, Fault report and Asset as linked records, Work notes as long text, Performed on as a date, Performed by as text and Review outcome as a single select.

Use distinct, stable Code value entries such as PJ-014 and PJ-015. The QR label should encode the exact text you intend the finder to search. Keep the printed code readable as text too, so staff can identify an asset when a label is damaged or camera use is unavailable.

This example scans an identifier inside the form’s record finder. It does not assume that pointing a phone at any QR code opens a prefilled fault form. A QR code that contains a website URL has a different payload from the asset code PJ-014; decide which workflow you are implementing and test the actual labels.

Configure scanning on the Asset linked field

Create a miniExtensions Form for Fault reports and add the reporting fields. Open the Asset linked-record field settings, then Record Finder Options. Set Record finder mode to List and enable Allow users to scan barcodes & QR codes in finder, following the scanning setup guide.

Choose Code value as the Barcode/QR code search field because this example stores the payload there. If you instead leave the search field blank, the documented behavior searches the record title. Make that choice intentionally; a well-printed code cannot match a field containing different text.

For a deliberate confirmation step, turn off Automatically link record after scan. Staff can inspect the matching asset label before selecting it. You may also turn off Automatically start camera so opening the finder does not immediately open the camera. Check the published experience on the device staff will use, including browser camera permission.

Disable creation and editing of Assets through the linked field. The creation and editing controls are separate from scanning. A reporter who cannot find an asset should contact the coordinator or use an agreed manual exception route, not create another asset record with an approximate name.

Collect observations that the next owner can use

Ask “What did you observe?” and “What was happening immediately before it occurred?” In the example, the reporter enters “Shut down after about five minutes while showing slides” and notes that the same presentation continued on another projector. Staff can review those observations without the form turning them into a diagnosis.

Photos can show the label, visible condition or a relevant error display. Ask reporters to exclude unrelated people, private documents and credentials. A modest Maximum allowed files setting can reduce clutter; the attachment limit documentation notes that existing files count toward the total.

Do not require someone to reproduce a dangerous behavior to complete a form. Keep the organization’s urgent-contact and equipment-isolation procedures separate and prominent where relevant. Submission does not guarantee that anyone has seen the report, and neither a scan nor a selected status establishes that equipment is safe to use.

Triage the report before changing the asset

The coordinator reviews new Fault reports in Airtable. Suggested Review state choices are New, Clarification needed, Assigned, Awaiting review and Closed. These are custom workflow fields maintained by staff, not built-in diagnoses or automatic dispatch rules.

For PJ-014, the coordinator checks the asset identity and asks a qualified owner to assess the shutdown. The owner and next action go on the report. Operational state on Assets is a separate staff-controlled decision; do not let the report form set it to Available, Repaired or Safe.

If another report describes the same unit on the same day, link it through Related report after comparing the evidence. Keep both original observations. One may add a useful timing detail even when the reports concern the same incident. A matching asset code alone is not enough to declare every report a duplicate.

Record work and review without erasing the observation

When work is performed, create a Work records entry linked to the report and asset. Preserve the original symptoms and photos. Record what was actually done and the review outcome, distinguishing a proposed action from completed work and an observed result from a hypothesis.

Only the responsible staff member closes the report and maintains the asset’s Operational state under the team’s procedure. A closed intake record is not a certificate of repair or safety. If the issue recurs later, create a new Fault report linked to the same asset and reference the earlier report where relevant.

Keep reporting inputs separate from staff fields, and do not expose reviewed records through an unrestricted edit link. If you later add a reporter portal, configure its user relationships and history-edit controls separately. This initial workflow is a staff-operated intake form with staff-managed review.

Test identification and exception handling

Try PJ-014 and PJ-015, an unknown code, duplicate Code value data and a damaged label. Confirm that the selected asset and new report are correct in Airtable, and that scanning alone creates no work record or availability change. These are acceptance checks to run, not runtime tests performed for this article.

The QR equipment checkout tutorial covers custody and returns. Fault reporting answers a different question: what was observed on a particular asset, who will review it and what happened next. Keep that evidence trail separate from both lending history and specialist maintenance decisions.