An Airtable construction punch list can connect each outstanding item to a specific area, responsible trade and closeout review. Use miniExtensions to collect observations and completion evidence, while the project team keeps the decision to accept work separate from a contractor’s report that the work is finished.

Consider fictional Alder Projects preparing a small office fit-out for handover. A walkthrough finds chipped paint beside one doorway, an unfinished trim section and a cabinet door that does not align. Each needs a different action and possibly a different trade. Keeping them as separate records makes it easier to explain what remains before handover than placing every issue in one visit note.

Define an item that someone can act on

Use one Punch items record for one identifiable piece of follow-up work. “Finish meeting room” is too broad; “Touch up paint on the corridor side of meeting-room doorway” gives the assigned person a location and a visible outcome. Add a location code and a photo so the description remains useful after the walkthrough.

This example covers ordinary finish-work coordination. It does not establish compliance, structural adequacy or safety certification. Keep urgent hazards and specialist inspections in the project’s established procedures; submitting a punch item is not proof that the appropriate person has received or assessed it.

Connect locations, assignments and review visits

Prepare a connected Airtable base with these suggested tables and field types:

  • Projects: Project name as single-line text and Site reference as text.
  • Areas: Area name as text, Project as a linked record and Location instructions as long text.
  • Trade contacts: Name as text, Work email as an email field and Trade as a single select.
  • Punch items: Item reference as text, Area and Assigned contact as linked records, Original observation as long text, First observed as a date, Original photos as an attachment, Target date as a date and Work state as a single select.
  • Work updates: Update reference as text, Punch item and Assigned contact as linked records, Update date as a date, Work performed as long text, Completion photos as an attachment and Reported outcome as a single select.
  • Closeout reviews: Review reference as text, Punch item as a linked record, Reviewed on as a date, Reviewer as text, Review finding as long text and Review decision as a single select.

Create item PI-026 for the chipped paint and PI-027 for the trim. Link both to the same corridor Area but give each its own assignment and evidence. A single trade may handle both, yet one can be accepted while the other still needs work. Keep the original photos on Punch items and later photos on Work updates so the reported repair does not replace the initial observation.

Give trades a focused update portal

Create a miniExtensions Portal using Punch items as the Data Table and Assigned contact as the User Field. If Work updates is also displayed, retain its direct link to Trade contacts. The Users table guide explains this requirement; an indirect path through the Punch item alone is not sufficient for a portal data table.

Configure a suitable verified login method from the login guide. For every private view, open Portal Tables, select the table, choose Views and its view, then use Filter and Sort to set Choose Records to Display to Personal records only (linked to the logged in user). The record visibility documentation covers the setting. Check with two fictional trade contacts before sharing actual project details.

Show the area, original observation and target date as read-only context. Let the assigned person add work notes and completion evidence, without editing the original finding or the review decision. Keep closeout reviews staff-operated in this first version rather than exposing a table of all inspection decisions to every trade.

When using a linked-record form to add Work updates, review the linked-record creation guide. Child-form saves can reach Airtable before a parent submission. Treat an update as a recorded report, not an automatic transition of the entire punch item to accepted.

Use annotation to clarify the location, not certify the work

A photo of an entire corridor may leave the trade guessing which mark needs attention. The documented form setting for image markup is attachment field, Upload Settings, then Field Mode set to Image Annotation. See the image annotation guide for the interaction.

Provide a working copy when you need to preserve an unmarked original; decide and verify that retention process before inviting annotations. Do not assume that drawing a circle creates an independent archival copy. Keep a plain-language observation too, so the record remains understandable without relying on color or markup alone.

For PI-026, the update says “Sanded and repainted the marked patch” with a close photo and a wider location photo. The coordinator can identify the work claimed and decide whether an on-site review is needed. Image evidence alone should not silently substitute for whatever inspection the project requires.

Keep reported completion and accepted closeout distinct

Use custom Work state choices such as Open, Assigned, Reported complete, Review required and Accepted. The trade supplies a Reported outcome on a Work update; the coordinator checks the update and maintains Work state. A separate reviewer adds the Closeout reviews decision after the actual review.

If the paint patch is acceptable but the trim remains unfinished, accept PI-026 and leave PI-027 open with its next action. If the paint issue needs another pass, add a review describing the remaining mismatch and a new work update when the trade returns. Preserve the earlier report and review rather than making the record appear to have passed the first time.

A newly discovered scratch nearby should normally be a new Punch item, optionally linked through a Related item field of linked-record type. Record why the items are related without assuming they have the same cause. This keeps new scope visible and avoids attaching every future issue in an area to one old record.

Review the closeout queue before expanding

Use Airtable views for unassigned items, reported completion awaiting review and items still open near a target date. A coordinator reviews those queues and confirms the next owner. Notifications, reminders and project schedules are separate configuration work; the fields described here do not automatically dispatch trades or notify the client.

Test two items in one area, two assigned contacts, a rejected closeout and a newly discovered defect. Confirm that each photo and review stays attached to the intended item, private views remain scoped and accepting one item does not complete the project. These are proposed acceptance tests, not observed runtime results.

The field inspection guide explains broader visit-and-finding collection. This punch-list design adds trade assignment and repeated closeout review around specific remaining work. The useful outcome is an explainable handover queue, with acceptance supported by an actual review rather than a single completion checkbox.