Find unfinished work in Airtable views: filters, sorting and sharing checks

Treat a view as a perspective on the same records

A view changes presentation, filtering and sorting; it is not another storage destination. Editing a state in one view changes the underlying record and may affect other views. Keep one request ID instead of duplicating enquiries into separate owner tables. Begin with a single intake table and make each view answer one operational question.

State the unfinished-work condition explicitly

Decide whether unfinished means everything except Complete or only an explicit list of active states. Blank values and newly introduced states can change the result. Distinguish AND from OR when combining filters: owned by me AND unfinished is very different from owned by me OR unfinished. Write the intended population in plain language before configuring its conditions.

Separate overdue work from missing deadlines

Filter unfinished records whose due date has passed. A missing deadline may not satisfy that test, so retain a separate deadline-missing queue. The overdue view alone does not account for all unresolved work. Agree whether dates are compared by day or by exact time, and define how work due today should appear in daily checks.

Organize owners and the next action

Group by owner and sort each group by deadline and received time. Keep the unassigned group visible. Show an identifier, subject, deadline and state so the operator can choose the next record without opening every long message. Sorting changes row positions, so use record identifiers rather than visual row numbers when referring to a request elsewhere.

Reconcile five representative records

Prepare your unfinished request, your completed request, another owner's unfinished request, an unassigned request and a request with no deadline. Write down their expected views before checking actual results. Closing a request should remove it from an unfinished view while retaining it in the table. If a record disappears unexpectedly, inspect it by ID instead of assuming deletion.

Review access independently of filtering

A view filtered to one owner is not inherently strict authorization preventing access to another owner's records. Base collaborators and recipients of external share links have different capabilities. Review the selected sharing method, hidden columns and record-detail visibility with a controlled viewer. Do not place sensitive notes in a supposedly private column merely because it is hidden in one presentation.

Assign responsibility for daily checks and filter changes

Review unfinished, overdue, unassigned and deadline-missing counts together. Decide who may change shared filters and how the team learns about a change. A personal adjustment should not silently remove the group's work from its operational queue. When a view becomes cumbersome, reassess columns and scope before adding more notifications. The checks described here are a proposed operating method, not a tested access-control certification.

• Build an Airtable enquiry tracker: intake, owners and follow-up states
• Assign Airtable form responses: category rules and an unassigned queue
• Airtable pricing: billable roles and workspace scope